Develop Bugs

T_Mobile MDA III, TomTom 3.03 and Bluetooth headset problems

Hi,
I have problems connecting to my bt headset since I have installed TomTom3. I am running the build3500 bluetooth stack from the 1.06.02 FRA radio. It was working fine without even losing connection with the mda, but after I installed tomtom, it can pair, but cannot connect. The weird thing is that I can sync using bluetooth. I suspect tomtom is keeping busy some of the bt com ports? i noticed that during installation, it required to close bluetooth (cause it said the file BtcoreIf.dll was in use) and as soon as I did that, it finished installation, but since then the headset stopped working. Anyone has similar problems??
Thanks in advance for any input.

Update
Managed to sort it out by upgrading my BT stack to 1.0.0.3900. Still cannot find any similar complaints in any forums. Can it just happen to my MDA III? Who knows....at least it works now, even if my engineering background is not happy with it :shock:

Upgrading the bluetooth stack
Hi,
I have exactly the same problem as you had, although I'm on the UK network Vodafone and have an XDA2s.
My current radio version is 1.06.02 but I can't fine what version my bluetooth stack is. How do I upgrade to 1.0.0.3900?
Thanks in advance for any assistance you can provide.

Hi,
I am using Qtek9090 with TomTom 3.07 and Jabra BT800 headset and have not the problems you people talk about here. I have to mention that I immediately updated my BT version from 2400 to 3900 the same day I purchased the whole stuff. I was - when I was in the shop - told that TomTom 3.07 can sometimes cause problems due to BT version of Qtek (1.0.0.2400) and I better upgrade it to 3500 and/or 3900. I was also told that there were known problems with earlier versions of TomTom wireless (like in your case TomTom 3.03) and that I (at least) had to use TT 3.07 and/or better upgrade the BT driver of my Qtek9090. In order to find your current BT version:
- Click on Bluetooth icon
- Select Bluetooth Settings
- Go to [About] tab
- And there you see your own Build
- You can also select [Advanced] button in [About] for more details
Anyway, once being at home and taking my device out of package I did a BT upgrade to 1.0.0.3900 right away and so far I have no issue with BT stack. Even Jabra BT800 which a lot people complain about works fine with my Qtek9090 (OK, I admit the CallerID at Jabra still not working but I already expected that).
I downloaded the 3900 version of Bluetooth driver (plus another Audio driver) at the following URL in The Netherlands: http://www.pdanieuws.nl/modules/mydownloads/singlefile.php?lid=37
kind regards,
- Avareh ([email protected])

tomtom gps
The problem is that tomtom is messing around a bit with bluetooth for bt gps receivers.
So after installing tomtom allways reinstall the latest bt drivers.

AFAIK you should always use TTN 3.07 (GPS and Navigator) on SE and Phone Edition devices (Blue Angels is both WM2003SE and Phone Edition)

Big Fat TY
I was getting stupid before reading this 3d.
Even went back to the shop with the motorola headset and had them show me it was working....
Tom Tom was the reason.

Avareh said:
I downloaded the 3900 version of Bluetooth driver (plus another Audio driver) at the following URL in The Netherlands: http://www.pdanieuws.nl/modules/mydownloads/singlefile.php?lid=37
kind regards,
- Avareh ([email protected])
Click to expand...
Click to collapse
This link is not working at the moment, is there another link for this, i am running an xdaIIs and installed navigator3 and could bond but not connect to my bt headset.
will try the stack upgrade also a link fopr nav3 3.07 would be handy too...
cheers.

all sorted now, have got the files and fixed the issue.

Bluetooth connection Qtek 9090

Hi all,
hope to find somebody able to help me. I have a Qtek 9090 purchased with the BT version 1.0.0. I'm using WM 03 SE. I would like to know if I can upgrade it the BT version and if yes how? Sometimes I really find it hard to configure BT devices (i.e. TOMTOM version 5.0).
Cheers

