Android 16 QPR2 Beta 2 Update: Google Starts Blocking Unverified Apps

After the Google Pixel 10 series launch event, Google rolled out the second phase of its Android 16 beta program, wrapping up QPR1. Android 16 QPR2 Beta 2 brought Pixel 10 series compatibility to Android 16 QPR2. This update introduces custom app icon shapes, native step tracking, expanded exercise data integration with Health Connect, improved garbage collection efficiency, and enhanced SMS OTP protection.

The latest Android 16 QPR2 Beta 2 implements refined SDK versioning that enables continuous innovation delivery while introducing comprehensive features spanning UI enhancements, media improvements, connectivity upgrades, security reinforcements, and advanced developer tools that create exceptional opportunities for application enhancement.

QPR2 Beta 2 represents a significant milestone by achieving Platform Stability. This update has locked the API surface and finalized app-facing behaviors.

However, it also adds the controversial developer verification, which could block the sideloading installation of unverified Android apps on any Android device.

The QPR1 Beta has concluded this month, and the features will be migrated to stable Android 16 reportedly in September 2025. The stable update will get Material 3 Expressive!

Eligible devices include Pixel 6, 6 Pro, 6a, 7, 7 Pro, 7a, Fold, 8, 8 Pro, 8a, 9, 9 Pro, 9 Pro XL, 9 Pro Fold, 9a, 10, 10 Pro, 10 Pro XL and Pixel Tablet series devices*.

What’s new in Android 16 QPR2 Beta 2?

The Android development has shifted with the release of Android 16 QPR2 Beta 2. According to the release notes, QPR2 Beta 1 includes new features and changes to try out with your apps. Details listed below.

Key features and changes include:

• Platform Stability achievement and its significance for developers
• Developer Verification – the new security requirement starting September 2026
• SMS OTP Protection – enhanced security against hijacking attempts
• Custom App Icon Shapes – new user personalization options
• Generational Garbage Collection – performance improvements in ART
• Health Connect Enhancements – native step tracking and expanded exercise data
• Minor SDK Versions – Google’s new rapid innovation approach

UI, System Experience, and Accessibility

• Expanded Dark Theme
• Auto-Themed App Icons
• Dark theming is getting an expanded option.
• Enhanced HDR Brightness
• Widgets on lockscreen
• Interactive Chooser Sessions
• Smoother Android Migrations
• PDF Document Annotation and Editing
• Display Topology API
• Device-aware View Configuration
• Granular Haptic Feedback Control
• Quick Settings Tile Categories

Media & Audio

• IAMF Decoding Support
• Personal Audio Sharing in Output Switcher
• New AAudio APIs
• HDR/SDR Brightness Slider

Connectivity

• Companion Device Management Enhancements
• MediaRouter Network Privacy Improvements

Privacy & Security

• Secure Lock Device
• Phone Theft Protection Toggle

Developer Productivity

• Widget Engagement Metrics
• Early Warnings for 16KB Page Size Compatibility
• Enhanced Profiling
• More Robust Multi-Display Testing

Android 16 QPR2 Beta 2: Platform Stability Achieved

Android 16 QPR2 Beta 2 achieved an important Platform Stability milestone. This update has locked the API surface and finalized app-facing behaviors, allowing developers to integrate the latest platform innovations into their applications confidently.

What is Android Platform Stability?

Platform Stability conveys a crucial phase in Android’s development cycle where the API surface becomes locked and app-facing behaviors are finalized. This milestone provides developers with the confidence needed to integrate new features without worrying about future breaking changes. Unlike traditional annual releases, Android 16 QPR2 introduces the concept of minor SDK versions, enabling Google to deliver platform innovations more rapidly while maintaining backward compatibility.

The achievement of Platform Stability in QPR2 Beta 2 means developers can begin serious implementation work, knowing that the features and APIs they’re building against will remain consistent through to the final release. This approach represents a fundamental shift in how Android delivers new capabilities to the development community.

New Android Security Implemented

The update has been implemented, we are doomed! Google finally blocks Sideloading of Android Apps. Google has announced what can only be described as an extinction of the open ecosystem that made Android the world’s most popular mobile platform. Under the guise of “security,” Google is implementing draconian developer verification requirements that effectively eliminate true sideloading freedom for millions, if not billions, of Android users worldwide.

The Android 16 QPR2 Beta 2 developer verification has been implemented. A security measure supposedly designed to protect users from malicious applications and repeat offenders. But it’s actually to block sideloading installation of unverified apps.

Starting in September 2026, Android will require apps to be registered by verified developers for installation on certified Android devices, with exceptions made for installations through Android Debug Bridge (ADB).

This requirement reflects a concerning shift in Android’s app security strategy. While the intention behind developer verification is to curb malware and scams within the ecosystem, it raises questions about the impact on app development and user experience. The phased rollout in select regions may lead to some regions, like the United States, with limited access to apps.

Google “strongly encourages” all developers who distribute apps on certified Android devices to sign up for early access to developer verification. This proactive approach allows developers to familiarize themselves with the new requirements and ensure their applications are ready when enforcement begins. The early access program provides valuable insights into the verification process and helps developers understand the end-to-end user experience.

Impact on sideloading or installing apps on Android

For developers, this change introduces both opportunities and responsibilities. The developer verification system won’t impact development workflows significantly, as developers can continue to install unverified apps through ADB for testing purposes.

Although end users, this could mean, you can no longer just normally install apps by tapping the APK file. This means users could still be able to install unverified apps through ADB. But knowing it’s Google, that could be blocked in the future, too.

