Related
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?
Hello
I have a Seat Leon with preinstalled bluetooth in-car.
I used to have dutty v1 installed on my hermes and everything was great!
When I installed Black 2.5 then I was able to pair the phone with the car but after a minute the connection is dropped.
same problem happens with dutty v2 and the newest lvsw
you know what is wrong with the new version? newest bluetooth?
any ideas?
i was going to start o similar topic... but i've seen yours... the reason... happy with wm6 and the car kit
so.. i have o parrot 3400LS-GPS car kit... and when i conected the phone to it for the first time it showed the signal strength and battery state... with wm5 i had nothing.... and the coolest thing is that i have also carrier's name... at first it was eandomly shown... but i think i figured it out... if it is on 3g it does not display the carrier's name... but on gsm it does... BUT if i disable the longnameprefix in regedit it also shows the carrier on 3g.. but on this i still got to test....
anyway no BT drops...
spv m3100
radio 1.41.
hardspl 2.10 oli
dutty v2 premium
Same on Audi A6, Black 2.5 (and latest LVSW) drop BT connection. Sucks.
i guess microsoft broke some compatability with this os build in a few weeks there might be a new os build....heh
Same issue here
working with an older version of LSVW (can't recall which one) and a 2006 Audi S4 -- pairs fine, shows signal strenght and other details not shown with WM 5.0, but drops and reconnects randomly. Very irritating. I don't use bluetooth anymore in my car -- a tremendous shame.
dutty said:
i guess microsoft broke some compatability with this os build in a few weeks there might be a new os build....heh
Click to expand...
Click to collapse
dutty do u think that if I downgrade to v1 of your rom the problem will be fixed?
MegaHz said:
Hello
I have a Seat Leon with preinstalled bluetooth in-car.
I used to have dutty v1 installed on my hermes and everything was great!
When I installed Black 2.5 then I was able to pair the phone with the car but after a minute the connection is dropped.
same problem happens with dutty v2 and the newest lvsw
you know what is wrong with the new version? newest bluetooth?
Click to expand...
Click to collapse
Hi, I don't know if this will solve your problem but here goes anyway. When I first got my phone (Orange SPV M3100), I could not connect to installed BT system in my Audi A4. I understand from what I have read that this is due to a slight difference in BT specification used by WM to that used by mobile phone manufactures. I had similar problems as you describe above - all fixed since I installed software from JetWare (use google to find). Hope this helps.
hdd123
hdd123 said:
Hi, I don't know if this will solve your problem but here goes anyway. When I first got my phone (Orange SPV M3100), I could not connect to installed BT system in my Audi A4. I understand from what I have read that this is due to a slight difference in BT specification used by WM to that used by mobile phone manufactures. I had similar problems as you describe above - all fixed since I installed software from JetWare (use google to find). Hope this helps.
hdd123
Click to expand...
Click to collapse
hrmm, I'll try that too but my question is that my phone used to work just fine, now with the latest rom the problems with bluetooth started, that's what I am pointing out.
Hi all.
I've a Seat Leon too, with bt integrated.
Since i upgraded to first WM6, i have no problems with hands free, but i must get the PDA on. If i put PDA off, BT starts to disconnects and reconnects, and finally BT goes off.
With all WM5 i've tested, the BT disconnects and reconnects every time with the PDA on.
Think there is an issue with the way the handsfree get info from the phone, cause normal phone works without this issue.
Regards.
Im also using Pro 2.5 and have noticed that my BT for my Handsfree car kit is playing up. I can connect and it works but when I leave the car and come back I need to shut down and then restart Bluetooth to reconnect. Bit of a pain atm.
try the widcomm stack
http://forum.xda-developers.com/showpost.php?p=1234724&postcount=507
Also having problems, Parrot Rhythm 'n Blue, it droppes during calls and reconnects after a minute (not always).
I already use Jetware, so I fear that doesn't do the trick. According to the reactions in this thread this really seems to be a problem...
jasjamming said:
try the widcomm stack
http://forum.xda-developers.com/showpost.php?p=1234724&postcount=507
Click to expand...
Click to collapse
Ok thanx, I'll try that and report back...
It's the BT implementation in the phone (either HTC or Microsoft), other phones work fine. Anyho: for me the previous LVSW (03-26) works fine and since I don't need the other 'stuff', I'm using that release.
My $0.02
nukenine said:
It's the BT implementation in the phone (either HTC or Microsoft), other phones work fine. Anyho: for me the previous LVSW (03-26) works fine and since I don't need the other 'stuff', I'm using that release.
My $0.02
Click to expand...
Click to collapse
if dutty is not able to release the v2 with the old bluetooth stack I will downgrade to that version too...
I will also try the jetware tonight and let u know.
thanks
MegaHz said:
if dutty is not able to release the v2 with the old bluetooth stack I will downgrade to that version too...
I will also try the jetware tonight and let u know.
thanks
Click to expand...
Click to collapse
as said: I use the jetware software already and got the same problems... not always, but frequently.
I'm currently using Black 2.5 w/an '07 Infiniti FX and have zero dropout issues. I love it actually, I got in my car this morning and it reconnected automatically when I got a phone call, no problem
MegaHz said:
if dutty is not able to release the v2 with the old bluetooth stack I will downgrade to that version too...
I will also try the jetware tonight and let u know.
Click to expand...
Click to collapse
guys, finally the jetware did the job, the bluetooth stopped on keep disconnecting, let's hope that MS will fix the problem on the next release.
Hi all, another SEAT Leon driver with bluetooth handsfree problems here
My Vodafone v1605 suffered the dropout problem when it was on the stock Vodafone ROM.
I used the WM Black 2.0 ROM for about a day before the 2.5 ROM came out and didn't suffer the problem.
Since going to Black 2.5 I have suffered the problem intermittently. When the phone is running on battery it frequently disconnects/reconnects. However it appears to be pretty stable when on charge in the Brodit powered mount. I would guess that the major difference is that when on charge the phone doesn't go into standby mode.
I am tempted to go back to 2.0 and test for a while longer, especially as my device code has been updated with 2.5 so TomTom is not currently activated
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.
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.
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