Google releases Android 16 QPR3 Beta 2.1 to Pixel beta testers with identical security patches but undisclosed fixes, continuing stability improvements started in Beta 2 across Pixel 6 through Pixel 10 devices.
![]()
Google has deployed Android 16 QPR3 Beta 2.1 to its Pixel beta channel, marking another incremental step in the Quarterly Platform Release (QPR) testing cycle. Dated February 10, 2026, this maintenance update carries build number CP11.251209.009.A1 for most supported devices including Pixel Fold and Pixel Tablet, while standard Pixel 6 through Pixel 7 models use CP11.251209.009.
Unlike feature-driven releases, Beta 2.1 maintains the January 5, 2026 security patch level and Google Play services 25.47.33 without listing specific fixes in the official release notes. This suggests under-the-hood refinements addressing issues previously targeted in Beta 2, which focused on system stability, battery optimization, connectivity reliability (including Wi-Fi and call performance), and UI refinements.
Supported devices span four generations of Pixel hardware:
- Pixel 6 series: 6, 6 Pro, 6a
- Pixel 7 series: 7, 7 Pro, 7a
- Pixel 8 series: 8, 8 Pro, 8a
- Pixel 9 series: Standard, Pro, Fold, 9a
- Pixel 10 series: All models
- Pixel Fold & Tablet
Enrolled devices receive updates automatically via OTA, typically installing rapidly in the background. For manual installations, Google recommends the web-based Android Flash Tool. Crucially, switching between beta and stable channels requires a full factory reset, permanently erasing user data. Google emphasizes this wipe is unavoidable when changing tracks.
Testers encountering issues should use the pre-installed Android Beta Feedback app or file reports via the public Issue Tracker. Google advises checking existing reports before submitting new ones to avoid duplicates.
This update continues Google's QPR3 stabilization phase ahead of the platform's public release, prioritizing reliability over new features for enrolled testers. The unchanged security patch and absence of explicit fixes indicate targeted refinements rather than fundamental changes.
Comments
Please log in or register to join the discussion