Linked by Thom Holwerda on Fri 12th Jun 2015 10:37 UTC

When Android Wear came out over the course of last year, Google promised that the young, new platform would receive updates "early and often". While it wasn't said with so many words, it's easy to read between the lines: Google was going to make sure Android Wear users wouldn't face the same headaches as Android users when it comes to updates. Wear would be a more tightly controlled platform, built in such a way that updates could go straight to users' devices without meddling from carriers or roadblocks thrown up by crappy customisations.

Fast forward to June 2015, and Google has recently released Android Wear 5.1.1, which, despite its humble version number increase over 5.0.1, is a pretty significant update to the smartwatch platform. It enables WiFi on devices that support it, adds new ways to interact with your watch, and makes it easier to launch applications. All in all, it looks like a great update.

Sadly, I can only go by what others have told me, despite owning the poster Android Wear device - the Moto 360.

Thread beginning with comment 612480
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Voting with my wallet
by gan17 on Fri 12th Jun 2015 13:58 UTC in reply to "Voting with my wallet"
Member since:

And how do you suggest we do that if we, quite literally, don't have an option to vote for? Should I buy a Nexus 6 even though I find it to be far too large and overpriced on the magnitude of an iPhone?

Size, price, and overall fugliness aside, I'm not even sure if the Nexus 6 is getting updates as timely as the Nexus 5. I recall reading that Google went back to partnering with carriers for this device (mainly because of the steep price). I assume those that bought it outright directly from the Play Store will get timely updates, but what about those who got it from carriers?

Reply Parent Score: 2