Bluetooth connection disappears after latest update. - LG Watch Urbane

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?

Related

Weird audio issues after latest T-Mobile update.

I have a bone stock, unrooted Nexus 6 on T-Mobile.
Android version: 5.1.1
Build number: LYZ28J
After the most recent update, I can no longer hear media through the speakers. Notifications come through fine, calls work just fine, etc.. But I can only hear Youtube videos, Google Play Music, or inline videos on Facebook through headphones or over Bluetooth.
I have repeatedly checked the volume, turned Bluetooth on and off, made sure that my MOTO 360 was turned off and disconnected, and today I did a factory reset. All to no avail.
Anyone have any ideas? Should I root and flash the previous version before the security updates?
JuanOfMany said:
I have a bone stock, unrooted Nexus 6 on T-Mobile.
Android version: 5.1.1
Build number: LYZ28J
After the most recent update, I can no longer hear media through the speakers. Notifications come through fine, calls work just fine, etc.. But I can only hear Youtube videos, Google Play Music, or inline videos on Facebook through headphones or over Bluetooth.
I have repeatedly checked the volume, turned Bluetooth on and off, made sure that my MOTO 360 was turned off and disconnected, and today I did a factory reset. All to no avail.
Anyone have any ideas? Should I root and flash the previous version before the security updates?
Click to expand...
Click to collapse
My first suggestion, to rule out hardware failure of some kind, would be to unlock your bootloader, and flash the entire factory image. Backup your important stuff first, as unlocking wipes all data.

Bluetooh pair fails after factory reset although pairing code is equal

Hi, I made a factory reset of my LG Urbane and since then it fails to pair with the phone. It shows the code for pairing, which is equal on phone and watch, but then Android Wear says, pairing fails.
Any hints, what I can do?
What I tried:
* Reboot Phone
* reinstaled Andoird Wear
* Used an old version of Android Wear
* Pair via Bluetooth menu
* Factory reset of the phone
What worked:
* Downgrade to Android 5 (Revolution HD 45)
On the watch (Stock, no root)
Model: LG Watch Urbane
Android Wear version:1.4.0.2576000
Google Play Services version: 8.6.98 (2574714-534)
Android OS version: 6.0.1
On the phone -
Model number: HTC One_M8
Android version: 6.0 (Android Revolution HD 51.0)
Android Wear number: 1.4.0.2552934.gsm
Google Play Services version: 8.4.89 (242871-438)
I'm pretty sure you can't pair it from your phone's Bluetooth menu, it is discovered through the Android Wear app instead.
JimSmith94 said:
I'm pretty sure you can't pair it from your phone's Bluetooth menu, it is discovered through the Android Wear app instead.
Click to expand...
Click to collapse
Sorry, Iw as unclear: It is not pairing neither via the app nor directly.
But it is possible to pair the watch with anything, also with windows 10 and an Ipad, but ofcourse with no function.
But it seems to be a general problem. Found it here and in the googl forums:
http://forum.xda-developers.com/watch-urbane/general/1-4-wear-update-t3308605/post65555056#post65555056
https://productforums.google.com/forum/#!topic/android-wear/--At7VrHkOk;context-place=topicsearchin/android-wear/authorid$3AAPn2wQfoU-IfUdTS6zoSHxDo0zldY35ehOKnIlPuzqVuveh-RKKHsVFcxdriwlzmPdJuOnHMW5LH|sort:date|spell:false

Pioneer MVH-2300NEX + Note 8 Oreo

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

After 60ish seconds I have complete audio loss

I posted this on the AA support page but didn't get an answer so I thought I'd seek help here.
Error message: None
Are you using Android Auto on your phone screen or car’s display? Car's Display
Car / head unit make & model: 2018 Honda Pilot EX
Phone make & model: Pixel 4
Android OS version: 10
Android Auto app version: 4.7.593824-Release
Google Play services version: 19.6.29 (120400-278422107)
Morning of the 13th, after 60ish seconds I lost all audio.
Worked fine from pixel 4 release until now. And worked with my Pixel 2 before that.
Tried:
-Unplugging and replugging in. AA does launch but no audio.
-Bluetooth: Removing phone from car and car from phone. Will work for 60ish seconds then quit.
-Audio DOES work with Bluetooth outside of AA.
-Uninstalled AA updates then reinstalled.
-Uninstalled GMaps Beta went back to release but no good.
-reinstalled GMaps beta no good
Android Device Policy was updated the previous night.
Also have a Samsung Galaxy S2 watch paired. Tried turning watch off and restarting AA but no good.
Rolled AA back to the previous version and it works. Unfortunately I'm back to the old interface.
Today found that Do Not Disturb was enabled with the update on the 12-13th which caused no audio.

Bluetooth issues following January update

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

Categories

Resources