Google announced last year that the venerable Galaxy Nexus would not be getting any of that sweet, sweet KitKat action. Well, not officially anyway. Owners were not pleased, but they couldn't properly flood the internet with complaints because their phones were already dead. There have been a few KitKat ROMs that work well enough, but now some developers have created a kernel and GPU driver combo that could keep this device chugging along through the L release.
It's that time of the month again, CyanogenMod ROM fans. In fact it's a bit past that time of the month, reportedly thanks to a heavy workload and the Labor Day weekend, but now that the CM11 monthly update is up to the M10 release, we won't hold it against the CyanogenMod Team. The biggest change to the M build is a brand new bug tracker app, which makes it easy for users to submit anonymized bug reports to CM along with a stacktrace whenever a system app crashes.
Typically Christmas day is a slow one for technology news, but apparently the good folks at the Android Open Kang Project have dragged their coding machines in front of the open fire. Today AOKP has posted the first nightly builds of Android 4.4.2, granting deliciously fresh custom ROMs to all the good little girls and boys. And all the bad ones too, I suppose.
The list of initially-supported devices doesn't cover AOKP's official support list yet, but it covers most of the major Nexus devices, Samsung's Galaxy SIII and S4 American and international incarnations, all five major versions of the HTC One, and a handful of Sony devices (because they tend to be pretty open as far as bootloaders and modifications go).
Did you know it's possible to unlock your Nexus 5 bootloader without wiping user data? If your device has already been rooted and relocked for optimal security, then unlocking is just a button tap away thanks to the latest update to BootUnlocker. Support for Google's latest flagship phone was just added with an update to version 1.4 of the app from XDA member segv11. Sadly, both generations of the Nexus 7 from ASUS remain unsupported.
Update: Here's an official Google Support answer stating the GNex will indeed be stuck in 4.3-land for eternity.
At the bottom of Google's official Android 4.4 announcement post on the company's blog, some rather pertinent information for current Nexus / GPE device owners is thrown in: OTA update news!
KitKat will be coming to the Nexus 4, Nexus 7 (presumably both models, but not explicitly stated), Nexus 10, and the Google Play Edition Galaxy S4 and HTC One.
Sprint Galaxy Nexus owners, you can put down those pitchforks. Your Android 4.3 update is finally coming. Sure, it's arriving just in time for Android 4.4, but hey, it's not like anyone promised that your updates would be timely. Oh, they did? Well, it gets worse. The update is rolling out in stages over a 10 - 21 day period, and device selection is random. Some of you may still have close to a month to go.
Google has just posted updated factory images and driver binaries for the Nexus 7 (2013 and 2012), Nexus 4, Nexus 10, and Galaxy Nexus (yakju / takju variants) based on the new Android 4.3 bugfix builds JWR66Y and JSS15Q (2013 Nexus 7 only). The new builds follow OTA updates that have been rolling out over the last couple of days.
You can get the binaries and images at the links below.
Yesterday T-Mobile rolled out a relatively small OTA for the Nexus 4 bringing about a set of security improvements. As it turns out, the latest Nexus handset isn't the only one receiving the update. The Galaxy Nexus is also getting the JWR66Y firmware, and there's a manual update available for those of you who just can't bear the wait. This one is for the yakju variant of the phone, those sold through retail channels other than Google Play.
Android 4.3 was officially unveiled and released two days ago to the Android Open Source Project. In a surprisingly timely fashion, Google also released both the factory images and OTAs to the Nexus 4, 7, 10, and the Galaxy Nexus.