If you’ve spent the last few weeks on the Android 17 QPR1 beta and had a notification or a song suddenly dissolve into a burst of static, you’re not imagining things. It’s been one of the more talked-about annoyances in the r/android_beta feedback threads, right up there with a Pixel Tablet dock that randomly stops charging. Good news: Google just shipped the fix.
Google released Android 17 QPR1 Beta 8 for Pixel on July 31, 2026, and it’s a quiet one by design. There’s no new headline feature here, no redesigned settings page, nothing to screenshot for a “look what’s new” post. This build exists to clean up exactly the kind of bugs that make a beta frustrating to actually live on day to day, and it lands with a build number of CP31.260623.010.
Think of it less like a new coat of paint and more like the final punch list before a house gets handed over. Here’s what actually changed in Beta 8 and what it means for your Pixel.
When Does Android 17 QPR1 Beta 8 Roll Out, and Which Pixels Get It?
Beta 8 started rolling out on July 31, 2026, about two weeks after Beta 7 landed on July 15. That cadence matters, because Android 17 QPR1 already hit Platform Stability back at Beta 6, meaning the underlying APIs and app-facing behavior are locked in. Everything since then, Beta 7’s Quick Settings patches and now Beta 8, has been Google sweeping up loose ends rather than changing how the OS behaves.
Quick facts on this build:
- Released: July 31, 2026
- Build number: CP31.260623.010 (up from Beta 7’s CP31.260623.005)
- Security patch level: July 2026, per build teardowns tracking the release
- Eligible devices: Pixel 6, 6 Pro, 6a, 7, 7 Pro, 7a, Pixel Tablet, Pixel Fold, 8, 8 Pro, 8a, 9, 9 Pro, 9 Pro XL, 9 Pro Fold, 9a, 10, 10 Pro, 10 Pro XL, 10 Pro Fold, and 10a
That’s the full current Pixel lineup, which is worth calling out because it won’t stay that way for long. Google has already confirmed the Pixel 6 and 6 Pro won’t be moving on to Android 17 QPR2, which makes this stable QPR1 release their last major platform update this September.
Worth knowing: this is still a beta, and Google’s own guidance is to expect the occasional rough edge even this late in the cycle. If you’d rather wait, the stable release is expected with September’s Feature Drop. If you’re already enrolled, the update should already be sitting in your notification shade, and you can also grab it directly through the Android Beta Program or check the official Android 17 QPR1 developer page for system images.
That Random Audio Crackling? Google Finally Fixed It.
The headline fix in Beta 8 targets a bug that had genuinely earned its reputation. Google describes it as an issue in the audio framework’s buffer management that caused “unexpected, loud audio corruption and static” during media playback and notification sounds. In practice, that meant a Spotify track or an incoming text alert could suddenly spike into a jarring crackle loud enough to make people yank their headphones off.
It wasn’t a minor edge case, either. The bug had racked up more than 30 separate reports in Google’s issue tracker before this build shipped, which is a decent signal for how many beta testers were running into it across different devices and use cases. Buffer management bugs like this tend to surface unevenly. Some people never notice them, while others hit the corrupted-audio moment constantly depending on what apps and Bluetooth devices they use. If you’ve been avoiding wired or Bluetooth audio on your beta Pixel because of exactly this, Beta 8 is the build to update to.
Pixel Tablet Owners Can Trust the Speaker Dock Again
The second fix is narrower but still meaningful if it applies to you: the Pixel Tablet’s Speaker Dock had been dropping connectivity mid-use, frequently going offline or failing to connect when you docked the tablet. Google says that’s resolved in Beta 8.
This one only matters if you actually own the dock accessory, so most phone-only Pixel users can skip past it. But it’s a good example of the kind of fix that never makes a keynote slide and still genuinely improves the experience for the people who paid for that specific hardware.
Two Smaller Fixes That Matter More Than They Sound
Beta 8 also closes out two regressions that had been quietly annoying people since earlier builds. NFC tags had stopped reliably reading data or launching URLs when tapped, which broke the kind of quick-tap workflows people build their routines around, like tapping a smart speaker or a transit card. And fingerprint unlock was failing to trigger on some unlock attempts, forcing people back to a PIN more often than it should.
Neither bug is flashy, but both are the kind of thing you only notice once it stops working reliably. If you’d been fighting connectivity oddities on Android 17 beyond just NFC, it’s worth checking our separate guide on fixing Wi-Fi that stopped working on Android 17, since that’s a related but distinct bug from what Beta 8 addresses here.
The Bigger Picture: This Is the Cleanup Before September’s Stable Release
Here’s what that release cadence actually tells you. QPR1 locked its feature set and API behavior at Platform Stability in Beta 6, Beta 7 mopped up a handful of Quick Settings annoyances like a broken Battery Share toggle and a font-size crash, and Beta 8 is squarely about audio, NFC, fingerprint, and dock reliability. That’s a textbook stabilization pattern, not a build with anything left to reveal.
It also explains why Google is already testing further out. QPR2’s first beta rolled out on July 20, 2026, meaning the company is running two release cycles in parallel right now, wrapping up QPR1 while getting an early read on QPR2 from a smaller pool of testers. If you want the fuller picture of what actually shipped as new capability earlier in this cycle, rather than this bug-fix pass, our breakdowns of Android 17 Beta 1’s early features and everything added in Beta 2 cover that ground, including the Pause Point feature designed to interrupt doomscrolling.
How to Check Your Build Number or Install Beta 8
If you’re already in the Android Beta Program, the update should arrive as a standard over-the-air notification. To confirm you’re on it, open Settings, tap About phone, and check that the build number reads CP31.260623.010.
If you’re not enrolled yet and want to try it, head to the Android Beta Program site, sign in with the Google account tied to your Pixel, and opt in. Your device will pick up Beta 8 directly rather than waiting for QPR1’s stable release. Just know that opting in now means riding out whatever’s left of the beta cycle until September, and Google’s own guidance is that you can only opt back out without a data wipe during specific windows in the cycle, not at any time. If you’d rather just confirm what Android version your Pixel is currently running before deciding, our guide on checking your current Android version walks through it.
Final Thoughts
Android 17 QPR1 Beta 8 isn’t exciting, and it isn’t supposed to be. It’s Google closing out the audio corruption bug, a flaky tablet dock, a broken NFC reader, and unreliable fingerprint unlock, four fixes that had real, daily impact on people running the beta despite none of them being new features. If you’ve been holding off updating because of the audio issue specifically, this is the build that resolves it. Everyone else can treat Beta 8 as one more sign that September’s stable Feature Drop is close, and that Google is spending its remaining beta cycles fixing what’s broken rather than adding what’s new.
All information current as of August 1, 2026. Feature availability, OTA rollout timing, and eligible devices can vary by carrier and region.
