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
Is anyone able to automatically connect to a bluetooth device from your captivate? I am using a sony bluetooth receiver a2dp profile so it's basically functioning like a bluetooth headset.
Pairing works. Manually connecting works. But it would be great if the captivate automatically connected to the bluetooth receiver as soon as i turn on bluetooth. It takes almost five clicks to manually connect but only one to turn on bluetooth.
Sent from my SAMSUNG-SGH-I897 using XDA App
I have a similar problem in that the phone will sometimes "forget" the bluetooth devices that it has been paired with. I then have to do the pairing all over again.
I'm having the same problem - if I turn the phone off & back on again, it won't connect to my car. The bluetooth menu still shows that it's paired, but it won't connect (even if I try to manually connect). The only way to get it to connect again is to turn bluetooth off & back on - then it connects automatically.
Mine connects right away.
I think it is relate to not being able to set the bluetooth to always visable. My fuze had the same problem untill I put the energy rom on it.
I'm having the same trouble. I have to click on the Connect option which is buried in the Bluetooth menu. Annoying.
Are you using a task manager or some sort of helper to keep battery usage low? I found I was having a blue tooth problem until I saw a OPP service pop up on my task manager. Every time I killed apps I had blue tooth problems until I set this service to be ignored and left alone. Now even after I shut off the phone and turn it back on, I quickly connect to my blue tooth headset.
I'm just a noob here and I am thankful to everyone who posts who have helped me so i thought I's throw this out as something to check on.
So I of course love my Thunderbolt, but I have one issue I can't seem to fix. My phone connects to my trucks headunit over Bluetooth for talk and audio. Once I start Pandora or the native music app, about 20 seconds later the phone says "Bluetooth Headset Disconnected" and thats that. Anyone else having this issue and are there any known fixes yet?
this just started happening to me after using BT successfully for months. i have tried pairing and repairing. initial pair connects headset and media, but after a few seconds i see the message headset disconnected.... the media profile is still paired but not headset.
any ideas?
thanks,
eric
i have this issue as well, but i'm running bamf 1.6.2... i wasn't going to say anything itll i was on CM again (it did work when i was on CM previously)
Try unpairing, then repairing - this time deny any requests to let your car access the TB's phonebook via bluetooth. That solved it for me.
happens to me every once in a while.
stock
no root.
i have to turn bt off and then back on and it reconnects without issue.
I've been reading and searching but I think I missed the thread that pertains to my issues. Running Stock everything and bluetooth connects from my phone to my headset fine but when I get in my car, the bluetooth system in my car starts screaming at me every 30 seconds that the "pairing process must be initiated from the car and not the phone". Well, I'm not trying to pair, why is the phone sending out a pairing attempt and how can I stop it?
I have the AT&T Galaxy S II Skyrocket and my phone used to auto-connect to my car via bluetooth without any problem, even after upgrading to ICS in early July. All of sudden since yesterday a problem has popped up: whenever I start the car, the car's control panel shows "bluetooth connection successful" or something similar, and then the car audio system switches into the talk mode as if the phone is in the mid of a phone call. Of course I am not in the middle of any phone call. So there is no audio heard (no radio, no cd playing, etc). I try to press the button on the car's panel to disconnect the call but it always returns to that talk mode. After some tests I find out that if I make any phone call, the call will be disconnected immediately and the status of my car's panel returns to normal. But next time when I start the car, the issue appears again until I make any phone call.
At the beginning I thought something was wrong with my car. Then I tried two other phones: one was iphone 3G, and the other was an old htc magic with android 2.2. Both of their bluetooth systems worked well with my car. So I believe it is something wrong with the Galaxy phone. However I am not sure what could be the problem exactly.
My phone is not rooted.
Any help is highly appreciated!
Have you tried unpairing the skyrocket and your car? Sometimes you just need to break the connection and set it up again.
Reported questions go in q&a and there are threads on Bluetooth issues
Sent from my SGH-I727 using Tapatalk 2
Firedcylinder said:
Have you tried unpairing the skyrocket and your car? Sometimes you just need to break the connection and set it up again.
Click to expand...
Click to collapse
Yes I have unpaired the connection, restarted the phone and the car, and paired them again. But the problem persists.
Today I tried my wife's iphone 4 with the car the didn't see any problem. I am pretty sure there is something fishy with the phone.
lik88888 said:
I have the AT&T Galaxy S II Skyrocket and my phone used to auto-connect to my car via bluetooth without any problem, even after upgrading to ICS in early July. All of sudden since yesterday a problem has popped up: whenever I start the car, the car's control panel shows "bluetooth connection successful" or something similar, and then the car audio system switches into the talk mode as if the phone is in the mid of a phone call. Of course I am not in the middle of any phone call. So there is no audio heard (no radio, no cd playing, etc). I try to press the button on the car's panel to disconnect the call but it always returns to that talk mode. After some tests I find out that if I make any phone call, the call will be disconnected immediately and the status of my car's panel returns to normal. But next time when I start the car, the issue appears again until I make any phone call.
At the beginning I thought something was wrong with my car. Then I tried two other phones: one was iphone 3G, and the other was an old htc magic with android 2.2. Both of their bluetooth systems worked well with my car. So I believe it is something wrong with the Galaxy phone. However I am not sure what could be the problem exactly.
My phone is not rooted.
Any help is highly appreciated!
Click to expand...
Click to collapse
Common problem:
http://forum.xda-developers.com/showthread.php?t=1630021
Also look in the last couple of pages here, there is some explanation for it.:
http://forum.xda-developers.com/showthread.php?t=1701189