Start on the below page:
http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel
Then, look here where it says "How to upgrade to the latest Bluetooth Stack version (currently 1.0.0.3900)"
http://wiki.xda-developers.com/index.php?pagename=BA_Bluetooth_1.0.0.3900_Upgrade
Hope this helps..?

Thanks for the quick reply. I have checked on my device and the version of the BT is 1.0.0.39. Therefore does not need upgrade. Now my problem is to configure Tom Tom 5.0 with my GPS device which is BT and is produced by Hamlet. Every time I receive a message from Tom Tom saying the it is an invalid GPS signal and then I can read that the GPS signal was lost as soon as i finish to configure the device. Hope to find a solution

Look at other posts
Please see this post further down the forum for possible solution..?
http://forum.xda-developers.com/viewtopic.php?t=30291
Thanks!

Hamlet GPS reset
I had the same problem but i was not related to BA, but to the bluetooth GPS.
I suggest to reset your GPS as shown on hamlet site:
http://www.hamletcom.com/ProductDet...7a44ba0c8c59dce6d&Mode=Support&ProductId=3549
letme know it this helps
cheers
fucsia

[HTC 8525 + WM6] Bluetooth keeps disconnecting

Hello!
I do not know if someone has the same issue. I upgraded the WM6 to my HTC 8525 and bluetooth just keeps disconnecting all the time. It happened without any reason at all. I am using "Plantronics 510". The headset is fine, just phone switches the bluetooth off and I need to go to settings to switch it back on. I saw some people have a problem with car-enabled bluetooth. Not sure if it is the same problem.
Any advice? Does someone get the same problem? Any patch or solution?
Thank you!

viva_unix said:
Hello!
I do not know if someone has the same issue. I upgraded the WM6 to my HTC 8525 and bluetooth just keeps disconnecting all the time. It happened without any reason at all. I am using "Plantronics 510". The headset is fine, just phone switches the bluetooth off and I need to go to settings to switch it back on. I saw some people have a problem with car-enabled bluetooth. Not sure if it is the same problem.
Any advice? Does someone get the same problem? Any patch or solution?
Thank you!
Click to expand...
Click to collapse
which WM6 ROM are you using?

I had this problem with my Audi A4 car phone. The ROM versions using build Build 17745.0.2.3 were not good for that. Now, I'm using the Black Majik ROM and that works like a dream for the BT connections.

walshieau said:
which WM6 ROM are you using?
Click to expand...
Click to collapse
I have Cingular HTC 8525 [HERM100]
ROM Version: 3.30.2.1
ROM Date: 04/17/07
Radio version: 1.41.00.10
Protocol Version: 32.74.7020.18H

viva_unix said:
Hello!
I do not know if someone has the same issue. I upgraded the WM6 to my HTC 8525 and bluetooth just keeps disconnecting all the time. It happened without any reason at all. I am using "Plantronics 510". The headset is fine, just phone switches the bluetooth off and I need to go to settings to switch it back on. I saw some people have a problem with car-enabled bluetooth. Not sure if it is the same problem.
Any advice? Does someone get the same problem? Any patch or solution?
Thank you!
Click to expand...
Click to collapse
Did you manage to solve this? Is so how?
Thanks
Msuk

i started having the same problems but i noticed it after i installed the voice command.. the rom that i use is the gm360 gold. the problem ive got was whenever i was in a phone call using my blutooth and i received a text message it would deactivate my headset. if ur having somewhat of the same problem try disabling ur voice command software...

