Android 17 QPR1 Beta 6: Platform Stability, Mapped in Full

Android 17 QPR1 Beta 6 hits Platform Stability. See the full beta timeline and every bug fix.

Google shipped Android 17 QPR1 Beta 6 on July 1, 2026, and buried inside the release notes is a milestone bigger than any single bug fix: Platform Stability. That single line means the API surface for this update is now frozen. Developers can build against it without fear of Google changing the rules underneath them next month.

Android 17 QPR1 Beta 6 locks the developer API surface, fixes five reported bugs, redesigns the home screen context menu, and adds calorie and distance tracking to Health Connect. It carries build number CP31.260618.005 and runs on the June 5, 2026 security patch. Stable release is expected with the September Feature Drop.

But there’s a wrinkle nobody selling you the changelog is telling you: Android 17 QPR1 Beta 6 is the sixth beta of a cycle that started back in April, and the gap between “Platform Stability” and “actually stable on your phone” has historically run eight to ten weeks. If you’re on the beta track hoping for a quiet ride to September, the last two builds tell a different story.

What’s Actually New in Android 17 QPR1 Beta 6

The headline features are small, almost deliberately so. Late-stage betas exist to stop shipping features and start hardening what’s already there. Android 17 QPR1 Beta 6 fits that pattern exactly.

Health Connect now tracks distance and calories directly on the phone, a metric that previously required a paired wearable to log. The Settings app icon has been redesigned, borrowing the look Google first introduced on the Pixel Watch; it only shows up once you move the icon manually on your home screen, which is an odd way to ship a redesign but consistent with how Google tends to soft-launch cosmetic changes before a wider rollout. The wallpaper picker menu got a visual pass too, tightening spacing and reordering a few sections.

None of that competes with the actual news: Platform Stability. Google confirmed through Mishaal Rahman, its Android community engagement lead, that Beta 6 locks the API surface for developers targeting this release. Practically, that means the five bug fixes below are close to what ships in September, barring a late-cycle emergency patch.

Small stuff. Nothing flashy.

The fixed issues in Android 17 QPR1 Beta 6:

