A new kind of Pixel issue. I just got my Pixel yesterday, and setup android wear and connected to my LG G Watch R, but right after saw each other and I paired them, they both dropped and now I can't get them to pair again. I've attempted restarting both devices in varying orders, uninstalled android wear and reinstalled, and even booted the watch into recovery mode. No love. Anyone else run into this?
Gabryael said:
A new kind of Pixel issue. I just got my Pixel yesterday, and setup android wear and connected to my LG G Watch R, but right after saw each other and I paired them, they both dropped and now I can't get them to pair again. I've attempted restarting both devices in varying orders, uninstalled android wear and reinstalled, and even booted the watch into recovery mode. No love. Anyone else run into this?
Click to expand...
Click to collapse
Hey,
On your watch
Open settings
Unpair your wear and the phone (This will reset your watch, and the first boot up takes some time)
On your phone:
Open phone settings
Open Application Manager
Click on "Google Play Services"
Click on Storage
Click on Manage Storage
Click on "Manage Wearable Storage"
"Clear Now"
Now try to pair them again
Hope it works,
Lucas
(If not, donate me your Pixel )
Yep! That did the trick, thanks!
Related
I have an LG G3, and I immediately paired & connected my R watch to it while running on 5.0.2 L no problem. When I noticed a few glitches with my blue tooth music play-back in my car, I decided to restore a previous KitKat nandroid I had backed up. I don't attribute the BT glitches to the watch. I had recently flashed the Lollipop rom hadn't driven with it a lot with BT. I'm thinking it's the rom.
Anyway, when I restored my old KitKat nanny, I had a problem connecting the watch. It paired just fine from my BT screen on my phone. I got the code confirmation on both devices and clicked "yes", but my watch just sits at "connecting...". After a while, it returns to the watch face. When I go back into my watch settings, it says "disconnected". I can click "connect" on the watch, but it goes through the same loop.
I realize there are device and software details left out of this OP, but I wonder if anyone can see something basic that I'm doing wrong based on what I've said. I tried unpairing and starting from scratch. Maybe there's something with the Kitkat rom (Vanir 4.4.4) that doesn't play nice with the watch, but maybe it's the way I'm pairing through the phone rather than through the watch.
Any ideas?
I have a galaxy note 3 running a leaked version of lollipop and I am having nothing but disconnection issues
I know when the watch was still on KK and my phone was I didn't experience any..
So don't know if it's my rom either or the watch since the lollipop update on that..
I'm toying with going back to KK on my phone and trying again to see if it fixes the issue
Will keep an eye on this thread and see what others say.
Whenever I restore a phone backup I always have to do a full Reset on the watch or it won't sync. Apparently the sync mechanism can't just pick up wherever and continue.
The only annoyance with this is having the "OK GOOGLE" banner hanging in there and getting rid of it (how I'd love to just kill it once and for all...) and the initial unskippable tutorial on the watch (dtto, kill it with fire!)
Apart from that, it is quite simple to reset and setup the watch again.
1) hold the crown on the watch
2) do a Reset from the menu
3) unpair the watch on the phone
4) when the watch starts up, pair it from the inside of the Android Wear handheld app.
I don't think there's a difference between choosing "Forget XXX watch" from the Android Wear menu before pairing or not in this scenario.
Back on kit kat on phone and watch is running perfect not disconnected once today
I upgraded today from a LG G Watch to a LG Watch Urbane. My Urbane has been constantly disconnecting all day. I have tried everything I can think of to try to remedy this issue but to no avail. I have performed several factory resets on the watch, as well as, cleared data/cache for the Android Wear App, Google Play Services, and the Google App. The watch and all apps are up to date. I have a OnePlus One running CyanogenOS 12.1 build number LMY48B.
Does anyone have any ideas on how to remedy this issue?
I've had the ZW3 since it came out. Never gave me a lick of trouble. Recently I got a Note 8. Now many of the apps that I have on my phone (Cerberus, Photo Watchface) just never show up as apps on the watch. I've done the usual things to fix this: Factory reset the watch. Delete the apps from my phone and reinstall them. I even went so far as to do a factory reset on my Note 8 (and watch) to get a fresh start. But, for some reason these apps never show up on the watch as they did with previous phones.
I'm pulling my hair out. What do I do next?
I had the exact same problem when I got my Note 8.
I finally got the apps to install by opening the playstore on the watch & installing the apps directly to the watch.
~John
jmorton10 said:
I had the exact same problem when I got my Note 8.
I finally got the apps to install by opening the playstore on the watch & installing the apps directly to the watch.
~John
Click to expand...
Click to collapse
Thanks. That worked for Photo Watch but it doesn't work for Cerberus since there's no Cerberus app in the watch app store. I know Cerberus works with Android 2.0 as it worked on my S8+. I just can't get Cerberus to recognize the watch on the Note 8.
Hey guys,
Switched from an lg v20 (which had no problems with the watch) to a note 9 on Verizon and can't seem to keep this phone connected to the Huawei watch (version 1) to save my life. Bluetooth disconnects probably once per hour or so and stays disconnected until I reboot watch or turn watch bt on and off.
I've tried hard resetting watch, reinstalling wear os app, clearing cache, and nothing seems to work.
Thoughts?
bump
I'm not sure it's correct form to bump one's own thread?
I just got into my car (2018 Ford Fusion with Sync 3) and connected my phone. When I pushed the infotainment "Android Auto" button, the screen went to black and stayed there. I then looked at my phone and saw that the phone was trying to launch AA (in my status bar, I saw the Android Auto icon), then the icon would disappear, and then the phone would try again. This continued repeatedly.
When I got back to my computer, I looked at google play store and saw there was an update yesterday (6AUG).
In the car, I also tried clearing out the data/cache for Android Auto and then reconnecting, but it continued to exhibit this behavior.
I'm wondering if others have noticed this issue.
For the record, I have a Pixel 3xl on the July Security patch.
Edit: I installed August Security Update and all seems to be well now. Strange.
Cheers,
B.D.
I am having the same issue. I have a Oneplus 7 pro and my car is a 2018 VW Golf GTI. When I plug it in to the USB, the head unit just goes black. When you touch the screen you can hear clicks, however then the screen cuts back out "No Communication". I've tried turning USB Debugging On/Off. I've uninstalled android auto, reinstalled..cleared cache, cleared data. I've also cleared cache on Google play services. I've tried older versions of Android Auto and different cables same issue. Any recommendations? I'm guessing it a Google Play Services update causing it.
change your cable.... android auto is terribly picky on the cable.
The only cable working with my oneplus 8 is the stock cable...
ShadowJP88 said:
change your cable.... android auto is terribly picky on the cable.
The only cable working with my oneplus 8 is the stock cable...
Click to expand...
Click to collapse
Well I've done some more trouble shooting...still haven't solved it, but still... I have tried 5 different cables to no success. 2 other "official" OnePlus cable, a high end cable and another standard cable. So we can eliminate that. I tried an Old Nexus 6 I have around and "bingo" that does work with the cable I've been using my and shows up with Android auto. So I know know it's the OnePlus 7. And after uninstalling and reinstalling android auto, clearing cache to no success. I'm thinking of only two options left
..Either wait for Google to provide an update or wipe and reset my phone which is a HUGE headache...
mullman85 said:
Well I've done some more trouble shooting...still haven't solved it, but still... I have tried 5 different cables to no success. 2 other "official" OnePlus cable, a high end cable and another standard cable. So we can eliminate that. I tried an Old Nexus 6 I have around and "bingo" that does work with the cable I've been using my and shows up with Android auto. So I know know it's the OnePlus 7. And after uninstalling and reinstalling android auto, clearing cache to no success. I'm thinking of only two options left
..Either wait for Google to provide an update or wipe and reset my phone which is a HUGE headache...
Click to expand...
Click to collapse
Are you using a beta version of Google play services?
I'm some situations it create different problems
Fishcat7 said:
Are you using a beta version of Google play services?
I'm some situations it create different problems
Click to expand...
Click to collapse
I was in Beta, and left it...it still doesn't work, unless there is a easier way to roll back to an earlier version of play services.
Play Services Version
version 20.26.14 (120400-320008519)
--Edited--
I ended up wiping my phone and putting paranoid android quartz 4 as a custom rom.
Android Auto works fine now.