Android Jelly Bean, KitKat and Lollipop rollouts and Nexus updates
Jelly Bean: 4.2.2 and the lead-up
Before Jelly Bean arrived, the rumours were piling up, and one post noted jelly beans scattered on the lawn at the Googleplex. That echoed the way earlier releases had been teased with statues and desserts.
Android 4.2.2 began rolling out officially to Nexus devices. Nexus 7 and Nexus 10 owners could expect an over-the-air update, while the Galaxy Nexus depended on where it was bought and whether the yakju software had been flashed before. The Nexus 4 had not received the update yet, although several Nexus 4 units were shipping with 4.2.2 preinstalled. The update looked like maintenance and bug fixes.
Google later published a full change log for Android 4.2. Notable items were a completely redesigned camera app with HDR mode enabled, a reworked clock app and widgets, and a triple tap gesture for full screen magnification, which helps people with poor eyesight.
KitKat: naming, teasers and the first updates
A leaked Google Play screenshot, taken from a Korean keyboard update, suggested the status bar icons in Android 4.4 might change from blue to grey. The debugging icon looked like a piece of pie rather than a jelly bean, which fed the idea that 4.4 had been planned as Key Lime Pie before the deal with Kit Kat. This was only a leak, and the release was then expected to arrive with the Nexus 5.
When the name was revealed, Google’s CEO received an Android shaped Kit Kat bar. The promotion also included a contest: buying a promotional Android Kit Kat bar entered the buyer in a draw for a new Nexus 7. It was first believed to be US only, but promotional bars with English and French packaging turned up in a Canadian supermarket, so Canadians could enter as well, though the bars were not necessarily available everywhere.
KitKat then started reaching the Nexus 7 (both generations) and the Nexus 10, Wi-Fi models first, with 3G and 4G variants expected later. As always the rollout was gradual.
KitKat maintenance releases
| Version | What it did | Devices |
|---|---|---|
| 4.4.1 | Camera improvements for the Nexus 5, minor bug fixes elsewhere | Nexus 5, Nexus 4, Nexus 7 |
| 4.4.2 | Small bug fix update; users still on 4.4 jumped straight to it and got 4.4.1 changes too | Nexus 4, 5 and 7 |
| 4.4.3 | Fixed more bugs, mainly on the Nexus 5, including the mm-qcamera-daemon bug that drained the battery when camera apps ran; slight redesign of the Dialer and People apps | Factory images, also pushed to AOSP |
| 4.4.4 | Arrived about two weeks after 4.4.3; newer Nexus 5 baseband and a patch for an OpenSSL vulnerability; no UI change | OTA for Nexus 5 first; others by factory image |
Factory images erase all data, so flashing one is a trade off against waiting for the OTA. The 4.4.4 update did not close the Towelroot exploit, so rooting stayed easy at the time. The 4.4.1 rollout was also described as slow on purpose, so Google can catch bugs, and sideloading through ADB was possible but at the owner’s own risk.
Lollipop: Android L and 5.0
A Google tweet about World Cup cards on Google Now showed three devices with the clock set to 5:00, which people read as a hint of Android 5.0 and a dessert starting with L. It was speculation. Later, a Google teaser video with candidate L treats did confirm that the next version number would be 5.0, a full number jump that fitted the heavy UI changes. The exact name was not yet known at that point.
A feature called Hands-free briefly showed up on Nexus devices running Lollipop after a language change and then vanished. It was inactive and was expected to read out notifications, similar to Moto Assist on the Moto X. This was an unconfirmed finding.
After 5.0 went out as an OTA on Nexus devices and some Motorola phones, two Google engineers were seen using Lollipop MR1 on a Nexus 5 at a talk in Belgium on Material Design. MR1 means Maintenance Release 1, which hinted at Android 5.1.
Android 5.0.1 and 5.1 on Nexus
Android 5.0.1 reached every supported Nexus device except the Nexus 5 first. It then started rolling out to the Nexus 5 with build LRX22C, with factory images available. It was aimed at bugs from 5.0 such as battery drain and memory leaks.
Before 5.1 shipped, a tip pointed to a release later that week for the Nexus 4, 5, 6, 7, 9 and 10, with fixes for memory use and battery life and maybe a redesigned silent mode. Builds LMY36B (Nexus 4) and LMY40 (Nexus 6) were spotted on an issue tracker. Android 5.1 then arrived with:
- device protection, which keeps a wiped phone tied to a Google account;
- HD Voice (AMR-WB) support;
- Dual SIM support;
- a Wi-Fi and Bluetooth dropdown toggle in quick settings;
- a fix for the memory leak and for old apps appearing in recents.
Factory images came first for the Nexus 5, 7 and 10. It was unclear whether Android Wear would receive the update.
Android 5.1.1 followed. It had already reached the Nexus 9, and the carrier Sprint listed it for the Nexus 5, though that carrier had jumped the gun before on release dates. It was expected to resolve memory leaks, the bouncing list bug and security issues.
Frequently asked questions
Why did Android 4.4 become KitKat?
Google partnered with Kit Kat for a promotion. A leaked screenshot suggested the release had once been planned as Key Lime Pie.
Which update fixed the Nexus 5 camera battery drain?
Android 4.4.3 fixed the mm-qcamera-daemon bug on the Nexus 5.
What did Android 5.1 add?
Device protection, HD Voice, Dual SIM and a quick settings toggle for Wi-Fi and Bluetooth, plus memory leak fixes.
Can these updates still be installed?
The devices and versions are long out of support, so this page is historical. Flashing a factory image wiped the data at the time.