I've had my Nexus 6 since Jan. 1, upgrading from an HTC One M7 GPE running 5.0 Lollipop. I experienced Bluetooth connectivity issues with the HTC One after upgrading to 5.0L from 4.4KK, and I knew they were 5.0 related, so I expected somewhat of the same when getting the N6. My problem is, even after upgrading my N6 to 5.01 and then 5.1, most of my Bluetooth issues still exist. I'm trying to figure out if they are indeed software related, or if maybe I have a defective BT radio. I'm rooted, running stock 5.1 LMY47M, with ElementalX Kernel and Nova Launcher. Here is a list of the issues I'm having with my N6 and Bluetooth:
1. Constant dropped connection to my car's bluetooth. Will connect when car is first powered on, then drops connection after about 20 seconds only to reconnect 30 seconds after that, then drop again within 30 seconds. Sometimes it will connect and stay connected for hours. This issue didn't exist with my HTC One running 4.4KK, but did happen intermittently after upgrading it to 5.0L. This issue also doesn't seem to exist when connecting my wife's N5 running 5.1 LMY47D.
2. Problem #1 also seems to exist when connecting my N6 to my Nvidia Shield Tablet running 5.0L, but not as persistent as with Car BT.
3. When my N6 does connect to my Nvidia Shield Tablet, I can send messages using joaoapps' AutoRemote over Bluetooth from my N6 to my Tablet, but not from my Tablet to my N6. Both phone and tablet are configured correctly. This one has me completely stumped and I've spent hours troubleshooting it before just giving up.
3. Audio stuttering when connected to my BT headphones. Again no issue when using said headphones with HTC One 4.4KK or wife's N5 5.1 LMY47D.
3. Bluetooth seems to turn off randomly. At first I thought it was one of my Tasker profiles, but problem still exists even after uninstalling Tasker.
4. My N6 will not connect to my BT OBDII adapter. N6 pairs with adapter, but adapter does not work with Torque or any other ODBII app. HTC One 4.4KK, wife's N5 5.1 LMY47D, and my Nvidia Shield tablet running 5.0L all connect with no issue.
I have tried every suggestion on threads (Reboot, clear Bluetooth Share cache, clear Bluetooth Share Data, forget all connections and re-pair, Bluetooth Auto Connect app) with no luck. I love my N6, but I've hated these BT issues since day one and I've crossed my fingers with every Lollipop update that they would be resolved, to no avail. I'm wondering if anyone (or everyone) is experiencing similar issues with BT, or is it just my N6, and I should return it for a new one before warranty expires. Thanks.
I only use my N6 Bluetooth with my car (ford sync) and occasionally my home phone. I haven't had any issues. Use it everyday on my commute to and from work.
Since you're experiencing this with multiple devices id assume its you phone too. Maybe contact google for warranty replacement?
Are you by any chance wearing a smartwatch? I had similar problem with my OnePlus One and narrowed the problem down to my Moto 360 smartwatch connection. If I didn't have my smartwatch on while in the car, my auto connection worked fine.
Recently, I switched to a Nexus 6 and find bluetooth to be even worse with this phone. Seems as if the signal being broadcast is too weak. Headset audio will start to breakup, with a clear LOS, after just 10-12 ft. Also, just putting my phone in my pocket will case choppiness. With this phone, however, I have yet to determine whether it is my smartwatch that is causing the problems as well or not.
Mit Hipster said:
Are you by any chance wearing a smartwatch? I had similar problem with my OnePlus One and narrowed the problem down to my Moto 360 smartwatch connection. If I didn't have my smartwatch on while in the car, my auto connection worked fine.
Recently, I switched to a Nexus 6 and find bluetooth to be even worse with this phone. Seems as if the signal being broadcast is too weak. Headset audio will start to breakup, with a clear LOS, after just 10-12 ft. Also, just putting my phone in my pocket will case choppiness. With this phone, however, I have yet to determine whether it is my smartwatch that is causing the problems as well or not.
Click to expand...
Click to collapse
No, not using a smartwatch yet. Holding off on purchasing one until I can get this bluetooth mess figured out. I did another factory wipe and rolled back to 5.01, this time staying encrypted (used no force before). Seems to be a little more stable this time, although I have no way of telling if it's because of encryption or just luck. I think it's just coincidental, I don't see how encryption would have any effect either way. I applied the 5.1 update to LMY47M and so far much more stable than before. Again, I don't know why. I can say I am rather disappointed with Google and the Nexus 6. My wife's Nexus 5 is far more stable and I can't believe Google would allow a 'flagship' device to remain this buggy. I never had any of these issues with my HTC One. I traded up to the Nexus 6 for the Google experience, no bloatware, fast updates, etc., thinking that meant more stability. It seems that trading bloatware for the Nexus experience has an unexpected consequence of being a beta-tester for Google.
Bluetooth is different on the Nexus 6 for sure.
lords8n said:
No, not using a smartwatch yet. Holding off on purchasing one until I can get this bluetooth mess figured out. I did another factory wipe and rolled back to 5.01, this time staying encrypted (used no force before). Seems to be a little more stable this time, although I have no way of telling if it's because of encryption or just luck. I think it's just coincidental, I don't see how encryption would have any effect either way. I applied the 5.1 update to LMY47M and so far much more stable than before. Again, I don't know why. I can say I am rather disappointed with Google and the Nexus 6. My wife's Nexus 5 is far more stable and I can't believe Google would allow a 'flagship' device to remain this buggy. I never had any of these issues with my HTC One. I traded up to the Nexus 6 for the Google experience, no bloatware, fast updates, etc., thinking that meant more stability. It seems that trading bloatware for the Nexus experience has an unexpected consequence of being a beta-tester for Google.
Click to expand...
Click to collapse
I also use Ford Sync system. For years it has been reliable and worked flawlessly. But starting with the Nexus 6, some of the common applications I use when mobile started crashing the bluetooth stack and giving the error, "Bluetooth Sharing as stopped working."
Before the Nexus 6 which is the first device I've owned with Lollipop, this never happened. The developer of the SMS texting app that is the main one affected by this, has tried everything to resolve the issue but he and I are now beginning to believe it is something baked either into the phone or lollipop, but before this device I never had any problems with bluetooth. I even went as far as to replace my HU in the car with the new pioneer that supports Android Auto, but to my chagrin, it still crashes on that head unit whenever the SMS reader trys to log off and switch back the stream to media. And unfortunately Android Auto currently does not support Pandora which is a must have for me. Pandora runs perfect on the new HU as it did on the Ford Sync as well, but the SMS reader causes BT sharing to error on both devices since the Nexus 6 and Lollipop, so there is something going on with the bluetooth stack and unfortunately no one I can find has any information about what has changed. Hoping Android Auto will soon add Pandora, but Pandora has not given any time estimation about when that will happen.
Mit Hipster said:
Are you by any chance wearing a smartwatch? I had similar problem with my OnePlus One and narrowed the problem down to my Moto 360 smartwatch connection. If I didn't have my smartwatch on while in the car, my auto connection worked fine.
Recently, I switched to a Nexus 6 and find bluetooth to be even worse with this phone. Seems as if the signal being broadcast is too weak. Headset audio will start to breakup, with a clear LOS, after just 10-12 ft. Also, just putting my phone in my pocket will case choppiness. With this phone, however, I have yet to determine whether it is my smartwatch that is causing the problems as well or not.
Click to expand...
Click to collapse
Funny that you mention that. Previously used my Nexus 6 in the car with no issues. Only thing that changed is that I started pairing with a smartwatch in addition, and now my Nexus 6 crashes a few minutes into using Spotify over bluetooth. Complete automatic reboot.
EDIT: Yep, can definitely confirm the combination of the smartwatch and bluetooth audio device kills my phone. Had no trouble without the smartwatch.
EDIT 2: Turns out Google just sucks at bluetooth. Phone can crash regardless, it's just more likely with the smartwatch.
EDIT 3: RMA'd the phone and the new one works perfectly. Turns out it wasn't the software after all, or maybe the watch update helped.
I don't know if this is the same issue or not, but....
Ever since I got my Nexus 6 I have had bluetooth issues with both my cars. One has a Pioneer headunit (2014 model, not Android Auto), the other is a 2014 Subaru Forester with stock head unit.
In both cases there are days when it works perfectly. Then there are other times when it's a nightmare.
With the Pioneer headunit, bluetooth audio will be playing for a brief period (maybe 30 seconds?) and then something will happen and the headunit will play a repeated beep (bing bing bing bing bing bing) till I turn off bluetooth on the phone, wait a minute or two and reconnect.
With the Forester's headunit, similar situation - i'll be playing audio and it will just drop out. Maybe 60 seconds later it may come back (sometimes). Same applies to telephone calls via the headunit with bluetooth.
The same 'issue' appears with both headunits with one playing a beep when it happens the other dead silence, but both dropping in and out whether it's bluetooth audio or a call.
N6 running latest firmware. Problem has existed since I got it last year. Recently unlocked and rooted, but hasn't made a difference.
I don't know if this is the same as my problem, but it is the closest thread I could find, so I'll post here.
I've had my Nexus 6 about a week. Running 5.1.1, unlocked bootloader and rooted. I've been using a bluetooth headset for phone audio and media audio. It had been working, though I have experienced some audio dropout and stuttering with media audio. I had not been able to determine if that was a bluetooth problem or an app problem, but now I am leaning towards thinking it was a bluetooth problem because of what is now happening.
Today, media audio just stopped playing through my headset. Phone audio is working. I've tried rebooting, I've tried forgetting and re-pairing, I've tried a different headset and I cannot get media audio to play over bluetooth.
I am having the same problem with Nexus6 I have tried two different Plantronics voyager bt headsets and a Motorola Sliver. Motorola said it may be a bluetooth antenna problem
Did a resit on phone and Motorola Bluetooth
I really need bluetooth connectivity so I am stuck
Only other option is either find someone to open up the phone and check the antenna or do it myself maybe replace it myself or look for another phone and use this one as a backup
What would you all suggest?
Thanks
Has anyone tried the GS6 with Android Auto? I recently upgraded the head unit in my car to the Kenwood DDX9702S with android auto support. I set everything up and it seems to work great for a few minutes however it intermittently disconnects. For instance one minute Im streaming spotify and utilizing google maps - next minute - deck goes blank (or sometimes goes back to the home screen on the deck), music stops and phone makes the usb disconnect sound. I've tried a second cable with no change. Longest I think its worked is maybe 10 minutes, however I tried my work phone which is a GS5 on sprint - and it works flawlessly. Anyone know if this is a known issue with the GS6?
Thanks in advance!
Hi all, I am able to connect my Mi 9 to my car android head unit with hotspot no problem at all. Connection is fine, but there is no internet on my headunit. When I hotspot with my Nexus 6P it works fine. Does anyone have any suggestions? I have looked at the phone wap settings but they are all good because data works on my phone, so there is a problem on the mi9 to head unit.
I have my Mi 9 turning Hotspot on automatically when it senses my car Bluetooth pairing, in order that my in-car Echo Dot can reach the internet - it works fine every time.
Have you set up something unusual in the head end like a fixed IP address that doesn't match the address range the phone gives out?
There is no possible ip settings on the head unit. When I had this issue once with my Nexus6P it was due to a problem with android 8.1 when upgraded. When I reverted back to the previous version, it worked fine. So I am having the same issue that's why I was thinking it might be an issue with the software. But I will try check out your suggestions incase there are some hidden settings. Thank you
bungalowbill said:
I have my Mi 9 turning Hotspot on automatically when it senses my car Bluetooth pairing, in order that my in-car Echo Dot can reach the internet - it works fine every time.
Have you set up something unusual in the head end like a fixed IP address that doesn't match the address range the phone gives out?
Click to expand...
Click to collapse
How did you set this up? Did you root and use tasker with hotspot nougat fix?
Everything is connected with just hotspot from my phone and wifi on the headunit. It worked fine with my old Nexus 6P phone. Pic attached
Has anyone experienced bluetooth issues since yesterday's (January patch) update? My device remains connected to my watch, but refuses to connect to my car audio. I hope I'm not left waiting until February for a potential fix.
Pumpino said:
Has anyone experienced bluetooth issues since yesterday's (January patch) update? My device remains connected to my watch, but refuses to connect to my car audio. I hope I'm not left waiting until February for a potential fix.
Click to expand...
Click to collapse
Exact same problem here, Pixel 4a (not 5G) from Italy and Ford Focus MK3 2011 bluetooth. Everything OK with my Galaxy Band 2 but the car connects and disconnects continuosly. I unpaired the phone and then I wasn't able to reconnect until I disconnected car's head unit fuse (the car won't give me the PIN for connecting). After the reset I was able to connect again wit the Pixel 4a, but it showed the same loop of connections/disconnections. Tried with a Nokia 4.2 and everything works, so January update must have messed something with the "old" Bluetooth standards
bandagufo said:
Exact same problem here, Pixel 4a (not 5G) from Italy and Ford Focus MK3 2011 bluetooth. Everything OK with my Galaxy Band 2 but the car connects and disconnects continuosly. I unpaired the phone and then I wasn't able to reconnect until I disconnected car's head unit fuse (the car won't give me the PIN for connecting). After the reset I was able to connect again wit the Pixel 4a, but it showed the same loop of connections/disconnections. Tried with a Nokia 4.2 and everything works, so January update must have messed something with the "old" Bluetooth standards
Click to expand...
Click to collapse
I'm glad it's not just me then (I mean that in the nicest possible way). I unpaired my phone from my Toyota Camry too and when I attempt to pair it, the phone says it's connected but the car remains searching. I tried with my Galaxy S21, and it worked fine. I'd also used the 4a 5G in the car an hour or two before installing the update, so I'm confident that it's the update that broke it.
I don't know if I should wait a month (which is annoying, as it means no music, Google Maps or phone calls through the car audio), or flash a custom ROM. Not having it work for (at least) one month is pretty bad.
Exactly, pretty bad. I chatted with the Google Pixel help and they told me to reset the phone connections and retry. I've done it (VERY annoying because it also resets ALL the Wi-Fi stored passwords and unpairs every Bluetooth device on the phone). I'll try to pair it again with the car when I'll go home later and I'll let you know
Nope, even after the reset of all phone's connections the behaviour with my car remains unchanged. Let's hope that February update fixes everything
bandagufo said:
Nope, even after the reset of all phone's connections the behaviour with my car remains unchanged. Let's hope that February update fixes everything
Click to expand...
Click to collapse
I might look into whether other Pixel models are impacted, too. I'll let you know if I find out anything.
Some Google Pixels are failing to connect to in-car Bluetooth after installing January's security patch
No, it's not just you — some Pixel owners are experiencing Bluetooth connection issues after updating to January's patch
www.androidpolice.com
The Pixel's January software update has broken auto Bluetooth pairing for some
Some Pixel owners are experiencing an issue with Google's latest software update that is breaking auto Bluetooth pairing.
www.androidauthority.com
When i had my pixel 5, the Bluetooth automatically turned on after a few minutes of driving, i can't find how to do that in pixel 7. Options does not looks to be the same...
How can i do that or what can i use as an alternative?
Android Auto as alternative
That's why i want Bluetooth on, if it's activated android auto will connect directly.
You can probably do it in Tasker, but I am not sure how you would detect you are in the car. Constant GPS checking would be power hungry.
Assuming you have home WiFi, a partial solution would be to turn Bluetooth on when it no longer sees your router. You can even turn it back off when you get home.