Google released Android 17 QPR2 Beta 4 to Pixel testers on Friday, two weeks after Beta 3, landing as build CP41.260814.003.A2 or CP41.260814.003.B1 depending on the device. It’s the fourth build in the android 17 qpr2 beta cycle, the year-end quarterly platform release Google is developing alongside QPR1, the update due to ship publicly as the September Feature Drop.
QPR1 and QPR2 run as two separate beta tracks at once, which is why the naming looks confusing from the outside. QPR1 is the nearer-term release, already at Beta 9 earlier this month and closing in on its public rollout. QPR2 sits a full quarter further out, still working through its beta run toward a stable release in December. Reaching Beta 4 in that cycle usually means the bulk of the platform’s feature work is already locked in: what’s left is mostly fixing what the earlier builds broke, which is reflected in what testers are reporting this time.
Device support: Pixel 6 out, Pixel 11 not yet in
As with every QPR2 build so far, the Pixel 6 and Pixel 6 Pro are excluded from this beta cycle. Google typically drops a phone from beta testing once it’s nearing the end of its guaranteed update window, ahead of public support actually ending, so this isn’t a new decision, just a continuation of one made earlier in the QPR2 cycle. At the other end of the lineup, the newest hardware isn’t covered either: 9to5Google reports that as of Friday afternoon the Pixel 11 series still isn’t compatible with the beta, though Google says support is coming “soon.”
That leaves the android 17 qpr2 beta track running on a shrinking middle: older Pixel 6 hardware aged out months ago, and the newest Pixel 11 line hasn’t been folded in yet. Anyone testing on either end of Google’s current lineup is currently locked out of QPR2 altogether, even though both phones can run other current Android releases without issue.
What’s actually in Beta 4
Coverage of this build leans heavily on bug fixes rather than new surface-level features, and testers describe it as a sizable but not dramatic update compared with Beta 3’s release two weeks ago. That pattern fits where QPR2 sits in its own cycle: four betas in, most changes are patches to things Beta 1 through 3 introduced rather than anything new arriving cold. Google’s own changelog, linked below, is the only place to see the itemised list rather than a summary of it.
Our take: read the build, not the vibe
The two writeups covering this release frame it differently: one treats it as Google simply keeping its beta cadence on schedule, the other walks through the fix list build by build. Neither substitutes for the actual document. For anyone running a beta on a Pixel that is supported, the Android 17 QPR2 Beta 4 release notes are the primary source worth bookmarking, since that’s where Google lists known issues alongside fixes rather than just a headline count of how many there are.
What to watch next
Two things worth tracking from here: whether Pixel 11 support actually arrives in the next QPR2 build as promised, and whether QPR1’s Beta 9 status means the September Feature Drop ships before the month is out. Both would land before QPR2 itself is anywhere near finished.
