Database Develop

Hands-free set: pairs, but does not connect

I've posted this in [this thread] too, so my apologies for the double post. However, since many people seem to have the exact same problem I thought it deserves a thread of its own.
I have an MDA III (T-Mobile) and with the original ROM I was never able to use a BT hands-free set. The MDA III would pair with it but it was never able to connect (I would get a "Connection Failed" error). I've tried several hands-free sets all with the same result.
One day I tried the [BT Stack 1.0.0 build 3900] upgrade and that actually solved the problem. But, it caused my MDA III to switch on by itself occasionally and that was pretty annoying so I reverted back to the original stack. I actually tried build 3900 a few times to make absolutely sure it was this new BT stack that solved the problem. And it indeed was.
So I was pretty excited to find out T-Mobile had an [official upgrade] that included the 1.0.0.3900 BT stack. I have flashed my MDA III a few days ago and all went well. BT Manager displays it's build 3900, and my MDA III reports it's using the new ROM and radio.
But...
I still can't connect a hands-free set! I get the exact same error as before! I'm able to pair, but not to connect - which is weird because the "previous" build 3900 solved that problem for me while now it doesn't.
Does anyone know if there's a difference between the one I downloaded from here and the one supplied with the upgrade?

Nobody?

O2 XDA IIi Bluetooth with Bluetooth Car Kit Issues.

Hi Guys,
Recent got an XDA IIi after being with the older XDA II for over 16 Months.
But I have recently run into problems with my BT Car kit :
Motorola Bluetooth Car Kit HFW-8000.
Basically the problem is that it does not always connect to the Car Kit and when it does it will only from time to time connect and let me have a handfree conversation.
I have also used the Broadcom Bluetooth Cab file here in order to extend what Bluetooth Profiles that can be used but seems not to have any great bearing to stablize the issue.
So I went down the Hard Reset Road but again still intermittent issues, I then upgraded the ROM to the New one on the O2 Website the v 1.11.169 ROM.
I also had similar issues with the XDA II but it was resolved by using the Pocket Bluetooth tools, which was great and never once after installing it did I have any issues with the Car Kit.
http://www.bluetooth.jazztel.es/
One of my questions is, is there a similar programme to to above Pocket Bluetooth tools for the XDA IIi as I have tried it with the XDA IIi but does not work.
Or does anyone know how you would revert to have the XDA II radio or is there a work around for it.
Thanks Guys
Woody

Hi Woody_XDA,
I have had my XDA2i for a couple of months now and recently got a O2 blue headset for it, I had simular problems with the headset disconnecting and having to manually connect every time I switched it on. After browsing this wonderfull forum I decided to do a corperate install and get rid of the O2 active interface, since then no problems at all. I now use Pugs modified ROM version 162 with radio 1.04 and have no stability problems at all with no twice weekly reset. Hope this helps you and many thanks to Pug for his ROM.
Mace

Ditto, I also use the custom firmware with 1.04 radio and bluetooth works a charm. It still eats battery like nothing else, but it works with no problems. Also like the fact that the XDA can cope with my GPS receiver and my handsfree kit simultaneously, that's handy for in the car.

Cheers Guys for the information, took it on board and works great, did a great deal of stress testing in order to confirm it and works excellent..Thanks to PUG again and guys thanks for the info much appreciated and this is by far a great forum

Mace - you mention some bluetooth issues being resolved since you applied the custom ROM... I posted in the Alpine Applications forum here the other day a list of issues with bluetooth that I was wondering had been addressed - so far no reply - are these the symptoms that were cured for you??

Hi Bewlay Brother sorry, I missed your other post on Bluetooth issues, my original problem was that every time I switched on my BT headset , which is a O2 Blue, I had to open the BT manager and make the connection, the phone would then occasionally lose the connection and sometimes whilst still showing a connection refuse to transfer the call. This was using the official 162 ROM with the O2 active UI. I have since installed Pugs 162 ROM with radio1.04 and done a corporate install and BT seems to work perfectly, switch on the headset, it connects, never loses pairing and transfers calls.
Hope this helps you, and thanks again to Pug,
Mace.

