Android Wear 2.0 - Anyone Receive the Update Yet?

  • Thread starter Thread starter AC Question
  • Start date Start date
You have a 2nd Gen Moto 360, correct?
I didn't think 2.0 was being sent out to the 360 yet.

Correct, and correct.

At this point I just want something that works. Doesn't have to be the latest or greatest... I'll take reliability over anything at this point.
 
Such a shame that after Motorola was one of the Pioneers of the platform that now it has fallen so far behind.
 
I got the update about a week ago for my LG Urbane; pretty much my watch is just a watch now. Got an update to the 2.0 update and then also did all the things the forums suggested. YES I turned on the Ok Google (thanks for turning it off for me??). My watch is pathetically slow to anything and still doesn't do the one thing it has actually been good at. "Ok, Google, remind me to...." or anything else Ok Google is completely broken. Notifications don't notify unless I drill into them manually (no buzz, no quarter moon display). Apps won't open, super slow, unresponsive. This is the worst update ever that makes my watch at best, a time telling device. WTF? This is the kind of thing that would make me consider going to a closed system (Apple) with (hopefully) better QA.... This is wasting my time and removing all the reasons I have a smart watch
 
Such a shame that after Motorola was one of the Pioneers of the platform that now it has fallen so far behind.

It really bugs me my watch notifications are dead after 1 year. One year of service is totally inexcusable for this kind of dough ($325).
Even in todays planned-for-obsolescence / disposable design philosophy, this falls FAR short of any realistic expectation.

I am not asking for much. I don't even want 2.0... I just want a watch that works.
 
Last edited:
My sympathies to those who have not had a good experience with wear 2.0. I have not heard a lot of folks who have had a good experience with wear 2.0. Maybe it is just because the people who are having issues are the only ones hitting the forums, those that have it working are not? I did not see this much chaos with the beta so it seems pretty odd to me. It almost reminds me of some of the early role outs with IOS. Early adopters in my office always seemed to have issues with some basic functionality in the early IOS updates. I am a little relieved that Huawei has not released it yet. I am always anxious to try the newest releases and betas but I know what I am getting into and I know I can always flash to the stable versions. When a "stable" version is released and there are so many issues I kind of question how good the QA testing is at these companies.
 
Part of me is starting to think this is their hidden ploy to force owners of older generation AW devices to upgrade.

I can understand if its a bug here or there, but to terminate bluetooth push notifications... of all the most basic, fundamental functions. Starting to smell fishy. For most its the primary reason to invest in a smart watch.

Its not just us here on AC. If you read the latest AW reviews on playstore, there are many many bugs being commented on.
 
My watch gets all notifications it just doesn't show on the watch that they are there unless you swipe up. It's very hit and miss.
 
My watch gets all notifications it just doesn't show on the watch that they are there unless you swipe up. It's very hit and miss.

That's actually worse than my scenario... yours is giving you a false sense of reliability. My notifications are completely down and out for the count.
 
Last edited:
Part of me is starting to think this is their hidden ploy to force owners of older generation AW devices to upgrade.

I can understand if its a bug here or there, but to terminate bluetooth push notifications... of all the most basic, fundamental functions. Starting to smell fishy. For most its the primary reason to invest in a smart watch.

Its not just us here on AC. If you read the latest AW reviews on playstore, there are many many bugs being commented on.

Well, if they were forcing us to upgrade, it sure is hard to find a new AW 2.0 watch right now. I'd be open to the LG Watch Sport if I could get one.
 
After a week on AW 2.0 on my LG Urbane, I can now say I'm pretty happy with it. The only thing I have changed is my watch face.

If you have issue with notifications, try to change your watch face. Currently, I'm using "Real LED Luxury Watch Face" and my watch does wake up for showing notifications (the watch face does have a designated stop to show the notifications)

However, I don't see really any big killer features on AW 2.0, sure the app list is cool and fast, and overall the UI is a little better.

For the most part my watch is not slow (showing notifications, and interacting with them is my main use. For instance deleting an e-mail, or sending a response to a sms). It can be slow when launching an application. Allthough I'm not using "Ok google", mainly because there is no speaker on the watch and without audible feedback it doesnt feel natural to me (even on AW 1.5)
 
I bought a LG Watch Sport at Best Buy yesterday and returned it today. Seemed extremely cheaply made compared to my Huawei watch. I'll just wait for update, if it ever comes.
 
I bought a LG Watch Sport at Best Buy yesterday and returned it today. Seemed extremely cheaply made compared to my Huawei watch. I'll just wait for update, if it ever comes.

I have both the Huawei Watch and the LG Watch Sport and while the Watch Sport is slightly below the HW; I prefer the LG.

