Google began rolling out Android 16 QPR3 Beta 2.1 to Pixel devices on Feb. 10, 2026, delivering a maintenance update for beta testers across the Pixel line. The patch arrives nearly four weeks after the prior QPR3 beta release and is labeled Beta 2.1 rather than advancing to Beta 3. Google also reiterated that the Android 17 Beta is coming soon. The update carries January 2026 security fixes and is available to all supported Pixel models enrolled in the QPR3 Beta.
Key Takeaways
- Android 16 QPR3 Beta 2.1 began rolling out on Feb. 10, 2026, to enrolled Pixel devices.
- Build CP11.251209.009 targets Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, and Pixel 7 Pro; CP11.251209.009.A1 covers remaining supported devices.
- The preceding beta was CP11.251209.007.A1; Google’s release notes do not list specific fixes for 2.1.
- OTA sizes observed: ~123 MB on a Pixel 9a and ~98.39 MB on a Pixel 10; full download sizes vary by model.
- OTA images are published, but the Pixel 10 series is again omitted from the image set.
- The update includes the January 2026 Android security patch and is available for all supported Pixels from Pixel 6 through Pixel 10 series and recent a/models.
- Devices previously enrolled in QPR3 Beta that have not opted out will receive Beta 2.1 and future beta revisions automatically.
Background
Google distributes Quarterly Platform Releases (QPRs) to provide cumulative bug fixes, stability improvements, and security updates between major Android releases. QPR3 is the third such tranche for Android 16, delivered via the Beta channel for testers and early adopters. Beta channels let Google validate fixes at scale while giving developers an advance look at platform behavior before a wider production push.
Historically, Google alternates incremental beta builds (for example, X.1, X.2) and occasionally pauses numbering when a focused patch is required; this update arriving as Beta 2.1 rather than Beta 3 suggests a targeted maintenance release. Pixel owners, enterprise IT teams, and app developers monitor these beta builds for regressions and compatibility signals before broader rollouts.
Main Event
On Feb. 10, 2026, Google posted two build identifiers for the QPR3 Beta 2.1 rollout: CP11.251209.009 for early Pixel 6 and 7 models and CP11.251209.009.A1 for the remaining eligible devices. The company did not enumerate the specific bug fixes or behavioral changes in its public release notes, leaving the update’s scope implied by the naming and security patch level.
Testers reported OTA sizes that varied by device: a Pixel 9a received a 123 MB download while a Pixel 10 reported a 98.39 MB package. Those sizes indicate an incremental, targeted patch rather than a full-system upgrade. Google also published OTA images for direct flashing, though the Pixel 10-series images were not included in the image bundle at posting.
The update carries the January 2026 Android security patch and is offered to all supported Pixel devices listed by Google, encompassing Pixel 6 and later models as well as the Pixel Tablet and Fold lines. Enrollment behavior is automatic for devices already in the QPR3 Beta channel unless an owner has opted out; that means beta participants will get 2.1 without additional action.
Analysis & Implications
The Beta 2.1 designation and modest OTA sizes imply Google issued a targeted correction or stability improvement rather than a broad feature change. For developers and early testers, smaller incremental updates typically mean fewer surface-level API changes but possible fixes for regressions encountered in previous betas. Because release notes are silent on specifics, organizations should treat this as a stability patch and test critical flows if devices in their fleet are enrolled.
Security-wise, bundling the January 2026 security patch is consequential: enterprises tracking monthly patch levels can consider this build as current for that security window, but should still verify the patch level string after installation. The exclusion of Pixel 10 series OTA images suggests a temporary distribution inconsistency rather than a device-level block, but it may slow manual flashing workflows for that series until images are posted.
Looking ahead, Google’s note that Android 17 Beta is coming soon shifts attention: engineering resources may pivot toward the next major preview, which could compress the cadence of further QPR3 beta builds. For end users, that means subsequent fixes could either appear as small beta updates or be deferred into broader Android 17 testing, depending on severity and priority.
Comparison & Data
| Device / Group | Build | Reported OTA Size |
|---|---|---|
| Pixel 6, 6 Pro, 6a, 7, 7 Pro | CP11.251209.009 | Varies (noted as available) |
| All remaining supported Pixels | CP11.251209.009.A1 | Varies (noted as available) |
| Pixel 9a | CP11.251209.009.A1 | ~123 MB (observed) |
| Pixel 10 | CP11.251209.009.A1 | ~98.39 MB (observed) |
The table above consolidates build names and observed OTA sizes when available; many devices report variable package sizes depending on local configuration and prior incremental deltas. Note that OTA images were published for most models but the Pixel 10 series images were not present in the image set at the time of reporting. Administrators should check the official image repository before attempting manual installs.
Reactions & Quotes
Google provided a brief forward-looking note about the platform roadmap while publishing the patch.
“Android 17 Beta is coming soon.”
Google (official)
That statement shifts some community focus to the next major preview while leaving QPR3 as a maintenance track. Independent reporting highlighted the lack of detail in the release notes.
“Google’s release notes do not identify what has been fixed.”
9to5Google (news)
The sparse public notes prompted developers and users to start hands-on testing to surface any regressions or behavioral changes introduced by Beta 2.1.
Unconfirmed
- Precise bug fixes included in CP11.251209.009 / CP11.251209.009.A1: Google has not published itemized fixes, so specific resolved issues remain unconfirmed.
- Reason for Pixel 10-series image omission: it is unclear whether the exclusion was deliberate or an administrative delay; Google has not commented.
Bottom Line
Android 16 QPR3 Beta 2.1 is a modest, targeted maintenance release rolled out to enrolled Pixel devices on Feb. 10, 2026, carrying the January 2026 security patch. The build names and observed OTA sizes suggest fixes or stability improvements rather than new features, but absence of detailed release notes means testers must validate behavior themselves.
Organizations and developers with devices in the QPR3 Beta should install the update on a test fleet, confirm critical workflows, and monitor public channels for additional notes or follow-up patches. With Google flagging Android 17 Beta as imminent, larger platform changes will likely land next in that preview track rather than in subsequent QPR3 betas.
Sources
- 9to5Google — news report summarizing the rollout and observations
- Google / Android Preview — official Android preview and beta program information (official)