Multiple AT&T/HTC WM6 ROMs?
My 8525 with the WM6 ROM can no longer route the audio to the BT headset (a Moto HS850 - but this is irrelevant, I suspect).
Basic BT headset usage was fine with WM5 (excepting the known issues with VoiceCommand).
I thought that perhaps the issue was related to the various little registry tweaks and sw patches. However, I had to do a reflash (for other reasons) and currently have just the default WM6, no registry tweaks, no BT sw patches, and MS VoiceCommand 1.6 installed (but set to NOT use the BT headset).
Pairing works fine. So does activation recognition (i.e. the little headset appears in the notification area when I open the boom on the headset and I can hear the background establishment of the BT channel). But audio (dialing tones and Connected call audio) do not reach the headset. The audio also doesn't go to the phone's speaker.
So, are the official ROM updates that repair this? Or, is the cost of going to WM6 the abandonment of BT headsets?
By the way, VoiceCommand 1.6 works fine--if I tell it to stay away from the BT headset.

Pays WM6 Roms
I had the same BT disconnecting problems with my original german Vodafone WM5 and also still have them with Pays WM6 ROMs (2.02 - 2.15) in my Audi A6 MMI.
With the original german HTC WM6 ROM BT worked very well.
Everything else on Pays ROMs is really great. He´s doing great jobs.
Any idea?

I have the same problem with my 8525 and I use plantronics 520. It did the same thing even with other headset too, and also happens in WM5.0, 6.0 and 6.1.
I am tending to believe its a hardware issue, but dont know how to prove it!

ai6908 said:
I have the same problem with my 8525 and I use plantronics 520. It did the same thing even with other headset too, and also happens in WM5.0, 6.0 and 6.1.
I am tending to believe its a hardware issue, but dont know how to prove it!
Click to expand...
Click to collapse
Come On, experts on the XDA portal, no solution?? noooo way!!??

My friend had the same issue with an tytn2 and last schap's rom in french language.
After an hard reset i get BT work fine with his OPEL.
But before i made lot of test desinstalling soft check registery key with no result. I still do know why BT was disconecting woth no reason.
Cheers.

Audi Bluetooth hands free
I had the same problems in wm6 with some roms.
I use the official HTC TyTn wm6 with excelents results, also Schaps 4.31 work very good (No disconection at all).
Now I am using Pay WWE 4.30 with many disconections.
BTW I have the audi TT bluetooth option.

On my 8525 Hermes I use the latest Pays Rom and it was disconnecting all the time (Parrot BT) - BUT then I decided to TURN OFF THE WAN and it improved greatly. Other thing I noticed is that the Hermes has to be in DIRECT LINE OF SITE of the BT device at all times or it is erratic.

BT
It seems there are differences in the WM6 versions. As said earlier in this thread for me original HTC and Schaps WM6 ROM versions are running without any BT disconnections.
Tried several WM6.1 versions now and every single one is working fine with my Audi MMI.

Similar problems handing BT control between applications
Hi all, I've been experiencing similar problems since changing ROMs. Originally with Schaps 3.60a I was able to make a call whilst listening to music all using my BT headphones. The Call would pause the music & resume afterward. It worked great! However since changing to Schaps 4.0, 4.2 & now CRC's PHKv12r9, I've never had the same. On a couple of rare occasions it has all worked fine but more often the bluetooth has to be turned off & back on again to reconnect. it seems to relate to what other programs are also running. I suspect there must be registry settings which control the bluetooth operational modes which are brought into play by the various programs running.

Bluetooth carkitt no longer working after upgrade to WM6

A few days ago I upgraded my HTC P3300 to the official WM6 rom.
All works fine except calling using my bluetooth carkitt.
The carkitt I have is the factory carkitt in a Peugeot 307SW. I've read somewhere this carkit is made by Parrot and can also be found in the Peugeot 207, Citroen C4 end some Seat models. Googling showed averyone with those carkitt's has the same problem sinde the upgrade to WM6. It all worked fine in WM5 by the way. I've also tested with several non official WM6 roms, but it's still not working.
Connection and pairing the phone is not the problem. I do see the contact list in my car display and I can even see the battery status. The problem is when I dail. My speakers mute my radio/cd sound, but I don't hear the phone through them. It's just silent. I can't hear the person answering the phone and I don't hear the dial tone. The strange thing it sometimes works. I have the impression it starts to work after I strated tomtom, but I'm not sure about it. What never works is when people call me. The phone rings, but when I answer I can't hear the person on the other side.
Is there any way to fix this? It looks like bluetooth 2.0 isn't 100% compatible with bluetooth 1.1 or it's a bug in WM6. There is no upgraded firmware for my carkitt available and like saif before, a lot of other car owners have the same problem.
Please help.
Rene

