Android Oreo is slowly coming to devices, both officially and unofficially. Google isn’t slowing down though, releasing the September security patch factory images of Android Oreo for the Nexus 6P, Nexus 5X and the Pixel C. These devices are still officially fully supported by Google, both for major upgrades and security updates. Other devices, such as the Nexus 6 and Nexus 9 received the security update to September 2017. You can view the final dates of scheduled updates for Google’s devices below.
The September Android Oreo upgrade includes the latest security patches from Google, which we covered when it was announced. A number of security tightening measures and vulnerability patching measures were taken, making this one of the most vital security updates yet. BlueBorne, “Cloak and Dagger”, and a number of other Qualcomm, Broadcom and kernel components were issued fixes for critical vulnerabilities. 81 CVEs were patched, if you’re not on this update then we highly suggest you upgrade if you can. It patches some of the largest bugs we’ve ever seen on Android, and all at once.
What if I can’t get the September security patch?
First off, it is extremely like you will be fine. Be careful, don’t install apps that you shouldn’t from non-Google Play Store sources. Use common sense and you should be okay. Still, it can happen to the most careful of people that they accidentally manage to run into an app exploiting one of these vulnerabilities. Here at XDA, we would recommend taking a glance at our forums for your device and seeing if a custom ROM has the latest security patches. There are so many well polished and updated ROMs on your forums, so go check them out for your device! If you would rather not unlock your device but still really want to receive the latest upgrades, then really all you can go with to be guaranteed updates are a Nexus or Google Pixel, be it the Google Pixel or the Google Pixel 2 which looks like it may be coming soon– though without the Snapdragon 836.
Source: Google
from xda-developers http://ift.tt/2jsNcFh
via IFTTT
Aucun commentaire:
Enregistrer un commentaire