Android 17 QPR1 Beta 4 Lands With 8 Key Bug Fixes

• Android 17 QPR1 Beta 4 arrives three weeks after Beta 3, targeting eight specific bugs across Pixel devices.
• The Android 17 QPR1 Beta release is heavily fix-focused, with no new features reported in this build.
• Pixel 6 and Pixel 6 Pro are skipped in this release, though Google says they’ll return in the next beta.
• Fixes cover everything from disappearing home screen widgets to a serious OpenGL ES graphics performance regression.

• Android 17 QPR1 Beta 4 arrives three weeks after Beta 3, targeting eight specific bugs across Pixel devices.
• The Android 17 QPR1 Beta release is heavily fix-focused, with no new features reported in this build.
• Pixel 6 and Pixel 6 Pro are skipped in this release, though Google says they’ll return in the next beta.
• Fixes cover everything from disappearing home screen widgets to a serious OpenGL ES graphics performance regression.

Android 17 QPR1 Beta 4 Is Here — and It’s All About Fixing Things

Google has released Android 17 QPR1 Beta 4, the latest preview build ahead of September’s scheduled Feature Drop, and it arrives about three weeks after Beta 3. There’s no headline feature to get excited about this time around — this is a maintenance release through and through, a focused sweep of eight tracked bugs that testers had been flagging across the Pixel lineup. That’s not a criticism. Sometimes the most important thing a beta cycle can do is get stable, and Android 17 QPR1 Beta 4 looks like Google is doing exactly that as it closes in on a public release.

Google’s Mishaal Rahman announced the release on X, laying out both the new build numbers and the full list of fixes. The split-build situation that surfaced in earlier betas continues here: Pixel 6a, Pixel 7, and Pixel 7 Pro users get build CP31.260522.006.A1, while the rest of supported Pixel hardware lands on CP31.260522.006. It’s a small but telling detail — different silicon generations sometimes need different low-level patches, and Google isn’t trying to paper over that with a single monolithic build.

What’s Actually Fixed in This Build

Eight issues are addressed in Android 17 QPR1 Beta 4, and while none of them are the kind of flaw that makes headlines on their own, several of them have clearly been annoying real users for a while. Here’s the full picture:

• Invisible mouse pointer on external displays — When a Work profile or an app using FLAG_SECURE was active, the cursor would vanish on an external screen. A frustrating one for anyone using a Pixel as a desktop replacement via DeX-style setups or USB-C monitors.
• Settings crash from Private Space — Launching credential provider settings from within a Private Space caused the Settings app to crash outright. Private Space is one of Android 15’s more privacy-forward features, so stability here matters.
• Screenshot sounds tied to ringer volume — This one’s been a long-standing annoyance for many users. Screenshots were playing their capture sound at ringer volume, meaning if you silenced your phone for a meeting, a screenshot would still broadcast itself. That’s now fixed.
• 5x zoom video jitter — Recording video at 5x zoom was producing frame jumps and panning jitter. On phones like the Pixel 7 Pro and 8 Pro where that optical zoom is a selling point, this is a meaningful fix.
• Back Tap not working on the lock screen — Google’s Back Tap gesture — which lets you trigger actions by tapping the rear of the device — was failing on the interactive lock screen. A minor but nagging accessibility and convenience issue.
• OpenGL ES performance regression — This is arguably the most significant fix in the batch. A graphics driver regression was causing severe 3D performance drops in OpenGL ES applications on newer hardware. Casual gaming, AR apps, and anything leaning on the GPU could be affected. Regressions like this tend to slip in with driver updates and can be surprisingly hard to pin down.
• Wireless ADB and local network connectivity failures — Developers using Wireless ADB — the tool that lets you debug Android devices over Wi-Fi without a USB cable — were finding connections failing entirely. Apps dependent on local network access were also affected. For anyone doing active development on a Pixel test device, this was a blocker.
• Home screen widgets disappearing after reboot — This one has a whopping six separate issue tracker entries attached to it, which tells you just how widely it was reported. Widgets were vanishing from the home screen or becoming unavailable in the picker after a device restart. It’s the kind of bug that erodes daily confidence in a device.

The Pixel 6 Situation

One notable gap in Android 17 QPR1 Beta 4 is the absence of the Pixel 6 and Pixel 6 Pro. These devices are supported in the Android 17 QPR1 Beta program, and they were included in previous beta releases — but Google doesn’t have builds ready for them this time. Rahman confirmed that Google plans to bring them back for the next beta, so it’s a temporary exclusion rather than a sign that the Pixel 6 is being quietly phased out of the program. Still, owners of those devices will be sitting this round out, which is mildly frustrating when you’re trying to stay on the bleeding edge of the beta cycle.

The Pixel 6 series runs on Google’s first-generation Tensor chip — the original GS101 — which behaves quite differently at a driver level compared to the Tensor G2 and beyond. It’s entirely plausible that a fix for one hardware generation inadvertently introduced a new issue on another, requiring a separate patch pass before Google can ship a clean build for those devices.

What Android 17 QPR1 Beta Tells Us About September’s Feature Drop

Reading between the lines of a bug-fix-only beta release is something of an art. The fact that Google is pushing nothing but fixes at this stage of the Android 17 QPR1 Beta cycle suggests the feature work for the September QPR1 drop is largely locked — engineers are now in stabilisation mode, not feature development. That’s a good sign. QPR releases have occasionally felt rushed in the past, with stability patches still arriving weeks after the public launch. A dedicated cleanup beta this close to release implies Google wants a clean ship.

The QPR cadence itself is worth understanding. Google releases these Quarterly Platform Releases as mid-cycle drops between major Android versions — Android 17 QPR1 would slot in between the initial Android 17 launch and next year’s Android 18. They typically carry smaller features that didn’t make the main release cut, alongside accumulated stability work. For Pixel owners, they’re often the more practically useful updates of the year: less splashy than a major version bump, but genuinely improving the day-to-day experience.

How to Get the Beta Now

If you want to try Android 17 QPR1 Beta 4 yourself, you’ll need to enrol your Pixel device in Google’s Android Beta for Pixel program. The enrolment process is straightforward — log in with your Google account, find your device, and opt in. Once enrolled, the update should land over the air within a day or two. If your device is already in the program from a previous beta, you should see the update notification arrive shortly without needing to do anything extra.

Pixel 6 and Pixel 6 Pro owners, as noted, will need to wait for the next Android 17 QPR1 Beta drop. Given the three-week cadence between Beta 3 and Beta 4, the next build could reasonably surface in mid-to-late July — though Google hasn’t committed to a specific timeline.

With Beta 4 in testers’ hands and the bug list continuing to shrink, the September Feature Drop is shaping up to land on reasonably solid ground. Whether there are any genuinely interesting features waiting in the wings still isn’t clear — but at this stage of the cycle, ‘boring and stable’ is exactly what you want to hear.

Source: Android Authority

Frequently Asked Questions