renepela said:
A few days ago I upgraded my HTC P3300 to the official WM6 rom.
All works fine except calling using my bluetooth carkitt.
The carkitt I have is the factory carkitt in a Peugeot 307SW. I've read somewhere this carkit is made by Parrot and can also be found in the Peugeot 207, Citroen C4 end some Seat models. Googling showed averyone with those carkitt's has the same problem sinde the upgrade to WM6. It all worked fine in WM5 by the way. I've also tested with several non official WM6 roms, but it's still not working.
Connection and pairing the phone is not the problem. I do see the contact list in my car display and I can even see the battery status. The problem is when I dail. My speakers mute my radio/cd sound, but I don't hear the phone through them. It's just silent. I can't hear the person answering the phone and I don't hear the dial tone. The strange thing it sometimes works. I have the impression it starts to work after I strated tomtom, but I'm not sure about it. What never works is when people call me. The phone rings, but when I answer I can't hear the person on the other side.
Is there any way to fix this? It looks like bluetooth 2.0 isn't 100% compatible with bluetooth 1.1 or it's a bug in WM6. There is no upgraded firmware for my carkitt available and like saif before, a lot of other car owners have the same problem.
Please help.
Rene
Click to expand...
Click to collapse
Same problem here... when upgrade to WM6 official the sound in the car is gone when dailing. Phone is connected but I'am unable to hear anything... everything goes into mute...

I'm stuck with the very same problem. I'll try JetWare and change some configs, but I fear it will not work.
If I have any news I'll post them.
Regards
P.D My car is a Citroen C4, and original Citroen bluetooth I think is a Parrot 3000 or 3100

I have the same problem.
Car kit BT Peugeot 207 and HTC 3300 with cooked room wm6.
I've installed jetware extension. I can hear sound in the first call but when I hang up the next call, the same problem .. no soud.

renepela said:
A few days ago I upgraded my HTC P3300 to the official WM6 rom.
All works fine except calling using my bluetooth carkitt.
e problem.
Please help.
Rene
Click to expand...
Click to collapse
Has anyone found a solution for this? I have found deactivating the bluetooth and reactivating on the call works.
I would hope someone finds a solution. What would be the downside of going back to WM5?? I cannot remember why I upgraded now.....

I finally downgraded to WM5, but I'm interested in knowing if new WM6.1 ROMs have corrected the problem. We have both Blak&Blue and Vanilla versions based on WM 6.1
I've not upgraded to WM6.1 because I'm tired of problems. If someone try to install it, please report
Regards

Alvinillo said:
I finally downgraded to WM5, but I'm interested in knowing if new WM6.1 ROMs have corrected the problem. We have both Blak&Blue and Vanilla versions based on WM 6.1
I've not upgraded to WM6.1 because I'm tired of problems. If someone try to install it, please report
Regards
Click to expand...
Click to collapse
Can you advise me how you downgraded? I have a UK o2 XDA. what is yours? Can you provide the links and instructions for me do get back to WM5

azreal1983 said:
Can you advise me how you downgraded? I have a UK o2 XDA. what is yours? Can you provide the links and instructions for me do get back to WM5
Click to expand...
Click to collapse
Mine is an HTC P3300 locked to local Movistar provider. To downgrade, you must find a WM5 ROM, that's all. I found ART_HTCESN_1.14.412.1_026790_ESN_Ship.exe but it is Spanish, so probably it doesn't interest you.
Downgrade procedure was exactly the same as upgrade.
Would you be so kind to test some WM 6.1 releases with the car's bluetooth before downgrading to WM5?. It could work and I assume that in any case you are going to reinstall everything, so a kick install should be not much of a problem.
Regards

