Hi all,
Since upgrading to Android 7.x, I've had problems connecting my phone to other Bluetooth devices, particularly my car heading it for hands-free. The headunit in one car works fine, the other car keeps connecting and disconnecting after about 1-2seconds in a continual loop. Before 7.x it was connecting fine. Even now my phone makes the notification sound of connecting when I'm in that car even when I choose 'forget this device' on both hu and phone, only way to stop the notifications is to turn bt off.
I've googled and found it's quite a common issue, but yet to find a solution. I joined the beta program and update everytime but yet to fix it.
My question is, will this problem be fixed if I install a custom rom like PureNexus or is it a flaw in 7.x affecting every rom? If that is the case, is it possible to downgrade to 6.x? I really want to be able to connect to my hu with hands free again, it's been months now with no luck!
Sent from my Nexus 6P using Tapatalk
glenb83 said:
Hi all,
Since upgrading to Android 7.x, I've had problems connecting my phone to other Bluetooth devices, particularly my car heading it for hands-free. The headunit in one car works fine, the other car keeps connecting and disconnecting after about 1-2seconds in a continual loop. Before 7.x it was connecting fine. Even now my phone makes the notification sound of connecting when I'm in that car even when I choose 'forget this device' on both hu and phone, only way to stop the notifications is to turn bt off.
I've googled and found it's quite a common issue, but yet to find a solution. I joined the beta program and update everytime but yet to fix it.
My question is, will this problem be fixed if I install a custom rom like PureNexus or is it a flaw in 7.x affecting every rom? If that is the case, is it possible to downgrade to 6.x? I really want to be able to connect to my hu with hands free again, it's been months now with no luck!
Click to expand...
Click to collapse
Hello,
Backup your data's and try to factory reset.
You can install a custom ROM, but I guess it doesn't fix drivers issues which are closed sources.
Otherwise you can downgrade to a 6.x stock firmware.
Option 1 and 3 needs you to unlock your bootloader. Backup important datas, unlocking bootloader wipe all datas!
Good luck...
glenb83 said:
Hi all,
Since upgrading to Android 7.x, I've had problems connecting my phone to other Bluetooth devices, particularly my car heading it for hands-free. The headunit in one car works fine, the other car keeps connecting and disconnecting after about 1-2seconds in a continual loop. Before 7.x it was connecting fine. Even now my phone makes the notification sound of connecting when I'm in that car even when I choose 'forget this device' on both hu and phone, only way to stop the notifications is to turn bt off.
I've googled and found it's quite a common issue, but yet to find a solution. I joined the beta program and update everytime but yet to fix it.
My question is, will this problem be fixed if I install a custom rom like PureNexus or is it a flaw in 7.x affecting every rom? If that is the case, is it possible to downgrade to 6.x? I really want to be able to connect to my hu with hands free again, it's been months now with no luck!
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I suggest you fully wipe your phone and install the May Google image (N2G47O). There was a major BT rework introduced with 7.1.2 that fixed an issue just as you describe. I went 5-6 months without being able to connect with one of my cars (2014 Cadillac). When the 7.1.2 beta came out I did a fresh install and it immediately fixed the problem. BT has worked flawlessly since.
glenb83 said:
Hi all,
Since upgrading to Android 7.x, I've had problems connecting my phone to other Bluetooth devices, particularly my car heading it for hands-free. The headunit in one car works fine, the other car keeps connecting and disconnecting after about 1-2seconds in a continual loop. Before 7.x it was connecting fine. Even now my phone makes the notification sound of connecting when I'm in that car even when I choose 'forget this device' on both hu and phone, only way to stop the notifications is to turn bt off.
I've googled and found it's quite a common issue, but yet to find a solution. I joined the beta program and update everytime but yet to fix it.
My question is, will this problem be fixed if I install a custom rom like PureNexus or is it a flaw in 7.x affecting every rom? If that is the case, is it possible to downgrade to 6.x? I really want to be able to connect to my hu with hands free again, it's been months now with no luck!
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
You need a completely clean 7.1.2 install.
There is a setting somewhere (I don't know where) left over from previous OS version or app.
My phone was doing the exact same thing with my BMW, and only my BMW.
Clean install of 7.1.2 fixed the issue for me.
I wiped my 6P today hoping it would resolve my BT issues with my 2015 Toyota Highlander. No such luck, it still boots my Toyota in an endless loop until I disable the BT on the phone. The car works fine on my Samsung S3.
What is the process to do a Clean install of 7.1.2?
Related
Hello,
Where my bluetooth previously worked on Android 5.0, ever since upgrading my i9505 to 6, Bluetooth does seem to connect, but calls still go though the speaker and I cannot change it to Bluetooth mode (my car, however, sees it). And when hanging up the phone, the phone will say "Hanging Up" yet still stay connected for what seems to be an indefinite amount of time - or until I restart the phone. Needless to say, callers on the other end cannot hear me. And, when playing music, the car's head unit does show that it's playing but again, music comes through the phone's speaker only.
Any advice? I've already tried flashing AOSP 6.0 and Kushan CM 13.0 and it's the same thing on both.
Thanks.
DJRepresent said:
Hello,
Where my bluetooth previously worked on Android 5.0, ever since upgrading my i9505 to 6, Bluetooth does seem to connect, but calls still go though the speaker and I cannot change it to Bluetooth mode (my car, however, sees it). And when hanging up the phone, the phone will say "Hanging Up" yet still stay connected for what seems to be an indefinite amount of time - or until I restart the phone. Needless to say, callers on the other end cannot hear me. And, when playing music, the car's head unit does show that it's playing but again, music comes through the phone's speaker only.
Any advice? I've already tried flashing AOSP 6.0 and Kushan CM 13.0 and it's the same thing on both.
Thanks.
Click to expand...
Click to collapse
Simple
6.0 Rom bugs.
Wait until they are fixed
They all are based on the same code. So if one roms has it they all have it.
Keep in mind that MM is brand new so you just have to be patient for it to be fixed.
DJRepresent said:
Hello,
Where my bluetooth previously worked on Android 5.0, ever since upgrading my i9505 to 6, Bluetooth does seem to connect
Thanks.
Click to expand...
Click to collapse
In a strange coincidence, I had all sorts of trouble on my i9505 with Bluetooth on 5 but is mostly resolved on 6 (CM 13 official).
mr.b00tl00p said:
In a strange coincidence, I had all sorts of trouble on my i9505 with Bluetooth on 5 but is mostly resolved on 6 (CM 13 official).
Click to expand...
Click to collapse
same here, but now i have new one's like connecting my mi band at all :/
I also had problems with BT with the CM13 Official Nightlies, and also with the Resurrection Remix.
But I now use the JDCTeam 6.0.1 ROM, and I don't have BT issues, I only use my BT in car, but I can send and receive phone calls, and also stream my music via BT.
Furthermore, almost everyone complains about the no sound with the calling issues.
I also had those issues back to the official CM13 and the RR 6.0.1 versions.
For me, this ROM is really good, you would maybe give it a try.
I use an old bootloader, the FNB8, but it seems to work pretty fine.
I recently purchased the N6P to replace my dying N4. The transition from one device to the other has gone pretty well, except for one issue. My N6P is unable to find the bluetooth signal from my Ford Fusion. Upon turning on bluetooth and searching for devices, the N6P cannot find the Ford Sync signal. I've rebooted the phone many times, Ive tried it many times in safe mode with no success, Ive turned the Sync's bluetooth on and off numerous times, the phone is still unable to detect it. I have also tried deleting all the paired devices on the Sync settings and had no luck with the N6P working. Aside from a factory reset of the phone, what else can I do?
My N4 was able to connect to the Sync right up to when I stopped using it. My fiancee's Samsung Galaxy (something) can detect, connect, and function with the Sync's bluetooth. I am beginning to think its something with the N6P. Ive tried it on all three versions of the OS Ive had on the phone. The original OS version didn't work when I first powered up the N6P, the next version of the OS i updated to didn't work, and this morning the phone ran the latest update and the bluetooth doesnt work.
I'm at a loss, I'm ready to return this phone and go back to my dying N4.
Edit: I am currently running Android 6.0.1.
My wife's N5x has the same problem with our ford sync, I think its related to the bluetooth disconnection bug I've had since the may update.
You can still connect it by opening the bluetooth screen on your phone so that it is visible to other devices and in the sync setup tell sync to search for devices and select your nexus phone.
My wife and I both own Nexus 6p's. I just bought a brand new Ford F-150 and my wife has a 2014 Toyota mini van (forget the model name off the top of my head, but still a fairly new vehicle). Neither one of our Nexus 6p's will connect to with vehicle. Prior to our Nexus 6p's (which I really had to talk my wife in to getting a Nexus 6p) our LG G4 and Note 5 connected flawlessly. I even bought a Bluetooth thing that plugs in to my trucks aux and that works after turning the Bluetooth on and off a few times. Totally freaking unacceptable. We both have Nexus Protect on both devices, but don't think a new Nexus 6p will fix the issue. No problem at all with Google maps other than audio coming through my brand new trucks speakers. Smh. Both of our phones are not rooted or changed in anyway. Out of the box stock.
Sent from my Nexus 6P using Tapatalk
Sent from my Nexus 6P using Tapatalk
Confirm working in Nissan Frontier. Wonder why its certain auto manufacturers?
Works in 2014 Toyota Camry.
Mine works with zero problems in my '13 Fusion Ti. I also have a bluetooth adapter for torque plugged in with no hiccups. Is your sync software up to date?
Mine detects fine , but once connected I loose all system sound. i.e I can't hear map prompts anymore. Anyone knows a fix for this ?
desilva79 said:
Mine detects fine , but once connected I loose all system sound. i.e I can't hear map prompts anymore. Anyone knows a fix for this ?
Click to expand...
Click to collapse
I can verify that I have this experience as well in one of my cars with an aftermarket bluetooth Sony head unit (that supports A2DP streaming). Haven't checked in the Nissan yet (no A2DP), but I will tonight.
Bluetooth on this model sure has some "quirks".....
I have a 2015 fusion Ti & N6P I have had zero issues. however i will say my bluetooth connection is much more stable after updating SYNC to the latest version. Bit of a pain because you have to create a ford account to gain access to the instructions/files. but here is the URL to get you started: https://owner.ford.com/tools/account/how-tos/keep-your-sync-up-to-date.html
I also have a Ford Fusion 2015 and I have no problems connecting to SYNC. It also connects just fine with my wife's Ford Escape. Which month's build are you using? Is your radio up to date? I don't think I've ever updated the SYNC software in either vehicle so I'm not sure it's that. Make sure BT is on and you have the BT page in settings open so that both devices can see each other. Then go into the car's phone menu and add a device. That's how I did it. Make sure the vehicle is not moving or preferably in park. Good luck.
It magically connected right after I posted above. Now I'm afraid to install the June security patch lol. Working flawlessly in my F-150 though.
Sent from my Nexus 6P using Tapatalk
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?
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!"
After freshly flashing 9 using factory image, every thing is running fine but bluetooth connection to my car. Anyone?
I never had this issue with 8.1 and even 9 beta.
With Official 9, my phone takes long time to detect bluetooth devices (or needs reboot to detect) (i had this issue with Pixel XL too) but with my PH-1, it cannot detect my car mazda6 2014 at all.
Anyone has this issue? or know the fix ?
Thanks in advance.
Solution:
thanks to all to helped.
1st solution:
go to "previously paired devices" and remove ur car if there is one already and try again
2nd solution:
remove all the paired devices from phone history and try again.
Works fine for me.
Car 2012 VW GIT rns-315 stereo.
[email protected] said:
After freshly flashing 9 using factory image, every thing is running fine but bluetooth connection to my car. Anyone?
I never had this issue with 8.1 and even 9 beta.
With Official 9, my phone takes long time to detect bluetooth devices (or needs reboot to detect) (i had this issue with Pixel XL too) but with my PH-1, it cannot detect my car mazda6 2014 at all.
Anyone has this issue? or know the fix ?
Thanks in advance.
Click to expand...
Click to collapse
Did you clear all the data for Bluetooth and get rid of paired devices?
That might help. I had issues and needed to get rid of all previous connections.
Factory reset.
tech_head said:
Did you clear all the data for Bluetooth and get rid of paired devices?
That might help. I had issues and needed to get rid of all previous connections.
Click to expand...
Click to collapse
since this is the freshly flashed factory image phone i had no other Bluetooth devices paired.
update:
you r right.
although it was clean install...i had connected it to my fitbit. i cleared that and now, its connecting.
thanks.
autosurgeon said:
Factory reset.
Click to expand...
Click to collapse
its the freshly flashed factory image device
[email protected] said:
After freshly flashing 9 using factory image, every thing is running fine but bluetooth connection to my car. Anyone?
I never had this issue with 8.1 and even 9 beta.
With Official 9, my phone takes long time to detect bluetooth devices (or needs reboot to detect) (i had this issue with Pixel XL too) but with my PH-1, it cannot detect my car mazda6 2014 at all.
Anyone has this issue? or know the fix ?
Thanks in advance.
Click to expand...
Click to collapse
I had the exact problem with my 2013 Subaru Crosstrek. The trick that did it for me is,
1) Pair the phone with the car. Car will most likely say "connection failed". If the car is already in the paired list, "forget it" then re-pair.
2) Reboot the phone and try re-connecting on the car again. Don't delete the car from the phone's paired list this time. Leave it as is.
3) It should be able to connect now.
I am seeing an issue as described by the OP. I paired up the phone successfully on my Subaru WRX 2015, but the phone doesn't connect automatically subsequently. I've not had time to check extensively but it seems that it's no longer able to connect to the car again.