Auto joining bluetooth handsfree - 8525, TyTN, MDA Vario II, JasJam General

hey all
I cant seem to find a lot of info about this topic, so hoping you guys can help me out somehow.
is there any way of getting WM to join to handsfree bluetooth profile when i'm in my car (using pioneer headunit)?
reason being is pioneer head units require you to be connected to the phone in order to use the head unit to make calls, phonebook, etc
with my nokia back in the day, provided bluetooth was on, i would sit in my car and turn my ignition on. about 10-15 seconds later, the headunit joins with the phone. the phone says its connected to 'Pioneer BT unit' and the headunit shows the battery and signal level, and shows the correct phonebook.
with my jasjam (running blacksatin wm6 - although had the same problem on wm5), the pioneer unit doesn't join automatically... it is only after i receive or make a call using the phone, that it quickly joins to the headunit. even then, the person could have started talking before the audio fully comes through...
however this is not a problem there on, as once the bluetooth connection has been made, it remains, and everything works as it should.
so is there any registry hacks or programs i can run that will allow the headunit to make the connection to the handsfree profile once ignition is on in the car?
Cheers,
Bill

hi bcx7,
I had his problem too. It may depend on what head unit you are using, but perhaps the solution is the same.
my pioneer head unit is a DEH-P75BT. It looks for a smartphone, but doesn't recognize the hermes as it's classed as a pda phone.
Solution:
Change the COD (Class of Device) from a PDA device to a smartphone device.
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 T-Mobile Vario II has the value: 1048852 (decimal) for WM5 & 5374228 (decimal) for WM6. Change this to: 5374476 (decimal).
3. Soft restart your device
4. Your device should dentify itself as a smartphone, and my pioneer unit finds it without problems. Note that for my Vario II, I also have to discovery mode always on, so I also protect it with a PIN code.
On the head unit, scan for the devices, save it in one of the P1, P2 positions etc. Then when you switch on your ignition, the head unit should recognize it.
One final tip. My head unit doesn't see the Vario II unless the screen is on (device not in standby). If the screen is off (device in standby), and even though bluetooth is on and in discovery mode, the head unit won't see it. Once connected I put the device in standby and it stays connected just fine.
I found this information a while back on this forum, so credit to the original poster - sorry don't know who it was.
Hope thats helps.
Mike

Related

Bluetooth bug with Car Kits. Turns off and on and off and .

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

Tytn / Vario II and Pioneer P55BT

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.

Bluetooth pairing diagnostics?

Hi all,
I am unable to pair my XV6800 to my Pioneer DEH-P980BT car stereo. The phone detects the stereo and requests the PIN, but fails after I enter the PIN with a 'Cannot Connect, connection failed or pin is wrong' error. I have used this stereo with my xv6600 Blue Angel for over a year (Can you say Widcomm stack?).
Anyway, I have been unable to come up with fruitful answers or even a next good step by searching the forums or general internet searching. I am wondering if there is some kind of Bluetooth tool that would allow me to determine what actual error is occurring?
Any help would be greatly appreciated.
I had the exact same problem with the same head unit. Here's what I did to correct it:
Code:
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.
That SHOULD work for you. Please let me know if does, because when I do it, the stereo finds the handset fine, but I can't hear any conversation coming out the speakers. It's like it is on permanent mute. This also happens with my BT headset - all controls work, but I can't hear anything nor can people hear me. Plus, my Mogul's speaker cracks and pops when I try using it with another BT device. I think it may be a bad unit. I want to know if you have better luck with the Mogul and 980BT.
I am using the newest ROM (2.17) and radio. The same thing happens to me with the older 2.09 ROM also.
sup191
Eureka!
It worked! I had tried this COD change before and had tried initiating pairing from the stereo, but had not tried both at the same time. I am able to connect the phone and bluetooth stereo simultaneously, and both are working with excellent sound quality. That's leap and bounds from where I was yesterday. Thank you very much!
Regarding your problems, I am not experiencing them at all. I can hear both sides of a conversation as can the other side. As it stands I think I will have to manually pair every time I get in the car (a pain, but I will work on it).
I am not sure what differences exists between the Hermes and Titan, but I would be happy to investigate for you wherever I can. My ROM is version 2.09 and my radio is version 1.30.
Thanks again. Feel free to post or PM me if I can help you figure your issues out.
Thanks for the offer to help. I think my first step is going to Sprint and showing them that BT is crap on my Mogul and see if they'll swap it for me. I'm also going to try pairing my headset there on the demo and see if it works. If it does, my unit it broken. I'll let ya know what happens.
sup191

Bluetooth pairing problems on Infiniti/Nissan

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?

Bluetooth Car Connection

