Google has released Android 16 QPR2 Beta 2, confirming that the API surface is now locked and app-facing behaviors are finalized. Developers can now safely adapt their apps to the latest features ahead of the stable rollout.
Matthew McCullough, VP of Product Management for Android Developer, said that at this stage of the development cycle, the team is focused on readying the platform for release. He also outlined several key changes introduced in this beta.
Key Features in Android 16 QPR2 Beta 2
1. Developer Verification Testing
A new developer verification system aims to improve user safety by reducing the risk of malware:
- From September 2026, in select regions, apps will need to be registered by verified developers to be installed on certified Android devices.
- Installs made through Android Debug Bridge (ADB) will remain exempt, so developers can continue to test apps without restrictions.
- New APIs are included to support verification checks during installation, along with tools for simulating both successful and failed verification results.
2. SMS OTP Protection
To prevent OTP hijacking attacks:
- SMS messages containing retriever hashes will be delayed by three hours for most apps.
- The
RECEIVE_SMSbroadcast and SMS database queries will be withheld during this delay. - Exemptions apply to core apps such as the default SMS, assistant, dialer, system apps, and connected device companion apps.
- Apps can still rely on the SMS Retriever API for timely OTP access.
3. Custom App Icon Shapes
Android 16 QPR2 adds support for multiple icon shapes. These apply consistently to app icons and folder previews, requiring developers to ensure adaptive icons display correctly in all available styles.
4. More Efficient Garbage Collection
The Android Runtime (ART) now uses a Generational Concurrent Mark-Compact (CMC) Garbage Collector:
- Focuses on newly created objects that are most likely to be discarded.
- Reduces CPU load from garbage collection.
- Provides smoother performance with less lag.
- Enhances battery efficiency.
5. Health Connect Enhancements
Health Connect introduces native step tracking using device sensors:
- Apps with the
READ_STEPSpermission can now directly access step data from the Android system. - This simplifies implementation and consumes less power.
- Updates to ExerciseSegment and ExerciseSession data types add support for recording weight, set index, and Rate of Perceived Exertion (RPE).
- As Health Connect updates independently of Android, developers are advised to check for feature availability to maintain compatibility.
Minor SDK Version Support
Android 16 QPR2 introduces the first minor SDK version, allowing Google to roll out new APIs more frequently outside the annual release cycle:
- These changes are additive, avoiding app-breaking behavior.
- Developers can detect and use QPR2-specific APIs by checking for the new minor SDK version values.
- Minor SDK versions cannot be declared in
uses-sdkmanifest attributes, as they are not intended to introduce breaking changes.
Availability and Getting Started
Supported Pixel devices can be enrolled in the Android Beta Program to receive the update over-the-air.
- Non-Pixel users can access 64-bit system images through the Android Emulator in Android Studio.
- Devices already in the Beta Program will automatically get Beta 2.
- Canary Program users must wipe and manually flash their devices to switch to the Beta track.
Google recommends using the latest Android Studio Narwhal Feature Drop (Canary) for the best development experience.