Google has begun pushing out Android 17 QPR2 Beta 4 to Pixel smartphone and tablet owners enrolled in the Android Beta Program. The release arrives two weeks after QPR2 Beta 3, following the company's typical cadence and giving testers a fresh batch of fixes to evaluate as the year-end Feature Drop draws closer.

A familiar rhythm for Pixel beta releases

QPR2 builds are part of Google's quarterly platform maintenance cycle, separate from the main Android version updates. While the Android 17 QPR1 release is currently being polished ahead of its September Feature Drop, QPR2 is being developed as the larger year-end update, expected to arrive in December. With the release of Beta 4, Google says the software has now reached platform stability, meaning the APIs and app-facing behaviors are locked in, and developers can finalize their apps against the upcoming OS version.

The new builds are identified as CP41.260814.003.A2 and CP41.260814.003.B1, with the exact build depending on the hardware. As usual with beta releases, users can expect a mix of improvements and potential lingering bugs, but this build is focused on ironing out issues discovered in earlier testing.

Device support changes

One important change in this beta is the continued exclusion of the Pixel 6 and Pixel 6 Pro. Those devices are outside Google's software update window, and by the time the QPR2 Feature Drop reaches its stable release, they will no longer be eligible for new feature drops. This is a natural progression as Google shifts its support focus to newer hardware.

Interestingly, the Pixel 11, which went on sale last week, has not yet received QPR2 Beta 4, but Google has indicated that compatibility is coming soon. Pixel testers with the Pixel 11 will need to wait a little longer before they can join this particular beta cycle.

Platform stability and what it means

For developers, platform stability is a significant milestone. It signals that the APIs, system behaviors, and app-facing changes are final and unlikely to be altered in future beta releases. This means app developers can update their applications with confidence that they will work with the final version of Android 17 QPR2.

For regular users, the platform stability designation also suggests that the beta is approaching a state close to what will ship to the general public. While there may still be minor fixes and adjustments in subsequent releases, the core experience should now feel largely complete.

Bug fixes and improvements in QPR2 Beta 4

This beta includes a substantial list of fixes, covering a wide range of issues reported by testers over the past few weeks. Some of the notable corrections include:

• Fixing a transparent status bar on the launcher after exiting fullscreen video playback, which occurred when the developer setting for rendering apps below the cutout area was enabled.
• Resolving a thermal management issue that caused devices to overheat and reboot unexpectedly during extended use.
• Correcting an issue that prevented screen mirroring to external USB-C XR glasses.
• Addressing a problem where gesture navigation became unresponsive when apps were rendered below the display cutout.
• Improving the 80% battery limit optimization, which previously caused excessive charge times as the battery approached the final 2% threshold.
• Fixing a launcher UI issue that prevented the app drawer from processing text input when searching for apps.
• Restoring the background blur effect behind the navigation bar when invoking the power menu via hardware buttons.
• Ensuring phone call audio routes correctly to connected Bluetooth devices, instead of defaulting to the phone speaker.
• Addressing a Recents app switcher rendering bug where the first task card could freeze and clip behind other apps during horizontal scrolling.
• Resolving an audio service resource lock triggered during screen recording that stopped microphone access systemwide until a restart.
• Adding the proper power-button screen-off animation when turning off the screen from the home screen, instead of a plain fade.
• Improving the contrast of the connected Wi-Fi settings cog icon in dark mode.
• Fixing a blank screen issue when enabling 3D mode on connected smart glasses.
• Correcting a UI issue that prevented the notification bar from being fully pulled down.
• Resolving a WebGL crash that occurred when combining shadow maps with vertex color attributes, caused by an invalid memory read in the PowerVR GPU driver's texture state processing.
• Fixing a low-light Face Unlock failure that bypassed Fingerprint Unlock and forced users to enter their PIN.

These fixes address both usability and performance concerns, and many of them stem from feedback submitted by beta testers. Google encourages users who encounter bugs to continue reporting them through the official channels, as each report helps refine the final release.

Potential hidden changes

As with past QPR2 updates, there may be subtle visual tweaks, performance improvements, or battery optimizations that are not listed in the official changelog. Beta testers who discover any new features or settings are encouraged to share their findings in community forums, as this often helps surface useful information to the broader user base.

Given that this is the fourth beta in the QPR2 cycle, it is possible that Google is nearing the end of its beta testing phase. However, the company has not confirmed when a Beta 5 might arrive, or when the stable version will be released. Based on previous release patterns, a final QPR2 build could land in December, but that timeline is speculative at this point.

How to get Android 17 QPR2 Beta 4

Pixel users interested in trying out the latest beta can do so by enrolling their device in the Android Beta Program. Once enrolled, the update will be delivered over-the-air, just like a standard system update. It is worth noting that beta software can be unstable, so users should back up their important data before installing it on a primary or daily-driver device.

Users who are already enrolled in the beta program will receive the QPR2 Beta 4 update automatically, assuming their device is still supported. Those who are not yet enrolled can visit the Android Beta Program website and follow the instructions for their specific Pixel model.

For those who prefer to wait for a more polished experience, the stable release of Android 17 QPR2 is expected to arrive as part of the December Feature Drop. That version will bring all the features and improvements tested in the QPR2 beta cycle to all supported Pixel devices.

As always, the beta release is a reflection of Google's ongoing effort to refine Android and deliver a more seamless experience across its hardware ecosystem. With platform stability now achieved, the next steps will likely involve additional bug-fixing and performance tuning ahead of the final release.

Source: Android Authority News