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.
T-Mobile's VoLTE rollout is continuing full steam ahead, and today, the Uncarrier is giving more customers access to it thanks to a new software update for LG's mammoth G Flex.
Now that Lollipop is out in the wild to be abused in every which way, we're starting to see the bugs pop up. The latest one has to do with that new flashlight toggle in quick settings. If you turn it on and leave it like that until it times out and shuts off, the camera and flashlight will stop working until you reboot. This is confirmed at least on the Nexus 5.
Turn those frowns upside-down, Nexus 4 stalwarts. Your beloved Nexus of yesteryear is finally getting that sweet, sweet Lollipop goodness in an official capacity, just as we expected. Google has posted the full system image that takes the Nexus 4 all the way to Android 5.0.
Update: Let us not forget the Galaxy Tab S 8.4. AT&T has updated that device this week as well, bumping it up to KOT49H.T707AUCU1ANJ5 after a 32MB download. As for the changes, they're a yawn.
- Carrier Billing enhancements
- Updates to ATT Mail, Keeper, YPMobile
Those changes are largely the same as the Galaxy Tab S 10.5's OTA this week. This 58MB update left the device at build number KOT49H.T807AUCU1ANJ5.
Nexus 4 owners will be pleased to hear that Lollipop build LRX21T is on its way for their devices. While there isn't a specific time frame for the rollout, Sascha Prüter states in a post to Google+ that the build is "locked and loaded," indicating in the comments that LRX21T is destined for the Nexus 4 some time soon.
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.
It's the moment you've been waiting for. Google just announced the Nexus devices are getting OTA updates to 5.0, and now the full system images have been posted on the Google Developers site. With these files, you can flash your device back to stock even after you've done unspeakable things to it.