Database Develop

Imate Rom BT Stack version

I am struggling to use my SonyEricsson HBH 35 Headset with my Tmobile MDAIII. But after a while the BT Stack stops working and I have to turn BT on and off to be able to use the headset again. Tmobile Service Line told me that they are aware of the problem and they will post a fix for that but no time frame was giving. Therefore I was wondering whether the latest Imate PDA2k Rom was having the same BT problems. Which version of BT stack is on this rom? Is it possible to copy the necessary files onto the MDA III and make it work with the never version?

PDA2K has the same issues with the BT Stack. In fcat it is just awful.

Anonymous said:
PDA2K has the same issues with the BT Stack. In fcat it is just awful.
Click to expand...
Click to collapse
Hell, its worse than 'just awful'....
...The Bluetooth on the PDA2K is just downright unusable.....
...I am still holding my breath, praying to GOD they get a real fix out and not just a 'here ya go' patch with more problems in it......

BT version... MDA III new ROM
I would like to know which version of the BT you guys have = which is most current for MDA III. To verify this go to settings/connection/bluetooth an check in About .
I have heard some news that ROM 1.20 is being tested internally, and somebody promised me to provide it to me. I am really waiting.. as current one keeps turning on device every minute...

have a hcb-30 bluetooth carkit that worked great with my Qtek 2020, but i cannot seem to get it to work with my qtek 9090....it finds the qtek allright and pairs with it, but cannot connect....my bluetooth version is 1.0.0 build 2200...
hope they get a fix out soon...

Re: BT version... MDA III new ROM
lukasz said:
I would like to know which version of the BT you guys have = which is most current for MDA III. To verify this go to settings/connection/bluetooth an check in About .
I have heard some news that ROM 1.20 is being tested internally, and somebody promised me to provide it to me. I am really waiting.. as current one keeps turning on device every minute...
Click to expand...
Click to collapse
I'm running v1.0.0 Biuld 2200
Mine also likes to turn the unit on every minute or two and run the battery down VERY fast...........

onurd said:
I am struggling to use my SonyEricsson HBH 35 Headset with my Tmobile MDAIII. But after a while the BT Stack stops working and I have to turn BT on and off to be able to use the headset again. Tmobile Service Line told me that they are aware of the problem and they will post a fix for that but no time frame was giving. Therefore I was wondering whether the latest Imate PDA2k Rom was having the same BT problems. Which version of BT stack is on this rom? Is it possible to copy the necessary files onto the MDA III and make it work with the never version?
Click to expand...
Click to collapse
You may tried that DON'T PAIR the HBH35, Afterwards, use a Bluetooth connection wizard to add it. This may be OK to add HBH35.

I don't know how those incompetent idiots could release the blueangel with such a obvious bluetooth problem, HOW CAN THEY NOT see it! the error messeges pops up so frequently.

Go for it, version 1.5
http://forum.xda-developers.com/viewtopic.php?p=65548#65548

I couldnt get 1.5 to work on my pda2k, cant overwrite certain files... how did you do it?

I didn't do it as i don't have a BT headset yet. because of these treads I'm waiting before i get the headset, gps, and keyboard for bluetooth

I didn't do it as i don't have a BT headset yet. because of these treads I'm waiting before i get the headset, gps, and keyboard for bluetooth

you don't have it yet and you are telling other people to go for it! i dont think it works for the pda2k

Did you read or post first?????????????????
As you can see Guest and firebird say it worked to some degree for them on the PDA2K (MDAIII). Since I didn't have a BT headset to try myself I thought I would help you by pointing you to someone who had.
Read posts before blasting back.
*********************
Guest
Posted: Mon Nov 08, 2004 06:20
Subject: BlueTooth manually updated on PDA2k to 1.5.081
--------------------------------------------------------------------------------
http://forum.xda-developers.com/viewtopic.php?t=11729&highlight=widcomm
Since I didn't see in any thread about someone updating their PDA2k to the latest widcomm drivers... Just an FYI, I copied the files from the other thread onto my PDA2k. Seems to be working. Will test further to see if I'm still getting memory issues like before.
NOTE - I used Resco to copy the files over. There were several warnings that I was updating a file in ROM.. but I went ahead and did that anyway...figured I could hard reset the device if need be.

