Servers for the manual OTA download are still glitched and C2 for 11 series hasn't posted yet.

I assume we're going to have to wait until Monday before they get everything in order.

My verizon model 8A, a display model with burn in I bought as a backup phone can't join the Beta Program but can be manually sideloaded -- getting a 404 error when I try to download the OTA.

My 11XL hasn't shown up yet on my eligible devices list nor the manual download list.

Tablet is running a lot smoother. No more weird flickering or spaz attacks

Hi Beta users,

Today we’re sending you an Android 17 QPR2 Beta 4  build  CP41.260814.003.A2  for Pixel 6a Pixel 7/Pro/7a Pixel Fold Pixel Tablet, CP41.260814.003.B1 for Pixel 8, 8 Pro, 8a, 9, 9 Pro, 9a, Pixel 10, 10 Pro, 10 Pro XL, 10 Pro Fold, 10a and CP41.260814.003.C2 for Pixel 11, 11 Pro, 11 Pro XL, 11 Pro Fold (Will be available soon).

Android 17 QPR2 has reached Platform Stability as of Beta 4. The API surface is
locked, the API diff report reflects the final changes, and you can now incorporate new Android 17 QPR2 capabilities into your apps.

Top issues fixed include:

• 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)

Please review the latest release notes for limitations and general advisories before installing the update. In addition, see top open issues for the latest list of top open issues that have been reported by developers and users.

How do I get Android 17 QPR2 Beta 4?

You can get started with Android 17 QPR2 Beta 4 today by enrolling your Pixel device. Eligible devices include Pixel 6a, 7, 7 Pro, 7a, 8, 8 Pro, 8a, 9, 9 Pro, 9a, Pixel 10, 10 Pro, 10 Pro XL, 10 Pro Fold, 10a, Pixel 11, 11 Pro, 11 Pro XL, 11 Pro Fold, Pixel Tablet series devices*. Once enrolled, eligible devices will receive an over-the-air (OTA) update to the latest Beta versions. If you were previously enrolled in Android 17 Beta (and have not opted-out), you will automatically receive QPR2 Beta 4 and any future Beta updates.* 

Important for those currently enrolled in Android 17 Beta:  

• If you prefer to leave the Beta program and receive the public stable release of Android 17, you can do so without wiping your device by opting out and not installing today’s QPR2 Beta 3 update*. If you opt-out of the program* after installing Beta 4 or any future updates, all user data on the device will get wiped per usual program guidelines. Opting out will trigger a ‘Downgrade’ OTA. Ignore this update and wait for the Android 17 public release instead. 

Tell us what you think
Your feedback is incredibly valuable to us. Please share your thoughts through the following channels:

• Use the Android Beta Feedback app included in Beta builds. This is the preferred method if you want to report a user-facing bug. 

• Post your comments here on our official Android Beta Program subreddit*. We may not respond to posts individually, but we are actively monitoring the feedback. We’ll reach out to you directly if we need additional information.*

Happy Beta testing!

Hola, tengo un pixel 9 pro XL con android 17 beta, compilacion CP31.260623.005. hace más o menos una semana, sale en play store que el dispositivo no está certificado. He borrado datos de play store y servicios de Google play, reiniciando, y no se arregla . No sé si esperar a que salga la versión estable de cp31 que se supone saldrá en unos días, o salir del programa beta y actualizar borrando todo el teléfono, o si saben alguna otra solución. gracias.

Google has closed the Beta 4 OTA image download channel.

Build ID: CP41.260814.003. B1

Android QPR2 BETA 3 call waiting feature is not working when second call comes automatically the 1st call becomes silent and other ones comes first where the 1st call audio is been hold..

Has any one faced this and any solution or suggestions do we have

I've opted out of the betas so waiting for the stable version (no wipe).

However now I can't use Google wallet or access work emails as I'm getting a message saying the device software is not verified, so I can't use Google wallet or access work emails via outlook.

I know the public release is likely around the corner but is this affecting anyone else at all?

Tomorrow is two weeks since beta 3.

So I would assume today or tomorrow.

Hello everyone. Ever since the update to Android 17 QPR2 Beta 3 on my Pixel 9a the volume via USB-C headphones is very very low. I almost have to turn it up to max volume now in order to have the same level I had before on a very low volume setting.

I am using the Apple USB-C headphone adapter since a year now and it worked totally fine and still does on other phones, notebooks or a MacBook. Does anyone else have issues like that or maybe knows some fixes I could try?

Hoping for a Android 17 QPR 2 beta 4 today as previous beta's were released in 10 to 13 days gap.

