Android 17 QPR2 Beta 4 has arrived for your Pixel phone

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.

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.

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. 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.

With this release, Google says that QPR2 Beta 4 has reached platform stability. Here’s what Google shares is fixed:

• 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)
• A thermal management issue that caused devices to overheat and unexpectedly reboot during use. (Issue #437116407)
• An issue preventing screen mirroring to external USB-C XR glasses. (Issue #439269938)
• Gesture navigation became unresponsive when rendering apps below the display cutout. (Issue #441378954)
• The 80% battery limit optimization caused excessive charge times during the final 2% threshold. (Issue #477009501, Issue #476803337)
• 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)
• An issue where phone call audio defaulted to the phone speaker instead of connected Bluetooth devices. (Issue #537908014, Issue #541501134, Issue #541772860, Issue #545047074)
• 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)
• 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)
• 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)
• Enabling 3D mode on connected smart glasses resulted in a blank screen. (Issue #536628506)
• 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)
• 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)

We’ll also be diving in to hopefully spot any new features. If you manage to find any additional changes yourself, give us a shot down in the comments with your discovery.

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.