just a warning, the ROM files he was talking about overwriting, cannot be restored by doing a hard reset, it is permanent. if it messes up you will have to re-flash your pda with a new copy of the OS. that's what i had to do since i couldnt get it to work

Connecting an O2 XDA IIs with a SE HCB-300 handsfree car kit

This is driving me nuts...
I have bought an XDA IIs (and love it) and needed a car kit, so bought the one recommended on the O2 website - the Sony Ericsson HCB-300.
I had the kit professionally fitted, and sat in my car at lunch time eager to get it to work.
It goes through the motions - it pairs up no problem, and I enter the 0000 code. However, when it goes to connect it just sits there for about 15 seconds, then announces "Connection unsuccessfull".
I have read a load of posts about patches for this device, is this what I need or do I need to change any settings on the devices????
Thanks in advance!
Steve

Steve,
I have the HCB-30 not the 300. However, once in a while I have the same problem as you. I get around it by deleting the BT pairing that exists, then hard rebooting the O2 unit, then pair it up again.
I think the BT software in the O2 XDA IIs is stuffed up. I have to hard reset my O2 unit regularly as it doesn't automatically link up to the HCB-30. I had no problems with my XDA II
I hope my suggestion helps you out.

I got a new car last week with the HCB-300 pre-installed and I have exactly the same problem - pairing no problem but no connection. I tried upgrading to the latest 1.40 ROM and then it worked just fine.
However, after reinaastalling TomTom Nav 3 it doesn't work again so I have come to the conclusion that TT3 and HCB-300 are incompatible. I'm looking for a solution still and if I cure it I'll post ot here.
Very annoying indeed.

WM6, bluetooth car kit and incoming port problem

Hi guys,
I am at the end of my tether... I just bought a JVC head unit with on board bluetooth, so I can use it as a car kit. But I can't get my Treo 750 to pair with it! It just locks up after I enter the passkey... and the car kit just says "error" after a certain amount of time. I'm running a vanilla (extended ROM removed) version of the 3 Australia ROM.
So, I rolled back to Windows Mobile 5... same problem... UNTIL I went into the Bluetooth settings and setup an incoming COM port. Then it paired up perfectly and all was well.
So I've reinstalled WM6, but it doesn't have the option to create an incoming COM port. That's really annoying. I've googled a heap, and searched these forums a fair bit too, but haven't been able to find any sort of workaround. Is there a registry hack, third party program, or some other way I can tell it to allow an incoming connection from the car kit?
Thanks in advance!

Has anyone had any ideas on this? I have a real issue now, as I rolled back to a WM5 ROM which I found on these forums but I'm having awful problems with it - it drops calls all the time and sometimes they just go silent..... the call stays connected but I can't hear the person on the other end.
I really need to get either the original Telstra WM5 ROM, or a way of getting WM6 to work with my car kit! Any ideas... anyone??

Okay... now I really feel like I'm talking to myself but anyway.... thought I'd give an update.
After heaps of trial and error, I managed to install the Universal version of the Broadcomm bluetooth stack onto my device. And it pairs - hooray!
However... when I make a call, no sound comes through the speakers
No other version of the Broadcomm stack will run on my Treo, I just get the memory error that lots of other people have mentioned.
Chalk another person down who's royally annoyed with Palm for putting such a dodgy implementation of Bluetooth into these devices. It's my one and only bugbear to date.

I have exactly the same problem when pairing my WM6 Treo 750 to a Parrot MK6100 carkit. After entering the passcode on the Treo, the device just hangs. The carkit says it has connected succesfully, but nothing happens. After restarting it does not recognize the carkit at all.
Did you find a solution yet? I am also looking for a different Bluetooth stack that is guaranteed to work with the Treo.

Good to see I'm not the only one. No, I haven't found a solution yet unfortunately
The closest I've come is that hacked Broadcomm Bluetooth stack. My only hope is that some nice developer will help us develop something that works!

Hi Ben,
I solved my problem yesterday. I tried two suggestions.
1) Leave the passcode field blank (do not enter '0000') and press next
2) Install http://www.jetwaremobile.nl (fully functional 30-day trial)
After that pairing succeeded in a couple of seconds and all is working well. Let me know how it works out.

