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

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 612505
To read all comments associated with this story, please click here.
Instead...
by patrix on Sat 13th Jun 2015 14:58 UTC
patrix
Member since:
2006-05-21

Instead, it would have been better if Motorola had pushed out a half-baked update that performed poorly or destroyed even more battery life? Just so you could get the update at the same time as everyone else?

Or perhaps ALL the other smartwatches updates should have been delayed because the 360 needed more optimisation?

Reply Score: 2