Alvinillo said:
Mine is an HTC P3300 locked to local Movistar provider. To downgrade, you must find a WM5 ROM, that's all. I found ART_HTCESN_1.14.412.1_026790_ESN_Ship.exe but it is Spanish, so probably it doesn't interest you.
Downgrade procedure was exactly the same as upgrade.
Would you be so kind to test some WM 6.1 releases with the car's bluetooth before downgrading to WM5?. It could work and I assume that in any case you are going to reinstall everything, so a kick install should be not much of a problem.
Regards
Click to expand...
Click to collapse
Yeah i would be happy to.
If someone can point me in the direction of what I have to do.
I have a UK o2 XDA, so I assume I would need to unlock it first?

azreal1983 said:
Yeah i would be happy to.
If someone can point me in the direction of what I have to do.
I have a UK o2 XDA, so I assume I would need to unlock it first?
Click to expand...
Click to collapse
Nice!
But I find a problem, isn't your O2-XDA also known as Wallaby? I mean, if I'm right you are posting in the wrong forum or at least you should be advised not to install another PDA ROM on yours becouse you risk to brick it. We are posting at Artemis forum. Of course, Bluetooth problem seems not related to PDAs but WM6
On this forum there is info about how to unlock your PDA. Unfortunately I dont find any ROM for your device.
Regards

Same Problem
hi all,
207 FACTORY KIT / M650
I have the same problem, only the original ROM under WM5 work properly...
I Tried many bluetooth soft on several tips and WM6 release...
AJE , 1.5 / 6 /8 / 9 / 2.0 beta........
Now i am under B&B 5 (WM6.1) and the problem persist
I note that if i desactivate bluetooth stereo and fix sample rate to 44Khz, it looks to work a little better than before.
If i wait between 2 phone call (out), it works much.
If i answer to a phone call with the remote control it never works.
If i answer with green touch on the phone it work ALL the time.
Are we condamned to stay under WM5 !??
WM5 -> bluetooth but no CRM (does'n't want to work)
WM6 -> No bluetooth but CRM...
I choose to work on this but any result, since more than eight month...
HEEEEEEEEEEELLLP US AND SHAME ON PA**OT
PS: HTC and parrot pass a deal to increase compatibility of their product...
Since this time does anybody tel to parrot on this problem ?
Does newer HTC product originaly under WM6 work fine one factory kit (peugeot/citröen 207/C3...) because if no, i think parrot sucks ! they update firmware on all their product, but for product sells to peugeot or citroen -> NOTHING

Thx for the info. It's a pity that the problem persist on WM6.1
We are hooked to WM5 and to my eyes, the Artemis and PocketPCs look older than ever.
At the end, I think it is a Microsoft problem. PSA Bluetooth CarKit works flawlessly with WM5 so Microsoft changed something to the Bluetooth stack on WM6. Shame on them.
I'll wait to WM7, but I don't have too much expectations.
Regards

Some hotfixes are available from HTC regarding bluetooh, only not for the Hermes. damm.
Anyone tried one of these already? Currently still not able to updrade to WM6.1
http://forum.xda-developers.com/showthread.php?t=385128
And one recently for the Diamond..:
6/16/2008
Hot fix for resolving Bluetooth headset sound problem that occurs when reconnecting with HTC Touch Cruise
If you are using the Bluetooth headset, “Jabra JX10”, “Jabra BT500” or “Samsung WEP 150”, and the headset becomes out of range or undetected by the HTC Touch Cruise, in certain circumstances, you may be unable to hear any sound from the headset even after it has reconnected successfully with HTC Touch Cruise. Please install this hot fix to improve the connection when using the above-mentioned Bluetooth headsets.