Thanks very much MattMax!
I had tried the Jetware software previously, and it didn't help. But I hadn't tried leaving the passkey field blank. Did that this morning... it popped up with a connection dialog asking if I wanted to allow the connection... went back to the passkey screen, I entered 0000 and away the sucker went. How simple was that!!
I just upgraded to the latest ROW2.23 WM6 ROM the other day, so I'm not sure if that made any difference either. But it's now paired and (seems to be) working well, just need to make and receive a few calls to make sure.
Thanks very much for your suggestion!

Good to hear that it worked out!
I had exactly the same experience, leaving the field blank, after that entering '0000' and it worked. I had just installed Jetware Mobile, but apparently that is not necessary for the solution.

Widcomm on Kaiser (searched and found, just a few q's)

So I have a shiny new Kenwood KDC-BT838U and for a $220 dollar toy it is pissing me off very much. It does not automatically connect or disconnect from my phone when powering on or off. Simple fix for that is an app to manually establish connection. a2dp will be running fine, then a call comes in. After the call sound will not work and I get all kinds of connection issues until I just power down the head unit then turn it back on (sometimes a few times).
I tested my kaiser with other bluetooth HU's and it worked fine. Then kenwood was not in the store but I love all its other features and it looks great. I contacted Kenwood support and they said that it is a problem with my phone's bluetooth protocol. I decided to give Kenwood the benefit of the doubt. I want to try the widcomm stack.
Found it here.
http://forum.xda-developers.com/showpost.php?p=1072773&postcount=72
I have read that it works with the kaiser. True? After installing the cab, do I need to delete the MS bluetooth reg key or do anything special?
Any Kaiser widcomm users out there? Can you comment on any issues you have? Thanks!

I went ahead and installed the cab linked above. At first I was getting the out of memory error on boot. I changed the baud rate ([HKLM\Software\Widcomm\BTConfig\SerialTransport]) to 115200 and it appears to be working now. Will report more findings later. If anyone else is using it please share your experiences here. Pretty much all the threads I found by searching were people with the same question and they pretty much all went unanswered.

Wellit only thinks it is working. Kasier would not find any bluetooth devices near by and my computer cannot find my kaiser. I guess I will give up now but if anyone else got it working please let me know.
Oh BTW, don't install the CAB unless you don't mind a hard reset. I was prepared for that of course, but just a heads up.

Can we put the 1.5 bluetooth stack into 2.1?

It's like the elephant in the room around here. The bluetooth service on 2.1 is some crazy, broken crap. No matter how many times and how many ways I try to get it to pair to my brand new Kenwood x994 it refuses to save. It will eventually link up BT audio if I search for devices and let the pairing fail, but what a PIA to mess with every time I get in the car. I rolled back to Fresh 1.1 today and I had it paired and working perfectly in 10 seconds.
So here is the question, can we put the 1.5 BT stack into the 2.1 ROM? I already tried the 1.5 libbluetooth.so in the /system/lib filesystem, but it didn't change anything about the pairing problem (obviously I have no idea what I am doing and stabbing blindly at anything bluetooth related).
Anybody have any ideas? Is the BT compiled into the kernel? Can we recompile it with the 1.5 version?

I've asked this question a few times already and the answers are usually 'no'. Gawd I wish we could as no 2.1 roms (I've tried almost all of them) will pair voice (audio is OK) with my Pioneer Avic D3 car radio. 1.5 works perfect

Mine works exactly the opposite. The hands free phone works perfectly, but the phonebook doesn't download and BT audio fails to connect.

It sounds like it may be your phone, your should update with the official 2.1, then take it to a sprint store and have them replace it.
My phone has worked flawlessly to my jeep stereo with any 2.1 rom I have used in the last several months.

So this whole time I thought it was because we had a leaked version, but is this the official ROM that still has this problem. It's not the device cause I've had it replaced twice and my wifes doesn't work either.
I am not able to connect to my Pioneer AVH btw.

djorijun said:
So this whole time I thought it was because we had a leaked version, but is this the official ROM that still has this problem. It's not the device cause I've had it replaced twice and my wifes doesn't work either.
I am not able to connect to my Pioneer AVH btw.
Click to expand...
Click to collapse
I agree, if it was the hardware it wouldnt work with 1.5 either. Besides, Dan Hesse is my boss. He'd get hacked if I took back my phone

Thread moved.