Google has brought plenty of security improvements to Android over the years, such as theft protection and scam detection<\/a>. However, the company is now bringing another noteworthy security feature to Android 17<\/a>.<\/p>\n Don\u2019t want to miss the best from Android Authority?<\/strong><\/p>\n Google has announced that it\u2019s bringing an OS verification feature to Android 17. The company says it developed this feature in response to bad actors releasing modified versions of Android that look like the real deal.<\/p>\n \u201cThese malicious versions are created to deceive you by mimicking the official OS while secretly compromising the integrity of your device,\u201d the company explains.<\/p>\n The company says Android OS verification will help you confirm that your device is indeed running an official, widely distributed Android build. A close look at an official screenshot (seen above) shows a menu displaying Play Protect status, bootloader status, and build number info. It also looks like you can verify your Android OS with another device, but Google didn\u2019t reveal more details about this option.<\/p>\n Google says Android OS verification will initially launch on Pixel phones<\/a>, ostensibly as part of the stable Android 17 release. So we\u2019re guessing that other OEMs will gain this feature when they eventually release stable Android 17 on their devices too.<\/p>\n This seems like a pretty passive take on OS verification, but we do wonder what this means for custom ROMs and Android forks like GrapheneOS. This news also comes a couple of days after the GrapheneOS team criticized Google\u2019s device verification systems<\/a>, saying it could lock people into the company\u2019s ecosystem.<\/p>\n Otherwise, Google also announced that it will offer a \u201cpublic, append-only ledger\u201d to provide cryptographical proof that Google\u2019s Android apps and APIs are legitimate releases.<\/p>\n The company describes this as a \u201cSource of Truth\u201d that anyone can check:<\/p>\n If a Google-signed app isn\u2019t on this ledger, we didn\u2019t intend to release it. For Pixel users, this works with our existing Pixel System Image Transparency to prove that both the system itself and the apps running on it are official production software.<\/p>\n<\/blockquote>\n Either way, we\u2019re glad that Google is bringing more security features to Android. We were a bit concerned this might adversely affect non-Google Android releases, and reached out to ask Google what OS verification means for custom ROMs and forks. The company tells us:<\/p>\n This feature provides transparency for users on Android certified devices and does not apply to custom ROMs or forks. Separately, developers use either Play Integrity API or Key Attestation for device transparency and making device trust decisions. Our goal is to empower users on certified devices with OS clarity without restricting the broader Android developer community.<\/p>\n<\/blockquote>\n That\u2019s just what we were hoping to hear!<\/p>\n Updated to add Google\u2019s response about custom ROMs and third-party devices.<\/p>\n![\"google](\"https:\/\/www.europesays.com\/uk\/wp-content\/uploads\/2025\/09\/google_preferred_source_badge_light@2x.png\"\/ "\\"google"){kind=icon}
![\"google](\"https:\/\/www.europesays.com\/uk\/wp-content\/uploads\/2025\/09\/google_preferred_source_badge_dark@2x.png\"\/ "\\"google"){kind=icon}
<\/a><\/p>\n![\"Google](\"https:\/\/www.europesays.com\/uk\/wp-content\/uploads\/2026\/05\/Google-Android-17-OS-verification.jpg\"\/ "\\"Google")
<\/p>\n\n
\n