Nexus 6 Gets Latest Android 7.1.1 Update With New Bug Fixes

Nexus 6 Gets Latest Android 7.1.1 Update With New Bug Fixes

Most tech and phone enthusiasts probably know that Google’s Nexus 6 started to receive the Android 7.1.1 update at the beginning of 2017, but multiple complaints about the issues and bugs appearing on the device made Google take a step back and pause the release. At the moment, it seems that the software company is finally ready to release the update on the device since it looks like they solved the bug problems that appeared back in March.

Android Police is the one who received the news from two users that stated their Nexus 6 devices received the update to Android 7.1.1 Nougat, meaning that Google released a new and more solid Android version. Despite the fact that Android users are excited about this news and understood why Google had to make a pause in order to fix the bugs and address the issues, some of the people were quite disappointed it took this long for an update/fix to be released.

The update has approximately 368 MB and users who run Android 7.0 on their devices should upgrade to the newer version with no problem. However, the users who had the original Android 7.1.1 for Nexus 6 will be required to go back to the original update track before upgrading to the latest version in order to receive all future updates as well. Even if it received this final update, it should be kept in mind that the device is nearing the end of its life on Google, since there is a small chance it will be seen on Android O.

It is rumored that this update will be the last official one, but there is a possibility that other security patches Nexus 6 will eventually receive. Furthermore, the Android 7.1.1 is considered more like a minor upgrade to Android 7.0, but the update was more than necessary in order for the device to run smoothly.

Get more stuff like this
in your inbox

Subscribe to our mailing list and get interesting products and updates to your email inbox.

Thank you for subscribing.

Something went wrong.