• Users couldn’t select multiple spell checker languages at once (Issue #147312111).
• Volume buttons stopped registering inside the Clock app across three separate tracker threads (Issues #527400457, #527395501, #524895625).
• Rapidly swiping the media carousel in Quick Settings caused visible glitches in the layout and settings icon.
• A WindowManagerGlobal bug was crashing apps outright (Issue #516639947).
• Turning on the Wi-Fi hotspot showed a generic SSID instead of your saved custom name (Issue #485168823).

Every fix here traces back to a public Issue Tracker report, which tells you something about how Google is running this cycle: react to what testers file, patch it, ship the next build two to three weeks later.

The Full Beta Timeline From Beta 1 to Beta 6

Every article covering Android 17 QPR1 Beta 6 treats it as an isolated event. None of them show you the full arc, so I pulled the build numbers, patch levels, and release dates for every beta in this cycle and put them in one place. This is the table nobody ran.

Two things jump out once you see it laid end to end. First, Google briefly dropped the Pixel 6 and Pixel 6 Pro from Beta 4 without explanation, then confirmed on Reddit it would restore them the following release, which it did with Beta 5. If you’re on either of those phones and skipped an update in early June wondering why, that’s why. Second, the pace itself is the real story: six betas in ten weeks, with Beta 5 and Beta 6 landing just seven days apart. That’s a noticeably tighter cadence than QPR1 cycles Google ran for Android 16, where gaps between betas regularly stretched past two weeks even in the run-up to stability.

The Linux Terminal Keeps Getting Power-User Upgrades

While most coverage of Android 17 QPR1 Beta 6 focused on Health Connect and the Settings icon, the Linux Terminal app quietly picked up its second major upgrade in as many betas. Beta 5 added new terminal tricks. Beta 6 goes further, adding a full “Keyboard shortcuts” menu under Settings, with individual toggles for each shortcut and the ability to record your own custom key combination through a pop-up.

This isn’t a phone feature. On a touchscreen with no physical keyboard, custom shortcuts are dead weight. It’s built for Pixel Desktop mode, tablets paired with a keyboard case, and reportedly the unannounced “GoogleBooks” Chromebook-adjacent hardware that’s been floating around leak reports. Google shipping this kind of granular control two betas before a stable release, rather than saving it for a flashier September announcement, suggests the Terminal app is becoming a genuine pillar of Desktop mode rather than the developer curiosity it launched as.

Desktop Mode’s Two Small But Real Changes

Desktop windowing picked up two adjustments in Android 17 QPR1 Beta 6. Both are minor. Both matter if you use a monitor. Taskbar icons moved from bottom-center to bottom-left, and picture-in-picture windows can now be dragged and dropped anywhere on screen instead of snapping to a fixed edge. Samsung’s DeX has supported free-floating PiP for years, so this isn’t new to the category. It is new to Google’s own implementation, and it’s a small tell that Google is still actively iterating on desktop windowing rather than treating it as finished after last year’s general availability launch.

The Bootloop Warning You Shouldn’t Ignore

Not every build in this Android 17 QPR1 cycle has been clean. Beta 6 itself is fine so far. The build before it wasn’t for everyone. Testers spanning the Pixel 6 Pro through the Pixel 10 Pro Fold reported a bootloop on an earlier build in this cycle, a restart cycle that wouldn’t resolve without a full factory reset. It wasn’t universal; some testers installed the exact same update without any trouble, and nobody’s pinned down the trigger. It’s a beta-only issue, so stable Android 17 users are unaffected, and it doesn’t touch anyone still parked on an older Android version.

If you’re running Beta 6 on a daily driver, back up your data before you tap install. That’s true of any beta, but worth repeating given this cycle’s history.

If You’re Testing Android 17 QPR1 Beta 6 From India

None of the coverage on Android 17 QPR1 Beta 6 addresses the one question that actually matters if you’re reading this from Surat, Mumbai, or anywhere else in India: is any of this region-locked? It isn’t. The Android Beta Program enrolls devices by hardware eligibility, not by carrier or geography. An imported or India-retail Pixel 8, 9, or 10 series device qualifies the same way a US unit does. No US SIM. No VPN. No US Google account required.

What does matter locally is your carrier’s own bug list. Jio and Airtel VoLTE handoff issues have shown up on earlier Android 17 QPR1 betas in threads outside the official Issue Tracker, and neither carrier publishes a compatibility statement for beta software, so you’re testing blind on network-specific bugs the way every beta tester globally is. Google’s official system images and OTA rollout are identical worldwide; the only difference an Indian tester will hit is carrier-side, not Google-side.

If you’d rather wait, the safer move is to stay off the beta track entirely and let the September Feature Drop bring Android 17 QPR1 to your device as a signed, stable OTA. Given this cycle averaged roughly two weeks between builds, and Beta 6 just reached Platform Stability, a September ship date lines up with Google’s own quarterly cadence rather than looking optimistic.

Should You Install Android 17 QPR1 Beta 6?

Short answer: it depends on your device’s role. If you’re already enrolled in the beta program, yes, install it. Platform Stability means the risk profile of this specific build is lower than any beta before it in this cycle; the API surface won’t shift again before September. The five fixes it carries are all quality-of-life patches, not experimental features that could regress.

If you’re not enrolled yet and you’re on a primary device, wait. Installing a beta mid-cycle to catch Platform Stability isn’t worth the bootloop risk that’s already shown up once this cycle, especially with stable arriving in roughly two months anyway. Enroll a secondary device if you want to test now, or hold off and take the stable build when it lands.

Frequently Asked Questions About Android 17 QPR1 Beta 6

What is Platform Stability in Android 17 QPR1 Beta 6? Platform Stability means Google has frozen the developer-facing API surface for this release. Apps built against the Beta 6 SDK will keep working without changes through the stable release, which lets developers finalize and publish updates ahead of the public launch.

What build number does Android 17 QPR1 Beta 6 use? Android 17 QPR1 Beta 6 uses build CP31.260618.005 and ships on the June 5, 2026 Android security patch, with Google Play services updated to version 26.20.31 or later.

Which Pixel phones can install Android 17 QPR1 Beta 6? Every Pixel from the Pixel 6 series through the Pixel 10 series is eligible, including the Pixel 6a, Pixel 7 series, Pixel 8 series, Pixel 9 series, Pixel 10 series, Pixel Tablet, and Pixel Fold models. Enroll through the Android Beta Program to receive the OTA.

When will Android 17 QPR1 go stable? Google hasn’t confirmed an exact date, but the update is expected to arrive publicly with the September Feature Drop, following the same quarterly cadence Google used for prior QPR releases.

Is Android 17 QPR1 Beta 6 safe to install on a daily driver phone? It’s safer than earlier builds in this cycle since Platform Stability limits further API changes, but a bootloop affecting some testers on an earlier build this cycle is a reminder that beta software carries risk. Back up your data first, and avoid installing on your only phone if you can’t afford downtime.

Does Android 17 QPR1 Beta 6 work the same for Pixel users in India? Yes. The Android Beta Program is hardware-eligibility based, not region-locked, so India-retail and imported Pixel devices from the 8, 9, and 10 series enroll and update identically to units anywhere else. Carrier-specific network bugs are the only variable that differs by region.