Starting in Android 4.4, Google implemented verified boot (known as dm-verity) in the Android kernel to prevent malware from hiding in your device. This was all behind the scenes until Android 6.0 Marshmallow—that's when Google started alerting users to system integrity. In Android 7.0, it's going a step further. In Nougat, verified boot will be "strictly enforcing" and won't allow your device to boot if the software has been compromised. Android will also be able to correct errors, but this will cause some headaches for modders.
Read MoreVerified boot in Android 7.0 won't let your phone boot if the software is corrupt was written by the awesome team at Android Police.
from Android Police – Android News, Apps, Games, Phones, Tablets http://ift.tt/29VpjQ5
via IFTTT
No comments:
Post a Comment