Android 16 QPR3 Beta 2.1 released for Google Pixel devices

Google has pushed Android 16 QPR3 Beta 2.1 to the Pixel beta track, dated February 10, 2026. If you’re enrolled, this is the kind of update that usually just shows up, installs quickly, and moves on.

The numbers Google is using this time

In Google’s release notes, most supported devices are tagged CP11.251209.009.A1. The Pixel 6 Pro, Pixel 6, Pixel 6a, Pixel 7 Pro, and Pixel 7 are listed separately on CP11.251209.009. The page also keeps the same 2026-01-05 security patch level, calls out Google Play services 25.47.33, and still lists emulator support as “TBA.”

What Google isn’t saying (and why that matters)

Here’s the catch: the Beta 2.1 entry is basically a label set - date, builds, patch level, Play services - but no Beta 2.1-specific fix list appears in the official notes. So if you’re looking for a neat “fixed X, fixed Y” changelog, it’s not there.

If you want context, Google does spell out what Beta 2 was trying to clean up in the same document, describing a broad sweep of stability and usability work... things like crashes/freezes, battery management behavior, connectivity issues (including slow Wi-Fi and missed calls), and some UI glitches. That’s Beta 2 context, not a promised Beta 2.1 fix list, but it gives you a feel for the kind of problems this QPR3 branch has been targeting.

Which Pixels can get it, and how it arrives

Google lists Android 16 QPR3 beta support across Pixel 6 and 6 Pro, Pixel 6a, Pixel 7 and 7 Pro, Pixel 7a, Pixel Fold, Pixel Tablet, Pixel 8 and 8 Pro, Pixel 8a, the Pixel 9 family (including Fold), plus Pixel 9a, and the Pixel 10 family (including Fold). Google also notes that once you enroll, your phone gets continuous OTA beta updates until you unenroll.

If you prefer to do things manually, Google recommends the Android Flash Tool as the preferred flashing method.

The part people forget: switching tracks can wipe your phone

Google is very direct about this: going from production to beta, or from beta back to production, requires a full device reset that removes all user data. Backups first, always.

Google also publishes OTA images for QPR beta builds and frames them as a practical option for testing — and, in some cases, for recovering a device after a bad OTA update.

Where Google wants bugs to go

For reporting issues, Google points testers to the Issue Tracker and the Android Beta Feedback app built into preview builds. Google also suggests checking the release notes and scanning “top open issues” before filing something new, so you don’t duplicate an existing report.