Develop Bugs

WM6 Bluetooth Headset Problem

Hi there I'am new here.... seached the forum and google a lot but didn't find an answer...
Just flashed from XDALive 2.0 to Black 2.0, radio 1.38.00.10 and HardSPL v6 with help of the manual of mrvanx.
My problem with the rom of XDALive 2.0 was that TomTom 6 keep hanging serveral time. The headset (bluetooth build in CAR, peugeot 207) was working perfectly. After the upgrade to Black 2.0 the TomTom problem was solved , it works perfectly now. The only what came up was the bluetooth headset probleem. The connection is ok but I don't hear any sound??
Flashed back radio ROM to 1.35 no results...
Found something interesting...
When its not connect with the carkit, turn on bluetooth, dail a numbers and turn on the Speaker, it will eventually connect to the carkit automaticly (and I got sound thourgh the carkit!
When searching for bluetooth devices it will find the headset and the carkit goes into 'calling mode'. When dailing a contact directly after that the carkit will work. But the next try it will mute the radio but doesn't give any sound on the carkit.
When allready connected with bluetooth on the carkit it wont give any sound thourgh it.... strange.. Tried serveral other ROMS but they are giving me the same problem...
Widcomm BT Stack (http://forum.xda-developers.com/showpost.php?p=1072773&postcount=72) also tried, didn't help... anyone some suggestions?
PS.: My old nokia still works, it can't be the carkit..

Question for you. after you setup your carkit do you go into the bluetooth and set it to your handsfree device. There seams to be a few changes to the way WM6 chooses the handsfree device if you have several set up.
I have to change in WM6 bluetooth which headset I am using when I switch between the 3 headset I have. I have to go to Start\Settings\Connections\Bluetooth Click/Hold on my headset that I want to make active - you will get a Menu wit Edit/Delete/Set as Hands-free/Set as Wireless Stereo (last should be grayed out if it doesn't support Strereo)
Choose Set as Hands-free
After doing this my headset works fine. Try it and see if it works for you.

jcb_home said:
Question for you. after you setup your carkit do you go into the bluetooth and set it to your handsfree device. There seams to be a few changes to the way WM6 chooses the handsfree device if you have several set up.
I have to change in WM6 bluetooth which headset I am using when I switch between the 3 headset I have. I have to go to Start\Settings\Connections\Bluetooth Click/Hold on my headset that I want to make active - you will get a Menu wit Edit/Delete/Set as Hands-free/Set as Wireless Stereo (last should be grayed out if it doesn't support Strereo)
Choose Set as Hands-free
After doing this my headset works fine. Try it and see if it works for you.
Click to expand...
Click to collapse
When searching for a new bluetooth device WM6 sees a headset and the connection is successful. The 'Set has headset' is availible and is set. The option Wireless Stereo isn't support I think, its not availible as an option.
When calling you can turn on/off your headset back to the phone. That works but there is still no sound on the headset.

balck 2.0 does have issues. i also have same with motorola hs850.
only just found out. havent fixed.
bt connects as phone pad shows it.
headset bleeps on connect call and disconnect call. but no sound is sent or received.
always set to headset though not hands free.
will have to test further but definitely an issue. i didnt ask jj out of respect for his withdrawl of support.

I don't think it a problem with Black 2.0. Too many people say it works no problem.
I'm on black and all three of my head sets work like a charm. I have 2 Motos an H810 and a H700 and an Plantronics 510. I also have been able to use internet sharing, BT file transfer, and BT sync with Black 2.0
But it could be an incompatability between the WM6 M$ BT stack and your hands free kits.
Test your phones with another BT device and see what you get.

Same problem with HS850
simon_darley said:
balck 2.0 does have issues. i also have same with motorola hs850.
only just found out. havent fixed.
bt connects as phone pad shows it.
headset bleeps on connect call and disconnect call. but no sound is sent or received.
always set to headset though not hands free.
will have to test further but definitely an issue. i didnt ask jj out of respect for his withdrawl of support.
Click to expand...
Click to collapse
I have exactly the same problem, and I didn't solved yet....but I've found this bypass:
When the phone rings I answer with the bluetooth handset and receive the beeb on connect call.....then I close the BT headset and as soon as I re-open it, I have the headset working.....I have to do this for every incoming or outgoing call.
My BT headset was working well with the black 1.2.
This is the only issue I've found in the black 2.0.....I think is the most stable and fast rom.
Bye prengo.

jcb_home said:
I don't think it a problem with Black 2.0. Too many people say it works no problem.
I'm on black and all three of my head sets work like a charm. I have 2 Motos an H810 and a H700 and an Plantronics 510. I also have been able to use internet sharing, BT file transfer, and BT sync with Black 2.0
But it could be an incompatability between the WM6 M$ BT stack and your hands free kits.
Test your phones with another BT device and see what you get.
Click to expand...
Click to collapse
My other Bluetooth devices are working fine. My bluetooth GPS receiver works just fine with TomTom... no issues there.

Just flashed back to XDA-Live (v0.20.1) and the headset works without any problem.
Only thing now is Tom Tom 6 hangs directly after the start of it. Anyone familiar with this issue?
thx
PS.: what is the differance between the Black 2.0 and XDA-Live (v0.20.1) ? other bluetooth driver versions besides the os version? Maybe there is a way to combine..?

A common thread seems to be the HS850
I have the exact same problem with my HS850. I get the call connect beeps but no sounds come through. The issue exists if the headset is connected when the call is made. If I make the call, then flip the boom and turn the headset on, then I get sounds no problem.
I had this issue with both LVSW 4-08 and Black 2.0. I eventually went back to XDA Live 0.20.1 and my BT issues all went away.

cruzer said:
PS.: what is the differance between the Black 2.0 and XDA-Live (v0.20.1) ? other bluetooth driver versions besides the os version? Maybe there is a way to combine..?
Click to expand...
Click to collapse
WMXL .20 is based on a beta WM6 build and Black 2.0 is built on an RTM build (non-beta)

With Moto HS850 too.
edwinyuen said:
I have the exact same problem with my HS850. I get the call connect beeps but no sounds come through. The issue exists if the headset is connected when the call is made. If I make the call, then flip the boom and turn the headset on, then I get sounds no problem.
I had this issue with both LVSW 4-08 and Black 2.0. I eventually went back to XDA Live 0.20.1 and my BT issues all went away.
Click to expand...
Click to collapse
Exactly the same here with HS850. Tried everything after 20070320_RUU_Hermes_WWE_3.23.0.0_1.34.00.10.exe but kept getting no sound.

I have experienced the same problem with my 407 hands free system. My Orange SPV C600 works without a problem, it does not show signal strength and battery level though. Using my M3100 with any of the following listed below works perfectly:
HTC English QTEK_001 2.11.255.1 03/07/07 2.11.255.102 1.38.00.10 32.71.7020.12H OS 15673.3.3.1 AKU 3.3.1
Cingular English CWS__001 2.15.502.3 04/09/07 ?? 1.40.30.00 32.73.7020.16H OS 15706.3.5.2 AKU 3.5.2
XDA-Live (v0.20.1) English 3.22.110.1 01/04/07 None None 5.1.195 (WM6) OS 17217.6.0.0
I have found all the above roms work perfectly with my TomTom 6.030 software. I am currently using Black Version 2, I have also used LVSW roms and found the same issue with any running the OS 17736.0.2.0

mike6502 said:
I have experienced the same problem with my 407 hands free system. My Orange SPV C600 works without a problem, it does not show signal strength and battery level though. Using my M3100 with any of the following listed below works perfectly:
HTC English QTEK_001 2.11.255.1 03/07/07 2.11.255.102 1.38.00.10 32.71.7020.12H OS 15673.3.3.1 AKU 3.3.1
Cingular English CWS__001 2.15.502.3 04/09/07 ?? 1.40.30.00 32.73.7020.16H OS 15706.3.5.2 AKU 3.5.2
XDA-Live (v0.20.1) English 3.22.110.1 01/04/07 None None 5.1.195 (WM6) OS 17217.6.0.0
I have found all the above roms work perfectly with my TomTom 6.030 software. I am currently using Black Version 2, I have also used LVSW roms and found the same issue with any running the OS 17736.0.2.0
Click to expand...
Click to collapse
It's great that you tracked this down so specifically. I guess this means for those of us with these issues, we have to avoid newer WM6 builds until someone looks into this.

idee2000 said:
Exactly the same here with HS850. Tried everything after 20070320_RUU_Hermes_WWE_3.23.0.0_1.34.00.10.exe but kept getting no sound.
Click to expand...
Click to collapse
Can't just be the ROM as my HS850 works perfectly with Black Pro 2.0

rabdo said:
Can't just be the ROM as my HS850 works perfectly with Black Pro 2.0
Click to expand...
Click to collapse
I have the same problem as the others with my HS850. No audio if the headset is on when a call is made or received but if I close the boom and re-open it, viola it works again.
I did have a problem with HTweakC where I changed the A2DP setting to on and now no matter what I do I can't get it off again. I might re-flash and see if that helps.
I don't know if it matters but I have MS voice command on my phone, even though the MSVC16BThack doesn't work anymore. (my phone is an 8525) Hope someone can figure this out, I really like the speed and stability of this ROM but if I can't get my BT to work I'm going to have to downgrade.

AdamsJourney said:
I have the same problem as the others with my HS850. No audio if the headset is on when a call is made or received but if I close the boom and re-open it, viola it works again.
I did have a problem with HTweakC where I changed the A2DP setting to on and now no matter what I do I can't get it off again. I might re-flash and see if that helps.
I don't know if it matters but I have MS voice command on my phone, even though the MSVC16BThack doesn't work anymore. (my phone is an 8525) Hope someone can figure this out, I really like the speed and stability of this ROM but if I can't get my BT to work I'm going to have to downgrade.
Click to expand...
Click to collapse
I am using Cyberon Voice Commander v2 - maybe that is why it is working for me

Hi,
I am using radio rom 1.40.30 and Black 2.0.
I am using H700 BT headset
the problem i face are opposite from you all.
If i am already talking halfway and i flip the boom to continue talking with the BT headset...it won't work.
if i receive a call and I flip the boom while the phone rings, it is ok and i can even press the button on the h700 to answer the call.
Radio 1.40.30 seems to connect with the BT headset much faster.
last time when i was using my previous default factory rom, when i flip the boom while the phone is ringing, it will take ages to connect
why not u guys try radio rom 1.40.30 also

rabdo said:
I am using Cyberon Voice Commander v2 - maybe that is why it is working for me
Click to expand...
Click to collapse
I did a hard reset, paired the headset, and tried it right away and still had the issue so it's not VC 1.6. It has to be related to the ROM as I have the same Radio ROM for all three OS images and only the XDA Live ROM works correctly.

edwinyuen said:
I did a hard reset, paired the headset, and tried it right away and still had the issue so it's not VC 1.6. It has to be related to the ROM as I have the same Radio ROM for all three OS images and only the XDA Live ROM works correctly.
Click to expand...
Click to collapse
Sorry, what I meant is that perhaps Cyberon Voice Commander is 'fixing' the issue on my system, rather than saying MS VC 1.6 was causing the problem. Next time I hard reset I will test my headset BEFORE installing cyberon software

Ok I'm still having this problem and this is what I have tried so far:
I downgraded to XDALive v0.10 and my BT worked, but no WiFi
So I upgraded to HardSPL v6, then installed the 1.40.30.00 Radio rom, and then went back to Cingular Black 2.0, WiFi back but no BT unless headset is activated after call is initiated.
Installed Cyberon Voice Commander, didn't effect anything, still no BT
Removed Cyberon Voice Commander and re-installed MS VC 1.6 installed all the hacks and still no audio in the headset.
So it looks like it is something in the ROM that is killing the BT functionality. Maybe because the XDALive is based on a beta WM6 and the Black is based on a full version?

[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.

Tomtom 6 is purposedly disable for the Tytn ??

Having just bought a Tytn I found that my tomtom 6 didn't work. I seemed to have two issues. 1) It hung up frequently and 2) It kept losing my external bluetooth GPS receiver.
I thought I'd go to Tomtom's page to see if there was a fix given that HTC mention this saying that Tomtom have updated version 6 for the device.
http://www.europe.htc.com/en/htctytn/support/faq.html?id=539&cat=applications
To my horror I I found this page which suggests that the device is not supported, never has been and never will be. The reason according to Tomtom is due to an agreement with HTC,
http://www.europe.htc.com/en/htctytn/support/faq.html?id=539&cat=applications
I am trying to catch up on this device so am swamped by data at the moment but this is a real blow to me as one of the main priorities is to run Tomtom 6. When I bought the device I assumed that it was just a pocket pc with a phone in it. Seemingly I am wrong as there appears to be differences with the hardware or Tomtom checks the device it's running on and presumably refuses to work properly.
Can anyone enlighten me as to how ( if at all to get around this issue). Currently my device still has mobile 5 but I am ploughing through the plethora of information on this site trying to figure out exactly what I should and shouldn't do. I've a lot of catching up to do..
Any advice / suggestions would be most welcome, it seems too strange a concept to be locked out of running a pc app just because of the hardware it's running on.
EDIT: Apologies moderator this probably shouldn't be posted in the wm6 thread even though I am intending to move over and would like to use tomtom on that. Please move it if necessary.

louiscar said:
Having just bought a Tytn I found that my tomtom 6 didn't work. I seemed to have two issues. 1) It hung up frequently and 2) It kept losing my external bluetooth GPS receiver.
I thought I'd go to Tomtom's page to see if there was a fix given that HTC mention this saying that Tomtom have updated version 6 for the device.
http://www.europe.htc.com/en/htctytn/support/faq.html?id=539&cat=applications
To my horror I I found this page which suggests that the device is not supported, never has been and never will be. The reason according to Tomtom is due to an agreement with HTC,
http://www.europe.htc.com/en/htctytn/support/faq.html?id=539&cat=applications
I am trying to catch up on this device so am swamped by data at the moment but this is a real blow to me as one of the main priorities is to run Tomtom 6. When I bought the device I assumed that it was just a pocket pc with a phone in it. Seemingly I am wrong as there appears to be differences with the hardware or Tomtom checks the device it's running on and presumably refuses to work properly.
Can anyone enlighten me as to how ( if at all to get around this issue). Currently my device still has mobile 5 but I am ploughing through the plethora of information on this site trying to figure out exactly what I should and shouldn't do. I've a lot of catching up to do..
Any advice / suggestions would be most welcome, it seems too strange a concept to be locked out of running a pc app just because of the hardware it's running on.
EDIT: Apologies moderator this probably shouldn't be posted in the wm6 thread even though I am intending to move over and would like to use tomtom on that. Please move it if necessary.
Click to expand...
Click to collapse
Try a search on the Hermes forum. I found lots of stuff.
I found THIS ONE . But there were MANY others. Some users reported success with some ROMs.

Don't fret, it works fine on mine... Are you running a WM6 image - you may wish to upgrade to wm6 if you're not. (or downgrade to TT5.....)
Treat the issue as 2 separate problems, bluetooth related loss of GPS unit, and the stability of the TT6 software.
There are any number of other applications that will let you connect and read signals from the GPS unit, try these to see if you have a faulty gps unit or if its TT playing up.
Once you're happy with this look at the TT issue.....

I have 2 Varios II and I can admit that I had some issues with TT6 with WM5. TT liked to freeze when I was typing in the address or browsing through menus. When I changed to WM5 AKU3.2 it was better, but still not perfect. Eventually, it was WM6 that helped me. Now TT6 is running without any issues (of course it can freeze from time to time when I have too many programmes running in the background). Just try any of new WM6 and everything should be fine.

I had TT5.21 which people said run fine which didnt on wm6 but TT6.1 works fine

Long time since i've been on here but while i was browsing about, i saw this problem. All i can suggest is using the inbuilt GPS and see how that works? I have TT6 as well and i have used it perfectly well on an XDA Mini, XDA Orbit, SPV M700, HTC Touch, HTC TyTn II... seems a bit odd that you're having these problems. Have you since cured the fault or is it still being a bit of a ****bag?!
While i'm here... anyone got the latest maps at all for TT6? Shout me on [email protected] if you have any info on TT6 or need any PDA / Pocket PC help.
Griz

ibanyard said:
Don't fret, it works fine on mine... Are you running a WM6 image - you may wish to upgrade to wm6 if you're not. (or downgrade to TT5.....)
Treat the issue as 2 separate problems, bluetooth related loss of GPS unit, and the stability of the TT6 software.
There are any number of other applications that will let you connect and read signals from the GPS unit, try these to see if you have a faulty gps unit or if its TT playing up.
Once you're happy with this look at the TT issue.....
Click to expand...
Click to collapse
Yeah, I had established that the gps was working fine, I've been happily using it on my ipaq 2210 for ages. Then with the Hermes testing with gpsgate and some other stuff showed no problems.
The problem I had was that my TT6 was a 2GB SD card version and I didn't have micro SD big enough to test it. I had about 1hour to play with my friend's one and that's when I discovered the two problems.
He lent me the card to play with this evening and I've made a little progress now. I've sorted the flakey GPS operation, primarily by changing the com port, deleting the pairing and pairing again. So far that's not dropped out since.
Tomtom runs but freezes, this appears to be a confirmed problem which I hope that WM6 will solve as (mean-machine) suggests.
I feel a lot happier that the damn thing runs at least. The freezing appears to be related to cpu usage as I find that that zooming right out on a map is a good way to cause this to happen. The menu screens can be a problem too and the rest appear intermittent. As others have stated in other threads, hitting the red button and then switching back to TT will free it up.
I guess the next thing is to study the Wiki and try an make sense of the order things need to be done to put WM6 in, which Rom if any, which version of WM6. ... Information overload, so I think I need to take it slow and ingest the data .
Thanks for all the replys guys, it amazes me how much support HTC has and how many of you are passionate about them. Up till a few months ago I had never heard of HTC, now I doubt I'd consider anything else.

TomTom6
louiscar said:
Having just bought a Tytn I found that my tomtom 6 didn't work. I seemed to have two issues. 1) It hung up frequently and 2) It kept losing my external bluetooth GPS receiver.
I thought I'd go to Tomtom's page to see if there was a fix given that HTC mention this saying that Tomtom have updated version 6 for the device.
http://www.europe.htc.com/en/htctytn/support/faq.html?id=539&cat=applications
To my horror I I found this page which suggests that the device is not supported, never has been and never will be. The reason according to Tomtom is due to an agreement with HTC,
http://www.europe.htc.com/en/htctytn/support/faq.html?id=539&cat=applications
I am trying to catch up on this device so am swamped by data at the moment but this is a real blow to me as one of the main priorities is to run Tomtom 6. When I bought the device I assumed that it was just a pocket pc with a phone in it. Seemingly I am wrong as there appears to be differences with the hardware or Tomtom checks the device it's running on and presumably refuses to work properly.
Can anyone enlighten me as to how ( if at all to get around this issue). Currently my device still has mobile 5 but I am ploughing through the plethora of information on this site trying to figure out exactly what I should and shouldn't do. I've a lot of catching up to do..
Any advice / suggestions would be most welcome, it seems too strange a concept to be locked out of running a pc app just because of the hardware it's running on.
EDIT: Apologies moderator this probably shouldn't be posted in the wm6 thread even though I am intending to move over and would like to use tomtom on that. Please move it if necessary.
Click to expand...
Click to collapse
I have been using TomTom 6 on my Imate Jasjam (TyTn) both with WM5 and many versions of WM6. It works flawlessly never missing a beat. What com port are you using? Have you turned off secure connection?

@louiscar: a good place to start with upgrading info (to avoid the overload) is THIS SITE . Great guides that make it simple.

rbin said:
I have been using TomTom 6 on my Imate Jasjam (TyTn) both with WM5 and many versions of WM6. It works flawlessly never missing a beat. What com port are you using? Have you turned off secure connection?
Click to expand...
Click to collapse
Hi rbin,
I've currently got the GPS panel set to 'program port = com2', 'hardware port = com0' and my bluetooth gps is set to 'outgoing = com0'
Currently this works well so the GPS issue has been resolved.
Tomtom on the other hand freezes pretty much as described here:
http://forum.xda-developers.com/showthread.php?t=299892&highlight=tomtom+freezes
and in a number of other threads.

todd_jg said:
@louiscar: a good place to start with upgrading info (to avoid the overload) is THIS SITE . Great guides that make it simple.
Click to expand...
Click to collapse
Great link, thanks Todd. Reading glasses are on already.

TT6 w/Pharos and Holux recievers work great
I've an AT&T Tytn upgraded to WM6 and have no troubles with my Holux or Pharos receivers and TT6.
Everything works great EXCEPT issues with data connections such as TT Buddies or traffic. This isn't unique to the PDA version of the software though, as I also have a standalone TomTom GO 910 paired with the phone and it works almost okay as a bluetooth speaker phone, but constantly has trouble getting a good data connection.
My $0.02

louiscar said:
Having just bought a Tytn I found that my tomtom 6 didn't work. I seemed to have two issues. 1) It hung up frequently and 2) It kept losing my external bluetooth GPS receiver.
I thought I'd go to Tomtom's page to see if there was a fix given that HTC mention this saying that Tomtom have updated version 6 for the device.
http://www.europe.htc.com/en/htctytn/support/faq.html?id=539&cat=applications
To my horror I I found this page which suggests that the device is not supported, never has been and never will be. The reason according to Tomtom is due to an agreement with HTC,
http://www.europe.htc.com/en/htctytn/support/faq.html?id=539&cat=applications
I am trying to catch up on this device so am swamped by data at the moment but this is a real blow to me as one of the main priorities is to run Tomtom 6. When I bought the device I assumed that it was just a pocket pc with a phone in it. Seemingly I am wrong as there appears to be differences with the hardware or Tomtom checks the device it's running on and presumably refuses to work properly.
Can anyone enlighten me as to how ( if at all to get around this issue). Currently my device still has mobile 5 but I am ploughing through the plethora of information on this site trying to figure out exactly what I should and shouldn't do. I've a lot of catching up to do..
Any advice / suggestions would be most welcome, it seems too strange a concept to be locked out of running a pc app just because of the hardware it's running on.
EDIT: Apologies moderator this probably shouldn't be posted in the wm6 thread even though I am intending to move over and would like to use tomtom on that. Please move it if necessary.
Click to expand...
Click to collapse
I have used TT6 on my MDA VArio II (TyTn) for almost a year...no problem. Now I have the TyTn II

Same here.. been using Tom tom 6 on my Tytn since the day i installed wm6, no problems here, works like a charm!

HEAT???
I have been using TT6 on my Imate JASJAM running the DOPOD WM6 ROM without much trouble (no hanging etc). The only problem I am experiencing is huge power drain and the unit being physically hot when running TT. Maybe this power drain and potential overheating can cause some units to hang and playup, or potentially any unit given the right environment!
Anyone else finding their units getting a bit hot?

I've been using TT6 on my Tytn (MDA Vario II) almost one year now. No problems. Started using TT6 while running WM5, upgraded to WM6 (schaps rom), reinstalled TT6 and it just continued as before. No problems, no hangups no freezing. I've been using all kinds of different charts with TT6, so I don't think the problem is with TT.

louiscar said:
Hi rbin,
I've currently got the GPS panel set to 'program port = com2', 'hardware port = com0' and my bluetooth gps is set to 'outgoing = com0'
Currently this works well so the GPS issue has been resolved.
Tomtom on the other hand freezes pretty much as described here:
http://forum.xda-developers.com/showthread.php?t=299892&highlight=tomtom+freezes
and in a number of other threads.
Click to expand...
Click to collapse
Going to try your settings too, cause on all WM6 roms I tried I keep losing my GPS BT connection. I'm not damn sure it got nothing to do with TT6. But when I delete my gps and reconnect it while TT6 is up and running, TT will find the gps straight away. So imho it's the BT connection that fails and not TT.
It's really annoying though.
Cheers, M

I have been running TomTom Navigator 6 on my JASJAM for some time. The hanging problem described is probably caused by having all the Points Of Interest (POI) active.
Go into the TomTom settings menu and de-activate ALL the POIs. Try it, then only turn on the ones you actually require.

oltp said:
Going to try your settings too, cause on all WM6 roms I tried I keep losing my GPS BT connection. I'm not damn sure it got nothing to do with TT6. But when I delete my gps and reconnect it while TT6 is up and running, TT will find the gps straight away. So imho it's the BT connection that fails and not TT.
It's really annoying though.
Cheers, M
Click to expand...
Click to collapse
Doesn't work either. Seems that after a soft-reset the BT connection with my GPS is f*d. Very strange because the BT headset doesn't suffer any of this. Maybe time to buy a new GPS, but with WM5 I never experienced this behaviour.

I found that with tt6 you need to have the WM6 internal gps settings set to "None" for both program and hardware port. Then make sure the box is checked in the last tab so it autodetects the com ports. Once all this is set and you goto add a bluetooth gps device in tt6 it gives you the option to use com port 0. select this port and it should detect your gps unit with no probs. Been running tt6 on my 8525 with tnt's latest cooked rom and things couldn't be running smoother.
Edit: On another note. I used to use Telenav with my 8525 with the original at&t rom. I had the worst luck with that application. I would constantly lose my gps connect and I almost always had to do a soft-reset to get it working again. It is quite possible that Telenav was not the issue and that the particular rom I was using had bluetooth connection issues that were resolved when I switched to a cooked rom such as the tnt one. So for those using tt6 with BT connection problems you may want to try a different rom and see how your luck goes.

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.

Bluetooth H/free & GPS Problems after WM6 upgrade

Hi all, First of all I'd like to say this is the most informative forum I have been involved with . Up till now I haven't needed to post any questions.
Now....
I have an i-mate Jasjam herm200 (purchaced from Telstra). Until recently I was running WM5 which it was shipped with. Apart from the slow speed of the PPC (due in part to the Telstra Bloatware) it ran fine.
Since then I have tried many cooked ROMS inc. all Jasjamming's WM black editions, Most of Schaps WM6 and a few others, and I'm having problems with connecting my HS850 headset & my Altina GBT709 GPS receiver.
The Headset,
After pairing the headset I found that when making or receiving a call the person on the other end can only hear me for a few seconds but I don't hear anything, then when the headset Icon appears on the screen the call remains active but I can't hear the other person & they can't hear me.
I reflashed the Telstra Jasjam shipped WM5 rom: 1.31.305.2_106_6275_1.38.30.10_108_ship and the headset stilled didn't work , reflashed it with the same rom again (various WM6 roms in between) and it will work fine.
Can someone tell me if the problem is with the HS850 or the WM6 upgrade?
The GPS,
Since I have started flashing different roms I have never been able to connect the Altina 709 to TomTom Navigator 6, even when reflashed with the shipped rom. I cannot figure out if the problem is with the Bluetoth or a configuration issue with my PPC.
I can live without the GPS as I have a stand alone TT GO 500, but not being able to connect the bluetooth headset properly is driving me NUTS!!!
Please Please Please can someone help me figure this out.
Squirt

Any ideas people?

Don't know if this helps,but I found the Telstra customisations that you can install give me grief with my parrot car bluetooth system - they mess with the bluetooth stack in some way. I found the Telstra WM5 rom didn't play nicely either, which was my main incentive to upgrade to WM6. Are you using a clean install of the WM6 roms without tacking any of the telstra stuff on top?
I eventually found a .cab with just the proxy manager which is all I needed, and schap's roms work nicely for me regarding bluetooth, so I'm a bit wary of fiddling with it now.... I know the black series (and a few others that must have used the same build) had bluetooth issues for me.

Thanks for your reply, I'm currently running Black 3.0.1 which has been the closest I've got to getting the BT H/Free working.
With 3.0.1 I can hear the person on the other end through the phone speaker not the BT, BUT, They can hear me through the BT headset........strange.
I'm just waiting to catch up with a bloke from work with a different brand BT Headset to see if it makes a difference.