Android 17 QPR1 Beta 6 Hits Platform Stability for Pixel

Google pushed the sixth beta of Android 17 QPR1 (the first quarterly platform release of Android 17) to compatible Pixel phones on July 1, 2026. Build CP31.260618.005 carries the operating system to its Platform Stability milestone, the point in Google’s quarterly cycle where the API surface developers need to target is locked.

Android development team member Mishaal Rahman flagged the rollout in Mishaal Rahman’s post on the Beta 6 release, writing that the build had reached “Platform Stability” and that the API surface “for developers has been locked.” Google confirmed the same milestone on the Android 17 QPR1 release notes page, telling third-party app creators they could start incorporating the new Android 17 QPR1 capabilities into their software. QPR1 builds are designed to pair with the next quarterly Pixel Feature Drop, and Platform Stability is the signal that the platform work is closed out before that bundling happens. Rahman cited the build number CP31.260618.005 alongside the milestone in the same post.

Beta 6 Lands Days After Beta 5

Beta 6 lands days after Beta 5. Google shipped Beta 5 build CP31.260608.007 on June 23, 2026, per the Android Developers release notes, the same page that tracks every QPR1 beta. The earlier build added ten fixes of its own, including patches for a Game Dashboard screen-recording failure, a camera freeze on cold launch, and a regression that cost Monopoly Go mini-games their saves.

The QPR1 beta series opened on April 22, 2026, with Beta 1 and ran on a roughly monthly cadence through the spring.

Beta 6 broke that rhythm by arriving shortly after Beta 5, an acceleration Google did not use elsewhere in this cycle. The new build also refreshes the security metadata. Beta 6 carries the June 5, 2026 security patch level. It pairs that patch with Google Play services version 26.20.31, per the release notes entry for the build.

The Five Bugs Beta 6 Patches

Google’s release notes list five resolved issues for Beta 6, each tagged with an issue tracker number. The list is short for a typical quarterly beta. It reflects the daily-driver focus Google has carried through the late QPR1 cycle, the kind of cleanup that fits cleanly at the Platform Stability stage. None of the five fixes touch a major Android 17 feature introduced earlier in the cycle. They target everyday behaviors a beta tester can flag in the field.

