Android Marshmallow, Nougat and O previews and security patches
Marshmallow rollout and 6.0.1
At its event, Google said Marshmallow would begin hitting current generation Nexus devices the following week. That matched the October 5 date from Telus for the Nexus 5 and Nexus 6. The Nexus 7 (2013 model) and Nexus 9 were also on the list. Older devices such as the Nexus 4, an older Nexus 7 and the Nexus 10 stayed on Lollipop. Rollouts are gradual, so not everyone had the update on the day.
Before launch, Google Now on Tap arrived through a Google app update on the third and final Android M developer preview. A long press of the home button shows information about things in any app. It had been announced at Google I/O as a Marshmallow exclusive. That update also moved to a vertical app and widget drawer.
Android 6.0.1 was a small update:
- a new batch of emoji;
- on tablets, home and back buttons moved to the bottom left corner and the multitasking button to the right, for easier thumb reach;
- the “until next alarm” option returned in Do Not Disturb, which existed in Android 5.1 but was missing in 6.0;
- the usual security and performance tweaks.
A later 6.0.1 update came first for the Nexus 5X, with fixes for the fingerprint sensor, camera, performance and Wi-Fi. The Nexus 6P followed with performance, a fix for the Do Not Disturb next alarm option disappearing, carrier-specific bug fixes and connectivity improvements. Factory images were available straight away, and the OTA was due within two weeks.
Nougat: name, delay and bugs
Android N was announced in March and went through many changes. At Google I/O, Google asked the public for name ideas, then revealed Android Nougat. The release was slated for the end of the second quarter for the Nexus 5X, 6, 6P and 9.
When Nougat 7.0 released on a Monday, only a few Nexus phones received it. Google then began posting factory images for a short list of devices, each on build NRD90M:
| Device | Build |
|---|---|
| Nexus Player | NRD90M |
| Pixel C | NRD90M |
| Nexus 9 (Wi-Fi) | NRD90M |
These images were meant for developers and needed an unlocked bootloader. The Nexus 5 and Nexus 7 (2013) were set to receive security updates only.
The Nexus 6 and Nexus 9 LTE were delayed by several weeks. Google told Android Police the update would arrive “in the coming weeks,” with no explanation. A guess at the time was that those devices might jump straight to Android 7.1 with the new Pixel phones.
After Nougat 7.1.1 rolled out to Nexus devices in December, Nexus 6 owners reported a faulty speakerphone. The person on the other end heard an echo and odd noises, while the Nexus 6 owner heard nothing wrong. Users who went back to 7.0 saw it disappear, and it returned with 7.1.1. Muting the mic during calls was the suggested workaround. Google acknowledged it and passed it to engineering, and owners were advised to hold off on updating until a fix appeared.
Android O developer previews
The first Android O Developer Preview was offered for the Pixel, Pixel XL, Nexus 6P, Nexus 5X, Nexus Player and Pixel C. It was not meant for public use and was expected to be buggy. Features highlighted:
- notification channels, which let people control an app’s notification types individually;
- automatic limits on background activity to save battery;
- picture-in-picture video while using another app;
- adaptive icons that can change shape by device;
- wide-gamut colour for apps;
- support for high quality Bluetooth audio codecs;
- Autofill APIs for secure saving of user names, passwords and addresses.
Developer Preview 3 followed three weeks after Preview 2. It contained hundreds of bug fixes and optimizations and the final API level 26. Enrolment in the Android Beta Program was needed for the OTA, and a manual flash was also possible. Google planned one more preview before the final build, and a report claimed Pixel phones might see the official release as early as late August. Notification dots and an Autofill feature like Chrome’s were also part of the plan.
The final release was Android 8.0 Oreo. It reached the Pixel and Pixel XL first, and Rogers set September 11 for the Nexus 6P. At launch the Nexus 6P had a 5.7-inch QHD (1440 x 2560) display, a Snapdragon 810, 3GB of RAM and 32GB, 64GB or 128GB of storage, and was made by Huawei.
Monthly security patches and factory images
Google began issuing monthly security updates for Nexus devices and made them mandatory for Android OEMs to deliver. The first one in the series fixed 12 issues, 5 of them critical. The worst allowed remote code execution through email, web browsing and MMS when processing media files. The update reached a Nexus 6P first, and users without a notification could check manually in settings.
A later July post listed builds for that month’s factory images:
| Device | Build |
|---|---|
| Nexus 6P | MTC19X |
| Nexus 5X | MTC19Z |
| Nexus 6 | MMB30K and MOB30O |
| Nexus Player, Nexus 9 (LTE and Wi-Fi), Nexus 5, Nexus 7 (Wi-Fi and 3G) | MOB30P |
Another release stopped being factory-image only: Google started giving OTA download links beside the factory images, so owners no longer waited for someone to find the URL. Installing still meant adb sideload, but it kept the phone data intact. A March patch fixed a serious remote code execution flaw and covered Nexus devices on Android 6.0 or newer. BlackBerry was the first OEM to ship that patch.
Frequently asked questions
Which Nexus devices got Marshmallow first?
The Nexus 5, 6, 7 (2013) and 9 were named for the first wave. The Nexus 4 and Nexus 10 stayed on Lollipop.
Why was Nougat late on the Nexus 6?
Google did not explain, only that it would arrive in the coming weeks.
Did the Android O preview work on every Nexus?
No. Only the Pixel, Pixel XL, Nexus 6P, Nexus 5X, Nexus Player and Pixel C were listed.
How was a factory image different from an OTA?
A factory image wipes the phone; an OTA flashed by adb sideload does not.