Related
Having moved to WM6, my handfree car bluetooth pairs with the car, but cannot be used to make/recieve calls using bluetooth (prior to this everything was ok, and even worked with WM6 for a while) ???
I've done resets on the device, reinstalls, etc.. and also been to the dealer this mornign to get the car bluetooth reflashed, but nothing (others phone work fine).
I started looking at the registry (i not really sure what i'm doing, but came across this HKLM\Software\Microsoft\Bluetooth\handsfreeprofileon, but there is only a blank default key.
Could this be the issue, if so which key should I add and values ?
Anybody reporting problems with the new 6.1 ROMs trying to pair up certain devices? I used the latest L26 V2 and am having problems pairing with my car, and pairing with my laptop took several tries and reboot. It was no problems with 6.0 or earlier 6.1 builds. Is bluetooth affected by the Radio version? thanks!
Same here...
In every cars with integrated Bluetooth something, I cannot pair the phone.
Either the car does not "see" it or the mobile does not "see" the car.
I tried with many cars, same issue...
I used to have the same problems connecting to my Pioneer AVIC HD3BT. On some other forum I did read about changing the registry and it worked for me. This is the key which needs to be adjusted, I hope it will do the trick for you too;
Go to HKLM\Software\Microsoft\Bluetooth\AudioGateway and find the BTAGExtModule. Most like the value will be something like OEM... (sorry don't remember exactly anymore), change it to \Windows\vcbthag.dll
Sometimes (depending on the ROM i use) it seems only possible to get it paired one way, for example start the pairing on the device instead of the carkit.
Also make sure that during pairing your device is set to visible in the bluetooth options.
Hope it helps
Hi,
I am using my HTC Touch Pro with an Opel Vectra built-in bluetooth carkit.
All functions, like browsing the address book and call registers, are working fine. However, at random times, my carkit reports no phone. When I then check my Touch Pro's bluetooth status, I see that it is has been disabled.
After manually re-enabling it, I can pair with my carkit for as long as it takes for bluetooth to turn itselves off again.
I've already tested with JETware, but that does not change anything. Also tried the universal broadcom bluetooth stack, but doesn't seem to work on the Touch Pro. HTC only comes with a standard answer that they don't support all carkits and headsets... Since the BT stack on the phone seems to crash, I don't think it's a carkit issue.
Anyone here with the same issue? And maybe a solution?
Thanks and regards!!
Start -> Settings -> Connections -> Bluetooth -> Timeout (tab). Turn off Visible mode set to "Never".
I think this must be your problem.
Hi Freco,
Thanks for your reply! This option is set. However it's not really the visibility that turns to invisible, but the whole bluetooth stack is being turned off completely. Need to fully re-enable it via Comm Manager.
Any other options? Does anyone know if there is a working broadcomm stack for the Touch Pro?
Regards!
Hi,
I have exactly the same problem with a Vauxhall kit, I have tried all sorts of things, but nothing seems to work
try:
start -> settings -> connections -> bluetooth
timeout tab
select 'never' from drop down box
Hi Brendo,
Unfortunately this doesn't solve the issue. Once paired, the connection even works without being visible. It's also not a fixed period of time before the disconnect takes place (can be within a minute, sometimes after half an hour). However, the whole bluetooth icons disappears from the top icon bar and comm manager shows it's turned off completely.
Hope somebody has any other ideas, because the only thing HTC can do is point to the carkit vendor :-(. Since all functionality is there when connected and the phone is turning off BT in some way, I really don't think this is caused by the carkit vendor. I should at least expect BT to stay enabled on the phone.
Thanks!
Yes, same here, BTW I have tried this in my Friends Saab, and the same problem.
same problem here with a Opel DVD90 buildin bluetooth carkit.
With other htc phones it always worked like a charm, but my mda vario IV continuously disconnects after a random time period and shuts down the complete stack.
Try this!
I have the same problem with my opel with original bluetooth-kit (2007). On the touch pro I changed the band and network from auto to GSM, as G3 reseption in this area is quit poor, especialy while driving. It helped for me, at least the last few days. I agree this has been an annoying problem.
I have tried to switch to "GSM only mode" in the past, but as far as I remember it does not completely solve the issue. However, I will give it another shot! Actually I can't figure out at what point it occurs... It can happen within a minute or after half an hour without using any funtion.
Does one of you know if there is a way to do some debugging on the Bluetooth stack?
And has anyone experience with other Windows Mobile 6.1 based phones in this combination (just curious if it's a WM issue or HTC only)?
Furthermore I did some tests with JetWare. You should be able to limit the number of synchronised items then (might be related to this issue). However, it looks like this configured limit is being totally ignored: when I limit my recent call list to 5 with JetWare, it still syncs about 25 items. Anyone tested with Jetware?
I have tried the GSM only mode, this didn't help either
I have now given up and got myself a Nokia E66, which works perfectly.
All contacts are pushed to car, no disconnects and AD2P works so my mp3 ringtones play through the car speakers! Sweet
Word of note, I had issues with N-Series phones, would connect ok, but contacts would not push.
I have the samen problem with my HTC Touch Pro and Saab.
bluetooth pairs just fine with my pioneer bluetooth enabled deck, but the problem iwth mine is once i receive a call sometimes no sound comes from the car, instead the earpiece is still on. but if i initiate the call first sound works just fine and earpiece on the phone is disabled, BUT once the call is ended bluetooth disconnects randomly and the phone takes a good 1-2min to reconnect. i absolutely hate the bluetooth on this phone!
ExTREmE99 said:
bluetooth pairs just fine with my pioneer bluetooth enabled deck, but the problem iwth mine is once i receive a call sometimes no sound comes from the car, instead the earpiece is still on. but if i initiate the call first sound works just fine and earpiece on the phone is disabled, BUT once the call is ended bluetooth disconnects randomly and the phone takes a good 1-2min to reconnect. i absolutely hate the bluetooth on this phone!
Click to expand...
Click to collapse
I am having the same problems you describe. Anyone got an suggestions???
I encountered the same problem; first with an opel udp carkit and next with the bluetooth interface software from homeseer.
It has something to do with phone signal loss.
With the opel carkit I noticed bluetooth automatically turns off when the phonesignal switched from 3g to gsm.
I also noticed that in my home, BT turns off whenever I have been in a room with no phone-signal reception.
try this thread, both registry change and attached cab file, reset. DOn't worry if the make visible to all option is unchecked.
http://forum.xda-developers.com/archive/index.php/t-314996.html
My touch pro seems to have real bluetooth issues with my JVC KD-NX5000 stereo system. My kaiser worked flawlessly with it but with the touch pro it wont pair at times and when it does it wont let me use any of the many functions that the stereo offers (voice dialing, downloaded phonebook, etc) I assume this is a problem with the ms bluetooth stack and was wondering how tough of a job it would be to switch to a broadcomm stack or if anyone has thought about making a custom rom with the broadcomm stack. Just curious if Im the only one with issues with wm 6.1 and bluetooth.
i have the same problem with my diamnd anbd jvc car audio
Slightly OT rant:-
I had the opposite problem with pioneer + broadcom...
Pioneer only looks for handsets which identify themselves as phone or smartphone, and my device identified itself as a pda.
I actually told pioneer about the problem, and rather than forwarding on to the developers, I got a stock reply:-
"This phone is not on our compatibility list" (so we don't care)
So I went and got an MS based phone (you can change it to smartphone with a regedit).
Never buying pioneer again...
- Anthony
Similiar issue with my opel carkit.
Tried to make the broadcom stack working, but got a memory error when opening its blue tooth manager.
After uninstalling, bluetooth didn't work at all anymore, needed to perform a hard reset.
Has anyone successfully installed the broadcom BT stack on the touchpro/raphael?
I found that my Touch Pro would pair and then drop out when connecting to my Kenwood DDX5032 car stereo bluetooth adaptor. I couldn't dial from the Kenwood kit, couldn't use A2DP (wouldn't even connect), and really couldn't use any Headset Profile functions at all.
I persisted with pairing and unpairing in different ways (you can initiate the pairing from the Kenwood itself rather than the phone), but nothing really worked.
Then trinode's post about changing a registry setting sent me down that track and now everything is working fine
I found the relevant setting from http://forum.xda-developers.com/showthread.php?t=290871, which is [HKLM\Software\Microsoft\Bluetooth\sys\COD], and then changed the HTC TP default value of '5898764' (decimal), to the value from my old Dopod838Pro, which was '5374228' (in decimal).
I didn't even need to repair the Kewood to the HTC TP - it just worked straight away, as if it said "Oh, sorry, did you want me to work? I thought you wanted me to be in 'stupid' mode! My bad - everything will work now."
So all good, and thanks to trinode for pointing me in the right direction.
Codenix.
After hard-resetting my Touch Pro to fix another separate issue, now this problem has come back and this time changing the COD value hasn't fixed it. It would appear my previous post may have attributed my success to the wrong thing
The search for the answer continues!
I found a firmware update for my Kenwood's bluetooth adaptor which fixed the problem. I don't know why it ever worked at all before this update, but there you go!
I'll create a separate thread to share this with others in case anyone else out there has a Kenwood bluetooth kit and a Touch Pro or a Diamond.
Thanks.
The thread I created re the Kenwood is at http://forum.xda-developers.com/showthread.php?p=2835805
@ Trinode
Pioneer sent my unit back, but never told me that my phone was not supported. Where did you flag the smartphone in the registry? Did it fix the BT connection/unti reboot issue? I had a AVIC F500BT (sold it) now have a AVIC X910BT same issue as the 500 had.
@ Trinode. I found the hack , tried it, but it still doesn't resolve my issue. Are there any other mods out there for the BT Stack prob?
Hi all,
I have a 2008 vehicle in which Bluetooth seems to be a problem depending on which ROM I have installed on the device.
I'm currently on Android 9 OB 7 and Bluetooth connects and stays connected through incoming and outgoing calls. Works flawlessly.
However, with for example Lineage (among others), the Bluetooth pairs, but connection drops soon after or drops after the first call with the car stereo showing "Net Search", meaning the car BT lost service but the phone Bluetooth is still connected. I've tried restarting and resetting network settings but no luck at all. Changing dev options doesn't work either.
I'm thinking it could be a Bluetooth stack difference?
Is there a way to replace the lineage Bluetooth with OOS?
There is no bluetooth.default.so file that I could find
Any help or direction is appreciated.
nickelnine said:
Hi all,
I have a 2008 vehicle in which Bluetooth seems to be a problem depending on which ROM I have installed on the device.
I'm currently on Android 9 OB 7 and Bluetooth connects and stays connected through incoming and outgoing calls. Works flawlessly.
However, with for example Lineage (among others), the Bluetooth pairs, but connection drops soon after or drops after the first call with the car stereo showing "Net Search", meaning the car BT lost service but the phone Bluetooth is still connected. I've tried restarting and resetting network settings but no luck at all. Changing dev options doesn't work either.
I'm thinking it could be a Bluetooth stack difference?
Is there a way to replace the lineage Bluetooth with OOS?
There is no bluetooth.default.so file that I could find
Any help or direction is appreciated.
Click to expand...
Click to collapse
I am having the same issue with 9.0.2 OOS. So not sure if this us a compatibility issue with more than 1-2 years old vehicles or something else? Glad to hear that OB7 is working fine for you. Hope fix is coming soon. It's simply annoying.
I am having car connection issues as well. I have a 2010 Ford Edge. Just moved from Sony Xperia XA1 Ultra on Orea to my first OP device - OP6 Pie 9.0.2 - I can connect to my car initially but once I turn off my car, I have to go through a series of reconnect steps. I called tech support and we spent about 45 min troubleshooting - of course I was told I was the only one who had complained of this issue - anyway no resolution. The only way I can "reconnect" is to go into my car's system settings and select "connect to BT device" then toggle bluetooth off and on in the phone - sometimes this works with the first go, other times I have to repeat this cycle 5 or 6 times. Simply selecting "previously paired devices" in the phone app doesn't work either.
Really a pain in the tush, because I am usually in a hurry and don't have time to go through all this scenario to get a connection.
On the other hand, I have a bluetooth ear piece (made by Samsung that is like 5 or 6 years old) that reconnects every time I turn it on, no problems.
Car connections too but was not present in omni
I found for stock, performing a network reset (mobile, wifi Bluetooth) then restarting the device fixed the Bluetooth connection issue.
For custom non-stock ROMs, for my issue at least, I found its not a Bluetooth issue at all but rather the mobile network drops and the car Bluetooth cannot reconnect. The same network reset as above does not work but what does work is toggle off the "automatically select network" and manually select the mobile network from the menu that pops up. This keeps the mobile network intact (until the next device reboot, at which point repeat the steps) with the car and all is good.
I only figured it out by accident; hope this helps others.