Google is closing out August with a fresh beta release for Pixel owners. Android 17 QPR2 Beta 4 is now rolling out to devices registered in the Android Beta Program, delivering a new set of fixes and finalizing the platform for developers. This is the fourth beta in the QPR2 cycle, and it arrives two weeks after Beta 3, following the same cadence that Google has maintained throughout the season.

Key facts at a glance

• Android 17 QPR2 Beta 4 is rolling out to Pixel testers today.
• The build is available as CP41.260814.003.A2 or CP41.260814.003.B1 depending on the device.
• The release arrives two weeks after Beta 3.
• Pixel 11 compatibility is expected soon but is not yet available.
• Pixel 6 and Pixel 6 Pro are not supported in this beta cycle.
• This beta marks platform stability for QPR2.

The latest build is labeled CP41.260814.003.A2 on some devices and CP41.260814.003.B1 on others. Google has not detailed exactly which model carries which build number, but the distinction is likely related to the hardware generation or regional segmentation. As with previous QPR2 releases, the Pixel 6 and Pixel 6 Pro are no longer part of the beta program for this update. Those devices will have fallen outside Google's software support window by the time the stable QPR2 Feature Drop ships, so they do not receive beta builds in this cycle.

A significant milestone: platform stability

The most important change in Beta 4 is that Android 17 QPR2 has reached platform stability. This milestone means that the final APIs, system interfaces, and low-level behaviors are now locked in for the release. App developers can begin testing their applications against the new platform without worrying about unexpected changes in later beta builds. It also signals that Google is satisfied with the overall feature set and is moving into the final phase of bug fixing and polish.

Platform stability is particularly important for large updates like QPR2. Because the update includes changes to system components, connectivity, settings, and possibly user interface elements, developers need time to test compatibility before the stable release. Beta 4 provides that window. The fact that this milestone has been reached before the next beta suggests that Google is on track for a stable release in the coming months.

Pixel device support

Google's Pixel 11 went on retail sale last week, but it is not yet included in the QPR2 beta program. According to Google, support for the Pixel 11 is coming soon. Historically, Google has added new Pixel devices to beta programs shortly after their retail launch, and QPR2 should expand to include the new hardware in the near future.

For existing Pixel owners, the situation is mixed. The Pixel 6 and Pixel 6 Pro have been excluded from the QPR2 beta cycle. Google says these devices will be outside the software support window by the time the stable release is publicly available. Pixel 6a owners, however, remain supported for now, along with later generations such as the Pixel 7 series, Pixel 8 series, Pixel 9 series, Pixel 10 series, and the new Pixel 11.

Users with a supported device can join the Android Beta Program by visiting the official website and opting in. Once enrolled, the latest beta build will appear as an over-the-air update. Installing a beta build does require backing up important data, especially for users who plan to switch back to the stable channel later, as a full data wipe may be needed.

What is new in Android 17 QPR2 Beta 4?

Google's release notes for Beta 4 focus primarily on fixes rather than new features. This is typical for a beta late in the cycle, especially once platform stability has been declared. The company is focusing on eliminating bugs and addressing user-reported issues before the final rollout.

As with previous QPR2 releases, the update includes refinements to the system user interface, connectivity, and device behavior. It also lays the groundwork for the Pixel Feature Drop that will accompany the stable release. While the feature list for QPR2 has not been fully revealed, the beta program provides a glimpse into the future of Pixel software.

Detailed list of fixes

Google's release notes include a long list of fixes in Android 17 QPR2 Beta 4. Here are the notable improvements:

