Android 17 QPR2 Beta 5 Is All About Fixes: Here’s What Changed

If Android 17 QPR2 Beta 4 left you dealing with random reboots, camera crashes, or Bluetooth problems, the latest beta should come as welcome news. Google has released Android 17 QPR2 Beta 5 for supported Pixel devices, and this update is focused almost entirely on stability and bug fixes rather than introducing major new features.

Google released QPR2 Beta 5 on September 15, 2026, following the previous beta’s move to Platform Stability. That milestone is important because it means the APIs and app-facing behaviors for this quarterly release are essentially locked down. Developers can now build against a stable foundation while Google concentrates on fixing remaining problems before the final release.

The result is a relatively modest update on paper, but potentially a much more important one for anyone already running the Android 17 QPR2 beta.

Here’s everything you need to know about Android 17 QPR2 Beta 5, including the supported Pixel models, build numbers, Quick Settings changes, major bug fixes, call-forwarding security improvements, and the expected stable release window.

Android 17 QPR2 Beta 5 Release Date and Supported Pixel Devices

Android 17 QPR2 Beta 5 became available on September 15, 2026. Google is distributing the release through two different builds depending on the Pixel device.

The supported devices receive the following builds:

• Pixel 6a, Pixel 7 series, Pixel Fold, and Pixel Tablet: CP41.260828.005.A6
• Pixel 8 through Pixel 11 series, including Pixel 11 Pro Fold: CP41.260828.004.A8

Both versions include the August 5, 2026 Android security patch and Google Play services version 26.28.33.

There is one important exception: the original Pixel 6 and Pixel 6 Pro aren’t eligible for Android 17 QPR2 Beta 5 because their official software-support period has ended.

If your device is already enrolled in Google’s Android Beta Program, you can check for the update through the normal system update screen.

For users who prefer installing beta software manually, Google also provides factory/system images through the Android Beta Program, while its Android 17 QPR2 release notes provide the corresponding build information.

Quick Settings Gets a New Audio Streams Tile

Android 17 QPR2 Beta 5 doesn’t introduce a huge visual redesign, but there are a few changes you’ll notice when interacting with the system interface.

One of the more visible additions is a new Audio streams tile in Quick Settings. It provides another way to access audio-stream controls directly from the notification shade.

At the same time, Google appears to have removed the option that previously allowed users to manually customize the arrangement of Quick Settings tiles.

Google has not clearly indicated whether the Quick Settings customization option has been permanently removed or is simply disabled temporarily during the beta cycle. Because it isn’t specifically documented as a permanent change in the release notes, it’s best to consider its status unresolved for now.

Another small interface adjustment affects the voice broadcast tile, which has been moved into the Connectivity section.

These changes may seem minor, but they show that Google is still making small usability adjustments even after Android 17 QPR2 reached Platform Stability.

Android 17’s Battery Settings Are Becoming More Unified

Another interface change can be found in the Settings app.

The battery section is now labeled “Battery & charging,” bringing battery and charging-related controls together under a single menu.

Google initially introduced this more unified approach on the Pixel 11 family, and QPR2 is extending the organization to other supported Pixel devices.

The change should make charging-related options easier to locate, particularly for users who want to manage features such as charging limits without searching through multiple settings categories.

It isn’t a dramatic Android 17 feature, but it’s the kind of interface cleanup that can make everyday use less frustrating.

Android 17 QPR2 Beta 5 Fixes Several Major Bugs

The most important part of Beta 5 isn’t what Google added. It’s what Google fixed.

The release contains eight documented fixes, addressing problems affecting system stability, Bluetooth, the camera, HDR, Google Wallet, Private Space, search interfaces, and media casting.

Random Reboots During Scrolling Are Fixed

One of the more disruptive problems in previous QPR2 builds could cause the phone to unexpectedly restart while scrolling through media-heavy applications.

For users affected by the issue, simply browsing an app containing large amounts of images or other media could result in an unexpected reboot.

Beta 5 addresses this stability problem.

This is particularly significant for anyone who experienced random restarts while using social media, messaging applications, or other content-heavy apps.

Bluetooth Audio Problems After Calls Should Be Resolved

Beta 5 also fixes Bluetooth problems involving connected audio devices.

Google specifically addressed situations where:

• Bluetooth device icons weren’t updating correctly in Settings.
• Audio could become noisy or distorted after ending a phone call.

The second issue could be especially noticeable for people who regularly use wireless earbuds or headphones for calls and music.

Panorama Mode No Longer Crashes the Camera

The Google Camera app gets an important stability fix as well.

Some QPR2 beta users encountered crashes when using Panorama mode, potentially interrupting a photo capture session.

Beta 5 resolves the panorama-related crash.

For a beta release that has already reached Platform Stability, fixing camera reliability is particularly important because camera functionality is one of the core features users expect to work consistently.

Google Wallet Could Leave the Touchscreen Unresponsive

Another unusual bug involved Google Wallet.

