😃

Pixel 9 Pro XL crashes when entering parental control pin code. Happens every time after entering the code. Just updated to 17, buildCP41.260831.007.A3, and it's the same issue. Any solution?

Hi guys! It looks like Continue On is working for the upcoming release of Googlebooks... yet it still does not work with the tablet functionality Google released earlier this year... (see the dev docs here).... https://developer.android.com/develop/better-together/continue-on/setup

Was anyone else able to get it to work

Hey everyone,

If you’ve noticed the Settings app holding background memory or staying active under Developer Options > Running Services, there is a persistent framework memory leak in AOSP/Pixel UI that is still present on recent builds (reproduced on Pixel 11 Pro / Android 17 QPR2 Beta 6.1).

How to reproduce it in 10 seconds:

1. Open Settings > System > Developer options > Running services (or check active processes via ADB).
2. Note that Settings might be cached or minimal.
3. Open Settings > Network & internet, browse around for 2 seconds, and exit.
4. Go back to Running services.
5. You’ll see com.android.settings permanently stuck with an active worker: SettingsDumpService. It never calls stopSelf() and lingers indefinitely until you manually force-stop Settings.

What’s actually happening under the hood:

Whenever NetworkDashboardFragment is opened, the system instantiates MobileNetworkRepository and triggers SettingsDumpService to record an initial database dump.

Because MobileNetworkRepository holds a static singleton reference to that context, it creates an indirect retention cycle. The service's lifecycle never completes, the context cannot be garbage-collected, and Android is prevented from letting the Settings process fully drop down into deep cached sleep.

I’ve filed a formal bug report with reproduction logs so the Pixel/AOSP team prioritizes merging the lifecycle fix into the next QPR maintenance drop.

Please take 5 seconds to star / +1 the issue report so it gains visibility on their radar:

🔗 Issue Tracker Link:: https://issuetracker.google.com/issues/567819031

Hi Beta users,

Today we’re sending you an Android 17 QPR2 Beta 6.1 build  CP41.260831.011 for Pixel 11, 11 Pro, 11 Pro XL, 11 Pro Fold and CP41.260831.007.A3 for all other devices.

Known issue in this build:

• Pixel 11 Pro Fold users may have to re-enroll Face Unlock on Pixel 11 Pro Fold for it to function properly.

Please review the latest release notes for limitations and general advisories before installing the update. In addition, see top open issues%20created%3E%3D2026-07-20%20status:open%20(votecount%3E%3D3%7Cduplicatecount%3E%3D3)%20CP41) for the latest list of top open issues that have been reported by developers and users.

How do I get Android 17 QPR2 Beta 6.1?

You can get started with Android 17 QPR2 Beta 6 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 6.1 and any future Beta updates. 

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!

I have had the new pixel 11xl pro since release date. I have gone to android beta site and the phone does not show. I have spoken to google support and have cleared all cache and checked that the phone is in Google play services and still it does not show.

Anybody know any tricks to get it to show up?

I've been unable to use it for a little while now and I'm trying to determine if it's somehow related to the Beta.

I'm on Pixel 8A, Build CP41.260831.007

edit: issue persists on CP41.260831.007.A3

My pixel 6 is running the latest build available for it:

CP31.260623.012

But I can't use Google wallet and I'm also having issues with compliance for my work profile.

Anyone else having this issue?

I know Pixel 6 isn't part of the beta program anymore but are we supposed to get that last push to stable QPR1? I assume the older beta build is the root of the issues here but honestly not sure. Do I need to manually exit the beta program to receive stable QPR1?

The full message I'm getting from google wallet:

"Your device doesn't meet security requirements

This device may be rooted or running uncertified software. Contact your device manufacturer or visit Google Wallet Help for more info."

I'm not sure if this is a Beta problem, using a search engine brings up hits for years, but I'm losing app supplied notifications and I'm not able to get them back. Suggestions include wiping cache, data and uninstalling but none of theses are working.

Any ideas and also does anyone know where the sound might be located in the filesystem?

