I got the June 2019 update a few days back (stock ROM) and since then my Note 8 won't connect to the car stereo automatically any more.
In fact I have to delete it and re-pair each time. Anyone else experiencing anything like this?
Related
Hi,
I recently got a LG Urbane as a gift. It worked fine out of the box with Android 5.x on it. Then there were a bunch of updates, the latest dated Feb 1, 2017. When the watch booted I connected it as normal. I then paired it with the Wear app which worked fine. Then came "updating" and "sync". Sometime during that the Bluetooth is disconnected and I can not see my phone from the watch or the watch from Bluetooth settings or the Wear app. I can see other Bluetooth devices and the watch sees one of my Bluetooth speakers but not my phone. I reboot. Nothing. I then factory reset again and pair without problems. Same thing happens. Connect, update, sync and then I lose the connection and can not get it back. I have looked at permissions and have allowed everything both on the watch and the phone but still nothing. I am relatively new to Android Wear so am I missing something obvious here, or if not what can I do to troubleshoot this issue?
Watch data:
Model #: LG Watch Urbane
Build #: M1D65H
Android Wear version: 1.5.0.3693151
Google Play Services: 8.7.01 (2590918-534)
Android OS 6.0.1
Date: Feb 01 2017
My LG-W150 is doing exactly the same thing as yours and seems to have occurred after the OS was updated to Nougat. I tried it both of our phones - a Pixel and a Moto Z-Force which are both running Nougat and I get the same sequence of events as you describe. Have you found a fix yet?
I had originally had T-Mo S7 edge and had it connected to my 2007 BMW E61 with no problem while it was on Marshmallow. But when T-Mo rolled out Nougat to my S7Edge, my Bluetooth stopped connecting to the Bimmer. It was connecting just fine with any other car or BT device, just not this one. Any other phone and even my Gear S2 paired to the Bimmer just fine. Somehow, there was some weird incompatibility with the two (which was strange because I also had the public beta of N S7edge Rom and it worked fine. It was the release that stopped it from working.) But I was months away from getting an S8+ so I just held on until I got the S8+. Of course after I got the S8+ I'd find out that it suffered from the same issue. The phone would see my cars BT, try to pair, accept the PIN, and then it went back to available BT device and refused to connect. My car would show it connected for a few seconds then disappear.
I was holding out for N 7.1 because I heard it fixed some BT problems. But just today, I downloaded an OTA dated 6/6 - G955USQU1AQEF and it appears to have fixed the problem. I was able to connect to my care right away!
Happy days. If any of you are experiencing failed BT connection with some cars, try the update.
I'm having Bluetooth problems on my N6. They began around the time of 7.1.1, like everyone else, but a repeated BT crash is ongoing. Searching it looks like other discussions indicate the known BT problems were fixed in the March update, but I am hoping I have missed something. Bone stock N7, running 7.1.1 with the June 5 security patch.
I have reinstalled from the April 7.1.1 system image, disabled Instant Tethering, and disabled power management on the BT apps.
- I use BT a lot: media, phone calls, and so on, at least a couple of hours a day; I also have an LG Watch Urbane (AW2.0), and a Moto 360 before it.
- I had the same issues as everyone else in February, with the shutdowns and so on. I had not noticed BT issues before that.
- I relocked the bootloader in April, with the accompanying reset and system reimage.
Ever since February, BT has reset at random. This will happen occasionally, as often as 3x in 20 minutes:
- BT icon will indicate disabled
- any BT media/call will stop
- watch will indicate disconnect.
- Calls usually transfer to the earpiece, after a couple seconds of silence.
- 3-5 seconds later, BT indicates enabled
- devices all reconnect
- call transfers back to BT headset, most of the time.
This does not only happen when I am actively using BT for audio - if I'm driving with media paused it will suddenly start playing, suggesting that the phone has disconnected and reconnected in the background. I have not tried completely disabling BT in the car, since I do sometimes need to take calls while driving.
I'd love to be able to change a setting to fix the problem, but if someone can confirm they don't have these problems with a custom kernel and/or firmware I'd be interested in knowing that too. Thanks for any suggestions/pointers/advice!
I've not been stock since early 2015 I'm running Pure Nexus without any 3rd party kernel. I use BT non-stop without trouble. The last time I remember having any BT issues (actually similar to what you're describing) was in 2016 when I was using a AOSPA based ROM.
tdcrone said:
I'm having Bluetooth problems on my N6.
... don't have these problems with a custom kernel and/or firmware I'd be interested in knowing that too!
Click to expand...
Click to collapse
Stock 7.1.1. June update. Rooted, unencrypted. No bt issues.
In the play store there's an app to fix Bluetooth issues on rooted devices.
I'm on SiX ROM + Blackbird Kernel + Magisk. Paired with a Huawei watch, and frequently use Bluetooth audio with my car stereo, Jaybird X2 headphones, and Anker portable speaker with no issue.
after updating to oreo i'm not able to use android auto.
everything right now is at latest version.
android auto will not detect the headunit and add it as a "Car".
have tried multiple quality cables including oem samsung
the phone detects the connection and is charging, it also shows up as "data transfer" mode
bluetooth works fine, the spotifty function on the headunit will work if android auto is running on the phone however android auto will not mirror to the headunit while usb connected.
What version of Android Auto? Maybe downgrade back to 2.9.
Was 3.1 I will try 2.9
Thanks
epofhouston said:
What version of Android Auto? Maybe downgrade back to 2.9.
Click to expand...
Click to collapse
2.9 didn't work either. and way to debug this?
I still can't get this to work.
pioneer wont help me, google wont help me.
I've reset my phone countless times.
any way to force AA to load on HU?
Was this ever solved? Not sure if these are related or not. I did not pay any attention to what version my S8+ was until now. Could it have taken ATT this long to upgrade my phone to Oreo?
Here is my story ...
I have Galaxy S8+ running 8.0.0. My Pioneer AVH-2330NEX is running firmware 8.35 dated July 2018. AA quit working after the Jan 2019 update to the phone. I get an "Andriod Auto stopped working" on the head unit. Here is the troubleshooting I have done so far.
I have tested the phone on a 2016 Honda factory head and all works. I have tested the Pioneer head with a friends old 1+1 (6.0.1 Cyaongen 13.1) and it works with the Pioneer.
But the S8+ and Pioneer do not.
Any thoughts?
Update to android pie solved all my problems with Android auto on pioneer avh z7100 dab
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