Launching Wallet using the power-button shortcut could, under certain circumstances, leave the touchscreen unresponsive.

Because Google Wallet can be accessed quickly from the power button for payments and other functions, an issue that temporarily interferes with touch input is more than just a cosmetic annoyance.

Google has fixed this behavior in Beta 5.

Enhanced HDR No Longer Stays Enabled Unexpectedly

Android 17 QPR2 Beta 5 also fixes an issue involving Enhanced HDR.

The setting could remain enabled even after users turned it off through Settings. Since HDR processing can have an impact on display behavior and power consumption, this could potentially lead to unnecessary battery usage.

The latest beta corrects the problem so the setting behaves as expected.

Private Space Gets Several Fixes

Google has also addressed problems involving Private Space.

Some users experienced glitches when attempting to leave Private Space after unlocking it.

Private Space is designed to isolate sensitive applications and data from the main Android environment, so navigation problems within the feature can be particularly inconvenient.

Beta 5 includes a fix for this behavior.

Search Highlighting and Casting Problems Are Also Fixed

Two additional issues have been addressed.

Search fields could display incorrect background highlighting, creating a visual glitch in parts of the interface.

Google has also fixed a casting-related issue in which the volume slider could disappear when users attempted to adjust media volume using the physical volume buttons.

Taken individually, these bugs are relatively minor. Together, however, the fixes make Beta 5 a more polished release than some of the previous QPR2 builds.

Android 17 QPR2 Adds Protection Against Call-Forwarding Abuse

There’s another QPR2 change worth knowing about, particularly from a security perspective.

Android 17 QPR2 introduces additional restrictions around apps attempting to activate call forwarding through USSD codes.

USSD codes are special dial strings used by mobile networks for different carrier services. Certain codes can be used to configure call forwarding, which creates an opportunity for abuse if a malicious application can trigger those commands without the user’s knowledge.

Under the new behavior, an application that only has the CALL_PHONE permission cannot silently use TelephonyManager.sendUssdRequest() to initiate call-forwarding operations in the background.

Instead, Android returns a USSD_ERROR_NOT_ALLOWED result.

Users who manually enter a call-forwarding code themselves will also see an operating-system confirmation prompt before the request is completed.

Why Android Is Restricting Call Forwarding

Call-forwarding abuse can be used as part of account-takeover and phone-verification scams.

For example, if an attacker manages to redirect a victim’s incoming calls to another number, calls containing verification codes could potentially be intercepted by the attacker.

By placing the restriction at the Android operating-system level, Google can prevent applications from quietly initiating these specific forwarding requests.

The change is deliberately narrow. Google’s documentation indicates that other USSD functions, such as mobile-money and account-balance checks, aren’t affected by this particular restriction.

Developers whose applications previously depended on the old behavior will need to account for the new error response or use an ACTION_DIAL intent where appropriate.

Is Android 17 QPR2 Beta 5 Worth Installing?

That depends largely on whether you’re already participating in the Android Beta Program.

If you’re already running an earlier QPR2 beta and have experienced the reboot, camera, Bluetooth, Wallet, or other bugs addressed here, Beta 5 is a meaningful maintenance update.

However, beta software can still contain bugs that haven’t been discovered or documented yet. Users who depend on their Pixel as their primary device and don’t need early access to Android releases may prefer to remain on the stable channel.

In other words, Beta 5 is primarily a stability release rather than a feature release.

That’s exactly what you’d expect at this point in the QPR2 development cycle.

When Will Android 17 QPR2 Be Released as a Stable Update?

Google has not announced an exact stable-release date for Android 17 QPR2.

However, the quarterly release has already reached Platform Stability, and the current beta schedule points toward a December 2026 stable release window, potentially arriving alongside the December Pixel Feature Drop.

That timing should be treated as an expected window rather than a guaranteed launch date until Google officially confirms it.

With Platform Stability already reached, future QPR2 beta releases are also likely to concentrate heavily on bug fixes, reliability improvements, and final polish rather than major new features.

Google can still change details before the stable version ships, so users should rely on the official release notes for the latest information.

Android 17 QPR2 Beta 5: The Bottom Line

Android 17 QPR2 Beta 5 isn’t designed to grab attention with a collection of flashy new features. Instead, Google is using this stage of development to make the existing Android 17 experience more reliable.

The update addresses unexpected system reboots, Bluetooth audio problems, camera crashes, Google Wallet touchscreen issues, Enhanced HDR behavior, Private Space glitches, search highlighting, and casting controls.

There are also smaller interface changes, including the new Audio streams Quick Settings tile and the consolidated Battery & charging menu.

For Pixel owners already running QPR2, updating to Beta 5 makes sense if one of the bugs addressed by Google has been affecting your device. For everyone else, the stable release remains the simpler option, especially with QPR2 currently expected to arrive around December 2026.

The broader takeaway is clear: Android 17 QPR2 has moved beyond major platform development and is now entering the final stretch where reliability and polish matter more than adding another headline feature.