With August nearly behind us, Google's September Feature Drop could be nearly ready to arrive any day now. That's the software the company's been testing as Android 17 QPR1, which hit its Beta 9 release earlier this month. But that's not all that Google's been cooking up, and we've also been following work on what's likely to be our big year-end update, in development now as QPR2. It's been two weeks since QPR2 Beta 3 landed, and today Android 17 QPR2 Beta 4 is arriving right on schedule.

What is a QPR and why does it matter?

For those unfamiliar with Google's release cadence, QPR stands for Quarterly Platform Release. These are incremental software updates that Google rolls out between major Android versions, typically bundled into the company's Feature Drops for Pixel devices. While a major Android version like Android 16 or Android 17 introduces platform-wide changes, QPRs bring polish, bug fixes, and occasionally small new features that didn't make the initial cut. They are tested through a public beta program that runs concurrently with the stable channel, allowing enthusiasts and developers to try out upcoming improvements before they reach the general public.

The QPR2 cycle is particularly important because it usually culminates in the first major Feature Drop of the following year. For example, Android 17 QPR2 is expected to become the stable December 2026 Feature Drop, which will include all the fixes and refinements that Google has been testing over the past couple of months. The beta program gives users an early look at these changes while helping Google identify and resolve issues before the stable rollout.

Android 17 QPR2 Beta 4: What's new

Google shares that Android 17 QPR2 Beta 4 is arriving today for Pixel testers, either as build CP41.260814.003.A2, or CP41.260814.003.B1, depending on your hardware. The two build variants account for differences across Pixel models, though the feature set and fixes are identical. This release lands precisely two weeks after QPR2 Beta 3, following a biweekly release schedule that Google has maintained throughout the QPR2 testing cycle.

Despite the Pixel 11 hitting retail availability last week, so far Google hasn't released QPR2 for it, but the company says it should be available soon. This is a slight departure from previous years, where the latest Pixel model was often included in the beta from the start. However, given that the Pixel 11 only just went on sale, it's reasonable that Google needed a little extra time to prepare the beta build for its newest hardware. We'll likely see Pixel 11 support added in a subsequent beta release, or perhaps in the stable rollout if the timing aligns.

Pixel 6 and Pixel 6 Pro support ends

Like previous QPR2 versions, the Pixel 6 and Pixel 6 Pro aren't supported, as they'll be outside Google's software window by the time this Feature Drop has its stable release. The Pixel 6 series launched in late 2021 with a promise of three major Android updates and five years of security patches. That means Android 16 was the last major version for these devices, and the December 2026 Feature Drop will mark the end of their security patch eligibility as well. While it's always a bit sad to see older hardware get left behind, it's a natural part of the Android lifecycle, and users of the Pixel 6 and 6 Pro can still enjoy the stable versions of Android 17 that were released earlier this year.

The Pixel 6a, which launched later, is still supported and can participate in the QPR2 beta. The Pixel 7 series and newer devices remain eligible, so the beta is still accessible to a wide range of users. If you're unsure whether your device is supported, Google's Android Beta Program page provides a list of compatible hardware.

Platform stability achieved

With this release, Google says that QPR2 Beta 4 has reached platform stability. This is a critical milestone in the beta development process. Platform stability means that all app-facing APIs and system behaviours are final, and developers can begin building and testing their apps against the upcoming release without worrying about significant changes. For users, it also signals that the software is feature-complete and Google is now focusing almost entirely on bug fixes and performance improvements leading up to the stable launch.

Achieving platform stability at Beta 4 is a bit earlier than in some previous QPR cycles, which suggests that Google is confident in the current state of the software. It also gives developers more time to optimize their apps for the new features and ensure compatibility before the stable release reaches consumers. If you're a developer, now is the time to test your apps on QPR2 Beta 4 and file any issues you encounter.

What's fixed in QPR2 Beta 4

As with most beta releases, QPR2 Beta 4 includes a long list of bug fixes that address a variety of issues reported by testers and discovered internally. Some of these are minor visual glitches, while others are more serious problems that could affect daily usability. Here's a closer look at what Google has fixed in this release.

Display and user interface fixes

