6.0.1 Changes for LG G Watch R

[cdaly1970]

So my watch updated last night, and now I am trying to figure out all the changes.

I see that we have new gestures. I don't really use them, so Meh.

I also see that my battery projection jumped from 50 hours to 3 days, so that I freaking awesome if it pans out.

Anyone see anything else?

-Chris

 

[matejilic]

So my watch updated last night, and now I am trying to figure out all the changes.

I see that we have new gestures. I don't really use them, so Meh.

I also see that my battery projection jumped from 50 hours to 3 days, so that I freaking awesome if it pans out.

Anyone see anything else?

-Chris

No more reboot watch.. Have to turn it off and on again.

 

[Hawke84]

No more reboot watch.. Have to turn it off and on again.

Yeah I noticed that. Find this odd as to why they removed that

 

[matejilic]

Yeah I noticed that. Find this odd as to why they removed that

I think Google's reason was: "Why? Because F**k you, thats why!" It also baffles me that they still haven't incorporated custom canned responses to declined phone calls; you are stuck with the default ones even though you set up custom ones on the phone - the reason was probaby the same as the reboot omisson.

 

[shobull.eu]

I think Google's reason was: "Why? Because F**k you, thats why!" It also baffles me that they still haven't incorporated custom canned responses to declined phone calls; you are stuck with the default ones even though you set up custom ones on the phone - the reason was probaby the same as the reboot omisson.

but how to make a factory reset now? there is no item in menu.

 

[jimbobtexas]

Yeah I noticed that. Find this odd as to why they removed that

Just hold down the button until it buzzes and reboots. Hardware reboot.

 

[Hawkeye3]

but how to make a factory reset now? there is no item in menu.

Have you tried 'Unpair with phone'? To me that sounds like it would do a factory reset since an unpaired watch is basically useless.

 

[cholm]

Big change

Hi all,

Also got marshmallow, and biggest change for me is that it won't pair with phone. It comes up alright, and after accepting the Bluetooth code the phone wear app says "couldn't connect with ...". I tried factory resets (via unpair phone setting item), fresh install of wear phone app, and what not - still no luck.

Will try to downgrade and see if that helps.

Yours,

Christian

 

[gabrymr]

Have you tried 'Unpair with phone'? To me that sounds like it would do a factory reset since an unpaired watch is basically useless.

From what I understand factory reset is "Unpair with phone" now, as when you select it asks: "are you sure you want to unpair and factory reset watch.

Interesting thing, is the new Reminders app, doesn't seem to work it asks to update android wear on phone when I open it, but nothing happens.

 

[mhacin]

Hi all,

Also got marshmallow, and biggest change for me is that it won't pair with phone. It comes up alright, and after accepting the Bluetooth code the phone wear app says "couldn't connect with ...". I tried factory resets (via unpair phone setting item), fresh install of wear phone app, and what not - still no luck.

Will try to downgrade and see if that helps.

Yours,

Christian

I replied to you in the other thread but will post here as it may be useful to others..

I have the same issue. After OTA , i factory resetted and now it will not pair. I get "failed to pair...." I have tried multiple resets and cleared the data on the android wear app but no joy. I have gone back to 5.1.1 using the first post of the factory image thread. I was able to flash boot.img and system.img but recovery.img failed due to a partition error. Now everything is working again. Paired and synced on first attempt.

 

[HKSpeed]

 

[cholm]

Downngrade wakes up watch

Hi there,

I replied to you in the other thread but will post here as it may be useful to others..
...
I have gone back to 5.1.1 using the first post of the factory image thread. I was able to flash boot.img and system.img but recovery.img failed due to a partition error. Now everything is working again. Paired and synced on first attempt.

I also went back to 5.1.1 and things now work again - recovery flash also worked.

Seems the problem is really on the phone end. I have a Nexus 4 with "Fake stock" ROM (marshmellow). I could get the watch to pair with my Nexus 7 running stock 6.0..1 and that paired just fine. I also see other problems with the same Nexus 4 ROM with other bluetooth devices - e.g., my Jabra Tag II bluetooth audio RX/TX. I've posted on the ROM bug report forum.

 

[thETImo]

My watch gives an error about a muted microfone although the mike is enabled everywhere in the settings where possible.
" Microfone disabled, waiting for injected audio."
Any suggestions?

Edit: Also the screen goes off after some time although I haven't enabled it anywhere?

Maybe I'll just reset it...

 

[Spo0f]

The biggest change for me - now we have native vibration when the watch disconnects (on connects) ... it was about f'in time ...

 

[mhacin]

I have a Nexus 4 with "Fake stock" ROM (marshmellow).

I also have nexus 4 running Chroma MM. I will wait for OTA again and this time I wont factory reset to see how it goes

 

[sotsoguk]

Manually updated mine to 6.0.1 using adb and now my iPhone (9.3 beta3 and latest android wear app) constantly looses connection. Have to pair as new device, restarting phone and/ or watch won't help.
Does anybody experience the same?
Might have to go back to 5.1.1 ...


Gesendet von iPhone mit Tapatalk

 

[ChrisM75]

Hmm, well thats a disappointing. The removal of the reboot and reset is moronic and the new gestures are useless.

For the most part I cant get them to work, and even if I could why would I want to look like I was a nutter because I was randomly flapping my arm around trying (usually unsuccessfully) to control my damn watch?

 

[justyourimage]

delete me

 

[SharpSA]

I replied to you in the other thread but will post here as it may be useful to others..

I have the same issue. After OTA , i factory resetted and now it will not pair. I get "failed to pair...." I have tried multiple resets and cleared the data on the android wear app but no joy. I have gone back to 5.1.1 using the first post of the factory image thread. I was able to flash boot.img and system.img but recovery.img failed due to a partition error. Now everything is working again. Paired and synced on first attempt.

Which 5.1.1 is better?

 

[mhacin]

Which 5.1.1 is better?

I used the one at the top of the list. I don't know what the differences are between 5.1.1 versions