jeudi 30 mars 2017

Android Wear 2.0 Rolling Out to Fossil, Casio and TAG Heuer Smartwatches, Bug Delaying Update

Google officially announced the Android Wear 2.0 platform update back in February, with the LG Watch Style and Watch Sport being the first devices to come running the new software out of the box. The Android Wear 2.0 update is in many ways a substantial upgrade and brings quite a few useful features, such as Android Pay support, Google Assistant, an on-watch Google Play Store, Standalone Apps and a whole lot of under-the-hood optimizations.

Since Google reportedly has a much bigger stake in rolling out updates for smartwatches, unlike smartphone updates, many were hoping that the Wear 2.0 would be rolled out to supported hardware in a timely manner. Sadly though, it’s been almost 2 months since the Google dropped the update and most devices haven’t received it still. But that seems to be changing now, as updates have officially started rolling out to some of the supported watches.

As announced on Google’s Android Wear support forum, the Fossil Q Founder, Casio Smart Outdoor and TAG Heuer Connected will be the first to receive the Wear 2.0 update. The OTA rollout was supposed to start from March 29th and will finish by April 4th, so we will assume that users will likely start seeing update prompts in the coming days.

As for when the update will be rolled out to other watches, it appears that a bug discovered in the final build of software is holding up the update rollout. Google has talked to Wareable about this issue and has promised that the update will be rolled out to remaining devices as soon as they found the fix.

“We have started rolling out the Android Wear 2.0 update to Fossil Q Founder, Casio Smart Outdoor Watch WSD-F10 and Tag Heuer Connected. For other devices, the update is currently being delayed due to a bug found in final testing. We will push the update to the remaining devices as soon as the issue is resolved.”


Source: Android Wear Support Forum Via: Wareable



from xda-developers http://ift.tt/2ocHubM
via IFTTT

Aucun commentaire:

Enregistrer un commentaire