Database Users

Bluetooth and Nougat

Anyone else on the newest 7.0 preview and unable to pair their bluetooth with their car?
Driving me nuts...hoping someone found a fix...

bongostl said:
Anyone else on the newest 7.0 preview and unable to pair their bluetooth with their car?
Driving me nuts...hoping someone found a fix...
Click to expand...
Click to collapse
Right after the DP5 installation, I had to unpair the phone and car (2016 Mazda) because the phone would never connect. It was no where near as easy as that sounds, took me the better part of 30 minutes because of repeated "unknown errors" coming from the car.
The phone paired up just fine but I still have frequent and completely unexplained dropouts on literally every Bluetooth device I have (headphones, Moto 360, car and the list goes on). So far this has been the absolute worst of the previews for BT that I have ever seen.
But then, if you read around here, it sounds like there were a lot of these that had flaky BT hardware. Have not exchanged mine, but that has certainly been my experience since I bought this back in December.

I have no issues with Bluetooth and the latest DP. I have my phone connected to a Kenwood deck.
Sent from my Nexus 6P using Tapatalk

I wonder if I have flaky BT hardware? Mine was a launch phone and it has worked perfectly in my Toyota since day 1. However I've recently bought a fitbit type band and with that application (veryfit 2.0) installed and connected to the band then if I make a call in car it drops the BT after about 30 seconds with an error message on screen saying 'corrupted probe message'. I can manually reconnect the call (it's still active on the phone) but after another 30 seconds or so it repeats the cycle. Have upgraded to Nougat Dev Preview NPD90G but still the same. Removing the app and its binding (it binds in the app not the phones BT devices in settings) and rebooting the phone resolves the issue. Tried again with a proper fitbit and the issue is identical.
I will RMA it to see if I get another one that works. Now to figure out how to put it back to stock marshmallow. gulp.

I have the same issue pairing to my car's Bluetooth keep pairing failed

bongostl said:
Anyone else on the newest 7.0 preview and unable to pair their bluetooth with their car?
Driving me nuts...hoping someone found a fix...
Click to expand...
Click to collapse
I had this same issue, I flashed the system file again and wiped the cache and dalvik. It seems to be ok now.

Check this solution. Pair with '0000' worked for me.
http://forum.xda-developers.com/nexus-5x/help/issue-android-nougat-bluetooth-issue-t3446073

Since switching from my Nexus 5 with 6.0.1 to a Nexus 6P with 7.0 I am also suffering from bluetooth issues. Pairing itself is not a problem but the connection sometimes drops, controls in my car don't work properly, remaining track time is not shown, etc. Haven't even tried to make calls yet. If I can't find a solution I'll probably be going back to 6.0.1.
The proposed '0000' solution is not working for me as I cannot change the PIN on my Seat Leon (2016). The PIN is autogenerated and shown on both displays to be confirmed upon pairing.
Has anybody tried flashing the latest 6.0.1 radio image and use it with a 7.0 system?

After Android 7.1.1 update - Bluetooth In-Car Connectivity PROBLEM

Hi all
Yestarday i updated my Nexus 6p to Android 7.1.1 OTA.
After that i am having problem with my Bluetooth Car stereo Connectivity, it's connect for a second and then disconnect.
Is there any solution or fix ?

fectivi said:
Hi all
Yestarday i updated my Nexus 6p to Android 7.1.1 OTA.
After that i am having problem with my Bluetooth Car stereo Connectivity, it's connect for a second and then disconnect.
Is there any solution or fix ?
Click to expand...
Click to collapse
No problem with mine. I did a factory reset after installing the update though. Maybe you could clear connected devices and try again.

It's seems to be only with my android 4.4 car head unit, i tried a several other Bluetooth devices and i success to connect, don't know why only with my car it's not working although it works until yesterday before the 7.1.1 OTA update...

http://forum.xda-developers.com/nexus-6p/help/contacts-syncing-via-bluetooth-to-car-7-t3514174
I'm having contact sync issues now I'm on 7.1.1.

2012 GMC Sierra. No Bluetooth issues at all with MM or Nougat 7.0. Side-loaded 7.1.1 OTA this morning, now my Bluetooth connection drops/connects repeatedly (every 2-3 seconds). Have deleted the BT device from phone & repaired, wiped cache, & rebooted with no success. Stock/no root here.

2016 Honda Accord. Won't sync call history and contacts. Cannot make or receive calls. Worked perfectly in 7.0. What's funny is that BT audio streaming still works fine. The car does have Android Auto built in and calls work fine through that so it's a weird issue. I don't use Android Auto all the time so it is definitely annoying

I Google this issue , and it's seems to be a much big problem. A lot of users reports this issue:
https://productforums.google.com/forum/#!topic/nexus/Mv5Hc6Lw7rA;context-place=forum/nexus
And this one:
http://www.techtimes.com/articles/184068/20161029/users-of-google-pixel-and-nexus-devices-running-android-7-1-nougat-report-pairing-issues-with-bluetooth-in-cars.htm

I have been facing the same problem too. My 6P connects & then disconnects to the media-nav of Renault Duster. I have tried factory resetting both, the phone & Car media player with no results.

