Hello everyone. So i got my GWR from repair (replacement of display) and they reset the device into AW 4.4 version. The problem is that its stuck and keeps on saying System is up to date,however even before i had AW 6.0.1. I even tried to reset both watch and android wear app several times,but still nothing. Wifi is on,of course. Any tips what i can do? Because AW 4.4 is really awful to use and apparently it isnt supporting all the apps i use as they are not installed even after hour. Thanks for any advice.
Nevermind,it started itself updating after while
Related
Hello, I have received an update to Android Wear 5.0.1 yesterday on my LG G Watch R. Ever since I've updated it, the watch as been freezing and giving me a static screen. The screen will remain there for 5-10 minutes and then it will act fine again, but then it will randomly freeze and give this issue again. I deeply regret updating as the watch has been perfectly fine and running smooth before the update. I will try to attach a picture of the screen, but has anyone else run into this problem? Is there a possible fix?
rsharzaman said:
Hello, I have received an update to Android Wear 5.0.1 yesterday on my LG G Watch R. Ever since I've updated it, the watch as been freezing and giving me a static screen. The screen will remain there for 5-10 minutes and then it will act fine again, but then it will randomly freeze and give this issue again. I deeply regret updating as the watch has been perfectly fine and running smooth before the update. I will try to attach a picture of the screen, but has anyone else run into this problem? Is there a possible fix?
Click to expand...
Click to collapse
I have a some what simillar problem.
After the update my custom faces no longer go on standby mode.
I'd remove all wear related apps on your phone. Uninstall android wear too. Then I'd factory reset my watch. Reinstall wear from the market and see if the problem persists
fr0st420 said:
I'd remove all wear related apps on your phone. Uninstall android wear too. Then I'd factory reset my watch. Reinstall wear from the market and see if the problem persists
Click to expand...
Click to collapse
This sounded like a hopeful idea but upon resetting to factory settings, the device shut off and reboot(as expected) and then it just gave a static screen. The static screen stayed there for five minutes and it allowed to select a language, ect. I have just re-installed Android Wear onto my phone(I had it uninstalled before resetting the watch) and it is now paired and it is behaving as it did after updating it yesterday, just giving me random static screens I'm leaving the country tomorrow, but I will be checking back for any solutions between now and then. Anything would be helpful. But it does look like I will be contacting LG about the matter, it doesn't seem to be a common issue to have a static screen...
Some face are not compatible with new face api in V5. Try with a LG Standard face (Camping) to see if you freeze or not ?
I have issue with intellicom, weather Watchface..... now I'm trying original face and no issue in 24H
rsharzaman said:
but has anyone else run into this problem? Is there a possible fix?
Click to expand...
Click to collapse
My first one did this, but would not get normal until the battery was empty, charging it did cause a reboot. Contacted LG, they said a Hardware failure, and send me a email with their conclusion (i send them a picture, with a description) so if the webshop i bought it from was reluctant to swap it for a new one, i was supported by this, not necessary, they swapped it, that one got the blinking issue, and now i have a third new one Get it replaced!
dersie said:
Some face are not compatible with new face api in V5. Try with a LG Standard face (Camping) to see if you freeze or not ?
I have issue with intellicom, weather Watchface..... now I'm trying original face and no issue in 24H
Click to expand...
Click to collapse
I've tried this as well with the suit face and there was no difference unfortunately
RoosW said:
My first one did this, but would not get normal until the battery was empty, charging it did cause a reboot. Contacted LG, they said a Hardware failure, and send me a email with their conclusion (i send them a picture, with a description) so if the webshop i bought it from was reluctant to swap it for a new one, i was supported by this, not necessary, they swapped it, that one got the blinking issue, and now i have a third new one Get it replaced!
Click to expand...
Click to collapse
I might just go ahead an do this once I get back home. This morning the screen was acting very odd as I was swiping through notifications and it just began blinking and showing black lines near the edge. It stopped once I hit the power button twice. I'll just get it exchanged before it gets worse Thanks guys, I really appreciate it. Hopefully I get lucky the second time!
ever since the Android Wear apps on my phone got updated to version 1.0.5.1785466 , my watch has been getting random "com.google.process.gapps has stopped" error ..
anyone else experiencing the same ?
EDIT : so after going through a rather painful day that involve several restart, connect and disconnect .. everything seems to be ok now .. hopefully just a bad update procedure ..
Yepp !
Many errors with this update.
Mine didn't synch steps with Google Fit anymore, even after full reset.
Same. I woke up this morning to the app being updated and it broke a whole bunch of things. WatchMaker for one. Its only my second day with this thing.
P.S. Try reverting the android wear app back a revision. Seemed to have fixed the issues. Also, determined the watch face doesn't work.
I've opened a ticket with Google. It's a bad update. I'm going to roll back a version using Titanium Backup.
It's really a bad update!
In my case this Android wear app update is DRYING my phone's battery (LG G2)
http://forum.xda-developers.com/android-wear/help/android-wear-app-version-1-0-5-1785466-t3060252
With my LG g watch R seems all OK...
Lorenzo
LG watch R No Longer Works Correctly after 1.0.5.1785466
Constant disconnect and battery drains. Android Wear doesn't display the watch faces anymore. Watch Maker no longer is work also. Performed Multiple factory resets on the watch and uninstall/reinstall Andriod Wear. NOTHING seems to work. Called Google and the Support person said there hand are tied and that the the Engineers are working on it. This watch is very expensive for it not to work make me extremely upset.
Hi guys,
I've received my Gear Live yesterday.
Immediatly begin to play with it, installing Android Wear on my Lollipop Note 3.
Btw, she was on Knx01q.
Paired the watch, surfing a little bit on the computer and some time after, the watch was no more connected to the phone.
On the screen there's a nice "Google Play services has stopped"... Then the same with "com.google.process.gapps"...
After some investigations and trials, I can tell this happen when the watch try to download the next update. No more bluetooth, force close again and again when I try to go on the "About" menu...
I've tried to downgrade to the kmv78y firm and it seems to resolve the problem, but if I upgrade, the mess continue, force close after a moment and I can't pair the watch anymore.
Trying to update to the lollipop update manually, no chance at all... Sideload failed, TWRP install failed, ...
Have you any idea of what's going on ? I think I'll send back the watch to the seller soon.
Thanks guys.
There was an update to Android Wear on the Play Store yesterday. All the comments say they lost connectivity after updating. I think I'm going to wait before getting the update for the app. You may see if you can find an older version of Android Wear from another app store.
Sent from my SAMSUNG-SM-G890A using XDA Free mobile app
Thanks for your answer.
In a last light of hope, i've installed the LDZ22J update provided here : http://forum.xda-developers.com/gear-live/development/unofficial-samsung-gear-live-restore-t3132500.
I simply replace the files in the Samsung Gear Live Restore Tool and choose to restore back the watch to stock.
It's working and the watch is now with Lollipop without loosing connection or force closes... Just a little problem persist, with some watch faces, when the screen become dimmer
the watch face just turn into some "inverted colors" mode... Don't know if it's normal ?
Thanks again.
The inverted color mode is kind of like a battery saving mode. Most watch faces have this mode.
Sent from my SAMSUNG-SM-G890A using XDA Free mobile app
A lot times after an update is performed, Google services crash. A simple watch reset should get it back working again
Thanks guys.
The weird thing is when I downgrade the watch to the first update, it was almost OK. But when she try to update from KNX01Q, after a little moment the force closes begin and the watch was completly useless.
Since I update to LDZ22J it's ok and I can finally play with it. Now the watch try to update to LCA43 (I suppose) I get an error about "libgnustl_shared.so" in the recovery. Again, I've tried to update manually with sideload, same error...
So for now I'm stuck with LDZ22J with an update card but no way to update... If you guys have a dump of LCA43 with .img somewhere...
Thanks.
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?
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?