Google Rolls Out Android 17 QPR1 Beta 4 for Pixel Devices

Google pushed Android 17 QPR1 Beta 4 to Pixel phones on June 10, 2026, the fourth quarterly beta in a series that opened on April 22. The build, numbered CP31.260522.006, ships with seven fixes aimed at daily-driver annoyances that slipped into earlier QPR1 drops: a vanishing mouse pointer on external displays, screenshot sounds tied to the ringer, 5x zoom jitter in video, and Back Tap gestures that refused to wake the lock screen.

The update carries the May 2026 security patch and runs on Google Play services version 26.18.35. Google’s release notes for QPR1 frame the builds as “suitable for general use” rather than as developer previews, and pair them with the next Pixel Feature Drop, the quarterly bundle of new features Google rolls out to Pixel phones after the platform reaches stability.

What QPR1 Beta 4 Patches on Pixel

Three of the seven fixes touch everyday features. Back Tap, the gesture that wakes the lock screen when you double-tap the back of the phone, stopped responding on the interactive lock screen, and tapping the panel no longer triggered the wake-up. Screenshot sounds were tied to the ringer volume, so a user who silenced the ringer for a meeting also lost the screenshot confirmation noise. Video at 5x zoom exhibited frame jumps and jitter during panning, the kind of stutter that ruins a one-take clip.

The remaining four fixes address heavier system issues. A mouse pointer connected to an external display could become invisible when a Work profile or FLAG_SECURE app was active. Launching credential provider settings from a Private Space triggered a Settings app crash. A graphics driver regression caused severe 3D performance drops in OpenGL ES applications on newer hardware. Wireless ADB and other local-network-dependent apps failed to connect, breaking developer workflows and some local casting setups.

Build CP31.260522.006 ships with the May 2026 security patch, runs on Google Play services version 26.18.35, and supports x86 and ARM v8-A emulator targets. The full list of changes, with issue tracker links, sits on all seven issues Google flagged in QPR1 Beta 4.

The QPR1 Beta Cadence Since April

Google opened the QPR1 beta series on April 22, 2026 with Beta 1, followed Beta 2 on May 6, Beta 3 on May 19, and now Beta 4 on June 10. The release notes call this “a quarterly cadence through Quarterly Platform Releases,” with each beta adding fixes on top of the prior build rather than introducing new features.

Beta 1 fixed four issues, including a Default Print Service crash under low ink and an Application Not Responding (ANR) loop in the Terminal app. Beta 2 added nine fixes, among them a Terminal launch bug, a lock screen overlap with the fingerprint sensor area, a Bluetooth tethering toggle that reset on restart, and a data-corruption risk in the F2FS file system. Beta 3, released during Google I/O week, addressed seven issues including Wi-Fi disconnecting despite a strong signal, crackling audio across media playback, and home screen widgets that disappeared after a reboot. Beta 4 closes the initial QPR1 beta cycle with seven more fixes.

Why the ‘QPR1’ Label Changes the Story

QPR1 stands for Quarterly Platform Release 1, the first of three quarterly platform updates Google ships to Pixel devices each year. The main Android 17 betas tracked the platform’s initial release; the QPR1 series picks up after the platform has reached stability, the moment in the cycle when the API surface locks and Google stops accepting new app-impacting changes.

Google’s release notes describe QPRs as fixes and improvements that “are then rolled out to supported devices” through a “quarterly cadence,” and “delivered both to AOSP and to Google Pixel devices as part of Feature Drops.” A Feature Drop is the quarterly bundle of new features and fixes Google ships to Pixel phones, distinct from a full platform release. QPR1 is the codebase behind the first Feature Drop of the year, and the same Android 17 release underpins other skins, including Samsung’s One UI 9 beta for the Galaxy S26.

That positioning explains why the QPR1 build reads as a maintenance release. All of the major Android 17 features shipped in the main beta cycle, and the QPR1 series is now polishing what is there. The release notes call these builds “suitable for general use,” a label the release notes reserve for quarterly updates in the post-platform-stability phase, and pair them with the next Feature Drop.

Every Pixel That Can Run the Beta

Google lists 21 supported Pixel models for the Android 17 QPR1 beta, ranging from the Pixel 6 and 6 Pro, the oldest devices in the lineup, to the Pixel 10a, the newest. Tablets and foldables are in the mix, including the Pixel Tablet, Pixel Fold, Pixel 9 Pro Fold, and Pixel 10 Pro Fold.