Mace - what you describe sounds similar - my problems were essentially the loss of pairing with my Motorola headset a lot of the times when the XDAIIi switched off its display and went into stand-by mode, also if I closed the boom bike on the headset (to temporarily turn off the headset) it would fail to re-pair when I next opened the boom mike... the other issue was that I had to make sure the phone keyboard was displayed on the XDA once I had paired up otherwise the last number redial function on the headset would not work - if I pressed the dial button on headset and the phone display was not on the screen it would simply open the phone display function but fail to then dial the number - really crap. Also reception was poor to headset even over relatively short distances from the XDA. IF these areas in particular could be cured by the upgrade then I am eager to do it - I must admit I have read that this upgrade has not been without problems for some people here so it is going to be a tough call.

Just a thought, but have you done a personal or corporate install as I think the main fix with Pugs ROM was the upgrade to radio 1.04, which I don’t think affects the BT, so a corporate install with your existing ROM may make a difference.

Did a corporate install when it was new out of the box...

whats the difference between the corporate and personal install?

Corporate doesn't install ANY of the branded O2 interface - so no gubbins, nothing to slow down the phone, you just get a bog standard Windows Mobile 2003 SE installation, aside from the O2 GPRS and SMS settings. Bosh.

hi
i've been reading the posts and i have the same problem where can i get hold of pug's ROM if it's possible cos this seems to get rid of the problem

And then today, headset will not automatically connect, needing Bluetooth manager to be opened to make the connection. AARRRGH!

BT car kit problems
I have the 1.04 Radio, but it still won't sync with my 2003 BMW 325xi bluetooh or with my 2005 Acura MDX bluetooth.
Help!

Unstable Bluetooth Signal Strength - Samsung WEP200 Bluetooth Headset
Hi, I just got a Samsung WEP200 Bluetooth Headset. It would pair with my O2 XDAIIi but I cannot hear any voice in both incoming and outgoing calls. When I check the BT Manager, it shows a totally unstable BT strength that varies from very strong to very weak. The same headset worked well with other BT phones. My ROM version is 1.11.00 WWE, Radio version 1.04.00.
Any help would be greatly appreciated.

Bluetooth Stack problem on Kaiser - automatically re-establishing pair

