Google pushed Android 17 QPR1 Beta 5 to Pixel phones on June 23, 2026, barely two weeks after the last build and only about a week after Android 17 itself went stable. That cadence tells you something before you even open the changelog. A short turnaround, ten resolved bugs, and no marquee feature add up to one thing: this is a cleanup build, not a feature drop. The release carries build CP31.260608.007 with the June 2026 security patch (level 2026-06-05), and Google’s own Mishaal Rahman confirmed on X that it was rolling out to Pixel 6 and newer.
There’s a quiet bit of context that makes this stability pass land harder than usual. Android 17’s stable debut wasn’t spotless. Android Central reported that Pixel owners hit 5G and display issues almost immediately after the public launch. So when a fix-only beta shows up a week later, it’s not Google being fussy. It’s Google catching up to problems people are already living with.
If you’re trying to figure out everything new in Android 17 QPR1 Beta 5, here’s the honest summary up front: a solid round of fixes, two or three genuinely nice quality-of-life touches, and a much bigger story sitting just offstage that this build pointedly does not address.
Android 17 QPR1 Beta 5 changelog: every fix in this update
Every line in the official changelog describes something that used to be broken. Read together, that list is basically a tour of everyday phone anxiety.
Take the camera. It was freezing or stuttering right after you opened it from idle, which is, of course, exactly the moment you need it most, the candid shot you’ve got about two seconds to catch. That’s fixed now, per 9to5Google. Same energy with Always-On Display: waking the phone could leave the screen stuck behind a pixelated bar until you restarted the whole device.
A couple of these carry weight beyond mere annoyance. A Private Space bug was letting locked apps surface in launcher search results while the Private Space UI crashed out from under you, effectively letting a privacy container leak the very thing it exists to hide. The fix is in this build, 9to5Google reports. The Game Dashboard, meanwhile, was blocking people from stopping an active screen recording or saving the captured clip, and that one had racked up two separate tracker entries before Google squashed it.
If you want a rough gauge of how irritating a bug really was, count the reports. Home-screen widgets vanishing after a reboot, disappearing from the picker entirely, drew six separate issue-tracker entries before this build addressed it. Six is a lot. That’s not an edge case; that’s a lot of people rebooting and watching their home screen come back wrong.
The remaining fixes round out the picture: Download Manager failing when a download was excluded from an active VPN, charging-time estimates disagreeing between the lock screen and the charging screensaver, a system crash (and device hang) triggered by downloading games, a WebView rendering regression that was breaking Monopoly Go’s mini-games, and a dead “bubble” option lingering in the archived-apps menu. Many smaller stability and compatibility fixes ride along under the headline ten.
Camera, lock-screen wake, app sandboxing, screen recording, widgets, charging, VPN handling, the sheer spread of subsystems on that list is the description of the build. This is Google sanding down the spots where the software quietly breaks the promises it made one screen earlier.
To confirm you’re on it, check Settings for build CP31.260608.007 with security patch 2026-06-05. Beta 5 covers the Pixel 6 and 6 Pro on up through the full Pixel 10 lineup, including the Pixel 10a. If any of the bugs above have been nagging at your device, this is worth installing.
What’s new in Android 17 QPR1 Beta 5 beyond the fixes
QPR betas this late in the cycle rarely hand you anything flashy, but Beta 5 isn’t only repairs. A few small, genuinely useful changes slipped in too, the kind you don’t see in the official changelog but notice in daily use.
The standout is a “Don’t ask me again” checkbox for mobile data. Flip mobile data on from Quick Settings and you’ll now get the option to silence that repeated confirmation prompt for good. It’s a tiny thing, and it’s the kind of friction-killer you wish had shipped years ago.
There’s also a sliver of branding worth flagging. Some devices, the Pixel 10 Pro Fold in particular, are surfacing “Gemini Intelligence” on the boot screen or in related UI. It reads like early branding experimentation rather than a feature, but it’s a hint at how Google wants to frame the AI layer going forward.
Beyond that, testers and teardown folks have spotted a handful of minor cosmetic and structural tweaks: the apps list and search settings reportedly renamed to “Pixel Search settings,” new highlight colors around apps in certain lists, dropdown arrows quietly removed from some menus, and possible adjustments to blur intensity (reports vary by device, with some seeing a lighter effect). None of it is going to change your day, but collectively it’s the usual pre-Feature-Drop polish settling into place.
It’s also a minor SDK release with a few new APIs. If you build apps, the diff report on developer.android.com is the place to check what shifted, since the near-final QPR1 APIs are exactly what you’ll want to validate against before stable lands.
Android 17 QPR1 Beta 5 updates and the Quick Settings redesign: what the leaks actually show
Here’s the thing none of the ten fixes touch: Quick Settings. And that absence is the most interesting part of the whole release.
A Quick Settings redesign has reportedly been in development since at least 2024, and Google still hasn’t confirmed it. The most concrete evidence isn’t a hands-on video or a tipster claim. It’s a settings string. Back in January, Android Authority reported that code analysis turned up a user-facing option labeled “Notifications & Quick Settings” tucked under Settings > Notifications, letting people switch between today’s combined panel and a new, separate design. The detail that matters: Google doesn’t build an explanatory toggle for a change nobody will notice. A setting like that implies the redesign is visible enough to need one.
That toggle reportedly sits next to a second long-overdue fix: the return of discrete Wi-Fi and mobile data tiles. A LineageOS lead developer first surfaced code pointing to an optional split of the merged internet toggle, and January’s leak corroborated it, per Android Authority. People have been annoyed by that combined tile since the day it launched, so separate toggles would be a usability correction carrying years of complaint behind it.
The trail goes back further than this year. Mishaal Rahman flagged the split shade in code in 2024; by January, a tipster-backed video showed a far more polished build with most of the earlier visual and functional rough edges reportedly ironed out, according to Android Authority. Rough strings turning into a working demo is the kind of progression that suggests an active shipping target rather than a shelved experiment. Google has still confirmed nothing.
If you’ve been tracking this through the Android 17 QPR1 Beta 4 coverage, none of this is a new direction. It’s the same thread, still unconfirmed, inching closer to a decision point as QPR1 nears stable.
The large-screen tradeoff: where the redesign gets complicated
For most phone users, both changes read as straight wins. Separate connectivity tiles are less ambiguous, and a dedicated Quick Settings swipe zone means fewer accidental notification pulls. For foldable and tablet owners, the leaked picture gets thornier.
Leak-based reporting indicates tablets would be permanently locked into the split view, with no setting to revert to the combined panel, per Android Authority. Foldables’ inner screens would reportedly behave the same way, left swipe for notifications, right swipe for Quick Settings, with only the cover display keeping the classic combined shade. A foldable footer string spotted earlier specifically noted the combined panel is limited to the outer screen, which lines up with that behavior.
And that’s the real tension in all of this. The “Notifications & Quick Settings” string suggests Google planned to hand users the choice, yet the reported large-screen behavior would yank that choice away precisely from the devices with the most room to configure. Whether the setting is gated by device type, or whether big-screen users genuinely get no opt-out, is still unresolved.
None of it is confirmed by Google, and nothing in the Beta 5 changelog goes near it. The settings string, the code findings, and the demo video are credible signals of direction. They are not committed features.
How to install Android 17 QPR1 Beta 5 and the factory-reset trap
Installing is the easy part: enroll your compatible Pixel in the Android Beta Program and the OTA arrives over the air. OTA images are also posted for anyone who prefers to flash manually.
The part that bites people is leaving. If you’re on the beta and you want to get back to stable Android 17 without wiping your phone, your move is to opt out before you install Beta 5. Apply Beta 5 first and then try to leave, and the downgrade forces a mandatory factory reset, including your apps, photos, and settings. This is the detail enthusiasts keep getting wrong: stable Android 17 and Android 17 QPR1 Beta aren’t the same destination with different labels, and the order you do things in decides whether you keep your data.
One more note worth keeping in perspective: Pixel 6 and 6 Pro support returns here after being skipped in the prior build. For those older Tensor devices, that’s both a practical fix and a small reassurance that they’re still part of the QPR1 test train rather than quietly aging out of it.
Signing Off
Beta 5 is the simple half of the story. Install it if you’re on the beta, confirm CP31.260608.007 in Settings, and expect the camera, lock-screen, widget, and Private Space fixes to hold. Nothing changes today for Quick Settings.
The Quick Settings question is the consequential half, and it’s still wide open. For everyday phone users, the reported direction, separate connectivity tiles, a dedicated Quick Settings panel, and a user-facing layout setting, would be a net improvement with years of frustration behind it. For foldable and tablet owners, a mandatory split on large screens would strip flexibility from exactly the people with the most reason to want it.
So here’s the single concrete thing to watch for: a Quick Settings entry showing up in an official QPR1 beta changelog. Not a leak, not a code string, not a demo, but a line in Google’s own release notes. That’s the moment “reportedly in progress” becomes “actually shipping,” and it’s when the large-screen tradeoff stops being a reported intention and becomes real policy.
Until then, Beta 5 is exactly what its changelog says it is, and there’s no shame in that: Android 17 quietly getting its reliability work done before the September Feature Drop.
