Google Releases Android 17 QPR3 Beta 1 for 23 Pixel Devices

Google released Android 17 QPR3 Beta 1 on October 2, 2026, the first preview build for Android 17's third quarterly platform update. The beta is available to developers and users on 23 Pixel device models, plus the Android Emulator in Android Studio. According to the official release notes, it is mostly bug fixes: from freezes when unlocking with a fingerprint, to missing cellular service, to eSIMs that fail to activate. Google says QPR3 carries no API changes.

What a QPR is, and where QPR3 sits

Android 17 is already out, and Google is not waiting for the next major version to fix it. According to the official Android Developers documentation, the platform is updated continuously with fixes and improvements that are then rolled out to supported devices. Those updates arrive on a quarterly schedule called Quarterly Platform Releases (QPR). Each QPR ships to AOSP (Android Open Source Project, Android's open code base) and to Google Pixel devices as part of a Feature Drop.

QPR3 is therefore not Android 18 or a new major version. It is a follow-on release on top of Android 17. Google calls Android 17 the start of a transition toward an "intelligence system," with development standards that prioritize adaptive screens along with improvements to privacy, security, media, camera and performance. QPRs carry that foundation forward through periodic fixes.

QPR3 Beta 1 landed right at the end of QPR2's run. The QPR2 release notes page shows Beta 6.1 arriving on September 29, 2026, just three days before QPR3 Beta 1. QPR2's first beta itself arrived on July 20, 2026, so a single QPR2 beta cycle ran a little over two months and spanned seven beta builds (Beta 1 through Beta 6.1).

Beta 1 build details

The official release notes give the following technical details for Beta 1:

On the download page, build DP11.260918.005 is used for the Pixel 11 family, while DP11.260918.006 is used for the other Pixel models. Google stresses that QPR3 includes no API changes. For app developers, that means this beta is not a trigger for code adjustments. Even so, Google still provides the images so apps can be tested against this release, so the update goes smoothly for all users.

Supported devices

Beta 1 is available for the following Pixel devices:

• Pixel 6 and 7 series: Pixel 6a, Pixel 7, Pixel 7 Pro and Pixel 7a.
• Tablet and foldable: Pixel Tablet and Pixel Fold.
• Pixel 8 series: Pixel 8, Pixel 8 Pro and Pixel 8a.
• Pixel 9 series: Pixel 9, Pixel 9 Pro, Pixel 9 Pro XL, Pixel 9 Pro Fold and Pixel 9a.
• Pixel 10 series: Pixel 10, Pixel 10 Pro, Pixel 10 Pro XL, Pixel 10 Pro Fold and Pixel 10a.
• Pixel 11 series: Pixel 11, Pixel 11 Pro, Pixel 11 Pro XL and Pixel 11 Pro Fold.

That is 23 models in total. Developers without a Pixel device can use the Android Emulator in Android Studio, which supports the x86 (64-bit) and ARM (v8-A) architectures.

Bug fixes in Beta 1

Google announced no visible new features in Beta 1. What it published is a list of "top issues fixed." From that list, the fixes can be grouped by the part of the system affected.

Device security and biometrics

Several fixes concern how users unlock their phones:

• The device freezes and stops responding when unlocked with the fingerprint sensor. The problem was tracked under three separate issue numbers (#490719716, #514867650 and #523022829).
• The device crashes when the "eyes must be open" option (require eyes to be open) is selected in Face Unlock settings (#466618368 and #522677686).

Both problems touch the most heavily used everyday functions. A fingerprint reader that freezes the phone is an immediately noticeable disruption.

Connectivity and cellular service

This group of fixes matters most to users who depend heavily on signal:

• The com.android.phone process enters a crash loop and cellular service disappears entirely when the modem reports an unexpected SIM slot index (#554049220).
• An eSIM profile cannot be activated and silently reverts to off in Settings (#541436675).
• Wi-Fi fails to reconnect automatically when the device wakes in the background, when the hardware's PNO (preferred network offload) scan fails or is unsupported (#551970385).
• The NFC service crashes with DeadObjectException and stops detecting tags after the first scan, on Android 16 (#456078994).
• Audio playback stops on an active LHDC v5 Bluetooth device when a second connected device disconnects (#554992287).
• A dot appears for no reason on the Mobile Data icon in Quick Settings (#551150806).

Audio, media and camera

• The audio output device cannot be switched while playing audio from an app that has no active media controls (#259180936).
• MediaPlayer crashes when processing non-ASCII audio attribute tags (#552043106).
• The front camera does not work while screen recording is active (#523313834).
• Camera images are rotated 90 degrees in video calling apps used on an external display in desktop mode (#432390710).

Interface and app stability

• Apps crash when trying to start a foreground service from a Quick Settings tile (#299506164).
• Calling apps crash with ForegroundServiceStartNotAllowedException when handling a call shortly after the device restarts (#409069722).
• Apps freeze and throw an Application Not Responding (ANR) error when opened (#484969809 and #475406236).
• App icons in the app drawer appear with excessive spacing (#316288379 and #300758716).
• App previews fail to appear on the recent apps screen (#515091621).
• An interface glitch when switching back to the home screen from an app (#566639975).

Battery and settings

• Excessive battery drain while the device is idle, when Flip to Shh is enabled (#560036427).
• The Settings app crashes when opening battery settings (#554603197).

Context: what is already in QPR2

QPR3 Beta 1 focuses on fixes, but the QPR2 that ran immediately before it carried one security change relevant to Indonesian users, who are familiar with phone-based fraud. According to the QPR2 release notes, Android 17 QPR2 restricts call forwarding (call forwarding) that is set programmatically.

The system now parses and selectively restricts call-forwarding USSD codes such as *21#, run through the TelephonyManager.sendUssdRequest() API. That API can no longer be used for call-forwarding codes with the CALL_PHONE permission alone. Ordinary apps that try to run them in the background are blocked and receive a USSD_ERROR_NOT_ALLOWED callback. Users who type call-forwarding codes themselves into the system's built-in phone app now see an OS-level confirmation dialog before the command runs.

Google describes the move as a defence against social-engineering fraud. USSD requests that are not for call forwarding, such as mobile money transfers and account checks, are unaffected. For developers whose apps are affected, Google recommends handling USSD_ERROR_NOT_ALLOWED failures properly, or switching to the ACTION_DIAL intent so the number is pre-filled in the dialer and the user confirms it themselves.

This change is recorded in QPR2, not in QPR3 Beta 1. Quarterly updates are cumulative, so QPR3 is built on top of earlier releases.

How to try QPR3 Beta 1

Google offers two routes: the Android Flash Tool and manual installation. The official documentation carries a stern warning that moving from a production build to a beta, or the other way around, requires a full device reset that erases all user data. Back up your data first.

Using the Android Flash Tool

The Android Flash Tool runs in a browser that supports WebUSB, such as Chrome or Edge 79 and above. No extra tools need to be installed, but the device must be unlocked and USB Debugging must be enabled in developer options.

1. Back up all data on the Pixel device.
2. Enable developer options, then turn on USB Debugging.
3. Connect the device to the computer via USB.
4. Open the Android Flash Tool for QPR3 Beta 1 in Chrome or Edge.
5. Follow the on-screen instructions until the process finishes.

Using a manual flash

Developers who need more control over the test environment, for instance to reinstall frequently, can download the system image from the download page and install it manually. Each model has its own file, for example the bluejay_beta-dp11.260918.006-factory file for the Pixel 6a. Each file comes with a SHA-256 checksum to verify the download.

After the beta is installed

Once a beta build is installed, the device is automatically enrolled in the Android Beta for Pixel program and keeps receiving over-the-air (OTA) updates to the latest beta build, including QPRs, until the user decides to leave the program. To return to a public build, users need to flash the stable build's factory image via the Android Flash Tool or the Factory Images for Nexus and Pixel Devices page. This step also erases all data on the device.

Who should install this beta

Google says Android 17 QPR3 Beta is open to developers and users. But Google's published terms are worth reading before installing. The download terms state that some feature implementations are still in development, that users should not rely on full functionality the way they would on a stable release, and that SDK development versions may contain bugs, defects and security vulnerabilities. The terms also state that Google may push SDK elements to devices through automatic updates.

With that warning in mind, the practical considerations:

• App developers have the strongest reason to try it, especially if their app depends on audio, calls, NFC, camera or foreground services. Many of the fixes in Beta 1 touch those areas.
• General users should weigh the risk. A main phone used for work, banking or communication is not an ideal device for a preview build, given that a full reset is required both to switch over and to switch back.
• Pixel owners outside the list of 23 models cannot use this build.

How to give feedback

Google asks developers and users to report problems through the official Android issue tracker. The documentation page also provides links for reporting platform bugs and documentation bugs. Each fix in the list above is referenced by an issue number, so developers can track the status of reports filed through that channel.

What is still unknown

A few things are not mentioned in official sources and so cannot be confirmed:

• The stable release date of QPR3 for general users. The pages reviewed do not list a schedule.
• The list of new features QPR3 brings through Feature Drop. The Beta 1 release notes contain only bug fixes, not features.
• Availability, pricing and the update schedule in Indonesia. Developer documentation does not cover specific markets.

Readers who want to follow developments can watch the Android 17 QPR3 release notes page on Android Developers, updated on October 2, 2026, which will carry the next beta. If the QPR2 pattern repeats, where Beta 1 was followed by several follow-up betas and a 6.1 release, QPR3 will likely also get several beta updates before its final release. That is an estimate based on the QPR2 pattern, not an announcement from Google.