Play Integrity

AppWizard
October 13, 2026
LineageOS has released a new nightly build, LineageOS 24.0, for the Google Pixel 10 (codenamed frankel), dated October 11, 2026, with a size of 1.61 GiB and an October 2026 security patch level. The build is named lineage-24.0-20261011-nightly-frankel-signed.zip and is based on the Android 17 framework. Installation requires the latest Android 17 firmware, a computer with adb and fastboot, USB debugging enabled, and prior booting into the stock operating system. Users should check essential features like SMS and calls, and remove Google accounts to avoid Factory Reset Protection issues. Apps requiring device-integrity checks may not function correctly. Nightly builds for the Pixel 10 Pro were reported available on October 12, 2026, while builds for other models like the Pixel 10a, Pixel 10 Pro XL, and Pixel 10 Pro Fold have not yet been released.
AppWizard
June 26, 2026
Brian from iodé discussed the project's goal of creating a user-friendly, privacy-focused Android distribution. Key features include a tracker blocker that enhances user privacy and two app stores—F-Droid and Aurora Store—to address app compatibility concerns. Users can uninstall pre-installed apps and experience reduced notifications and ads. iodé promotes sustainability by encouraging the use of refurbished devices and aims to support a wider range of devices beyond just Google Pixels. The user base is estimated at over 10,000 individuals across various countries, with a focus on privacy and usability. iodé offers integrated privacy features and monthly security updates, supporting over 60 devices.
AppWizard
March 11, 2026
UnifiedAttestation is a new initiative from Europe aimed at creating a free and open-source alternative to Google’s Play Integrity checks, which are essential for banking, financial, and government applications. Many of these applications currently rely on the Play Integrity API, which does not support custom ROMs or alternative Android forks, limiting access for users of these systems. The initiative is backed by smartphone manufacturer Volla and partners like Murena and iodé OS. UnifiedAttestation will be distributed under an Apache 2.0 license, allowing developers to adapt it, with Volla stating that integration requires only a few lines of code. However, the Graphene OS team has expressed concerns about the ethical implications of smartphone manufacturers determining which operating systems can use their applications, advocating for the regulation of the Play Integrity API instead.
AppWizard
February 19, 2026
Google blocked over 255,000 Android apps from gaining excessive access to sensitive user data and rejected more than 1.75 million apps from publication on Google Play due to policy violations. The company banned over 80,000 "bad developer accounts" and detected more than 1.75 million policy-violating apps. Google blocked 160 million spam ratings to prevent an average 0.5-star drop in targeted apps. Play Protect scans over 350 billion apps daily, identifying over 27 million malicious apps sideloaded from outside Google Play, and successfully blocked 266 million installation attempts from 872,000 unique risky apps. The Play Integrity API processes over 20 billion checks daily, and new hardware-backed signals and in-app remediation prompts were introduced in 2025. Android 16 includes built-in protections against “tapjacking attacks.”
AppWizard
August 1, 2025
Google has implemented a measure to enhance the security of its messaging platform by preventing devices that fail Play Integrity checks from sending Rich Communication Services (RCS) messages. This decision has led to users experiencing vanished messages without explanation, particularly affecting those with rooted phones or custom ROMs. Recent developments indicate that Google Messages will now inform users when their devices do not meet security requirements, with a new text string stating, "Your device does not meet security requirements," expected to appear in the RCS settings. Additionally, a "Details" button is anticipated to provide further clarification on RCS limitations. This change aims to improve user communication and reduce confusion regarding message disappearances.
Search