I have a problem where my HD2 does not work properly with my Land Rover Freelander 2 in-built bluetooth car kit.
The HD2 pairs with the car and I can search my phone book, see my last dialled number, I can even dial a number, BUT, the phone does not connect properly - the car radio should cut out and phone audio come through the car speakers, but instead the radio just continues to play. And shortly after the call is connected to the other party the line is terminated.
My Nokia phone works perfectly with my car, but this phone does not. Even my Sony Ericsson Xperia X1 did not for properly with the Freelander 2.
I did manage to make one successful call, but after I stopped and restarted the car, the problem returned!! Arghhhhhhhhhhhhhhh!
So, does any one know of a fix? Surely hands free/car kit is a standard?
Help!
same problem here. i have a bluetooth car stereo. Always worked fine with my previous HTC's. But now with the HD2 i get the exact same problems as you... I think it's software bug. i have rom version 1.43.404.1 NLD
i hope this gets sorted out cause i use bluetooth audio streaming a lot in the car....same for handsfree calling
Paired it with my Pioneer FH-P80BT on my way to sell my 3GS and recieved a call. Got the same issue as described above - just a bug i presume.
I'm experiancing similar problems. All works fine (incoming call's or outgoing call's) but they get disconnected randomly it seems. I'm using a JVX NX7000 by the way. No problem with my iPhone. Hope they fix it soon!
I tested it with my BMW Idrive last night which is notoriously difficult and it worked fine, I was really surprised tbh! But was able to recieve and make calls, the stereo cut out and could see the phone book too. With my N82 i was only ever able to make/receive calls.
Same problem - Jaguar XF - it docks ok but I have to initiate calls from car (vs phone). Just some weirdness going on...
glenner05 said:
same problem here. i have a bluetooth car stereo. Always worked fine with my previous HTC's. But now with the HD2 i get the exact same problems as you... I think it's software bug. i have rom version 1.43.404.1 NLD
i hope this gets sorted out cause i use bluetooth audio streaming a lot in the car....same for handsfree calling
Click to expand...
Click to collapse
Mercedes brutality
I have a new Mercedes C, and when the HD2 is connected over bluetooth I get an extremely loud, strange ringtone when receiving a call. It is so loud it could really make your shoes go off.
Also it is none of the ringtones available to choose from, inside the phone - it sounds more like a BIOS beep from a PC and hits me while the normal ringtone is playing as well.
It definitely comes from the phone, not from the car stereo. I have not figured out how to resolve this, I think it is outright dangerous for unprepared drivers.
I have a Nissan Pathfinder; it paired ok, and dials from the Pathy without probs. Ringtone is ok too. Sound quality seems better than my old Tytn so all in all v happy.
Doesn't stream music, but that's Nissan's fault, not HTC.
Works fine with the Ford BT system in the Ford Focus (2009).
HTC HD2 Pairing with a Freelander 2 - SUCESS!!!
Success!!!
So far so good, I applied a known change to the HD2 registry and I am now making and answering calls without fuss!
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.
Hope this helps everyone.
graemenwallace said:
Success!!!
So far so good, I applied a known change to the HD2 registry and I am now making and answering calls without fuss!
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.
Hope this helps everyone.
Click to expand...
Click to collapse
Hello i have same problem with my BMW X5. Can you explain better your steps ?
graemenwallace said:
Success!!!
So far so good, I applied a known change to the HD2 registry and I am now making and answering calls without fuss!
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.
Hope this helps everyone.
Click to expand...
Click to collapse
Interesting, I have a similar problem with my 2009 BMW 3 I explain here (sorry I posted before discovering this thread) and I'll try your registry tweak.
But you say that it is "a known change" to the HD2, could you tell us where you saw it ? Is there another discussion about the BT stack somewhere or more generaly about the Widcomm implementation in the HD2 ?
The HD2 being so recent and in short supply, I'm a bit surprised something like that is "well known"
Thanks for your help.
It works !
graemenwallace, I just tried after applying your tweak and... OMG, this is AWSOME man, it just WORKS !
I still just have one gripe though, it seems that the car doesn't always receive the RF level correctly at the first connection. Sometimes it sees the phone as having no carrier at all (no bars in the RX level display), preventing the car to make any calls, but as soon as I receive a call, the level resets to full bars and I can pick the call and make calls myself after that.
When the first call comes in, I can see the display with no bars and a "?" appearing on top of it for a short time before it becomes full bars.
So there is still some compatibility problems, but at least now I can pick-up incoming calls without risking my life.
So I suppose you are a potential life saver then
Thanks mate,
Yves.
Bluetooth is working YES with JVC KD-AVX44 ADV49
After the registry tweak from graemenwallace the bluetooth connection is working properly with my car radio (JVC KD-AVX44/KD-ADV49).
The phone functions ok now (incoming & outgoing calls) Also the AD2P connection is super (very good sound)
Also the ID3 tags are functioning (didn't function with the X1 Xperia)
I see the track title now into the JVC display
Skipping etc. all is functioning. I will tell HTC about it because I have a ticket running for this issue. I think they have to solve this issue
Big thanks for this trick
By doing a little search on the net, it seems like graemenwallace suggested that this problem is not new with smartphones that identify themselves as such.
The tweak above forces the BT stack of the phone to identify itself as a standard phone instead of a smartphone.
What's puzzling is that my BMW handsfree worked with other smartphones so far, including the iphone.
Anyway, it's ok now, but I wonder what bad press this will cause to HTC.
The majority of the users are unaware of this kind of wizardry and this justs adds up to the long list of bugs of the HD2.
When I first got the phone a few days ago I was rapidly convinced to return it immediatly as it's fancy interface wasn't enough to overcome all the shortcomings. It was plain unusable as a business phone.
Now after applying most of the tweaks, it begins to show potential, but HTC really has to work on the problems we can't fix by tweaking the registry.
I tried this also, but for me it didn't work.
But my situation is a bit different, as I am not able to connect the HD2 through the Sim Access Profile with my car, which is an Audi A6 mit Bluetooth preparation and I have also the Audi rSAP Adaptor installed in the centre arm rest.
My problem is, that I get a connection to the car, but SAP does not activate and I can't get access to my phonebook - so I only have kind of a handsfree profile...
Am I right that you all use the handsfree profile in your cars and no SAP?
jah said:
Works fine with the Ford BT system in the Ford Focus (2009).
Click to expand...
Click to collapse
Does your Ford system have the Bluetooth audio choice?
I get my Ford Focus changed every six months coz i'm a driving instructor and it comes as part of the deal.
On my last Ford Focus my htc tytn 2 connected ok and I could make and receive calls ok.
However, when the new car was delivered the Ford system had bluetooth audio choice and ipod integration which the other one didn't.
Now my htc tytn 2 didn't connect very well at all.
Now with my HD2 it does connect only if I have the bluetooth audio profile selected.
But now the music player keeps appearing and wants to play music all the time. If I pause the music on the phone it just starts replaying.
Anyway I will try the registry tweak in this thread and hopefully that will solve the problem.
Paul.
Jolig said:
I tried this also, but for me it didn't work.
But my situation is a bit different, as I am not able to connect the HD2 through the Sim Access Profile with my car, which is an Audi A6 mit Bluetooth preparation and I have also the Audi rSAP Adaptor installed in the centre arm rest.
My problem is, that I get a connection to the car, but SAP does not activate and I can't get access to my phonebook - so I only have kind of a handsfree profile...
Am I right that you all use the handsfree profile in your cars and no SAP?
Click to expand...
Click to collapse
I have the same problem. I`ll try to pair my HD2 with MB C-klass using SAP but i can`t get them connected it seems like a SAP adaptor can`t activate a PIN input window on HD2 (i guess). With other phones it works perfect (tryed with Nokia 5800, 6500).
Shark_Abuser said:
I have a new Mercedes C, and when the HD2 is connected over bluetooth I get an extremely loud, strange ringtone when receiving a call. It is so loud it could really make your shoes go off.
Also it is none of the ringtones available to choose from, inside the phone - it sounds more like a BIOS beep from a PC and hits me while the normal ringtone is playing as well.
It definitely comes from the phone, not from the car stereo. I have not figured out how to resolve this, I think it is outright dangerous for unprepared drivers.
Click to expand...
Click to collapse
could you pls describe, how did get them paired? when i try to pair them, i see the device`s id, try to "call" it, see pin code and after that i hear the descending tone. and it nothing occurs. SAP is enabled, device is discoverable, what else? Any idea?
Jolig said:
I tried this also, but for me it didn't work.
But my situation is a bit different, as I am not able to connect the HD2 through the Sim Access Profile with my car, which is an Audi A6 mit Bluetooth preparation and I have also the Audi rSAP Adaptor installed in the centre arm rest.
My problem is, that I get a connection to the car, but SAP does not activate and I can't get access to my phonebook - so I only have kind of a handsfree profile...
Am I right that you all use the handsfree profile in your cars and no SAP?
Click to expand...
Click to collapse
I feel your pain, my wife has a GolfPlus and the rSAP instalation is crap.
It's overly expensive and useless if you don't have one of the few phones compatible with it.
Unfortunately, many customers are falling in this trap, thinking it is a standard handsfree, but it is not, it is a full GSM build-in which only access your phone SIM card to log into the network and download your contacts.
In the case of my wife, the dealer was honest and clearly stated that it was a mistake to order this option.
The only problem is that he had no other alternative than proposing an Parrot retrofit which wasn't really an option for me as it wasn't integrated in the car and certainly not in the navigation system.
But internet is your friend and the solution is quite simple, the Kufatec kit.
This is brilliant, it is a small box that connects to the CAN bus of many german cars and integrates perfectly into existing navigators, it uses the steering wheels command buttons and so on.
It is much better (more functions) than original BT options, is tailored to each brand so that the displays are in the same style as the original ones etc.
More interesting, it is field upgradable (just a laptop with BT) so that it is potentialy compatible with anything existing or not yet.
And it only costs a fraction of this crappy rSAP option.
In your case, the good news is that it can simply replace your actual rSAP kit for a minimal installation fee. (the CAN bus has to be reprogramed however, so professional instalation needed)
There is another solution: to replace the unit you have (it is situated under the driver's seat) by a skoda unit. This unit has the same connector but is simple handsfree instead of rSAP.
Hope this helps.

Categories

Resources