A few months back the Nexus 6 received the Android 7.1.1 update, likely the last major update the device would receive. A while after however, the update was retracted and strangely an OTA was pushed to roll Nexus 6 users back to 7.0, citing no reason as to why. At the time, a community manager on Reddit had this to say.
“Hey All,
There was a recent OTA update for Android 7.0 that is causing confusion for some Nexus 6 users. For those of you that want to guarantee future OTA updates, you will need to get back on the 7.0 supported track. If you are experiencing issues after accepting the 7.0 update, please factory reset your device to help resolve any problems.
For any Nexus 6 users that want to continue flashing/sideloading future builds, you can stay on 7.1.1 and continue to do so.”
This update caused many problems, including people having to factory reset their devices after rolling back to 7.0. Any users who stayed on 7.1.1 were warned they would not receive any future updates, and so that does seem to be the case for anyone who stayed on 7.1.1 without rolling back. This hasn’t been the only mistake made with the Nexus 6 in terms of updates however. The March 2017 security update also broke Android Pay support, although that was fixed soon after.
However now according to claims from Nexus 6 users on Reddit, the seemingly-forgotten Google device has now received an OTA update for Android Nougat 7.1.1.
With this comes a few changes, such as a reboot option in the power menu among other optimizations and improvements gained from Android 7.1.1. It appears Google is being extra cautious with this update, as it was reported on Reddit nearly a week ago to be rolling out. This is likely to be the last official incremental version upgrade, and anyone looking to upgrade to Android O when it comes out should keep an eye on our Nexus 6 forums. The Nexus 6 should still enjoy security updates until October 2017, and after that the device is officially end of life.
Source: /r/Nexus6 on Reddit
from xda-developers http://ift.tt/2wPA0gx
via IFTTT
Aucun commentaire:
Enregistrer un commentaire