Bluetooth connects no problems in 7.0 to my 2011 Chev Cruze. Update to 7.1.1, drops every second. Flash factory image of 7.1.1 in hope that it might have been an OTA issue, and no luck. Flash 7.0 factory image, and bluetooth works and stays connected with my car. But after downgrading I lost the ability to restore all my apps and data, just had the Gapps. There wasn't an option to restore the info from my 6P previous to factory imaging it.. So now I have to manually search the apps out and reinstall them.
I just don't understand how Google keeps screwing this up. I'm grateful to have a Nexus and I can rescue myself, but it would be a piss off if I was not aware of how to get myself back to a place when the phone actually WORKED. It's just nonsense.
Post in the bug tracker and star it, so they know it's important to look into: https://code.google.com/p/android/issues/detail?id=225774

I am on stock rom without root, can any one with 7.1.1 custom rom can tell us if that problem exists?

It is a widely spread problem. Almost everyone I've seen trying to connect a N6P or N5X to a car after any update to 7.1.1 (was also present on the Public Betas) has this problem.
I've been having this since the first Beta. got back to 7.0 and everything was normal. got final public version OTA and the problem is back.
Tried to flash factory version (to see if it was an OTA problem) and problem persists. Even after several full wipes.
https://productforums.google.com/fo...ce=footer#!msg/nexus/Mv5Hc6Lw7rA/bLJjs-W8DQAJ
Lets put some pressure on Google about it.

Same problem here, having loads of issues with a 4.4 head unit in my car. Only issues with call (connect-disconnect every couple of seconds) connection with my bluetooth headphones is great though.

Here is a screen record:
https://youtu.be/WPBOBuOZviE

[Guide] Fool/Noob proof way to do clean installs on Nexus Devices
http://forum.xda-developers.com/nexu...talls-t3518311
try this clean install should work i encountered a problem in my car too
---------- Post added at 01:30 AM ---------- Previous post was at 01:30 AM ----------
[Guide] Fool/Noob proof way to do clean installs on Nexus Devices
http://forum.xda-developers.com/nexu...talls-t3518311
try this clean install should work i encountered a problem in my car too

Can someone test this?
Can someone that is on 7.1.1 test something for me as I rolled back to 7.0. I'm not exactly sure if it is a fix, but I do know it has fixed other issues in the past.
Go to Settings>Battery>Tap the three dots top right>Battery optimization>There is a drop down menu there that says "Not optimized", tap on that and switch to "All apps">Look for "Bluetooth Share" and tap on it>Select Don't optimize
Try then to pair again with your vehicle.
If someone could test on Nexus 6p, 5x on 7.1.1 that would be much appreciated.
Thanks!

TREMER said:
Can someone that is on 7.1.1 test something for me as I rolled back to 7.0. I'm not exactly sure if it is a fix, but I do know it has fixed other issues in the past.
Go to Settings>Battery>Tap the three dots top right>Battery optimization>There is a drop down menu there that says "Not optimized", tap on that and switch to "All apps">Look for "Bluetooth Share" and tap on it>Select Don't optimize
Try then to pair again with your vehicle.
If someone could test on Nexus 6p, 5x on 7.1.1 that would be much appreciated.
Thanks!
Click to expand...
Click to collapse
I tried it. Didn't work. Bluetooth still broken

Same issue here. Nexus 6P OTA update to 7.1.1 now 2016 Honda Accord has issues with phone calls. No caller ID on head unit. The head unit rings & rings even after I manually answer the phone. I have to hit the ignore button on the screen to get the head unit to stop ringing. Then I cannot use the head unit for anything (radio, satellite, streaming) until I turn off the bluetooth in the phone.
WTF Google?

Same problem here on my Renault clio 4 with medianav system. Phone just keeps connecting and disconnecting over and over. The headset on my motorcycle helmet (Maginon MBH-100) just functions like normal.

TREMER said:
Can someone that is on 7.1.1 test something for me as I rolled back to 7.0. I'm not exactly sure if it is a fix, but I do know it has fixed other issues in the past.
Go to Settings>Battery>Tap the three dots top right>Battery optimization>There is a drop down menu there that says "Not optimized", tap on that and switch to "All apps">Look for "Bluetooth Share" and tap on it>Select Don't optimize
Try then to pair again with your vehicle.
If someone could test on Nexus 6p, 5x on 7.1.1 that would be much appreciated.
Thanks!
Click to expand...
Click to collapse
It's working on my honda it also did before
---------- Post added at 08:53 AM ---------- Previous post was at 08:52 AM ----------
Guys if you have a Honda vehicle don't worry 7.1.1 works perfectly

I following the topic on Google Nexus Help Forum, here is the announcement of the Nexus Community Manager.
"‏Orrin - Nexus Community Manager:
Hey Everyone,
Thank you for your reporting your issues with bluetooth connectivity on 7.1.1. We made certain changes to support a communication standards upgrade in 7.1.1, which seem to have resulted in interoperability issues for some users. We have identified a fix which we should be able to release soon.
Some of you have mentioned that reverting back to 7.0 Nougat fixes the issue, so that is an option to try until the issue is fully resolved in a future OTA update.
We will keep you all updated!"

