Google released Android 17 QPR2 Beta 5 on September 15, 2026. It’s a developer-preview build, separate from the Android 17 QPR1 stable update most Pixel owners are already running. Beta 5 carries a security patch level of 2026-08-05 — a month behind the CVE-2026-58704 modem fix that reached the general public at the 2026-09-05 level. Beta testers should keep that gap in mind rather than assume the newest build is also the most secure one.
What Beta 5 actually fixes
Google’s own release notes list eight fixed issues for this build. The most consequential one addresses “a system stability issue that caused unexpected device reboots during continuous UI scrolling in media-heavy applications.” That’s the kind of bug that could hit mid-scroll in a photo-heavy app or a long social feed. Another fix targets something more disruptive: Google Wallet, launched via the power button shortcut, used to leave the touchscreen unresponsive. Beta 5 resolves that.
The rest of the list is smaller but still practical. Bluetooth device icons now update correctly when you change a device type in settings. The volume slider shows up properly again when you press hardware buttons while casting media. A text-rendering bug that left odd background highlights in search fields is fixed. A related patch also stops Private Space from failing to unlock. Enhanced HDR mode no longer stays stuck on after you turn it off. Camera panorama processing no longer crashes, and Bluetooth audio should no longer distort right after a call ends.
Beta, not stable — and a different build for different Pixels
Keep this separate from the Android 17 QPR1 stable update androidpure covered rolling out to eligible Pixels. QPR2 is the next quarterly release after that. It’s still in its developer/beta channel, and it’s targeting a December stable launch. Builds are numbered CP41.260828.004.A8 and CP41.260828.005.A6, with Google Play services at 26.28.33.
Outlets tracking the rollout, including Android Authority and Droid Life, report that Google is shipping this as two separate builds. One covers older Pixel hardware; the other covers Pixel 8 and newer. Those outlets put eligibility starting at the Pixel 6a. That device-split detail comes from their own testing and reporting, not from Google’s release-notes page directly, so treat the exact cutoff as outlet reporting rather than an official Google list.
Beta updates are opt-in. If you’re not enrolled in the Android Beta program, none of this reaches your phone until the stable QPR2 release in December.
How to check for it
If you’re already enrolled in the Android Beta program on an eligible Pixel, go to Settings, then System, then Software updates. Check for Beta 5 there. Anyone not enrolled won’t see this update, and joining the beta program now means trading some stability for early access to fixes like these.
Source: Android Developers
