Following closely behind the 2012 and 2013 Nexus 7 KitKat OTA updates, it's finally the Nexus 10's turn to receive the same treatment. You can now flash the 219MB KRT16O Android 4.4 build without having to wait for your tablet to alert you, no matter what your rooting/bootloader situation is. Of course, if you've modified the system partition in such a way that the OTA won't apply cleanly anymore, you have to either revert those changes or wait for the factory image.
Artem is a die-hard Android fan, passionate tech blogger, obsessive-compulsive editor, bug hunting programmer, and the founder of Android Police.
Most of the time, you will find Artem either hacking away at code or thinking of the next 15 blog posts.
Yesterday, Google announced the kickoff of the KitKat OTAs for the Nexus 7 and 10, though we haven't seen the update for the 2012 N7 actually pop up until a few minutes ago. (If you have a 2013 Nexus 7, head over here.)
2012 Nexus 7 Wi-Fi (not 3G yet) owners, listen up. You can now flash the 185MB KRT16O Android 4.4 build without waiting any longer, no matter what your rooting/bootloader situation is.
Now that the KitKat update has started rolling out to various Nexus devices, we're, unfortunately, seeing no traces of the Google Experience Launcher, which confirms an earlier report stating as much. No GEL means no transparency in the default and a pretty barebones boring AOSP launcher. It also means no Google Now integration and no "Ok Google" hotword support while on any home screen.
Boring Nexus 7 launcher
However, not all is lost.
Last night, roughly two weeks after the Nexus 5's release, Google announced the first round of KitKat updates for the Nexus 10 and 2012/2013 Nexus 7. While most of us are still waiting our turn, maniacally mashing the Check for updates button, the over-the-air update url has been discovered.
That means you can easily flash the 243MB KRT16O Android 4.4 build right now without waiting any further, no matter what your rooting/bootloader situation is.
It was understandable when early pre-release specs listed the Nexus 5 as having a fictional 802.11nc (as opposed to 802.11ac) Wi-Fi, which many definitely noticed at the time. After all, the Nexus 5 wasn't official yet, and something like that could have been a typo made by a PR person or an intern.
Earlier this week at a Google+ event, the company announced several important additions to Hangouts for Android. The updated version 2.0 comes with SMS support as well as location sharing, the ability to display animated GIF files, as well as the previously discovered in a teardown statuses and moods. AndroidPolice covered the rumor on October 7th following my initial Google+ report on October 4th.
The coveted update may take a while to reach you, considering it hasn't even started officially rolling yet.
Android 4.4 is out, and that means developers and tinkerers have already started digging through the code and various APKs in hopes of porting as many updated apps as possible for use with existing devices. The first and easiest app to extract is, unsurprisingly, the clock, which also acts as an alarm, timer, and stopwatch. I've installed it on my Galaxy Nexus without any issues and only had to clear data to get rid of the pesky force close, which is completely undestandable.
Just a quick note to anyone waiting for full OS factory images and drivers for existing Nexus devices (outside of the Galaxy Nexus, which bit the dust with KitKat) - as is customary, they will follow over-the-air updates released according to Google's favorite timeline: "in the coming weeks."
The Nexus 5 factory images will be out later today, but don't sit there hitting F5 expecting factory images for the Nexus 4, 7 (new and old), or 10 to pop up any time soon.
After announcing KitKat and the Nexus 5 earlier today, and releasing the Android 4.4 SDK, tools, and other related goodies, Google has moved on to the next important step - source code. As announced on the Android Building forum, Android 4.4 is now trickling in, bit by bit, into the AOSP repos. If all goes well, we can expect it to complete within several hours.
Update: The source push is 100% complete.