The only negative for the LG WS is the non-replaceable band.
 
No Wear 2.0 update day 70. It has been 10 weeks and there is still no update from Huawei.
What have we learned:
Huawei is not an effective communicator.
Wear 2.0 is really Wear 2.NO.
I have to say that I was really excited to get wear 2.0. However, on a scale of 1 to 10. I was around a 9 in Feb. I am about a 2 now.
 
No Wear 2.0 update day 70. It has been 10 weeks and there is still no update from Huawei.
What have we learned:
Huawei is not an effective communicator.
Wear 2.0 is really Wear 2.NO.
I have to say that I was really excited to get wear 2.0. However, on a scale of 1 to 10. I was around a 9 in Feb. I am about a 2 now.

I emailed Huawei and they said when they get the update from Google they will send it out...but who knows. I'm with ya though, my excitement has dropped from 9 to maybe its time to bail on Android wear all together. I think the programming logic is weak anyways. I came from a Samsung gear 2 to Android, and really, it was a much better OS. I'll be going back to them next watch.
 
I got sick of waiting for 2.0, so bit the bullet, and flashed the dev. preview a few days ago.

TBH, I was getting a little tired of AW anyway. Yeah, it had it's uses, but it was fairly rare that it wasn't just as simple to check my phone, or was just more functional anyway, so I had nothing to lose really.

Personally, AW 2.0 is big disappointment. One of the uses I have (had) was the speaker on the HW, as I sometimes may be upstairs at home, and I get a call. A quick swipe and I can answer on my watch, even if to say I'll call back on the phone. No longer - answering functionality removed. Just reject a call now. Part of the Huawei's individuality gone.

I also found the odd 'OK Google' useful. The new Google Assistant constantly tells me 'I can't do that' for anything other than basic 'What's the time' or 'Who's the Prime Minister', etc etc.

The new version of the cards show a small counter at the bottom of the watch face to show unread notifications - unless you use anything other than the stock faces, and then it doesn't (at least the ones I've tried from AW 1.5 that I liked).

Swipe right - watch faces/ Swipe left - watch faces. Surely you only need one of these? Changing watch faces is not something most people do more than once a day (at most) I would think?

Of course, this is the preview, but I have done a little online research, and the current preview is near final build, so these are clearly issues anyway.

I've decided to sell the HW online to make a few £££. I thought of flashing 1.5 back, but 2.0 is going to be forced at some stage anyway probably, and, regardless, I'm just a bit miffed that what I think is a step back in software is really the best Google could muster for what is already and ailing market.
 
The only problems I have are pressing the pause and prev/next buttons when listening to music. Sometimes they works and then don't.
 
I'm Lukewarm to AW 2.0. It is just a little too slow on my LG Watch Urbane and raising my wrist to look at notifications only works 1/2 of the time. And also can't "gesture" my wrist to go between notifications.
 
I got sick of waiting for 2.0, so bit the bullet, and flashed the dev. preview a few days ago.

TBH, I was getting a little tired of AW anyway. Yeah, it had it's uses, but it was fairly rare that it wasn't just as simple to check my phone, or was just more functional anyway, so I had nothing to lose really.

Personally, AW 2.0 is big disappointment. One of the uses I have (had) was the speaker on the HW, as I sometimes may be upstairs at home, and I get a call. A quick swipe and I can answer on my watch, even if to say I'll call back on the phone. No longer - answering functionality removed. Just reject a call now. Part of the Huawei's individuality gone.

The ability to make/ answer calls has NOT been removed. I used it on my Huawei Watch with the developer preview. You may have to set it up on the watch and phone.
 
I got the update about a week ago for my LG Urbane; pretty much my watch is just a watch now. Got an update to the 2.0 update and then also did all the things the forums suggested. YES I turned on the Ok Google (thanks for turning it off for me??). My watch is pathetically slow to anything and still doesn't do the one thing it has actually been good at. "Ok, Google, remind me to...." or anything else Ok Google is completely broken. Notifications don't notify unless I drill into them manually (no buzz, no quarter moon display). Apps won't open, super slow, unresponsive. This is the worst update ever that makes my watch at best, a time telling device. WTF? This is the kind of thing that would make me consider going to a closed system (Apple) with (hopefully) better QA.... This is wasting my time and removing all the reasons I have a smart watch

I am experiencing the exact same issue. If I wanted a watch, I would have bought a cheap one. I do NOT like not getting a vibration, or any kind of notification at all that I have a notification. It's called a "notification" for a reason.
 
Until I get the update on my Zenwatch 3 I will be calling it Where 2.0. I guess "early Q2" can mean all the way up to May 15. Asus appears to be mum on any further clarification. Maybe I should start tweetshaming them.