Related
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.
Bluetooth appears to be broken on my Galaxy Nexus I can discover other bluetooth devices fine, and they can discover the Nexus, and pairing appears to be successful from either direction. But as soon as I try to connect/transfer a file immediately I get a notification on the Nexus saying 'connection unsuccessful', 'transfer cancelled by user' (when I didn't cancel anything!) etc.
I've tried this with three different devices (my old HTC Desire, my wife's HTC Legend and my MacBook Pro) with the same results on all three.
Has anyone else run into similar problems, or does this sound like I've got a faulty unit and should send it back? Is there anything I can do to troubleshoot this any further? (I've not rooted the phone and its running the stock Android 4 ROM).
I wish I had an answer; just got my Galaxy Nexus yesterday; it won't pair with any of my bluetooth(s) -- they were all working fine in my Droid so I know how to pair. Any suggestions? Help!! Thanks
After further investigation, it seems it's just outgoing connections that don't work on mine. I can transfer files from other devices to the GN fine, just can't transfer from the GN to any other devices. Haven't tried connecting to a headset or anything like that as I don't have one.
I asked an acquaintance who also owns a GN to test it out on theirs and they experienced exactly the same thing - everything works ok except for outgoing connections/transfers.
I'm wondering if its a software bug if that's the case. If it were hardware related you'd have thought the whole bluetooth thing would be broken.
FWIW: I have been able to pair and connect via bluetooth with my car, with no problem. Downloaded my phonebook to my car via bluetooth as well.
Bt phonebook pairing
I'm having BT issues as well with my G-Nex on Verizon. Will connect/pair with my car, works for making/receiving phone call audio, but will not synch the contact list. Thus, cannot use voice dial in my car (Nissan).
Have searched all over the internet, no real answers. Tried to disable the existing bluetooth PBAPservice as suggested somewhere else - no dice, and it just restarts itself anyway. I've seen some suggestion about rooting the phone and replacing the PBAPservice which may be my next step. Hate to root a phone this new when I may end up returning it if I can't make this work ... sorta a deal breaker for me.
Anyone have any suggestions? Could my phone just be defective? Seems like there are a number of BT issues around, but I can't find anything "official" acknowledging the issue(s) ..
Thanks ...
I'm having a problem with my new GNex bluetooth as well. I'm using a Blackberry Stereo Gateway (an A2DP adapter) in my car and it -does- work, but only after I toggle bluetooth off and back on again. That's kinda annoying.
Previously I had been using an Incredible and it was working fine.
Having problems with Bluetooth as well. I have a BlueFusion unit installed in my car. Worked perfectly fine with my Droid X. Every time I got in the car, it just connected and calls and music both played over the stereo fine. Got my Galaxy Nexus paired and it worked great. However, whenever I get back in the car and the Galaxy Nexus reconnects, the audio does not work. It says it's connected, it plays with no audio coming out of the phone or the car speakers though. Tried re-pairing, no go. Tried bluetooth on/off, no go. The only way to get it to work, is to reboot the phone every time I get in the car.
DoubleVision81 said:
...Tried bluetooth on/off, no go. The only way to get it to work, is to reboot the phone every time I get in the car.
Click to expand...
Click to collapse
Okay, I don't feel so bad now. Ouch.
---------- Post added at 02:07 AM ---------- Previous post was at 02:04 AM ----------
cam30era said:
FWIW: I have been able to pair and connect via bluetooth with my car, with no problem. Downloaded my phonebook to my car via bluetooth as well.
Click to expand...
Click to collapse
Does A2DP work properly? And what sort of bluetooth device are you pairing with?
Same here, sending files works, receiving doesn't. Pairing with my bt headset also works fine....
Sent from my Galaxy Nexus using XDA App
mattots said:
Bluetooth appears to be broken on my Galaxy Nexus I can discover other bluetooth devices fine, and they can discover the Nexus, and pairing appears to be successful from either direction. But as soon as I try to connect/transfer a file immediately I get a notification on the Nexus saying 'connection unsuccessful', 'transfer cancelled by user' (when I didn't cancel anything!) etc.
I've tried this with three different devices (my old HTC Desire, my wife's HTC Legend and my MacBook Pro) with the same results on all three.
Has anyone else run into similar problems, or does this sound like I've got a faulty unit and should send it back? Is there anything I can do to troubleshoot this any further? (I've not rooted the phone and its running the stock Android 4 ROM).
Click to expand...
Click to collapse
I had this problem when I fist boot the Nexus and after the first boot of the update to 4.0.1. Reboot the phone, re-pairing the devices and everything is fine since then.
Sent from my GT-P7300
I can't even get my Nexus to pair with my car (Kufatec FISCON unit for Volkswagen). Just straight up error "unable to pair" when I try it. :/
And I have a problem as well. I did get it to pair with my PC but I can't send any files from my PC to Nexus (it works fine with Desire).
I have two Nexus (one is my wife's) and both car have Blackberry Bluetooth Gateways in them. In both cases I am seeing the same issue as the OP, the bluetooth will not connect automatically. However if I manually power on the bluetooth on the phone when the gateway is in connecting mode than they will connect. I never had a problem like this with previous phones.
Is there a official way to inform Samsung of this issue?
I'm also having problems with bluetooth on my Galaxy Nexus. I wanted to transfer files via bluetooth from my old Incredible 2 to my new Galaxy Nexus and it just wouldn't work.
Edit: A reboot appears to have fixed the problem.
DoubleVision81 said:
However, whenever I get back in the car and the Galaxy Nexus reconnects, the audio does not work. It says it's connected, it plays with no audio coming out of the phone or the car speakers though. Tried re-pairing, no go. Tried bluetooth on/off, no go. The only way to get it to work, is to reboot the phone every time I get in the car.
Click to expand...
Click to collapse
I have this same issue exactly - and had this issue after a System Update on my Droid Incredible for a few weeks before I ended up buying the Galaxy Nexus. I had hoped the new phone wouldn't have this issue. Anyways, it also seems to happen when I take a phone call.
Scenario: I'm listening to music over bluetooth to my bluetooth audio enabled headunit in my car. I receive a phone call, and toggle the bluetooth off so I can take the call privately over my phone's earpiece. When the call is finished, I toggle the bluetooth back on and the phone will connect - however the music is playing, but no audio comes through the phone nor the speakers of my car.
I started having this -exact- scenario issue when System Updates started rolling out for Droid Incredible, and they added the options for "Phone Audio" and "Media Audio" under the bluetooth options. Before these System Updates, my Droid Incredible had worked perfectly with bluetooth audio in my car.
Bluetooth Phone and Stereo
SnarfvsMaximvs said:
I'm having a problem with my new GNex bluetooth as well. I'm using a Blackberry Stereo Gateway (an A2DP adapter) in my car and it -does- work, but only after I toggle bluetooth off and back on again. That's kinda annoying.
Previously I had been using an Incredible and it was working fine.
Click to expand...
Click to collapse
I am having similar problems with both my car's BT phone and BT audio.The phone through my car gets terrible static until I stop and start Bluetooth again, which is dangerous on the highway.
I hope it can be fixed with a little software update.
I have the same problem with new nexus galaxy, pairs well with car bluetooth audio, can hear a confirmation beep on car speakers but no luck in the phone. It just stays on paired but not connected. It doesnt allow to remove pairing and redo it untill rebooting the device.
I'm also having issues with the bluetooth audio in my car. I pair okay with my Sony Xplod head unit, then when I turn off the car and reconnect, the GN starts playing music through the internal speaker instead of the car speakers.
I'm having the previously mentioned A2DP issue as well. Everything connects fine but occasionally, no audio is heard via the deck in my car. Phone calls via bluetooth work, just no A2DP audio.
For those having this same problem, you can fix issue by toggling airplane mode on and off. This is quicker than rebooting (which also fixes the issue).
This has to be a bug. I'm running 4.01. Anyone having the same issue with 4.02/4.03?
AdamUpNorth said:
I'm having the previously mentioned A2DP issue as well. Everything connects fine but occasionally, no audio is heard via the deck in my car. Phone calls via bluetooth work, just no A2DP audio.
For those having this same problem, you can fix issue by toggling airplane mode on and off. This is quicker than rebooting (which also fixes the issue).
This has to be a bug. I'm running 4.01. Anyone having the same issue with 4.02/4.03?
Click to expand...
Click to collapse
Yes. I just got mine last night...ran some errands today. Paired fine in my car, can make and receive calls through the car's audio system, but no sound. I'm running 4.02. Tried this with my BT headphones and the same thing happens.
The airplane mode trick works, however. Thanks!
Hopefully this will get fixed rather quickly!
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?
Is anyone else having issues with their 5x connecting to their car's bluetooth automatically (I drive a 2015 Subaru Forester)?
My Nexus 5 would always just automatically connect, but since I switched to the 5x I have to either connect to the car from the phone or vice versa.
I'm sure I could work something out with tasker or whatnot, but that feels to me as though it should not be necessary?
I have yet to get back in my car after pairing to my bluetooth adapter (I just paired this morning) but I will check later.
Do you have a list of saved or prioritized devices in the car? I wonder if the Forester bluetooth is trying to connect to your first device (Nexus 5) unsuccessfully.
I have a 2014 Ford Focus. The bluetooth will connect automatically, but I have noticed weirdness when placing calls. The car will take a while to initiate the call and then display an error saying "call cannot be completed". Then, 2 seconds later the call audio (ringing) will occur.
I am hoping that these are just some initial bluetooth issues that will be ironed out.
I had deleted my old device from the car's memory.
Another thing I am experiencing is that even if my phone IS connected, the calls are going through the device, and not my speakers.
It still pauses the music...
It could be either my car or the device. I've heard of other Subaru owners having issues with multiple devices in their car, just wasn't sure if it was a little of Column A and B. It seems likely enough it's a little bit of both.
No issues at all. I have a 2012 Dodge charger with the 8.4 Uconnect. This phone actually connects quicker than my S6 edge did and the sound is louder at max volume (on the phone) than the S6E. The only thing that doesn't work is the text messaging from the Uconnect, but overall I am very pleased.
stu_brainsurgeo said:
I had deleted my old device from the car's memory.
Another thing I am experiencing is that even if my phone IS connected, the calls are going through the device, and not my speakers.
It still pauses the music...
It could be either my car or the device. I've heard of other Subaru owners having issues with multiple devices in their car, just wasn't sure if it was a little of Column A and B. It seems likely enough it's a little bit of both.
Click to expand...
Click to collapse
My in-laws own a 2015 Forester so perhaps next time I see them I'll try to pair my 5X. May be a while before that happens though so don't hold your breath
2013 Honda Civic here (so cool, I know). I'm getting mixed results on it automatically connecting. Sometimes yes, but other times I need to connect manually. Yesterday, Bluetooth audio got really choppy in the car, and I had to restart in order to stabilize that again. Have not seen the choppiness issue with my other Bluetooth devices.
Sent from my Nexus 5X using Tapatalk
I had no problem with my Mazda 5 connecting to my Moto E on 4.4.4, but since the upgrade to 5.1 I now have to turn bluetooth off then back on every time I get in the car for it to connect. Also, the connection can drop. I tried deleting existing connection data from both car and phone, setting up from scratch, but it hasn't made any difference. Wish I could downgrade by phone's OS back to 4.4.4.
Might depend on the sound system. Reconnects to my 2013 VW Passat every time.
Sent from my Nexus 5X using Tapatalk
No issues in my Audi or aftermarket radio in the Subie... It sounds like you may not have calls being routed through the phone (based on your comment), maybe that is causing the connection issue? Something like only a phone connection is automatically connected (and the audio comes with it), but an audio connection is not?
I have a 2011 Mitsubishi Ralliart and i don't have any issues with my 5X auto connecting to the factory bluetooth system, my problem is the factory bluetooth is garbage since any time someone calls there is too much interference i can't hear what the other person is saying.
JC Why said:
I have a 2014 Ford Focus. The bluetooth will connect automatically, but I have noticed weirdness when placing calls. The car will take a while to initiate the call and then display an error saying "call cannot be completed". Then, 2 seconds later the call audio (ringing) will occur.
I am hoping that these are just some initial bluetooth issues that will be ironed out.
Click to expand...
Click to collapse
Exact same issue here but with a Kia. As soon as the phone "reacts" to a call being started on the headunit, the headunit says "call was hung up". As soon as the call is answered, it offers to be used for handsfree. It's as if the phone's "CallStatus" messages over bluetooth aren't correct
Subject crosstrek 2014, BlackBerry z10 never had an issue whatsoever, but since I got my 5x, I get half a connection (Bluetooth connects with no audio), with 6.0.1, no automatic connect... Blackberry's reputation may be downhill, but I sincerely miss its reliability and the hub...
Nexus 5X and 6P Uconnect 8.4 Grand Cherokee 2014
I recently started experiencing a similar issue.
I use my 6p for music and audio only, and my 5x for phone calls and sms.
About a week ago, they would stay connected as long as nothing was being streamed. However, as soon as I received a call on the 5X, the phone would lose BT connection to the system, and then connect back after about 30 seconds. It would do that throughout all of the calls, regardless of the length of each call. After the first 2 calls, I started streaming music from Google Play Music on my 6p, and the same thing would happen.
I removed Uconnect from both phones, and both phones from Uconnect. Paired them back again, and it is still doing the same thing.
I will try resetting the Uconnect to factory default later today and see if it has any positive effect, and will post my findings here.
If anyone else has a uconnect system with the same issue, please post it here, and we can try looking for a solution together.
Thank you,
So, somewhere in May I received the automatic update to Oreo 8.0. Hurray! Sadly though, that's when my bluetooth problems started:
It connects to my car, as normal. And I can make and receive calls, as always. But during the call my bluetooth connection with my car would just drop. If the person on the other end of the line is patient enough, I can just reconnect while driving and continue. But it will drop once each minute. It's very frustrating. This worked flawlessly before the update.
Funny thing is there are no issues at all when playing music of a portable speaker. I can even play spotify through my car's speakers without problems. The problem only presents itself during calls on the carkit. To make sure it's not the car, I tried some other phones. My wife's samsung, also with 8.0, worked perfectly. So does my daughters Iphone with IOS. My car is a Volvo C30 from 2012. It has built-in phone connectivity.
What I tried:
- Unpairing and pairing again.
- Hard reset. In combination with re-pairing.
- Using the developer options to use Bluetooth AVRCP 1.4. In combination with unpairing and re-pairing.
- Using the developer options to use Bluetooth AVRCP 1.5. In combination with unpairing and re-pairing.
- Disabling automatic bluetooth/wifi scanning in the location settings.
- It even went to the repair center for a different issue (unresponsive touch-screen) and the repair notes stated that they also installed the newest software. So I had hopes that this would resolve my carkit issue, but it didn't.
Do you guys know any more tricks for me to try?
I have an XA1 ultra with Oreo 8 as well (build 48.1.A.2.21) and I'm experiencing the same problems, but adding that mine disconnects also when streaming music. Other problem I'm experiencing after the Oreo update is that,when using my watch (LG G Watch R) paired with the phone, the sound streaming is just crap, with lots of jumps and bad audio quality. This is so frustrating that I'm seriously considering buying a new phone ( not from Sony, of course)
:crying:
Anyone?