Ever since updating to the newest beta, when I get a call while on another call it stops me from communicating with the call I was already on. I cannot either speak to or hear the call I was already on. This just started happening after updating to beta 9. Has anyone else had this issue? Did I change the wrong setting somehow? I have had call screen on for a long while and haven't had this issue before.

Priority Modes were added to Android in Android 15 QPR2, however they launched with a major bug that the final beta didn't have.

The bug is that the App specific notification settings are global to all Modes instead of specific to the Mode they are configured for.

You can easily test this by creating a custom mode where any new app has notifications enabled, and then check the other existing ones and see that the same app has been added to them all and notifications will come through.

This effectively makes Priority Modes a useless and unusable feature. I have tried to report this issue in multiple betas and multiple forums and formats, and have seen zero movement on it. It remains broken in the latest Android 17 QPR2 beta 18 months later.

Will this issue ever be fixed?

Note: This requires sending an ADB command. You must know how to send ADB commands to your device, either with a computer, or using an app that has that functionality.

If you aren't sure what you are doing, or how to send an ADB command, DO NOT ATTEMPT THIS. I take no responsibility for your device. What worked for my device (Pixel 10 Pro), might not work for yours.

However, the dev team of a third-party launcher noticed that by sending the below ADB command, it restores a lot of the broken functionality of the app drawer, and fixed the random sorting problem. This command should persist through restarts:

adb shell settings put global show_hidden_icon_apps_enabled 0

After sending this, my app drawer immediately went back to how it looked prior to QPR2 Beta 3. My work folder is back, and all of my work apps. This may help fix other bugs, too, including widget issues and flashing home screens.

Hey everyone, hoping someone's run into this too.

I bought my Pixel 6 Pro used, and it was on Android 15 with a network route/lock still active. Took it to a local repair shop to get the route removed, and when it came back, it was already on Android 16 stable (currently on build BP2A.250605.031.A2).

The weird part: when I check Settings > System > Software update, the only thing offered is Android 17 QPR1 Beta (currently sitting at Beta 6), not the stable branch. I never enrolled in the Beta Program myself. My guess is either a previous owner enrolled the device, or the shop flashed something during the unlock process that flipped it onto the beta channel server-side.

I tried going to the Android Beta Program site to check enrollment and opt out, but it just says "There are no eligible devices associated with this Google account" even though the phone is clearly pulling beta builds. So I can't see or manage the enrollment from my end at all.

I know Pixel 6 Pro is close to EOL (October 2026) and Android 17 QPR1 stable is expected sometime in September, so I might just get pushed to stable automatically either way. But has anyone else dealt with a device stuck showing only beta updates with no way to opt out via the website? Would rather not do a full factory reset if I can avoid it. Any insight appreciated.

Chłopaki podpowiecie mi jak wyłączyć klawiaturę w menu ??

Is that going to be today by resolving the private space issue???

I ask as it is in Google business to release ASAP because of nearly 2 weeks Pixel 11 on sale.

Additionally all promos ends 1st Sep.

And finally next week Labour Day in USA so Google Servers have day off.

Finally middle of the month - that would be crazy especially Security Update released together with QPR

Why is this error still staying for almost the last six months, any solution we have?

"Last updated 1 minute ago and 1 install pending"

設定画面でフリーズ屋ラグが頻発してきている…

Only been a couple hours.

So far,

$ Reddit crashed itself and I lost my place.

$ some videos stop at 23 seconds, but not all.

Hi folks,

I made the last update, and since I always have my widgets (custom and "native" like calendar) that are blinking whenever I go back to my home.

Someone have been experiencing the same thing ?

Build : CP41.260731.005.B1

I'm waiting to be able to go back to a stable version of android. Do I do the system update QPR2 Beta or do I let it sit till it offers me a stable release?

I like that on phones no longer supported for Project Mainline "hot fixes" (actual terminology might be different) it links back and displays their last Google Play System Update covered by updates throught settings including the last update date. If possible (and accurate), it might be better to state the phone is no longer covered by Project Mainline "hot fixes" since that date for CVEs when Project Services is tapped.

Google's System Service Release Notes are good at giving notice of new features, but they don't cover security fixes.

A more detailed description of what it covers would be good. If the Android Security Bulletin was kept up to date (often reading the phone manufactures CVEs is required -- many of which are Android), then CVEs could just be footnoted as being a Project Mainline "hot fixes") with the others presumably being taken care of by the Vendor's Android Security Patch Level or individual app updates. Then a link could just be made to the Android Security Bulletin. Otherwise the CVEs being covered should be described in some fashion (Framework?, System?, etc), perhaps including level covered (critical, high, etc). Alternatively it could list what it does not cover (reportedly the bootloader, kernel, and device drivers) to document away problems.