Google has begun rolling out Android 16 QPR3 Beta 2.1 to the Pixel beta channel, with the release dated February 10, 2026. If your Pixel is enrolled in the Android Beta Program, this is the type of update that typically arrives as a quick over-the-air install, without much fanfare, but it can still be important for anyone tracking Android 16’s stability in the quarterly platform release cycle.
Android 16 QPR3 Beta 2.1 build numbers and what they mean
According to Google’s release details, most supported devices are assigned build CP11.251209.009.A1. A separate listing appears for the Pixel 6 Pro, Pixel 6, Pixel 6a, Pixel 7 Pro, and Pixel 7, which are shown on build CP11.251209.009. The update continues to use the 2026-01-05 security patch level, and the release notes also reference Google Play services version 25.47.33. Emulator support is still not confirmed, as it remains listed as “TBA.”
No Beta 2.1 changelog: what Google isn’t spelling out
The biggest detail that stands out is what’s missing: there’s no dedicated list of Beta 2.1 fixes in the official notes. In other words, you won’t find a clean “this update fixes these bugs” summary for Beta 2.1, even though the update is now live on the beta track.
For context, Google does describe the kinds of issues Android 16 QPR3 Beta 2 was meant to address, and that gives a reasonable clue about the broader areas this QPR3 testing cycle is focused on. Those Beta 2 improvements included general stability and usability work such as reducing crashes and freezes, improving battery management behavior, addressing connectivity problems like slow Wi‑Fi and missed calls, and clearing up certain user interface glitches. While that’s not a promise of exactly what changed in Beta 2.1, it does frame the type of problems Google has been targeting in this branch.
Supported Pixel devices for Android 16 QPR3 beta updates
Google lists broad support across recent Pixel generations, including Pixel 6 and Pixel 6 Pro, Pixel 6a, Pixel 7 and Pixel 7 Pro, Pixel 7a, Pixel Fold, Pixel Tablet, Pixel 8 and Pixel 8 Pro, Pixel 8a, the Pixel 9 family (including a Fold model), Pixel 9a, and the Pixel 10 family (including a Fold model). Once a device is enrolled, Google notes it will continue receiving over-the-air beta updates until the user unenrolls.
Prefer manual installation? Here’s what Google recommends
If you’d rather install the beta manually instead of waiting for the OTA rollout, Google points users to the Android Flash Tool as its preferred method for flashing builds. Google also makes OTA images available for QPR beta releases, positioned as a helpful option for testing and, in certain situations, for recovering a device after a problematic OTA update.
One warning that matters: changing tracks can erase your data
Before jumping into any Android 16 beta release, it’s worth repeating Google’s most direct warning. Moving from the stable production track to the beta track, or returning from beta back to stable, requires a full device reset that wipes user data. If you’re planning to enroll, unenroll, or switch tracks, backing up your phone first is essential.
How to report Android 16 beta bugs the right way
Google encourages testers to submit issues through the Issue Tracker and the Android Beta Feedback app that comes built into preview builds. It also recommends reviewing the release notes and checking the “top open issues” list before filing a new report, which can help avoid duplicates and speed up triage.
For Pixel owners who enjoy testing new Android features early, Android 16 QPR3 Beta 2.1 is another incremental step in the quarterly release path—quiet in the notes, but still part of the ongoing effort to make Android 16 more stable, reliable, and ready for wider rollout.