The new APIs introduced in QPR2 Beta 2 support developer verification during installation, providing developers with the tools needed to integrate this security feature seamlessly. The addition of the adb shell pm set-developer-verification-result command allows developers to simulate verification failures, enabling comprehensive testing of both successful and unsuccessful verification scenarios.

Enhanced SMS Security: OTP Protection Measures

Android 16 QPR2 Beta 2 introduces sophisticated SMS OTP (One-Time Password) protection mechanisms designed to prevent hijacking attacks. The system implements a three-hour delay for message delivery containing SMS retriever hashes to most applications, effectively thwarting attempts to intercept sensitive authentication codes.

This security enhancement specifically targets the RECEIVE_SMS broadcast and filters SMS provider database queries, creating multiple layers of protection against malicious interception. The three-hour delay window provides sufficient time for legitimate authentication processes while significantly reducing the window of opportunity for attackers.

Applications can continue using the SMS Retriever API to access messages intended specifically for them in a timely manner, maintaining the balance between security and user experience.

Custom App Icon Shapes

Android 16 QPR2 introduces the ability for users to select from various icon shapes that apply universally to all app icons and folder previews. This feature continues user personalization and visual customization options within the Android ecosystem.

The implementation of custom app icon shapes requires developers to ensure their adaptive icons work seamlessly with any shape users might select. This consideration becomes crucial for maintaining visual consistency and brand recognition across different user preferences and device configurations.

With the introduction of custom icon shapes, developers must pay increased attention to their adaptive icon implementations. The new feature emphasizes the importance of creating flexible, well-designed adaptive icons that maintain their visual appeal and functionality regardless of the shape container applied by users.

Advanced Memory Management

The Android Runtime (ART) receives a significant upgrade with the introduction of Generational Concurrent Mark-Compact (CMC) Garbage Collection. This advanced garbage collection system focuses collection efforts on newly allocated objects, which statistically are more likely to become garbage, resulting in more efficient memory management.

Developers can expect reduced CPU usage from garbage collection operations, resulting in smoother user experiences with less jank and improved battery efficiency. These improvements directly translate to better app performance and enhanced user satisfaction.

By intelligently focusing on recently allocated objects, the system can perform more efficient cleanup operations while minimizing the impact on application performance.

Health Connect Enhancements

Health Connect receives substantial improvements with native step tracking capabilities that automatically utilize device sensors. Applications with READ_STEPS permission can now access step data directly from the “android” package, simplifying implementation while improving power efficiency.

This native integration eliminates the need for complex sensor management code and provides a standardized approach to step tracking across different device configurations. The power efficiency improvements result from centralized sensor management, reducing battery drain compared to individual app-based sensor access.

Read more on Android 16 QPR2 Beta 2 is Here

Getting Started with Android 16 QPR2 Beta

Device Enrollment and Setup

Developers can begin exploring Android 16 QPR2 Beta 2 by enrolling supported Pixel devices to receive over-the-air beta updates. This straightforward process provides immediate access to the latest features and capabilities without complex setup procedures.

For developers without Pixel devices, 64-bit system images are available for use with the Android Emulator in Android Studio.

Existing Android Beta program participants will automatically receive over-the-air updates to Beta 2, streamlining the upgrade process. Google regularly updates system images and SDK components throughout the Android 16 QPR2 release cycle, ensuring developers have access to the latest improvements and bug fixes.

Development Environment Optimization

For the optimal Android 16 QPR2 development experience, Google recommends using the latest Canary version of Android Studio Narwhal Feature Drop. This recommendation ensures access to the most current development tools and features optimized for the new platform capabilities.

Developers transitioning from the Canary program to the Beta program should note that device wiping and manual flashing to the beta release may be necessary. This process, while more involved, ensures a clean transition between development tracks.

Device Compatibility and Availability

Android 16 QPR2 is available for a wide range of Pixel devices, including:

• Pixel 6 and 6 Pro
• Pixel 6a
• Pixel 7 and 7 Pro
• Pixel 7a
• Pixel Fold
• Pixel 8 and 8 Pro
• Pixel 8a
• Pixel 9, 9 Pro, 9 Pro XL, and 9 Pro Fold
• Pixel 9a
• Pixel 10, 10 Pro, 10 Pro XL
• Pixel Tablet series devices

Download Android 16 QPR2 Beta 2

Users can join the Android 16 QPR2 Beta program by enrolling their eligible Pixel device through Google’s official beta website. Once enrolled, devices automatically receive beta updates, including this latest release.

1. New beta testers: Visit Google’s Android Beta Program website to enroll your eligible Pixel device
2. Current Android 16 Beta users: You’ll automatically receive QPR1 Beta 3 and future updates as they become available. Vsisit Settings > System Updates.

OTA Download Links

• Apply OTA images — can be installed without data reset and bootloader unlocking
• Factory Image Files (Downloads)
• Android Flash Tool Files (Install)
• Installation Instructions (Install)
• Download Android 16 QPR2 GSI (Generic System Image)

Important Considerations for Beta Users

For those currently enrolled in the Android 16 Beta program, Google has provided some critical information:

• If you prefer to receive the public stable release of Android 16 instead of continuing with beta updates, you can opt out without wiping your device data—but you must do so before installing QPR2 Beta 1
• If you opt out after installing Beta 1 or future updates, your device data will be wiped according to standard program guidelines
• Opting out will trigger a “Downgrade” OTA update—if you want to wait for the stable release, simply ignore this update