14 DAY TRIAL // A few days ago, leaked documents coming out of Canadian carrier TELUS revealed that the highly anticipated Android 6.0 Marshmallow update was bound to hit the Nexus 6, Nexus 5 smartphones on October 5 in the country.
Google is expected to host a press event today (September 29), during which the new operating system will be launched for the masses, after being made available in its technical preview form.
But even if Android 6.0 Marshmallow is officially released on September 29, along with the brand new Nexus 5X and Nexus 6P, the new build won’t be available right away, as the TELUS documents clearly showcase.
Well, a new report coming out of Android Police is here to confirm the previously known date. So, it seems that the official rollout for supported Nexus devices will start on October 5 in the US as well.
The models that are going to receive the OTA update are: the LG Nexus 5, Motorola Nexus 6, ASUS Nexus 7 (2013), HTC Nexus 9, and ASUS Nexus Player.
Not all Nexus models will be getting Android 6.0 Marshmallow
Sadly, that means the older LG Nexus 4, ASUS Nexus 7 (2012) and Samsung Nexus 10 will not be getting the Android 6.0 Marshmallow update due to their advanced age. Unfortunately, these troopers are bound to remain stuck to Android Lollipop forever.
The final Marshmallow code will be pushed to the AOSP (Android Open Source Project) on October 5, as well.
As it often happens with Google updates, the OTA updates will probably reach some users sooner than others based on their location across the globe. Luckily, the update ZIP files will probably be made available soon after the official launch, so if you can’t wait, you’ll be able to go ahead and update manually. The factory images will also be offered, in case users need to flash back to stock.
Stay tuned for more information today, when Google finally takes the stage to officially launch its latest Nexus hardware efforts alongside its newest Android iteration. The two new Nexus phones will be offered for purchase in mid-October, if nothing goes wrong, that is.