• Enabling the render apps below the cutout area developer setting caused a transparent status bar on the launcher after exiting fullscreen video playback. This is now fixed.
• A thermal management issue that caused devices to overheat and unexpectedly reboot during use has been addressed.
• An issue preventing screen mirroring to external USB-C XR glasses is now resolved.
• Gesture navigation became unresponsive when rendering apps below the display cutout; this bug is fixed.
• The 80% battery limit optimization caused excessive charge times during the final 2% threshold. Google has fixed this problem.
• A launcher UI issue where searching for apps in the app drawer failed to process text input is no longer present.
• Invoking the power menu via hardware buttons caused a missing background blur effect behind the navigation bar. This visual glitch is fixed.
• Phone call audio sometimes defaulted to the phone speaker instead of connected Bluetooth devices; Google says this is resolved.
• The Recents app switcher had a rendering bug where the first task card could intermittently freeze and visually clip behind other apps during horizontal scrolling. This has been fixed.
• An audio service resource lock triggered during screen recording prevented microphone usage across apps and input methods like Gboard and Gemini until a device restart. This is now fixed.
• A System UI visual inconsistency where turning off the screen from the home screen triggered a plain fade instead of the power-button screen-off animation is resolved.
• A low-contrast rendering issue in dark mode where the connected Wi-Fi settings cog icon was barely visible has been fixed.
• Enabling 3D mode on connected smart glasses resulted in a blank screen. This issue is now addressed.
• A User Interface issue prevented the notification bar from being pulled all the way down; Google has fixed this.
• WebGL applications could freeze or crash the browser process when combining shadow maps with vertex color attributes due to an invalid memory read in the PowerVR GPU driver's texture state processing. This crash is now fixed.
• Low-light Face Unlock failures bypassed Fingerprint Unlock and forced PIN entry. Google has corrected this behavior.

These fixes touch many areas of the Pixel experience, including display rendering, connectivity, audio, security, and the launcher. The wide range of corrections shows that Google is committed to delivering a polished release.

Background on this beta cycle

The Android 17 QPR2 beta program began earlier this summer, and Google has been releasing new builds every few weeks. The previous release, QPR2 Beta 3, arrived in early August. This latest Beta 4 comes exactly two weeks later, which is slightly faster than the average interval for some earlier builds, but Google has intentionally moved the schedule forward to get a stable release done before the end of the year.

Meanwhile, Android 17 QPR1 is nearing its own release. The September Feature Drop, which is based on QPR1, has already been tested through Beta 9 earlier this month. That means Pixel users may soon receive a stable update with new features and improvements. QPR2 will then follow a few months later, likely in December, with its own set of changes.

The distinction between QPR1 and QPR2 is important. QPR1 is the first quarterly platform release after the main Android 17 launch and typically accompanies the September or December Feature Drop on Pixel devices. QPR2 is the second quarterly release and often carries a larger set of improvements, preparing the ground for the next major Android version preview. For users, this means multiple feature drops per year, rather than waiting for a single annual upgrade.

How to install the beta

Pixel owners who want to try Android 17 QPR2 Beta 4 can enroll in the Android Beta Program. The program is available for most recent Pixel devices that are still supported. Once enrolled, the beta update will be delivered over the air. Users should be aware that beta software may contain bugs and that some features may not work as expected. It is recommended to install the beta on a secondary device if possible.

If you're already running a previous QPR2 beta, Beta 4 should appear as a normal OTA update. You do not need to wipe your device to install it. If you are switching from the stable channel to the beta channel, however, you may need to perform a factory reset in some cases. Google also provides images for manual installation if you prefer to flash the build yourself.

The Android Beta Program is a useful way to see what Google is working on and to provide feedback before the final release. Users who discover issues can report them through the official issue tracker. Google has addressed numerous user-reported problems in Beta 4, as shown in the release notes.

What remains before the stable release?

With platform stability reached, the next steps will likely include a couple more beta updates with additional bug fixes. Google may then release an RC build before the stable rollout. The final version of Android 17 QPR2 is expected to debut as the year-end Pixel Feature Drop. That update could bring new features to Pixel cameras, system UI, connectivity, and more.

For now, Pixel testers can enjoy the latest beta and explore the changes that come with platform stability. As always, Google encourages users to share their feedback so remaining issues can be found and fixed before the public release.

Source: Android Authority News