Hi all,
I have posted this question also over a 4winmobile as I cant access xda-dev from work. Hopefully someone here can help.
I've been having difficulty with my Kaiser and a Parrot MK6000 car kit. I have tested the carkit with a Nokia as well, and have some results to report to aid in troubleshooting.
The Nokia was paired with the Parrot MK6000 kit, answers and makes calls and streams audio no problem. When the car is turned off, the pairing ends, when the car is started again the pairing starts back up ... auto, no probs. In addition, if you make a call with the phone, at the end of the call the pairing is ended, but within a few seconds is re-established.
On my Kaiser, I can pair the phone and car kit, but if the connection is lost (ie the car is turned off or bluetooth is stopped on the phone) and then I turn the car back on, it will not automatically pair. It attempts to, the car kit mutes the car radio and plays a tone, but the pairing is not established by the phone. It continues to do this every 30 seconds or so, but does not establish a connection.
Also, if I make a call with the phone when it has been sucessfully paired, on ending the call, the phone will not re-establish the pairing.
My conclusion is that all of my troubles relate to the fact that the pairing will not re-establish once lost.
Is anyone able to assist? I have upgraded the Kaiser radio to 1.27.12.32 (yes ... just tonite, see http://forum.xda-developers.com/showthread.php?t=349528&page=2) but have also tried radio roms 1.27.12.11 and 1.27.12.17 with no success. The ROM version is 1.81.861.0. Ive also tried installing some of the BT stacks that were developed up for the Hermes with no success. I've also installed Jetware with no sucess.
Getting very frustrated!
Adam

adamcullen said:
Hi all,
I have posted this question also over a 4winmobile as I cant access xda-dev from work. Hopefully someone here can help.
I've been having difficulty with my Kaiser and a Parrot MK6000 car kit. I have tested the carkit with a Nokia as well, and have some results to report to aid in troubleshooting.
The Nokia was paired with the Parrot MK6000 kit, answers and makes calls and streams audio no problem. When the car is turned off, the pairing ends, when the car is started again the pairing starts back up ... auto, no probs. In addition, if you make a call with the phone, at the end of the call the pairing is ended, but within a few seconds is re-established.
On my Kaiser, I can pair the phone and car kit, but if the connection is lost (ie the car is turned off or bluetooth is stopped on the phone) and then I turn the car back on, it will not automatically pair. It attempts to, the car kit mutes the car radio and plays a tone, but the pairing is not established by the phone. It continues to do this every 30 seconds or so, but does not establish a connection.
Also, if I make a call with the phone when it has been sucessfully paired, on ending the call, the phone will not re-establish the pairing.
My conclusion is that all of my troubles relate to the fact that the pairing will not re-establish once lost.
Is anyone able to assist? I have upgraded the Kaiser radio to 1.27.12.32 (yes ... just tonite, see http://forum.xda-developers.com/showthread.php?t=349528&page=2) but have also tried radio roms 1.27.12.11 and 1.27.12.17 with no success. The ROM version is 1.81.861.0. Ive also tried installing some of the BT stacks that were developed up for the Hermes with no success. I've also installed Jetware with no sucess.
Getting very frustrated!
Adam
Click to expand...
Click to collapse
Have you tried these registry tweaks? http://msdn2.microsoft.com/en-us/library/aa915920.aspx

There is a know problem with the Parrot kit and you will find a thread in this forum where a member has contacted Parrrot who replied that they are addressing the issue.
This one my be usefull.
http://forum.xda-developers.com/showthread.php?t=340908&highlight=parrot

NuShrike said:
Have you tried these registry tweaks? http://msdn2.microsoft.com/en-us/library/aa915920.aspx
Click to expand...
Click to collapse
Hi, thanks for that pointer ... most of what is described in that MSDN library isn't in my registry.
Im going to manually insert them all and see what happens.
A

Still no luck
I tried updating the Reg with the tweeks as suggest ... but still no luck. All i get is still the initial pair, but on disconnection, no automatic re-pairing of the device to the car kit.
Im doomed at this stage.

You're not alone. I have the same problem with my Motorola S9 headphones and Microsoft SYNC in my 2008 Ford Edge. Sometimes I have to turn BT on and off a couple of times for it to connect.

agreed
Turning the BT on and off a few times has also be part of my "solution" package.
This really isn't acceptable though. This device should automatically pair up, just like every other BT device does. BT is a protocol that should be adhered to and just work.
I have also tried this on my other WM device. It pairs a little better, but is not great. I've tried compairing the registry values of that device to my Kaiser, but I just dont understand the functionality of the reg settings enough to work out what to change.
Is there some developer out there who can help? This type of problem was experienced by us all back in the early days of the Hermes and this community sorted it out.
Can any developer out there help, like working out a port of the Widcomm BT stack for Kaiser?
a

Interesting. I have a Nokia CK-7W bluetooth car kit and the Tyn II has re-connected/connected to the kit every time. Actually more reliable than my SE K800i. Sorry that it doesn't help you.

Hey Juzzman,
nah, that doesnt help ... but does increase the frustration level!
Seems like you need to have a Nokia component in there somewhere for it to work ;-)
Anyhow, Im still convinced it is a bluetooth stack problem in the Kaiser. I'm going to try flashing one of the AT&T based roms and the other radio version and see what happens.
Cheers
Adam

I've had BT issues with all of my HTC devices, it's very frustrating.
Currently I've got a Kaiser (Orange), E650 (Orange) and a new S730, none of which work on my Pioneer headunit without Jetware.
The Kaiser with Jetware pairs up ok, but the sound is really tinny.
The E650 with Jetware sounds fine, but I can only send 150 contacts to the headunit.
The S730 doesn't pair, haven't put Jetware on it yet.
In the past I've had BT issues with M3100, C600, C500 etc etc.
Why the hell doesn't MS sort out their bloody BT stack!!!

Bluetooth problems
I am having the same problem with my JVC bluetooth unit BT1000. It will pair ok first time, allows me to make 2 calls. Will not the reestablish a connection/pairing. JVC worked fine with my sony erricson and nokia phones. Anyone found a cure to this?

Same problem with the stock AT&T rom (1.27.12.11) with the H700 headset.
Turn bluetooth on it normally sees the headset. If not turn it off and on again to get it to work. Once working it normal looses the connection after an hour or so.

Could it be a BT 2.0 Compliant issue?
I have posted this same problem earlier in xda-deveopers, on htc wiki and aximsite. Many people have viewed and are experiencing this same problem, but no one has posted any solution specific to my problem either. I hope a developer can solve this one for us. Is it a BT stack problem, or a BT 2.0 compliant problem, or a need for an updated ATT ROM to solve this issue? (I currently am using the stock ATT ROM 1.57.. that shipped with my Tilt.)
When I use my Motorola H700 with the Tilt the BT works fine, UNTIL, I use the voice speed dialing from the Tilt. Once I use the voice speed dialing directly on the Tilt, the Motorola H700 will no longer connect. I have to do a soft reset or go through the pairing process again. Once I re-establish pairing again, the H700 will continue to work fine, UNTIL, I use the voice speed dialing on the Tilt. Then we're back to having to do a soft reset to again establish H700 connection with the Tilt.
NOW, I just received a call back from an HTC tech who told me the problem is likely due to the Motorola H700 being only BT 1.2 compliant. He recommended that I try the Motorola H12, which is BT 2.0 compliant, but he could not absolutely guarantee this would solve my problem.
Does anyone know for SURE that the Motorola H12, being BT 2.0 compliant, will solve my problem? Or is there another solution?
Note: I have tried MS Voice Command 1.6 (full version), but the above problem still occurs. I have also tried Jetware, but again, no go. I am not sure that there is going to be an updated AT&T ROM to solve this issue either.
Additional Note: I have also tried other BT devices, such as the Jawbone, and the Plantronics Voyager. All do exactly the same thing as above.
Anyone have any solution? If the Motorola H12 is the solution, that would be great...
Thanks in advance.

I'm having the same problem with my new carkit. Did anyone ever find a solution to this??

Parrot MK 6100 compatibility

Just before my S730 died I tried to connect it with a Parrot MK 6100. It didn't work. The S730 stalled right after the connect. After 2 minutes it disconnected. Does anyone know if the S730 is compatible with this carkit? I might need to buy a new one, but I don't buy it if it isn't compatible.

can't find result for HTC S730 and MK6100:
http://www.parrot.com/usa/support/o...ompatibility/?idproduct=24&idbrand=41&etape=2
But I Have a HTC TyTN II and MK6000 and it's not really working 100%.
If I'm using navigation SW and streaming mp3 at the same time as I have to take an incoming call it'll lock up.
The Parrot do some strange after ending a call before it releases the mute function of my radio etc.
http://www.parrot.com/usa/support/o.../?idproduct=20&idbrand=41&idmodel=672&etape=3

HTC S730 works (almost good)
I bought the HTC S730 and it works fairly good. I experience the following problems:
Phone connects automatically, but A2DP needs to be connected manual. No big issue, because I seldom use the A2DP profile.
You need to pick up the phone using the Parrot's green button. Pressing the phone's button doesn't route the sound/mic through the Parrot, but leaves it on the phone (this might be done intentionally to allow private calls).
Sometimes the phone disconnects when calls are made quickly after eachother.
It's not perfect, but it works rather good. I only had very bad experiences with Windows Mobile and BT carkits, so I am already quite happy. I hope that Parrot fixes the last few flaws, but I suspect a lot of problems are in WM (or HTC).

update
You will have to flash you're parrot with latest firmware 1.3
We also did it here and now the htc S730 works although the tytn II (kaisers) don't work that fine.
Flashed my kaiser with dutty rom and now it syncs fine and i have no problems, but my collegue's with standard kaiserrom still do have problems.
This afternoon i will have a look into the other kaisers

anonymouz said:
You will have to flash you're parrot with latest firmware 1.3
Click to expand...
Click to collapse
I have firmware MK-6100 v1.03, but it isn't good. I always thought that my HTC S730 was causing the problems. However, I connected it to a built-in Audi carkit and the HTC S730 works great. I suspect it's not only the S730 that is causing the problem.
The main problem is that the S730 disconnects after finishing a phonecall.

TyTN II + Parrot 3200+ LS Colour

Hello,
I wonder if somebody can help me get to the bottom of this.
Basically, I have a TyTN II (branded as a T-Mobile MDA Vario III). I also have a Parrot 3200+ LS Colour car hands free kit.
Initially, I had a TyTN (branded as a T-Mobile MDA Vario II) and this worked fine with the Parrot. Problems began when I upgraded it to Windows Mobile 6 after an update was released by T-Mobile. What would happen is as I started the engine and the Parrot connected to the phone, it would say I was in a call even though I wasn't. It could only be resolved by rebooting the phone.
When I got the TyTN II, the problem became more frequent to the point where it was just annoying to use.
Now, this is where it gets interesting. Parrot are blaming Microsoft for this problem and aparently the problem *may* or *may not* get fixed in 6.1 which is some time off yet. It is a Bluetooth Stack issue aparently but I am not sure I believe them on this nor their attitude to if it will actually get fixed.
I am wondering if anybody knows anything more about this or any fix for it.
Best Regards,
Craig Brass

craigbrass said:
I am wondering if anybody knows anything more about this or any fix for it.
Click to expand...
Click to collapse
Install one of the 6.1 ROMs here and see if it helps?

I have this with my TyTn II and parrot 3300. It also used to happen with my Orbit.
I noticed that it only does it when a data connection is active. If I press the red button on the Parrot it clears and all is good.
Not sure if yours is the same issue.

I have a Parrot 3100, and have loads of problems! It randomly crashes, it randomly decides to want to call random people, it randomly decides to route the call through the Tytn II rather than the Parrot, and it randomly works without a problem. I emailed Parrot and got this response:
--------------------------------------------------------------------------
The HTC TyTn II is still undergoing compatibility tests with our products, thus is not listed as being compatible at present. We are currently also working closely with HTC to improve compatibility and functionality with new PDA devices running Windows Mobile 6.
I would recommend dialing out from the Parrot as opposed to using your handset as from experience this works best.
I would also recommend updating the software on your Parrot, the latest version is 4.16. To update you will need a Bluetooth enabled PC (preferably a laptop) and our Parrot update tool software. http://www.parrot.com/usa/support/downloads
--------------------------------------------------------------------------
Just noticed tonight that a new version is available for download, (4.17) so I have upgraded the Parrot and will give it a try tomorrow.
Cheers

so, was the upgrade succesfull? did it solve ur issue?
I'm also having issues using my tytn ii with the parrot ck3100. (standard firmware in it)

No, it hasn't completely. It has solved most of the problems, but it now decides to (randomly) mute incoming calls, and route the audio through the handset instead. It also decided to route the TomTom audio via the parrot! I didn't think that was possible???

I'm having some of the same sorts of problems w/ the Parrot CK3100 and my Tilt. Of course, I just go it installed last nite, so I haven't had a ton of time to play with it. I DID, however, do a long road trip today and here's what I've found.
When initiating a call from the phone, there's about a 50/50 chance that it will go thru the handset or Parrot.
One time, the Parrot locked up to a point that I had to get off at an exit and restart the engine to reset it.
I had to re-pair the phone and Parrot once, because the lost one another.
I'm running the latest AT&T ROM on my phone and latest firmware on the CK3100. I never had ANY of these problems w/ my Nokia CK-7W, but it had a REALLY annoying echo on the other end when used w/ anything but a Nokia phone.
Dan

Today, things got even stranger. As of this morning, the kit would try to initiate a phantom call every time the car was started and it connected w/ the phone.
Then, it was muting the radio for 1-2 seconds every 3 to 5 minutes - very annoying when listening to an audiobook.
As of this afternoon, both problems magically stopped. I have e-mailed Parrot tech support, but I'm not hopeful that I'll get a useful reply.

I have had so many problems with the 3200 that ,due to anger, I have broken the bracket and front screen. It mutes the radio even after the call has finished. Crashes too often. I have no audio at least half of the calls I make.
I must add that it also did this with my Trinity running WM6 but worked flawlessly with my SP5 smartphone.
I read "HTC and Parrot Announce Strategic Alliance" on the Reuters website.
How I chuckle.