Related
After playing around some days (and yes: i read through a lot of threats) i think that this problem (using a bluetooth headset to activate ms voicecommand for dialing and so on) is not only bugging me but a lot of others.
Thats why I want to start ANOTHER, more structured thread about this topic. If something is wrong, please correct me!
WANTED SOLUTION:
Most of you want to use voicecommand activated via a bluetooth device... in your car beside TomTom for example.
PREPARATION: Headset working
I assume that you already got your device working. For myself, I am testing with Supertooth II and a Nokia BH200 hands-free device.
PROBLEM 1: TRIGGERING
First off all, voicecommand needs to be "started" when you press a button on the headset. Usually, the application "windows/sddialer.exe" is launched when bluetooth gets a "voicecommand"-commando.
(Some headsets got their own button, some wants kinda double-click, others want their button hold for some seconds to do so...)
This problem can be solved by changing a key in the registry:
Code:
HKEY_LOCAL_MACHINE/Software/OEM/VoiceCommand/
..Then change the path value to:
\Program Files\Voice Command\voicecmd.exe
(or whereever you installed your voicecommand exe-file!)
Okay. Now the right application is launched when tapping on your bluetooth headset. But here you may encounter the next problem: It works only once.
PROBLEM 2: IT WORKS ONLY ONCE
That problem seems to be caused by voicecommand, because the gateway is left open after useage. (I have no idea if this is correct - i am just citing the opinion of some threads)
There are some attempts to solve this:
Darryl Burlings "Voice Enable": http://www.burling.co.nz/downloads.aspx
Project VCABT http://forum.xda-developers.com/viewtopic.php?t=23558&highlight=vcabt
VCBTFixer0.01.
JETware Hands-free Extension for Windows Mobile phones
http://www.jetwaremobile.com/
I tried them all and for me (german T-Mobile Rom 2.21) only Jetware's Tool worked. A reason MAY be that some of the hacks (vcabt, VoiceEnable,VCBTFixer0.01.zip) only work with an english ROM where all paths are correct: /programs and not /programme)
PROBLEM 3: Correct Audiotransfer
Some users report that it seems like there is still Wizards microphone in use - and NOT the one of the bluetooth device. Others again claim that voicecommands "answer" isnt delivered back to the headset but speaken via Wizards speakers... Since I used Jetwares Tool i didnt had that problem.
PROBLEM 4: Recognition Quality
Lets say you got somehow the correct and everlasting triggering of voicecommand via bluetooth working... then you may find out that recognition ends up with very poor quality.
Here a question for the "pros" in here: Could it be possible that this problem is related to poor bitrates in the audiotransmission via bluetooth? Could we increase recognition quality by tweaking that bitrate? Or will that end up with another problems (bt-bandwidth, cpupower while coding/encoding)?
PROBLEM 5: Interfering with other applications
Thats a future question... When everything works well with voicecommand - then you maybe want to use it in your car to have your hands free. And what else do most of us have there too? TomTom (or another navigation tool)!
So how will that work together with your voicecommand/bluetooth environment? Will TomTom "speak" via your headset too? Will the bluetooth gps mouse keep on working without problems?
And last but not least: Will you still be able to use your phone as a "phone" then?
Please share your ideas about theese problems... and if anyone got everything up and running (Voicecommand & Bluetooth, TomTom / GPS) it would be *very* appreciated if you could post a well written Tutorial / Howto
Regards, Licht
Good luck - for what its worth it works fine with certain BT headsets like the Moto HS850. Just the reg key does it.
Only thing is you have to hit the button on the BT headset 2-3 times sometimes to get it to work but it works perfectly otherwise.
Would LOVE to have a fix that would let me use with all headsets.
How does the jetware stuff work? I heard it screws up some other things?
Cause of "works only once" problem discovered?
I've gone through 4 different headsets with my Wizard and I found at least one commonality to which ones suffered the "works only once" problem:
All of the ones that had this problem were BT 2.0 headsets. The ones that worked fine were all BT 1.x headsets.
I also verified that on my new TyTN (which natively support BT 2.0) the BT 2.0 headsets worked correctly (no "works only once").
Not that this is any consolation to anyone with a BT 2.0 headset and a Wizard, but might help those looking for a new headset.
Changed over to Tytn... works perfectly without any hacks
here's my FWIW answer:
After extensive reading here and at Hofo, I settled on a Plantronics 510. Installed Burlings app and it worked. I hold the button to turn on VC (it will also wake the device from standby if its sleeping, even if its locked) and say my command. It will reply through the headset speaker. After that all audio is oing through my BT headset. (If you have VC telling you who's calling and telling you your appointments thats pretty nice, but if the phone rings you might need some new underwear)
Another long push of the headset button return audio to teh MDA's speakers. If I need to use VC again, I start all over. It sounds more complicated thatn it is in reality.
Recognition is so-so. I don't really use it in my pickup (its hot so my windows are down most of the time), but its pretty good in my car. I have to repeat myself maybe 10% of the time, at most.
Not sure how well written that was, sorry. if anyone has any questions I'd be glad to answer them. I've been pretty pleased with the combo. Especially since I got the 510 for $40 from amazon.
I searched and didn't find any previous postings regarding an issue with Parrot and Audi Hands Free (Bluetooth) car kits and the TyTn.
This issue is only with the TyTn and the Wizard devices work fine.
It seems to pair fine with the car kits but 5 minutes into usage...the TyTn turns the bluetooth off on the device.
Then about 1 min later, turns Bluetooth on again. The cycle then begins Off and then On ....
Here's a link on the Parrot forum.
http://www.parrot.biz/forums/english/viewtopic.php?id=2667
I've got the same problem with my Seat Leon (new model) bluetooth carkit !!!
I think it's the same module as in the Audi (all VAG related cars).
It's very irritating !
I hope they will fix it soon....
http://forum.xda-developers.com/viewtopic.php?t=58789&highlight=
:wink:
Er... not followed as far as parrot (down for maintennance) BUT
I've found with my Seat Leon kit that the phone needs to remain in a fully powered state - you can't put it into the sleepy state by the power button otherwise you get the intermittent but eventually endless dingling of it connecting and disconnecting.
Best way I've found is to leave it on asking for a password with the cover on.
edit: Should just point out that you also need to turn off any power off settings - except for the backlight.
Pyranwolf said:
Er... not followed as far as parrot (down for maintennance) BUT
I've found with my Seat Leon kit that the phone needs to remain in a fully powered state - you can't put it into the sleepy state by the power button otherwise you get the intermittent but eventually endless dingling of it connecting and disconnecting.
Best way I've found is to leave it on asking for a password with the cover on.
edit: Should just point out that you also need to turn off any power off settings - except for the backlight.
Click to expand...
Click to collapse
I'm going to try this !
I hope that it works.
Thanks anyway.
What kind of Leon do you have ?
I've got an A6 with BT kit and am having this problem. I cannot make/receive a call whilst running my BT GPS device & TomTom, although from reading this the issue may be the Audi kit anyhow.
Are there any fixes available - be it HTC or Audi? Or are there any work-arounds, such as add-on software for the TyTN??
Please help - it is driving me mad. Spoiling what is otherwise a great piece of kit.
I have been having this exact problem with my Audi A4 with Audi Bluetooth.
I did wonder if it was in some way connected with the phone going into sleepy mode as it is being powered by the phone battery.
Also, the bluetooth stops responding after 5-10 minutes, but if I am continously using the phone, it seems to be ok.
Therefore, I think I need to buy an in car charger, and see what happens...
Has anybody else tried this that can confirm it works?
Markee
Just a quick note to Paul_o
My Audi A4 / SPV M3100 / Tom Tom / Bluetooth GPS work fine together.
If I am in Tom Tom, and get an incoming call, the little call window pops up over Tom Tom, Tom Tom carries on and the phone audio is routed through the speakers - the only irritating thing is that the Tom Tom lady keeps interrupting... :wink:
Mark
Hi,
I'm using Vario 2 with Audi Bluetooth and also having the BT ON - BT OFF issues.
These are my findings.
- Without JETWARE software:
- BT goes ON and OFF in the car regardless of the VARIO 2 being on or stand-by, or the phone being battery powered or connected to the car.
- Once a conversation is started the BT connection seems to be remain ON.
- With JETWARE software
- If I leave the screen always on the BT connection stays always ON. Only backlight automatic switch-off is selected
- I have tried several screen toggle programs (which claim that they only power down the screen) but the BT goes OFF in the car after a few minutes.
I'm happy to test any other proposal.
Cheers,
C
What version of JetWare are you running, they have a beta which has settings for the Audi kit, this may help, there is also a registry setting that is meant to change the power settings when bt is connected. An extract from an email conversation with Jetware...
We have also addressed the power issue, but this fix requires a registry change. Please create a DWORD registry value in HKLM\Software\JETware\AGExt named InSessionPower with a value of 0 (valid values are 0-4, with lower values indicating greater power availability). This will tell the OS that the Bluetooth device should stay at full power while it is in a Hands-free session.
Not sure if this will help, my Hermes is ariving on Monday, I'm was hoping that all the problems i've had with my magicain and the audi kit would go away with the Hermes, but maybe not.
Give the key a go and let me know
Hi dh,
thanks for your reply.
I haven't installed the Beta version yet. However I have changed the registry setting and will test first thing tomorrow. If this doesn't fix the problem I will try the Beta version with the Audi setting.
I'll keep you posted.
Cheers,
Carles
Hi dh,
I have tested the two proposals (Change in the registry and the Beta version + Audi settings) without much luck. The BT connection with the car keeps going ON and OFF when the phone is running on battery.
Have you got your Hermes? any luck?
Thanks,
Carles
Got my Hermes (Orange M3100) a couple of days ago. I've installed the JetWare extention, and without the InSessionPower set the connection is dropped. So far with the setting applied it has stayed connected. I have had other problems like not being able to make calls etc, which is a bit of a issue. I need to do some more testing, as i've been messing with the phone a bit.
I'll update here in a couple of days
Must say i'm very disapointed with the phone regarding this. A couple of weeks ago i had a Wizard which worked flawlessly with the JetWare extention, no power issues, calls made and received without a single problem. I wonder what has changed with the bt implementation between the Wizard and the Hermes?
Hi dh,
You will see from my previous postings I have had the same problems too.
It should be noted, though, that the Vario (wizard) worked flawlessly with the Audi A4 Bluetooth without Jetware software.
Has anybody been able to prove there is no problems if the phone (SPVM3100) is powered whilst in the car?
Cheers
Mark
I have a factory fitted hands free system in my Vauxhall. Every other phone you can think of works with it...EXCEPT my XDA mini. It seems to pair up, but there is no signal showing from the carkit. It might work for a minute and then it drops out. Is it the XDA or Vauxhall that's at fault? It seems that nobody knows the answer and I paid serious money for this bit of car kit. I like the phone, it really is annoying. I have tried another XDA mini as well and that doesn't work either. Does anybody else have a Vauxhall with the same built-in system and not connecting?
Markee
I've had the phone plugged in without the registry entry and it seemed to be ok. If I can get to a stage of a working solution i'll test again without the registry entry and with external power.
dh said:
Must say i'm very disapointed with the phone regarding this. A couple of weeks ago i had a Wizard which worked flawlessly with the JetWare extention, no power issues, calls made and received without a single problem. I wonder what has changed with the bt implementation between the Wizard and the Hermes?
Click to expand...
Click to collapse
I'm guessing that since they went from BT1.1 to BT2.0 they had to make a new stack.
My Wizard worked PERFECTLY on my Parrot, my TyTN is almost useless on it.
you make a very good point ScottC, that'll be what it is.
Just driven home and could not make a single call with Jetware installed. Removed it and i could at least make a call, but i didn't get any status info or phone book. I didn't get a chance to leave it connected without Jetware for longer enough to see if it disconnected without external power, i imagine it will. I will test some more later/tomorrow. I'll also send an email to Jetware to see what there thoughts are regarding bt v2.0 and their product
Hello,
I have an Audi A3 with the factory fitted Phone kit but without the Audi Craddle so I'm using the Bluetooth connection.
I have tried the Vario (Wizard/QTEK 9100) and Vario 2 (Hermes/TyTN) and had similar problems with the two of them. Once the connection is stablished I can make and receive calls without problems. The issue is that the BT connection goes ON and OFF without an apparent reason.
The only thing I have seen is that when the Vario is kept on (only the backlight is off) the BT connection normally stays ON, regardless of the phone being powered or not.
I have tried Jetware, the Beta version, the registry entry, programs to switch off the screen...but haven't seen any real difference.
I have bought a bluetooth USB stick and will do some test at home to see if the problem is with the car or the phone.
I called T-mobile and they said it was a faulty phone, but I don't think so.
Keep the postings, we might end up finding a solution
Cheers
C
Try upgrade the BT software. I had the same problem after that i upgraded de Parrot software. Now i have the version 4.16
Hi all,
I've got a Pioneer P55BT headunit in my car, and it has support for bluetooth to use it as a handsfree, however I cannot connect my Vario II to it, as it doesnt detect it as a phone, so doesnt come up when trying to pair it.
Has anyone managed it? or have any advice?
Cheers
have you tried pioneers tech support on this one? I know its not directly helpful, but if they are not currently aware of a problem they cannot patch the firmware
timbouk said:
have you tried pioneers tech support on this one? I know its not directly helpful, but if they are not currently aware of a problem they cannot patch the firmware
Click to expand...
Click to collapse
Havent no, not yet, always try the forum first.
Solution
Hi,
I've got exacly the same problem with a Vario II and a Pioneer DEH-P75BT. After a lot of email's and phonecalls with pioneer in the Netherlands, they came everytime back with the answer "Your phone is not on the supported models list". Yea i knew that already.
Before my Vario II is always used a SDA without problems. I discovered that when i select hands free from the vario itself, it pairs without problems. The radio just have some problems with discovering the Vario II.
The problem:
The vario II identifies itself as a PDA bluetooth device. The pioneer modules are searching for a phone or smartphone, so it just ignores the Vario II.
Solutions:
Change the COD (Class of Device) from a PDA device to a smartphone device.
This can be done this way:
1. First make sure you've got a backup, or remember all settings you change in the registry.
2. Edit with a registry editor the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\SYS\COD
By default my vario II does have the value: 1048852 (decimal)
Change this to: 5374476 (decimal).
3. Soft restart your device
4. Voila! Your device now identifies itself as a smartphone, and my pioneer unit finds it without problems.
flue said:
Hi,
I've got exacly the same problem with a Vario II and a Pioneer DEH-P75BT. After a lot of email's and phonecalls with pioneer in the Netherlands, they came everytime back with the answer "Your phone is not on the supported models list". Yea i knew that already.
Before my Vario II is always used a SDA without problems. I discovered that when i select hands free from the vario itself, it pairs without problems. The radio just have some problems with discovering the Vario II.
The problem:
The vario II identifies itself as a PDA bluetooth device. The pioneer modules are searching for a phone or smartphone, so it just ignores the Vario II.
Solutions:
Change the COD (Class of Device) from a PDA device to a smartphone device.
This can be done this way:
1. First make sure you've got a backup, or remember all settings you change in the registry.
2. Edit with a registry editor the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\SYS\COD
By default my vario II does have the value: 1048852 (decimal)
Change this to: 5374476 (decimal).
3. Soft restart your device
4. Voila! Your device now identifies itself as a smartphone, and my pioneer unit finds it without problems.
Click to expand...
Click to collapse
You're a legend... did as you said and all worked perfectly!! well after I remembered what the code was to pair it, lol 1111.
Cheers tho, appeciate it.
Luke
that's got to be worth adding to the wiki!
how's it done?
I would def say so, sure it's a problem on a number of devices (i.e. stereos)
It's also a solution for other devices using a Microsoft BT stack.
Maybe it's worth to make it a general wiki update?
flue said:
It's also a solution for other devices using a Microsoft BT stack.
Maybe it's worth to make it a general wiki update?
Click to expand...
Click to collapse
gets my vote
Vario II working with 55BT
After several tries with 55BT, I have finally managed to connect it.
The way to do that was only by using radio and not PDA. Wherever I tried to pair the devices from PDA, I was getting PIN code screen over and over.
However, after running detection as advised in the manual from the radio side, all was running fine. What might have helped was the pairing with other phone (Motorola RAZR3 to be precise) and pairing on position 2. Magic but was my case Generally, the worst thing with 55BT was the duality if I may say so of the buttons and knobs changing its funcion is different steps of the pairing - simple mistake and you need to start over.
Given the problems, I have tried Sony BT5000 and it worked like a charm, but I was afraid of the sound quality, given the mic is builin in the radio.
Finally I have decided to go Blaupunkt route, but can confirm, when paired, 55BT was working fine, althoug some echo was present during call.
mKotek said:
After several tries with 55BT, I have finally managed to connect it.
The way to do that was only by using radio and not PDA. Wherever I tried to pair the devices from PDA, I was getting PIN code screen over and over.
However, after running detection as advised in the manual from the radio side, all was running fine. What might have helped was the pairing with other phone (Motorola RAZR3 to be precise) and pairing on position 2. Magic but was my case Generally, the worst thing with 55BT was the duality if I may say so of the buttons and knobs changing its funcion is different steps of the pairing - simple mistake and you need to start over.
Given the problems, I have tried Sony BT5000 and it worked like a charm, but I was afraid of the sound quality, given the mic is builin in the radio.
Finally I have decided to go Blaupunkt route, but can confirm, when paired, 55BT was working fine, althoug some echo was present during call.
Click to expand...
Click to collapse
The problem described above is that the radio doesn't detect the PDA. As i understand from your post, is that your radio does find the PDA by default, right? Or have you paired the pda once, and registered on the radio? This shoud work by default.
flue said:
Hi,
I've got exacly the same problem with a Vario II and a Pioneer DEH-P75BT. After a lot of email's and phonecalls with pioneer in the Netherlands, they came everytime back with the answer "Your phone is not on the supported models list". Yea i knew that already.
Before my Vario II is always used a SDA without problems. I discovered that when i select hands free from the vario itself, it pairs without problems. The radio just have some problems with discovering the Vario II.
The problem:
The vario II identifies itself as a PDA bluetooth device. The pioneer modules are searching for a phone or smartphone, so it just ignores the Vario II.
Solutions:
Change the COD (Class of Device) from a PDA device to a smartphone device.
This can be done this way:
1. First make sure you've got a backup, or remember all settings you change in the registry.
2. Edit with a registry editor the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\SYS\COD
By default my vario II does have the value: 1048852 (decimal)
Change this to: 5374476 (decimal).
3. Soft restart your device
4. Voila! Your device now identifies itself as a smartphone, and my pioneer unit finds it without problems.
Click to expand...
Click to collapse
flue,
I have the HTC Prophet pda and the pioneer DEH P75BT and have just changed the value in the registry as you suggested (haven't had chance to test it yet though) but I trust it will work.
Have you used the BT Audio function on the stereo to stream music from your pda to the stereo yet?
My experience is that it's a painful process to pair but the quality of music once paired is second to none. I eventually gave up with it though because of the dreadful pairing process.
Could this be to do with the COD? I mean is there a seperate COD code for a wireless stereo?
neomagik said:
flue,
I have the HTC Prophet pda and the pioneer DEH P75BT and have just changed the value in the registry as you suggested (haven't had chance to test it yet though) but I trust it will work.
Have you used the BT Audio function on the stereo to stream music from your pda to the stereo yet?
My experience is that it's a painful process to pair but the quality of music once paired is second to none. I eventually gave up with it though because of the dreadful pairing process.
Could this be to do with the COD? I mean is there a seperate COD code for a wireless stereo?
Click to expand...
Click to collapse
Hi,
I don't really know if the prophet has a different stack of modified stack for a2dp because i don't use that phone.
I've got the universal and tytn phone here. I never figured out how to get the universal working without stuttering. My conclusion was it's a lack of processor power.
The vario II does work better with a2dp, especially after a soft-reset.
I never got pairing problems with both of them for a2dp. The radio connects fine and directly after choosing "set as wireless stereo" on the phone.
This does have nothing to do with the COD. Even with the COD set to the default value (pda), and you set your radio as headset/wireless-stereo from the phone, is should work without problems. Even registering on the pioneer should be possible then.
The only thing it doesn't with the default COD is automaticly connecting to the bluetooth headset when powering on the pioneer device.
I seems that the pioneeer deh-b75bt does not have the funcionality to auto-connect a2dp, such as the headset does. Too bad
Thanks for the info flue.
I've now had chance to see if the phone will auto connect with the new COD and can confirm that it does. So well done that man!!!!
I can also confirm that both times I tried "set as wireless stereo" it paired with no problems and I was able to listen to mp3's on my phone through my car speakers in almost perfect quality!
BTW I installed the Tornado A2DP hack in order to get A2DP working as the Prophet isn't capable of it without it.
this procedure don't function with my TyTn on mercedes Benz Bluetooth kit.
It recognized the phone with a 16 numbers code but don't pairing. Someone have the same problem ?
Hi guis!I've got an HTC MTeor smartphone and pioneer bluetooth car stereo.Excuse me for the stupid question, but I couldn't understand how to change my phone COD from PDA to smartphone.Where do I have to type this code?Or what settings I have to change? Thank you in advance
I have a DEH-75BT as well. Have anyone found out how to get adress book transferred to the radio?
/Kasper
StoianZh,
The MTeor is a smartphone and its COD will by default already be set to smartphone. No changes are required.
Kasper_m
Use outlook on your PC
First do a Select All on your contacts* You may have more than 1000 contacts and if so may wish to break this up into one or two attempts to provent overloading the PC.*
Then choose Action->Forward as VCard
On the mail that appears choose File-> Save Atachments.
Save the VCFs to a folder and move them to your phone.
In the car use SmartExplorerEN or Resco Explorer and Select All the VCFs. Choose Send Files Via Bluetooth and the Headunit will appear in the list. Send them all to the HU
flue said:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\SYS\COD
By default my vario II does have the value: 1048852 (decimal)
Change this to: 5374476 (decimal).
3. Soft restart your device
4. Voila! Your device now identifies itself as a smartphone, and my pioneer unit finds it without problems.
Click to expand...
Click to collapse
Hi,
I have a HTC TyTN and a Pioneer DEH-P4900IB
I have the same problem as described. If I pair the phone with the Pioneer it will work fine, but as soon as either the car-stereo or the phone's bluetooth has been switched off, it will not automatically connect.
I can either re-pair it, or alternatively choose the Pioneer radio in the list of paired devices on my TyTN, click update, re-choose "Handsfree" and click save.
I have now tried your solution, and unfortunately it hasn't solved the problem.
I still have exactly the same problem. When I turn on my car, the radio will search for bluetooth devices but ends up displaying "NO TEL".
Can anyone help with a solution to this problem?
Thank you in advance.
/Erik
Hi, I have a Pioneer P75BT. I've used the COD hack, which works very well. Thanks to the original poster.
I've found that I have to leave the Vario II in discoverable mode in order for the P75BT to connect to it automatically, even though the P75BT has the Vario II registered. I can also connect it manually.
I don't like the idea of leaving my Vario in discoverable mode all the time, but it looks like thats the only way to automatically connect each time, unless someone has found another solution. Perhaps its not so much of a problem as I tend to turn off bluetooth on the Vario II when i'm not using it.
Has anyone had any problems pairing their X1 with any Nissan or Inifniti cars? There seem to be some mumblings on the web about their cars and WM6 devices and I've had no luck getting it to work on my '08 G35. Thanks.
bluetooth pairing
i just checked the aproved phone list for your g35 and the x1 is not aproved by infiniti. only certain phones will link to our cars others will not
I have an 08 G35 and have no prob. pairing it with my car. How are you pairing this up with the car?
it also depend if you both have navagation or not
elee888 said:
I have an 08 G35 and have no prob. pairing it with my car. How are you pairing this up with the car?
Click to expand...
Click to collapse
I don't have the navigation so I just click the phone button, tell it I want to pair a new device, and have my X1 start searching. At least now I know it can be done. Thanks for the reply
Well... I do have the navigation. So maybe the pairing process is a little different. But it should work though, it even allows me to download the whole phonebook into the car. Something my other phones in the past did not allow me.
baashha said:
Managed to solve this now.
Of course both Merc & SE didn't have any good solutions.... so had to continue googling & XDA-ing... This is what I did:
i.) Jetware, as I posted earlier has been removed.
ii.) I still had the SAP Profile addition downloaded from one of the forums in XDA on.
iii.) Change Registry setting:
HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\Sys\COD
the default is 5898764 (Decimal) which is "Telephone (Smartphone)" which you would think would work. Changed to 5374476 (Decimal) which is a normal phone.
iv.) Restarted the phone.
v.) Started the pairing process from the car - failed as per before.
vi.) Started the pairing from the phone, and they work!!
Now, they pair automatically as how they would before....
Ram
Click to expand...
Click to collapse
this is how i got mine working with my pioneer deck.
here's the link to the SAP Profile he was talking about.
http://forum.xda-developers.com/showpost.php?p=997872&postcount=166
hope this works for you.
which PIoneer do you have?
I have the DEH-P5900IB and a BT adapter, and i can't get my X1 connect.
All my previous phones worked fine.
it looks like the X1 won't let me pair without passcode, and the radio says Error.
Do you mind explaining exactly how you did it?
Thanks
i have the DEH-790BT.
what i did was after i changed what i mentioned above, then i set my deck to be able to be noticed by other bluetooth devices, then added it through my X1. After I added it through my phone it said successfully connected on my deck and the phone displayed it connected as wireless stereo and hands free. now the only weird thing was it was trying to connect as both the wireless stereo and hands free which seemed to mess with the deck, so I had to turn off my ignition and turn my car back on for it to actually recognize the connection fully. oh and the passcode if you connect through the deck to phone like I did it should be default '0000' but i would check your manual just to be safe, and if your connecting through your phone to the deck (which i haven't tested so I don't know if it works) you can pick your own passcode, which i suggest just making 0000 or nothing.
I have a problem also with my HTC Touch HD (Blackstone)
I can pair with my Nissan Qashqai carkit but soun dis very bad, and the caller on the otherside doesn;t hear anything.
Strangly, but try, when during a call i switch from carkit to phone and back (using the options in my carkit/buttons on stearing wheel) everything is fine!
Checking the internet learned me that this is related to the bluetooth stack (or settings) in WM6.1 (and 6.5 also)
So does anybody have any idea how to solve this, maybe by registry changes or maybe by even "downgrading" the Bluetoorh stack to 6.0 or maybe even 5.x.
Maybe it is also possible to replace the complete MS stack for an other stack?
There are a lot of problems with carkit connections & the HD2.
I tried several things to get it working without success.
When I try to connect to the JVC KD-AVX44 it connects but give no sound at all. (making 2 connections, handsfree & stereo audio)
Then I tried the registry tweak mentioned into this forum and had success once. I was very happy because also the title track was shown onto the JVC display and also the phone was functioning ok both ways.
The sound trough AD2P was perfect. Only one time.
After that i get a lot of disconnects.
Then I tried to make only connection with the phone function and this is working ok now. When I want to make the connection trough AD2P then the problem is back. Also when you make it without making the phone connection
So I think the problem lies into the stereo connection. For instance when you skip a track onto the JVC then the connection will be lost and reconect again and giving 2 seconds of sound and then it's quiet again.
Also when to 2 connections exists the phone is blocked by incomming calls because it's thinking it's connected so the earpiece & mic are dead at that time. And also the radio.
Did you try the LineSpeed setting to 256 in the AV key of the Widcomm registry settings ?
Don't know if it could help in your case but it did for me, I don't have disconnects with my Sony headphones anymore and sound is better.
Bluetooth
Ok thx I will give it a try and post the results.
which registry tweak did you applied first, cause i too keep having issues...?
tweak
Change Registry setting:
HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\Sys
Add the DWORD setting COD=5374476
This makes devices see the HD2 as a 'Normal' phone
Do I have to add this line somewhere? I found the AV key into widcomm but the line was not there
valos said:
After that i get a lot of disconnects.
Click to expand...
Click to collapse
Try turning WiFi off on the phone, it makes a big difference on my IO Play system.
valos said:
Change Registry setting:
HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\Sys
Add the DWORD setting COD=5374476
This makes devices see the HD2 as a 'Normal' phone
Click to expand...
Click to collapse
Ok i make this in my BMW X5 and one of problems is solved - HD2 working correct when i am on call and power the car, but i have another problem - after 5 - 6 min on call Bluetooth connections is droped and i can't lisen nothing from Car or for Phone - i must to press Menu and switch off Hands free to continue conversation.
Ok but are you also making stereo connection. I only have the handsfree conected at this time and then the connection is stable. Only with the A2DP it goes wrong.
valos said:
Do I have to add this line somewhere? I found the AV key into widcomm but the line was not there
Click to expand...
Click to collapse
Yes, you have to add the key, sorry not have said that.
kmeta said:
Ok i make this in my BMW X5 and one of problems is solved - HD2 working correct when i am on call and power the car, but i have another problem - after 5 - 6 min on call Bluetooth connections is droped and i can't lisen nothing from Car or for Phone - i must to press Menu and switch off Hands free to continue conversation.
Click to expand...
Click to collapse
Strange, so far I didn't experience any disconnection.
I have conversations during more than 20 minutes daily and line quality is far better than with my Diamond, with no drops.
With the Diamond I had the BT stopping regularily on the phone, it was very annoying because I always discovered it when receiving a call and not being able to answer.
So far it didn't happen on the HD2, but it is really too soon to jump to any conclusion.
I don't use A2DP in the car as I didn't order the option, which I viewed as useless because the hard disk capacity of the iDrive is sufficient to hold a good collection, the audio quality and functionality is much better and I can still connect the phone to the USB plug as mass storage if I want to play or transfer something from it or any memory stick or external HD.
So maybe not having the A2DP profile active may help also.
I also not any problem with my old HTD HD and Cruize ... but with HD2 i have this issue.
Today i receive answer of my ticket from HTC: they offer me to contact with BMW and to ask them why they not support HD2 ... I think this is stupid becouse every new device must support old protocols and older devices.
Now the choice is to change Car or Phone ... sorry but HD2 not have any chance to survive.
kmeta said:
I also not any problem with my old HTD HD and Cruize ... but with HD2 i have this issue.
Today i receive answer of my ticket from HTC: they offer me to contact with BMW and to ask them why they not support HD2 ... I think this is stupid becouse every new device must support old protocols and older devices.
Now the choice is to change Car or Phone ... sorry but HD2 not have any chance to survive.
Click to expand...
Click to collapse
Yes how lousy is that
Got the same answer first, but they realised that BMW coudn't recall thousands of vehicles to do a BT upgrade just because HTC decided to adopt the crapy Widcomm BT stack.
So they say they are working on a fix, but given how many issues there are with this stack, they better switch back to the old MS stack instead.
To be clear, it is the Widcomm stack at fault here, not BMW. Every single phone not equipped with this stack, I could try on the BMW, worked flawlesly.
I hope they will recognise this officialy and not blame the others each time a customer opens a ticket about these flaws.
In the meantime, the registry hack works perfectly for handsfree profile, but it seems it doesn't fix everything when the A2DP profile is activated.
MacGyver4321 said:
Yes how lousy is that
Got the same answer first, but they realised that BMW coudn't recall thousands of vehicles to do a BT upgrade just because HTC decided to adopt the crapy Widcomm BT stack.
So they say they are working on a fix, but given how many issues there are with this stack, they better switch back to the old MS stack instead.
To be clear, it is the Widcomm stack at fault here, not BMW. Every single phone not equipped with this stack, I could try on the BMW, worked flawlesly.
I hope they will recognise this officialy and not blame the others each time a customer opens a ticket about these flaws.
In the meantime, the registry hack works perfectly for handsfree profile, but it seems it doesn't fix everything when the A2DP profile is activated.
Click to expand...
Click to collapse
After much playing around - I found a linespeed of 300 works best for the HD2. 256 still has questionable quality and 320 for some reason skips a lot. Reducing it to 300 seems to be a workable equilibrium!