• Spell checker: users could not select multiple spell checker languages (Issue #147312111).
• Clock app volume: pressing the device volume buttons inside the Clock app failed to trigger the expected user interface actions, including silencing an active alarm (Issue #527400457, #527395501, #524895625).
• Media carousel: rapid swipes through the media carousel scrambled the Quick Settings layout and hid system toggle icons (Issue #514947195).
• WindowManagerGlobal: an internal bug in WindowManagerGlobal produced random app crashes (Issue #516639947).
• Wi-Fi hotspot SSID: enabling the Wi-Fi hotspot showed a generic factory SSID instead of the user’s saved custom name (Issue #485168823).

The five entries are the only fixes Google lists in the release notes for this build. Rahman separately confirmed the build number and the Platform Stability milestone in his X post.

Visible Changes Beyond the Patch Notes

The Settings icon has been redesigned in the style first introduced on the Pixel Watch. The change is visible the moment a tester pulls down the Quick Settings shade or opens the app drawer. Long-press the home screen and the wallpaper picker has been refreshed too.

The Wallpaper & style label has moved to the top of the context menu. The spaces between menu items have been removed in the same pass.

Testers who flip into desktop windowing will find the taskbar icons parked in the bottom-left corner of the display, no longer centered the way they sat in earlier QPR1 builds. Picture-in-picture windows now float freely inside that desktop space too, instead of snapping to the right or left side of the screen. Health Connect on phones picked up distance and calorie tracking in the same build, a quiet expansion of the platform-level health surface. None of the visual changes carry new app-facing APIs. They sit on top of the locked surface Beta 6 establishes.

Which Pixels Can Run the Build Today

Beta 6 covers 21 Pixel models, the same lineup Google has supported across the QPR1 cycle. The list ranges from the oldest Pixel 6 series to the newest Pixel 10a, and it includes tablets and foldables in the lineage. System images for each are available on the Android Developers site the same day.

Pixel owners enrolled in the standard Android Beta Program can pull the OTA directly from Settings, without waiting for the carrier rollout that gates most stable releases. The Android Beta Program for Pixel enrollment page handles sign-in, lists the eligible devices on the signed-in Google Account, and walks testers through opting in. The same program warns that opting out and rolling back to a stable release will wipe the device once the next beta is installed. Google also published raw OTA images for users who prefer to flash manually.

Emulator support includes x86 64-bit and ARM v8-A system images, both shipping the same day per the release notes entry. Beta tester feedback flows through the Android Beta Feedback app, the Android Developers issue tracker, and the Android Beta Reddit community.

Beta testers who want to read further back into the same cycle can start with the timeline and patches from QPR1 Beta 4. The Android Developers release notes cover Beta 1 through Beta 6 in one running document. Each row of the release notes table lists the build number, release date, emulator support, security patch level, and Google Play services version for that specific build.

What ‘Platform Stability’ Means for App Developers

The Platform Stability language is Google’s way of saying the structural work on Android 17 QPR1 is finished. From Beta 6 forward, app creators can compile against the locked API surface and ship QPR1-ready updates. They no longer need to worry that a future quarterly bump will rewrite the surface underneath them. Google’s release notes frame the milestone in plain terms.

Android 17 QPR1 has reached Platform Stability as of Beta 6. The API surface is locked, the API diff report reflects the final changes, and you can now incorporate new Android 17 QPR1 capabilities into your apps.

For most consumer-facing apps the lock is invisible in practice, and target SDKs, runtime permissions, and broadcast contracts that worked in Beta 5 will keep working through the stable QPR1 release. For apps that lean on QPR1-specific behavior, including the new Health Connect distance and calorie metrics or the refreshed wallpaper picker, the lock gives developers a fixed surface to test against before the general rollout. The full QPR1 release notes, including the API diff report Google promises and any future patch entries, sit on the Android 17 QPR1 release notes page on the Android Developers site.

How Beta 6 Fits the QPR1 Cadence So Far

The QPR1 cycle opened on April 22, 2026 with Beta 1. That was followed by Beta 2 on May 6, Beta 3 on May 19 (Google I/O week), and Beta 4 on June 10. Beta 5 arrived on June 23. Beta 6 closes the beta run on July 1 with the API surface locked and the patch queue thinned to a short daily-driver list.

The shortened gap between Beta 5 and Beta 6 is the cleanest signal of where Google is heading this quarter. The Android Developers release notes tie the QPR1 codebase to “Feature Drops” on Pixel, the quarterly bundle of fixes Google ships alongside platform updates.

Beta 6 itself remains a pre-release build for testers enrolled in the beta program. The QPR1 release notes describe the cycle as “suitable for general use,” a label reserved for the post-platform-stability phase. Pairs of QPR1 and the next Pixel Feature Drop have shipped together in earlier years, and the release notes frame QPR1 as the codebase that pairs with the next quarterly Pixel bundle.

Frequently Asked Questions

What does Platform Stability mean for Android 17 QPR1?

Platform Stability is the point in the beta cycle where Google locks the API surface for the upcoming quarterly release. From Beta 6 onward, third-party app developers can target the final Android 17 QPR1 APIs without further breaking changes before the stable rollout.

When did Android 17 QPR1 Beta 6 release, and what is the build number?

Google released Beta 6 on July 1, 2026. The build number is CP31.260618.005, and it carries the June 5, 2026 security patch level alongside Google Play services version 26.20.31.

Which Pixel phones can run Android 17 QPR1 Beta 6?

Google supports 21 models on Beta 6: the Pixel 6, Pixel 6 Pro, and Pixel 6a; the Pixel 7 series plus the Pixel Tablet and original Pixel Fold; the Pixel 8 series; the Pixel 9 series including the Pro Fold; and the Pixel 10 lineup including the 10 Pro Fold and the Pixel 10a.

What bugs does Android 17 QPR1 Beta 6 fix?

Beta 6 patches five issues: a spell checker limitation on multiple languages, missing volume-button responses inside the Clock app, a glitch that scrambled Quick Settings during rapid media carousel swipes, an app-crashing bug in WindowManagerGlobal, and a Wi-Fi hotspot SSID that reset to a generic default instead of showing the saved custom name.

How do I install Android 17 QPR1 Beta 6?

Enroll a supported Pixel in the Android Beta Program through Google’s enrollment page, then pull the build over the air from the system Settings menu. Users comfortable with manual flashing can also download the raw OTA images from the Android Developers site and apply them with the Android Flash Tool.