Bluetooth issues

Since the previous two updates on my Verizon V20 were installed (VS99518A & VS99519A) running 7.0 , I have been having bluetooth issues where there are momentary pauses while connected to BT earphones and random "rustling" sounds when I am connected to my car stereo (A2DP). There are even times the bluetooth does not reconnect (have to manually select the paired device at the pop-up).
I have already performed a factory reset and it still happens. These issues do not occur on other android phones so it can't be my stereo and bt earphones' at fault.
Any ideas? What should I check?
Thanks.

I really wish I could help you. Ive been having the same issues. Please follow up if you figure it out and I will as well

Same here
The 7.0 update took a while to get to me but now that it has, I'm not impressed and wish I could revert.
Immediately after I started noticing the same issues as OP. In addition, I can no longer BT FTP send to my desktop but I can receive from the desktop.
I've tried quite a number of things to resolve but none have. Several soft resets, hard reset, network reset, factory reset, reset of desktop settings (although apparently not needed a SIM-less Galaxy S4 does NOT have issues with BT FTP to the same desktop....
Attempting to pair the two, the S4 can see the V20 but the V20 does not recognize the S4.
I believe it is 7.0 update related because all was fine prior and the issues were noticed just 20 minutes after.

Bluetooth wont connect to multiple devices

Running my Mi A1 with stock ROM but having numerous bluetooth issues.
It will connect to my earphones without issue, and to my keyboard. However it will not connect to my Ford Fiesta, or to my Amazon Echo. Tested my oneplus 3 with these to confirm and they work fine, so its purely the Mi A1.
I have tried clearing bluetooth cache and forgetting the link.
Any other steps to resolve this?
Generally the devices never even connect at all, says connecting then gives up.
Update: ran the latest software update so I am now running 8.1, still not able to connect to 99% of the devices I try, says pairing then gives up. Any ideas?

I have some BT issues as well, this is my experience.
With Oreo 8.1 stable (updated OTA from 8.0) I was unable to pair further BT devices ("wrong PIN or passkey"),
although those paired previously (some from Nougat) still worked. Neither clearing BT cache and data or resetting
the network settings helped. I saved a couple of logcat logs during the unsuccessful attempts to pair a BT headphone and a BT speaker that worked earlier.
After a full factory reset BT pairing starts working again, although it seems that this happens only for a while,
then it may stop again, maybe I have some interfering app or whatever. I am not trying to delete some paired device
to check again.

This issue is still ongoing, tried more devices and same issues.
Another one I tried is connecting my phone to a bluetooth keyboard (Anne Pro). This works fine, however now the phone keeps popping up with "Please connect a keyboard".

azboxgo said:
I have some BT issues as well, this is my experience.
With Oreo 8.1 stable (updated OTA from 8.0) I was unable to pair further BT devices ("wrong PIN or passkey"),
although those paired previously (some from Nougat) still worked. Neither clearing BT cache and data or resetting
the network settings helped. I saved a couple of logcat logs during the unsuccessful attempts to pair a BT headphone and a BT speaker that worked earlier.
After a full factory reset BT pairing starts working again, although it seems that this happens only for a while,
then it may stop again, maybe I have some interfering app or whatever. I am not trying to delete some paired device
to check again.
Click to expand...
Click to collapse
Did you ever manage to isolate the cause of this? I still can't connect to devices

Fenwick17 said:
This issue is still ongoing, tried more devices and same issues.
Another one I tried is connecting my phone to a bluetooth keyboard (Anne Pro). This works fine, however now the phone keeps popping up with "Please connect a keyboard".
Click to expand...
Click to collapse
I have never had a problem but have read in several threads people say they have trouble pairing with Bluetooth while Wifi is turned on, not saying it will work but try turning off the Wifi and maybe data too and see if it helps, other have reported it does.

Done another factory reset, issue still persists. Have tried removing all Bluetooth devices, wifi, and mobile network off. Still unable to connect to a bunch of devices.

Tried a bunch of different things, but still can only connect bluetooth to my earphones, and sometimes Amazon Echo. Everything else will just say connecting and then stop.

Lost Bluetooth Media function after August 2018 security update

Hi all,
I sideloaded the August 2018 security update yesterday, and I'm noticing that the bluetooth media function is no longer working.
When I view paired devices I see "(no media)" next to them, and the bluetooth receiver (in this case, two car stereo's) also report that the device is not connected.
My phone still pairs and calls can be made and received without issue.
Checking the bluetooth settings on my phone I have media audio switched on. Toggling it makes no difference.
I've completely removed the pairing from the phone and car and re-paired successfully but still without the option to stream media.
Before I go down the road of wiping the phone and installing the full factory image I thought I would ask here if anyone else has experienced this?
Some googling revealed it has happened to other Android phones over the years with varying rates of success from re-pairing to factory resetting.
As a side note, should I be updating the driver binaries that are available on the Android Factory Images page when I sideload these updates?
PS. I have an unlocked bootloader with custom recovery using TWRP 3.2.3.0 and root access using Magisk 16.7.