I'm having nothing but trouble since I updated my 360 2015 to Marshmallow. It connects to my phone (Motorola X Style ) after unpair / reboot, but sits for half an hour "updating" and than looses connection. I've tried everything I could think of short of factoryresetting the phone: removing android wear app, clearing caches and data from all wear apps as well as moto connect, google play services, and so on to no avail. The only way from keeping this bloody thing crushed under a big hammer (yes, I'm seriously frustrated with that piece of crap) is if I can go back to the previous lollipop that it came with.
Does anyone know if (and how!) rolling back is possible at all?
Related
Android wear can not find LG G Watch
After a factory reset my android wear can not find my watch. I have already reinstalled the app, cleared catch and data. Toggled airplane mode and bluetooth. I have unpaired the watch from the phone pre factory reset on the LG G watch.
When I get to the starting screen on my LG G watch it says lets get started so I pair it my phone it gives me a 6-9 digit number I hit pair, then it goes into updating then after that syncing. Once all that is done I get to the main page on the LG G Watch. From that point on the phone android wear can not find me watch. Also on the bluetooth settings on the watch its self it cna not find my phone. HTC one M8/ I have also tried it on a samsung galaxy S6 and S6Edge. Software is update on both devices and all apps ( Goolge play, services and wear are up to date)
Can anyone think of anything I have not tried? I have it scheduled for repair but I do not want to send it off for 14 days if I can fix it myself.
Thanks in advance
Ben
I just updated my phone T-Mobile Galaxy Note 4 to the new LG v10
Love this phone, really sleek and beautiful.
Problem is I cannot get my Moto 360 1st gen to connect.
Ive paired the two devices and no problems there, but the two will not connect. The blu-tooth shows the watch on my phone, but will never connect. Ive gone thru several sites that give you the basics to troubleshoot, including reset the Moto 360 to factory specs which I have done several times.
The two pair perfectly, but will not connect. If I go to the blu-tooth settings on the watch, I don't see my LG v10 anymore, it just searches and never finds. I have to completely un-pair and reset to pair again and again no connection.
I have paired the Moto 360 with several devices and I know its working perfectly, the only change is this phone.
The phone is connected to my Car Stereo and it works perfectly there, so I know the blu-tooth does work there.
Anybody else having issues with Android Wear, or similar?
Thanks
I have the T-Mobile V10 and I paired my 360. I had issues after the initial pairing like you described but after rebooting the phone it has been working constantly.
I had to factory reset my watch twice
It connect fine here with my Moto 360 first gen (and my Jabra Rox headphones).
Same here...before I upgraded to the v10...my note 5 and gold moto360 out of nowhere just stopped connecting...I had to reset a few times to get it together.maybe after a certain while all Android wears have to be factory reset at some point...hopefully an update will fix what's going on
Have tried resetting several times and nothing. It's as if the phone only sees the watch long enough to pair, but won't connect.
Thank you all, I finally figured it out. I was trying to sync thru the Bluetooth option. You have to sync thru the android wear app.
What I did was reset the watch, this time I had my wear app open and waiting. When the watch asks to sync, the app kicks in. I've had my watch so long, I forgot how the proper way of doing it.
Speaking of which...has anybody had issues replying or sending messages and or asking ok Google with the moto 360
psn1819 said:
Speaking of which...has anybody had issues replying or sending messages and or asking ok Google with the moto 360
Click to expand...
Click to collapse
I haven't had any issues yet, but one thing I do notice is the messages app doesn't turn on the Moto 360 like my Note 4 did
Sent from my LG-H901 using XDA Premium HD app
How's the 360 holding up for you guys? Is on sale on the play store and I'm tempted to get it
Anyone figure this out yet? I just picked up the v10 and have the same issues
Like others have said, I had to reset my watch to be able to get it to connect. Just like starting over.
I've had to factory reset my watch every time I wanted to pair with a new device.
Raztrax said:
How's the 360 holding up for you guys? Is on sale on the play store and I'm tempted to get it
Click to expand...
Click to collapse
Its good and all,battery life is absolutely horrid though.
I have an LGv20 and a moto 360 sport and had the same issue everyone has described. I reset the watch endless times. The way you need to do this is as follows. Unpair the watch from the phone. This will do the factory reset. On your phone, open the Android wear APP. Have the APP set to discover your watch. It's the very first step you have when opening the app. The watch is now ready to connect to your phone. Essentially you are pairing your phone and watch through the Android Wear app. The mistake I was making was pairing the watch and phone from the phones Bluetooth area. Big mistake. I am happily paired to my phone now. It took 2 days of frustration to finally find this posting.
smacis said:
I have an LGv20 and a moto 360 sport and had the same issue everyone has described. I reset the watch endless times. The way you need to do this is as follows. Unpair the watch from the phone. This will do the factory reset. On your phone, open the Android wear APP. Have the APP set to discover your watch. It's the very first step you have when opening the app. The watch is now ready to connect to your phone. Essentially you are pairing your phone and watch through the Android Wear app. The mistake I was making was pairing the watch and phone from the phones Bluetooth area. Big mistake. I am happily paired to my phone now. It took 2 days of frustration to finally find this posting.
Click to expand...
Click to collapse
I have a new V20 and I was having the exact same problem... This fixed my issue IMMEDIATELY! Thank you so much for your help
I have a problem, my moto 360 (2015) is crashing and i have to force close it. It happens usually ever day. I´ve tried to reset it but with no luck and reinstalling google play services (I was told that that was a fix) but no luck there ether.
I can´t see this topic anywhere on this forum. Am I the only one?
Android Wear version: 1.3.0.2230669
Phone and os version: Sony Z5, 5.1.1
Google play services: 8.4.89 (2428711-534)
Your not the only one, I have tried everything that I could find in the internet...
I have however discovered that when my WiFi on the phone is on I would always get this problem, so after many factory resets I decided to switch off the WiFi on my watch.
touch wood, I have not had this problem anymore.
I passed the Info onto Motorola as I was thinking of returning the watch. They say they have passed the Info on and I am just waiting for a reply.
Hope this fixes your problem?
Your not the only one me to
I noticed mine started crashing the same day I started installing watch faces - which was about a week after I bought it over a month ago.
I deleted a few of them and the problem went away as if it had never happened.
Hi all!
Im sorry if its already been posted but I didnt see it. I, regretfully, followed the prompt to update to 2.0. Its awful and ruined my watch!! NO longer can I get notifications (ive checked the settings, uninstalled android wear and reinstalled, toggled bluetooth, connected and disconnected from the watch, master reset the watch, and powercycled both.). 2.0 is complete garbage!!! any ideas on how to roll it back to the 1.2 OS??? THank you in advance for all your help and im sorry if its already been answered!!
Thank you!!
No there isn't
Sent from my m1 note using Tapatalk
are a lot of other people having this issue of notifications?
found any solution?
unfortunately here is the same mate did u find any solution?
well yes actually.
Do a disconnect and reset.
Forget the watch in the phone wear app.
Go through the reconnect procedure, BUT disable mobile data and get ready to disable the wifi on your phone.......
When the watch says "searching for updates" during the re-pairing procedure TURN THAT WIFI OFF on your phone so it cannot get to the updates.
Once the watch is setup, go to the settings on the play store of your watch and turn off auto updates.
Turn the data back on on your phone. You will have to update the play services on the watch for your apps to work, BUT you don't have to update from Android wear to Wear OS, and you can keep the stock look and feel!!
(found whilst trying to get to the bottom of the battery meter lying to me)
** This post should be in the "Help & Troubleshooting" section of the Nexus Player - ooops. **
My Nexus Player started hanging up at the 4 balls bounce routine last week. After trying a factory reset, the only thing that I've been able to do to get back to Android boot with TV interface is the OTA restore from the latest version 8.0.
This however doesn't stick, as if the device powers off, powering up, the problem returns.
I had the hdmi output connected to a switch that allows the monitor to be shared with a laptop. If the NP device goes to sleep, the switch automatically opens up the feed from the laptop (dual monitor). If I switch back, the wake up mode becomes the 4 balls again.
Someone pointed to the Oreo upgrade as being problematic. Do these symptoms sound like software or hardware?
I did connect the unit without the switch directly to the monitor and got slightly different results. Now the unit tells me that I need to run system restore which formats /data and another partition then partially loads get the Android screen and starts over. Tried to restore from OTA again and it won't pair with the controller saying "Can't play this video" .
Got it running again, let it run overnight with a channel selection and by morning it had died.
Tried loading a different OTA Ver.8 and it is too smart for that. I am reading though from several sites that I'm not the only one with a partial brick since the update to Ver. 8. - Unfortunately, that was "supposed" to be the last update, yet there appears to have been a "zero day" failure built into it.
OK Google (seems as if Asus isn't responsible) the ball is in your court, yet it's going to be difficult to patch when the device is partially bricked.
ggregor said:
My Nexus Player started hanging up at the 4 balls bounce routine last week. After trying a factory reset, the only thing that I've been able to do to get back to Android boot with TV interface is the OTA restore from the latest version 8.0.
This however doesn't stick, as if the device powers off, powering up, the problem returns.
I had the hdmi output connected to a switch that allows the monitor to be shared with a laptop. If the NP device goes to sleep, the switch automatically opens up the feed from the laptop (dual monitor). If I switch back, the wake up mode becomes the 4 balls again.
Someone pointed to the Oreo upgrade as being problematic. Do these symptoms sound like software or hardware?
I did connect the unit without the switch directly to the monitor and got slightly different results. Now the unit tells me that I need to run system restore which formats /data and another partition then partially loads get the Android screen and starts over. Tried to restore from OTA again and it won't pair with the controller saying "Can't play this video" .
Got it running again, let it run overnight with a channel selection and by morning it had died.
Tried loading a different OTA Ver.8 and it is too smart for that. I am reading though from several sites that I'm not the only one with a partial brick since the update to Ver. 8. - Unfortunately, that was "supposed" to be the last update, yet there appears to have been a "zero day" failure built into it.
OK Google (seems as if Asus isn't responsible) the ball is in your court, yet it's going to be difficult to patch when the device is partially bricked.
Click to expand...
Click to collapse
There are a couple threads on this already. Mine is bricked too at the moment.
https://forum.xda-developers.com/nexus-player/help/stuck-google-screen-t3044191
https://forum.xda-developers.com/nexus-player/help/nexus-player-suddenly-dead-t3814519