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 612531
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Comment by sb56637
by Bill Shooter of Bul on Mon 15th Jun 2015 15:08 UTC in reply to "Comment by sb56637"
Bill Shooter of Bul
Member since:

There is more to an operating system than just a kernel, device drivers and a gui. I think this is where you're misunderstanding lies.

With that division, I think everything you'd care about that you didn't name would be in the "GUI". And we'd still be stuck in the same place we are now. Can't just update the "GUI" without consequences.

Reply Parent Score: 2