6.1 and tom tom, bluetooth working now?

Can any body tell me the best 6.1 cab to use tom tom on have trouble with bluetooth at the moment wont stay paired up.
Will consider using a 6.0 cab if this is the only way.
is there a fix
thank you

Had no problems with either Farias R-32 versions, and Schaps was fine too.
i found TomTom pretty good with pairing and finding bluetooth signals.

TNT 19999
Hy...
no problem with this rom.... i hope this notice can help you.....
If you need some other information cantact me!!!
Bye!!

there must be another problem, mabe with your bt-gps. Been flashing about 7 different 6.0 and 6.1 roms's the last few weeks and none of them heve instable bluetooth gps pairing and using.
i'm using a bt-gps and bt-stereo headset intensive together. listening to mp3, on the same time tomtom is telling directions, while on the background pushmail is bringing me new mail that i can read at the same time, being interrupted for incoming sms.
on top of that all an incoming phone call on my bt-headset will work, just as using a voice command to dial a number myself. and the mp3 player automaticaly pauses and restarts at the end of the phonecall.
tomtom keeps working.
just when ending a phonecall sometime the mp3 sound goes to the pda speaker instead of the headset.

Pays 6.1 ROM works with tt6 and bt.

My hermes kept droping out with TomTomon WM5 all the time, but since I switched to WM6 i never had a single drop.
For me WM5 > WM6 stopped all TomTom problems I had

l3it3r said:
Pays 6.1 ROM works with tt6 and bt.
Click to expand...
Click to collapse
Better late the never: Correct

photoscubaman said:
Can any body tell me the best 6.1 cab to use tom tom on have trouble with bluetooth at the moment wont stay paired up.
Will consider using a 6.0 cab if this is the only way.
is there a fix
thank you
Click to expand...
Click to collapse
hi Photoscuba, i have the exact same problems
First it wont pair properly (says that the key is incorrect).
Its there in the Bluetooth device list, so i open a com port for it then run my gps software, goto detect GPS but then i keep getting GPS reciver wants to pair with you message, as soon as i can answer yes or no, another screen will pop up saying the same
i have asked in several other threads if anyone else is having the same issues, but everyone elses seem fine.
i did read some where about all wm6.1 rom having problems with pairing when using the pass code 0000 (something along the lines of it sending a NULL or a single 0), but i cant find now. ill keep looking for it maybe someone has over come this, on a thread on XDA.
i use a HOLUX GPSlim240 receiver and it works flawlessly with wm6's
im using K's 1.3 at the mo

All these ROMS worked for me
I like to test new ROM and play around a lot.
I have tested Tom Tom 6 and my Bluetooth GPS on the following WM 6.1 ROM all worked.
Below are the ROM in the order i used them.
FARIA-R-32-CLEAN
TNT.19199_Professional_Hermes
CRCs_PHKv12r10
Binky11'sv3_3 - Great Clean ROM and i loved S2U2
PDACorner.V10 - New ROM i am testing right now

What map software and GPS units are everyone using?
maybe theres a incompatibilty problem with certain makes of GPS and wm6.1
im using destinator 7 and igo6 with a holux 240 GPSlim

crusti said:
What map software and GPS units are everyone using?
maybe theres a incompatibilty problem with certain makes of GPS and wm6.1
im using destinator 7 and igo6 with a holux 240 GPSlim
Click to expand...
Click to collapse
Considering they are talking about Tomtom, I assume thats the software they are using....

yea, lol, shoulda seen that coming
but the problem seems to be the gps unit connecting or staying paired to the phone, so if there a list of bluetooth gps units that are working fine with wm6.1 then maybe see why some units wont connect
It all works fine on all the WM6's, so the change is in how wm6.1 handles it as far as i can work out
if theres a list of workin and non working GPS's then maybe i could see what the problem is