We've now seen the entire first generation of Android Wear watches, many of which have their own angle—a reason for being, if you will. The Sony SmartWatch 3 is great for outdoors, the Moto 360 is pretty and round, the G Watch R is rounder, and the original G Watch is cheap (sometimes). The Asus ZenWatch is the last device to hit the market, but just like the others, it now has the Android Wear 5.0.1 update.
Of our many jobs here at Android Police, one is to make our readers' lives easier when we can. With that in mind, here's a roundup of every known Nexus Lollipop OTA. As new ones become available, this post will be updated accordingly.
Lollipop will be released to Nexus 4, 5, 7 (2012 and 2013), and 10, plus bugfix OTAs to Nexus 6 and 9. As I'm sure you've guessed, there will be plenty of files to be had.
Google has just updated the language of the support page where software update policies for Nexus and GPE devices are summarized, and the new text is not exactly encouraging on first read. The following clause, regarding carriers, was added:
Based on your carrier, it may take longer than two weeks after release to get an update.
We do not know if this is merely a safety net to avoid the ire of customers in the case of things like the Nexus 7 2013 LTE and the whole Verizon debacle, or if this is actually a forward-looking change in policy that could affect new devices like the Nexus 6 and Nexus 9 LTE.
You don't need a lot of money to get your hands on Android 5.0. You don't need a current device, either. The Nexus 4 and 2012 Nexus 7, despite being over two years old at this point, both get to taste Lollipop.
Picking up either of these devices is one of the more affordable ways to play around with Google's latest software. But Expansys USA is holding a blowout sale where it will let you digitally walk out with both devices for as low as $159.99.
Yesterday, Google posted the latest factory image for the Nexus 9 (the third one so far), but still had yet to release a factory image for the Nexus 6. Well, LRX21O just went live on the Google Developers site, marking the first available image for Shamu.
This is the version Nexus 6's purchased from retailers today are being upgraded to out of the box, as well, many of which shipped with the LNX07M build, presumably a considerably older ROM.
It's not unusual to see slightly customized builds of Android rolling out to Nexus devices shortly after the release of a new version. It certainly happened a few times with KitKat, and it looks like Lollipop is on track to do the same. As the rush of factory images and OTAs roll out, AOSP is also receiving commits for the new device-specific builds; and Al Sutton was quick to put out changelogs for each version.
Into every life a little rain must fall. Across every software update a few bugs will crawl. The most glaring problem for new users of Android 5.0 on the Nexus 7 2013 is a bug that appears to be stopping video playback dead. You can see a few users reporting the issue here, and we've seen it on at least one Android Police staff member's tablet. The good news is that there appear to be a few ways that you can fix it.
There are a few great choices if you want to jump into the world of Android wearables, but maybe the ZenWatch with its surprisingly reasonable price is the one to wait for. The device has popped up in the Play Store as "coming soon," but Best Buy also has it listed. However, it's sold out there. Update 11/14/14: The ZenWatch is now available for purchase in the Play Store.
If you're trying to flash your Nexus 5, 7, or 10 to Android 5.0 now that the factory images are out, there's nothing more infuriating than running into an error in the process. The most common error we're seeing today as part of the flashing process is the dreaded "missing system.img" dialog, which aborts the update process on the target device.
The reason this happens is because the flash-all script that comes in the image package, which most of you are undoubtedly trying to use, is attempting to flash the .img files in the update using the 'fastboot update' method, which appears to be failing for some reason for some users.