• Enabling the "render apps below the cutout area" developer setting caused a transparent status bar on the launcher after exiting fullscreen video playback. (Issue 295747911)
• Gesture navigation became unresponsive when rendering apps below the display cutout. (Issue 441378954)
• A launcher UI issue where searching for apps in the app drawer failed to process text input. (Issue 505157934, Issue 527921034, Issue 530531588, Issue 537704656)
• Invoking the power menu via hardware buttons caused a missing background blur effect behind the navigation bar. (Issue 537202501)
• A Recents app switcher rendering bug where the first task card could intermittently freeze and visually clip behind other apps during horizontal scrolling. (Issue 530484511, Issue 505564040, Issue 545574713, Issue 551022006)
• 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. (Issue 541261786)
• A low-contrast rendering issue in dark mode where the connected Wi-Fi settings cog icon was barely visible. (Issue 536320341)
• A User Interface issue that prevented the notification bar from being pulled all the way down. (Issue 539244095, Issue 547801203, Issue 547017781, Issue 546896889, Issue 547163658, Issue 547281675)

Connectivity and media fixes

• An issue preventing screen mirroring to external USB-C XR glasses. (Issue 439269938)
• Enabling 3D mode on connected smart glasses resulted in a blank screen. (Issue 536628506)
• An issue where phone call audio defaulted to the phone speaker instead of connected Bluetooth devices. (Issue 537908014, Issue 541501134, Issue 541772860, Issue 545047074)

Performance and system fixes

• A thermal management issue that caused devices to overheat and unexpectedly reboot during use. (Issue 437116407)
• The 80% battery limit optimization caused excessive charge times during the final 2% threshold. (Issue 477009501, Issue 476803337)
• An audio service resource lock triggered during screen recording that prevented microphone usage across apps and input methods like Gboard and Gemini until a device restart. (Issue 538229807)
• An issue where WebGL applications could freeze or crash the browser process when combining shadow maps with vertex color attributes by resolving an invalid memory read in the PowerVR GPU driver's texture state processing. (Issue 541322087)
• Low-light Face Unlock failures bypassed Fingerprint Unlock and forced PIN entry. (Issue 547597971, Issue 545329611, Issue 541723970)

These fixes address some long-standing annoyances, particularly the Bluetooth audio routing issue and the notification bar pull-down problem. The WebGL crash fix is also notable for users who rely on browser-based games or complex web graphics, as it resolves a potential crash caused by a driver-level memory read error. And the Face Unlock fix should make it easier to get into your phone in low-light conditions without having to fumble with your PIN.

How to install the beta

If you're a Pixel owner who's interested in trying out Google's latest in-development software, you can go ahead and register your device with the Android Beta Program to get started testing releases like today's. The process is straightforward:

1. Visit the Android Beta Program website on your Pixel device or computer.
2. Sign in with the same Google account you use on your Pixel.
3. Find your device in the list of eligible phones and tap "Enroll."
4. Accept the terms and conditions, and the beta update will be delivered over-the-air to your device, usually within 24 hours.

Once enrolled, you'll receive all subsequent beta updates automatically until you opt out. If you decide to leave the beta program, you can unenroll, but note that leaving will trigger a full data wipe on your device as it rolls back to the stable version of Android. As with any beta, there's always a risk of bugs and instability, so it's best to install it on a secondary device if you have one, or make sure you back up your important data before enrolling.

What to look for next

With QPR2 Beta 4 now out, Google will likely release one or two more betas before the stable rollout in December. The next beta could arrive in early September, and Google may use that release to address any remaining issues and perhaps introduce a few final optimizations. Meanwhile, QPR1 is still in its later beta stages and should go stable as the September Feature Drop in just a few weeks. Pixel users have a busy few months ahead with two feature drops on the horizon, and both are shaping up to be worthwhile updates.

We'll also be diving into QPR2 Beta 4 to hopefully spot any new features that weren't mentioned in the official release notes. If you manage to find any additional changes yourself, give us a shot down in the comments with your discovery. In the meantime, if you're running the beta, let us know how it's performing on your device. We're particularly interested in whether the thermal management fix resolves the overheating issues that some users reported in earlier builds, and whether the Bluetooth audio routing is now working seamlessly with your headphones and car systems.

Google's beta program continues to be one of the best ways for enthusiasts to get a taste of what's coming to their Pixel devices, and QPR2 Beta 4 is a solid step toward the year-end Feature Drop. With platform stability now locked in, the focus shifts to final polishing, and we're optimistic that the stable release will bring a smooth and refined experience to all supported Pixel phones.

Source: Android Authority News