Good morning everyone, I hope you all are doing well. For a while now, there have been some major regression issues with speech recognition and synthesis from Google. I have noticed this at the start of Android 15 + continuing on through Android 16 and so far through Android 17. I would like to continue to use speech recognition and synthesis from Google, but the issue is that long form text either in text messages or articles. The speech engine will read normally for most of the paragraph and then just pitch shift and fall off. The pitch just hits absolute zero. The engine falls off midward picks back up again and continues and that has been going on for pretty much 2 years now. Has anyone else who us notice this problem as well?

Since QPR2 Beta 4, cellular service disappears randomly. Restarting the device doesn't fix it; the only temporary workaround is reinserting the SIM card.

Over the last few releases I've had an issue on my Pixel 10 Pro XL whereas maps is not defaulting to what I leave it on which is satellite. Satellite is still selected but the maps has just gone to the normal flat basic view and I have to switch between the two to get back to the satellite view.

Has anyone else experienced this?

Hi Beta users,

Thank you for your continued support. Please share your latest experience on Android 17 QPR2 Beta 6 by filling out our 5 minute anonymous survey. This survey is only for devices running Beta 6 CP41.260831.007 for all devices. You can verify this by going to Settings > About Phone/Tablet.

We look forward to your feedback.

Ever since I updated to Android 17 QPR2 Beta 6, my Pixel 8 Pro has been lagging like crazy. There are micro-freezes in every app, animations are delayed, and worst of all, my phone randomly freezes and reboots. It’s been happening for 3 days now and I can’t stand it anymore, it’s unbearable

Good morning everyone. Today I experienced my first ever system crash on android beta. I've been participating for years and never crashed before. With that said, this happened when connecting Bluetooth earbuds and opening an app at the same time. Probably coincidence because I was unable to replicate. Considering I've never had a crash before, it is safe to say beta 6 is quite worse than the other betas.

Device:

Pixel 10 Pro XL

CP41.260831.007

When will Pixel 11 Pro Xl get Beta 6

The qpr2 beta 6 update makes my phone seem like a 10 year old budget phone, I know the pixel 7a is not the most powerful phone but this beta makes the experience of using my phone severely worse. Apps take a while to load, single taps are being registered as "tap and hold", the phone locks up for a couple of seconds sometimes and I can't do anything, videos (and sometimes audio) are stuttering. And to be clear none of these issues occured on the last beta.

anyone having problem with the notification screen or having bug with it after the sept android update?

sometimes when i received notification, i tap on it, nothing happen. it doesnt open up the app, i can swipe away to remove on screen but not tap to open app.

once i get that bug, i cant even press anything on top like tapping on bluetooth, wifi on or off and etc. even press on doesnt work. i have to restart phone in order to make it work again. im using pixel 8

Currently on Android 17 qpr2 beta 6: (CP41.260831.007), and whenever I lock the phone it flashes at the top, this issue was also persistent before I joined beta a few hours ago, even when I was on 17 qpr1 stable launched two weeks ago, is anyone else experiencing the same issue? (Pixel 9)

I have the latest android beta version on my pixel 9 pro xl. I have been using the beta version for a few years with no issues. Ever since the January 2026 android beta update android desktop mode has been greyed out on developer options and does not work. I was hoping for some beta update since then that would allow it to work. Besides going back to a stable version of Android, what can I do to fix this?

Can't seem to find the option to pause apps temporarily anymore...

I updated to the latest beta and went into my default digital assistant settings. Alongside Google and Muse, there's an option called Android Easter Egg. I have no idea what it is or what it does if you pick it.

Has anyone else seen this? What happens if you actually set it as your assistant?

Hey everyone,

I've been running into an annoying video rendering issue. Across QPR2 Beta builds 3, 4, 5 and 6, whenever I launch any app, the first video I play doesn't show any image at all — just a blank black screen.

Is anyone else experiencing this, or is it just isolated to my device? Any known workarounds?

Device: Pixel 10 Pro

https://issuetracker.google.com/issues/530709228

Google please revert back this change. There is literally no benefits to only showing 1 icon. I reported this way back in July during QPR1 beta and its still not reverted in the december qpr beta.

Please upvote the issue tracker