I have been having issues with this device and bluetooth hands free ability. No matter the app: Skype, Line, WhatsApp, QQ, etc. any attempt to make or receive a voice call causes the device to disconnect from the headunit. For example, making a call the phone tries to dial and the dialing only happens on the phone and the bluetooth connection breaks. Receiving a call, the headunit shows dialing and then the connection breaks. It's really frustrating because bluetooth audio using Spotify, Songza or any other music app works fine.
Another issue that is likely not related: After around 24-48hrs the device no longer will connect to the headunit unless I delete the pairing and remake it. I tap the device in the bluetooth screen and it does nothing. If i delete the pairing and reconnect, it immediately reconnects without issue and the pairing will work for the next day or so, then the problem reoccurs.
Does anyone know ways to help fix this?
Anyone?
Related
I'm trying to connect my Sprint TP2 to my car stereo's bluetooth.
It works great for streaming audio from my phone, but when I try to make or receive a call, it's as if it's not even connected. If I call from the phone, and then click the connect button on the stereo a few times, it will connect, but then only for a second or 2 before it drops off again. The phone call never gets lost, it just doesn't work like a hands-free headset should.
What is interesting though, is if I'm playing a song from my phone, then the head set portion works exactly as it should.
I tried another phone, a Treo800, and it works as is should; you can make and receive calls as you would w/ any headset, and doesn't have to be connected via the audio profile first.
Any suggestions?
batpot said:
I'm trying to connect my Sprint TP2 to my car stereo's bluetooth.
It works great for streaming audio from my phone, but when I try to make or receive a call, it's as if it's not even connected. If I call from the phone, and then click the connect button on the stereo a few times, it will connect, but then only for a second or 2 before it drops off again. The phone call never gets lost, it just doesn't work like a hands-free headset should.
What is interesting though, is if I'm playing a song from my phone, then the head set portion works exactly as it should.
I tried another phone, a Treo800, and it works as is should; you can make and receive calls as you would w/ any headset, and doesn't have to be connected via the audio profile first.
Any suggestions?
Click to expand...
Click to collapse
Check this thread out: http://forum.xda-developers.com/showthread.php?t=591322
The TP2 can have some weird behavior with bluetooth car kits due to the Widcomm bluetooth stack. I applied the fix in thread linked above and haven't had any problems since with the Tilt 2 and my Acura's bluetooth system.
thanks, I'll give that a shot tonight.
didn't work for me; exactly the same behavior as before.
Additionally, the BDAddr key in HKLM\Software\WIDCOMM\BtConfig\General always resets itself when i reboot my phone (the instructions say to set the value to "no value").
I even tried changing the key type, and it reverted to binary upon reset.
I'll keep searching, but in the meantime, any other suggestions?
Hello guys,
I just got a Sony bluetooth headset and I am trying to use it with my HTC TYTN II. At first I paired the phone and the headset and I was able to listen to music and talk through the headset, all perfect. When I was listening to music, the bluetooth icon on my phone represented a music note and a headset over it.
When I turn the headset off once and then on again, it connects automatically with the phone but in some other mode. The bluetooth icon now represents the bluetooth sign with a headset over it. Now when I listen to some music, it comes from the speaker of the phone, not from the bluetooth headset. Talking through it is not a problem.
If I pair the phone and the headset again, it works just fine (showing again the music note) but once I turn the headset off and on again, I lose the music mode.
Does anyone know how to fix that? Thanks in advance.
I fixed the issue by installing AutoA2DP (found in this forum).
I've had a similar problem on my Tilt. I originally posted the following on the ROM thread. Since then, I have found that the AutoA2DP has not fixed the problem. I still have this issue about 70% of the time, and sometimes I can't get the bluetooth to work at all, not even after a soft reset. Sometimes it seems as if the bluetooth has no power, the phone can't communicate with the headset except when within a few inches of one another. Then it magically seems to resolve itself. Anyway here's my original post from the ROM thread.
The other day I installed an app on my phone called Schaps Network Plugin, which allows you to map network drives to the phone the same way you can do with a desktop. It allows me to access the home network directly via my wifi. It was something I needed and it seemed to work great, for a day. The next day my bluetooth headset would not connect. Long story only slightly shorter, it seems the problem was with the headset connecting via A2DP and doing so automatically. This always worked just fine in the past. Suddenly it wouldn't work. I tried a ton of things including a "fresh" install of everything and formatting my memory card to start with nothing on it. I flashed the original rom and then flashed this rom. I did hard resets each time. Did this twice. Even tried the bluetooth in the oem rom to see if I still got the problem. I did, and it is still with me. I can manually get the headset to connect via A2DP using the bluetooth settings, though even then it may take reconnecting several times to get it to work. However, when I turn the headset off and then on again, the A2DP does not reconnect, just the hands free. But the sound is not routed through the phone's speaker either, at that point. In fact you often get no sound at all, nothing via the headset or the speaker. OTOH, if you activate Voice Command, the headset does work while Voice command is running. After it shuts off, you are back to no sound. It seems as if the hands free works fine, but the audio gets partly routed to A2DP but does not connect to the headset. If I reset the phone, the headset connects correctly and efverything works until I turn the headset off again. Also if I pair the headset again, everything works correctly until I turn the headset off. Though pairing is not as trouble free as it used to be either. Sometimes it will not pair up wihtout repeated attempts. I did find this program, AutoA2DP which has patched the problem. It detects when a paired bluetooth device connects, and forces a connection via A2DP as well. But I never had this issue in the past, and my wife's phone still has no problem. I am not sure the Schaps Network plugin had anything to do with it, other than the timing. Seems odd to me that the bluetooth stack would suddenly develop issues that persist even after two fresh flashes of the rom. Any ideas, suggesitons, etc.? This is really bugging me, and although the patch seems to be working, the phone is still not acting "right." In the past, and on my wife's phone, if a bluetooth headset is turned on, it automatically connects, and all sounds, including the system sounds, are routed through the headset. Now, sometimes they are, and sometimes they aren't.
Is any one with problem for the bluetooth connetion? It will drop after a few min. and try to reconnect have no respond, need to reboot the phone. Is it the setting or bug?
andych888 said:
Is any one with problem for the bluetooth connetion? It will drop after a few min. and try to reconnect have no respond, need to reboot the phone. Is it the setting or bug?
Click to expand...
Click to collapse
Mine has not done this with my Jawbone Icon, Motorola S10-HD stereo headphones or my Volkswagen Tiguan. Perhaps you might try another bluetooth device?
buletooth issue?
I had try different device and do the same thing, like my audi q7 and jarba headset and the garmin. Can you tell me what buletooth setting you are using?
Mine has intermittent issues as well, I'm using an older Motorola 710 BT earpiece. I'll only turn on BT on the phone when I know I'm going to use the earpiece, such as when driving or needing to be hands-free. I only activate the earpiece after enabling BT on the phone, but there are times when the earpiece does not connect.... the only fix is to reboot the phone. Is that similar to the issue you are having?
I'm having issues connecting to my car. If I reboot the phone and connect it will work. But once it's disconnected and I turn bluetooth off and then back on from the phone, it will not connect. Only way to fix it is to reboot. Don't know how to fix the issue. Never had a problem connecting my Sensation to my car's bluetooth.
My issue is similar in turning bluetooth on and off via the power widget and not being able to re-connect to my bluetooth earpiece after a few cycles. I'm wondering if it may be an issue with it being BT 2.0 versus BT 3.0 on the phone?
I thought it was my car but a lot ppl is having this issue too.
Sometimes it wont connect but it says connected so i have to go to BT settings and click where it says connected n overwrite the connection for it to work if not gotta restart the phone. :/
Tmo Galaxy S2
I'm having problems with a SoundFly FM Transmitter in my car.
At first it took forever to pair. And even when paired & connected it's really glitchy.
I'm using this mainly for GPS turn by turn over the car sound system. But because it is glitchy I can't use it because some of the directions get cut off.
I had a MyTouch 4G before. No problems whatsoever. I don't if it's a hardware or driver or BT device issue.
I'm willing to get a new FM Transmitter but not if it does the same thing.
It didn't work well on stock or rooted w/ Juggernaut rom
this is quite annoying. I wonder why this topic died so quickly, there have to be more people with this problem? Maybe has something to do with a bluetooth power saving sleep feature? Streaming music, pause music for a few minutes, incoming call gets connected but I get no sound through headset.
Does anyone know a way to tell the phone to connect to the car bluetooth for calls rather than the watch when I get in the car? Then also switch back to watch bluetooth calls when I leave the car?
thanks
Does the car connect to the phone at all when you get in, or does being connected to the watch block this?
I'm wondering if you place the call/answer the call with the car's menu system/steering wheel controls what happens, or if you are unable to even get this far.
Same problem
I'm having the exact same problem.
Carkit does connect (you can see in settings) but it says "(no phone calls)".
Watch is alsoo connected and says "(phone calls)
When i use voice control or the buttons on the dash to start a call it says no phone connected.
So my phone says that it is connected to carkit (no phone calls notification however), but if i look in settings from carkit it does'nt show phone connected...
The phone doesn't even connect to the car - I have to go into bluetooth settings on the phone and manually swap between the two when I get in and out of the car. I only connect to the cars on phone, not media audio.
I use the phone in 2 different cars, so ideally want to be able to automatically prioritise which bluetooth it connects to. I know there are apps like tasker which can do this but they are so complicated (or I'm too blonde!).
other thread
Found another thread already covering the subject...
Hope this helps...
http://forum.xda-developers.com/huawei-watch/help/android-wear-6-0-vehicle-bluetooth-t3327307
After an OTA, stock 5x, I did a full reset because I seemed to have battery drain. Unfortunately I could not pair my phone with my 07 Acura Tl w/ navigation. The pairing process would cut off when I was to enter my pin on the phone.
Apparently, going to location settings of my phone and turning off the scanning option for wifi and Bluetooth solves the pairing problem.
My phone paired and most is well. Unfortunately, I still have issues with starting a call on the phone. I can transfer the call to Bluetooth until the call is answered. But I can start calls from my cars voice commands. This was an issues since 6.0.
YMMV, but this likely works with most Hondas of this era.