Google is rolling out Android 17 QPR2 Beta 4 to Pixel phones today, August 28, confirmed on Google’s own Android Beta Program release notes and corroborated by 9to5Google, Droid Life, and NokiaPowerUser. The build, carrying version CP41.260814.003, lands on the Pixel 6a through Pixel 10a, with a separate build already prepared for the Pixel 11 series, though Google says that version isn’t available quite yet and will follow “soon.”
The headline milestone in today’s build isn’t a specific feature at all: Android 17 QPR2 has officially reached Platform Stability with Beta 4, meaning the app-facing APIs are now locked in place ahead of the update’s stable release, expected in December 2026 alongside that month’s Pixel Feature Drop.
What’s New in The Android 17 QPR2 Beta 4 Build
Status Bar settings mark a genuinely new addition to stock Android; Google has never offered this level of status bar control on Pixel phones before, even as other manufacturers like OnePlus have had similar options for years. The options are modest for now: choosing which notification levels show in the status bar (All, Priority only, or None), plus toggles for Mute, Vibrate, and Battery Percentage icons. It’s a small addition, but one that opens the door to more granular status bar customization in future builds.
Notification Intelligence isn’t introducing new functionality so much as reorganizing existing settings under a clearer, dedicated menu. Notification Summaries, the Notification Organizer, and Notification Cooldown, all features that previously lived scattered across different settings screens, now sit together under one heading, each with its own toggle and configuration options. The Voice Broadcast Quick Settings tile follows a similar pattern of giving an existing feature more direct, one-tap access.
How This Build Fits Into the Broader QPR2 Cycle
Beta 4 builds directly on top of Beta 3, released August 14, which Google itself described as the biggest build of this update cycle so far. That release introduced the Quick Settings layout editor, letting users drag and reorder the brightness bar, tiles, and media player within the shade, alongside deeper color customization through a new slider and four style presets (Neutral, Soft, Bright, and Bold), plus additional lock screen blur effects. Beta 3 also introduced new restrictions on programmatic call-forwarding, blocking apps from silently executing fraud-enabling USSD codes like *21# in the background and requiring a mandatory system confirmation dialog when a user manually dials one.
Today’s build carries that security work further, alongside a notably long list of bug fixes: a thermal management issue causing unexpected reboots, a bug where the 80% battery charge limit caused excessive slowdowns near the final 2%, an audio lockup bug that disabled the microphone for apps like Gboard and Gemini after screen recording until a full reboot, and a Bluetooth issue that defaulted call audio to the phone speaker instead of connected headsets. Google also fixed a bug where low-light Face Unlock failures were bypassing fingerprint unlock entirely and forcing PIN entry instead.
Why Platform Stability Matters Here
Reaching Platform Stability is a meaningful checkpoint in Google’s quarterly release cycle, distinct from a stable public release. It signals that the APIs app developers build against are now finalized for this QPR cycle, giving developers a stable target to test their apps against ahead of the December rollout, even while Google continues shipping bug fixes and minor refinements in the builds between now and then. In practice, that means QPR2’s remaining beta builds are likely to focus on stability and polish, following the pattern set by past Android Platform Stability milestones.
What to Watch Next
With the Pixel 11 series build still pending, the next concrete signal will be when that version actually reaches Pixel 11 owners, since Google’s own notes only promise it’s coming “soon” without a firm date. Beyond that, expect the remaining QPR2 beta builds between now and December to lean primarily into stability fixes, given that Platform Stability has already been reached with this release.