The full device list, organized by release wave:

• Pixel 6, Pixel 6 Pro, Pixel 6a
• Pixel 7, Pixel 7 Pro, Pixel 7a, Pixel Tablet, Pixel Fold
• Pixel 8, Pixel 8 Pro, Pixel 8a
• Pixel 9, Pixel 9 Pro, Pixel 9 Pro XL, Pixel 9 Pro Fold, Pixel 9a
• Pixel 10, Pixel 10 Pro, Pixel 10 Pro XL, Pixel 10 Pro Fold, Pixel 10a

The full list and any per-device limitations are on the supported Pixel devices page on the Android Developers site.

Two Ways to Install the Build

Most users take the OTA route. Enroll a supported Pixel in the Android Beta for Pixel program through Google’s enrollment page, and the device will receive the QPR1 Beta 4 update over the air. The enrollment page warns that, in most cases, no data wipe is required, but recommends backing up the device before enrolling.

For users who prefer a clean flash, full system images for the QPR1 Beta 4 build are also available. The Android Flash Tool is Google’s recommended flashing path, but manual flashing works for anyone comfortable with the command line. Both paths deliver the same build, and the QPR1 emulator system image runs in Android Studio’s x86 and ARM v8-A configurations for app testing.

Details on enrollment and flashing sit on how to enroll a Pixel in the Android Beta program, while the SDK and tooling for the manual path are linked from the Android Developers site.

The ‘Suitable for General Use’ Label, Explained

The distinction between QPR1 builds and the main Android 17 betas sits in the introduction to the QPR1 release notes, in wording the mainline betas do not use. The framing is more deliberate than a typical disclaimer. Google’s main Android 17 betas, by contrast, are framed as developer previews, useful for testing app compatibility but not polished enough for a daily driver.

Unlike developer previews and betas for unreleased, major versions of Android, these builds are suitable for general use.

The line is from Google’s QPR1 release notes on the Android Developers site, the official document for the Android 17 QPR1 beta program. The fixes in Beta 4 fit that positioning: Back Tap, screenshot sound, and 5x zoom jitter are all consumer-facing behaviors, and the Settings crash, mouse pointer visibility, and Wireless ADB regression touch the work-and-presentation side of the device. The QPR1 cadence and the Feature Drop pairing are the post-platform-stability chapter of Android 17, and this build sits inside that chapter. The wording is the language Google uses to set the QPR1 builds apart from the mainline Android 17 betas, which are framed as developer previews. The build is on the path to consumer release, with the QPR1 codebase delivered as part of the next Pixel Feature Drop, per the QPR1 release notes’ framing.

Frequently Asked Questions

What does QPR1 stand for, and how is it different from the main Android 17 betas?

QPR1 stands for Quarterly Platform Release 1, the first of three quarterly updates Google ships to Pixel devices each year. The main Android 17 betas tracked the platform’s initial release; the QPR1 series picks up from there, with Google describing the QPR1 builds as “suitable for general use,” a label reserved for quarterly updates rather than for the developer previews of unreleased major versions of Android.

Which Pixel phones can run Android 17 QPR1 Beta 4?

Google lists 21 supported models: the Pixel 6, 6 Pro, 6a, the Pixel 7 series, Pixel Tablet, Pixel Fold, the Pixel 8 series, the Pixel 9 series (including Pro XL, Pro Fold, and 9a), and the Pixel 10 lineup (including Pro XL, Pro Fold, and 10a).

Is Android 17 QPR1 Beta 4 safe to install on a daily-driver phone?

Google’s release notes describe the QPR1 builds as “suitable for general use,” but the company still recommends backing up your data before enrolling. As with any pre-release software, occasional rough edges can show up even by the fourth beta.

Will installing QPR1 Beta 4 wipe my phone?

Google’s enrollment guidance says that, in most cases, you will not need to do a full reset of your data to move to the Android 17 beta. A backup before enrolling is still the recommended move.

How often does Google ship QPR updates to Pixels?

Google describes the QPR1, QPR2, and QPR3 series as a quarterly cadence, with each release tied to a Pixel Feature Drop that follows the main platform release across the year.