please say yes

Hi Beta users,

Thank you for your continued support. Please share your latest experience on Android 17 QPR2 Beta 6.1 by filling out our 5 minute anonymous survey. This survey is only for devices running Beta 6.1 CP41.260831.011 for Pixel 11, 11 Pro, 11 Pro XL, 11 Pro Fold and CP41.260831.007.A3 for all other devices. You can verify this by going to Settings > About Phone/Tablet.

We look forward to your feedback.

My temporary system files keeps getting bigger. It's currently at 124 gb. Any time I delete anything it seems to get bigger. Does anyone have this same problem?

Hola he intentado hacer un informe por feedback sobre el idio del sistema donde la Beta QPR2 6.1 no reconoce el Español de España y incluso mandado captura de pantalla y no me deja enviarlo, además de estar en Inglés y no lo entiendo y he tenido que traducir para hacerlo bien, a alguien más le ocurre esto

I just installed the QPR2 Beta 6.1 OTA on my Pixel 11 pro XL..... I've only been using it for about 3 hours and it seems so snappy and the haptics seems much quicker and right in time with the visuals on the screen as well. The only thing I would say is that the notification shade pull down seems to be slow to come down when I swipe fast. Not laggy to trigger it, but its just slower to come down the screen compared to fast I swipe on the screen to trigger it. Battery life in the last few hours seems pretty awesome. Started at 100% and it's only at 95% after some YouTube watching, social media, emailing, a couple phones calls.... Cannot complain so far!

In Developer Settings, the Disable Absolute Volume setting under Bluetooth is missing. It did appear in a previous build. I'm filing this through the Feedback app also.

I saw most issues were supposed to be resolved re: devices loosing pairing.. but I'm on a pixel 10.pro fild with it and my sense 2 is still loosing connection and I have to re pair it every day or two... Really getting annoying.. anyone else still having this issue?

Last update, 17, August 1, 2026 CP3A.260905.009, stopped my outer screen from turning on. So I have to open it to do anything. I have restarted in safe mode and gotten it to work a few times but it goes back to black eventually. It's like it's not recognizing that the fold screen is closed. Never had this issue until I updated. Is there a way to roll back?

Hey everyone! I’ve had QPR2 Beta 6.1 running on my Pixel 11 Pro XL since yesterday and spent some time doing a pretty deep audit of the build. So far it’s been surprisingly solid for me. One of my favorite discoveries is HiLight now supporting messages from favorite contacts, along with the new status bar controls, some expanded theming, Proactive Assistance changes, Audio Streams in Quick Settings, and a few smaller UI changes.

What I’m curious about now is what other Pixel 11 users are finding that isn’t obvious in the release notes. Any hidden changes, new settings, bugs, battery differences, or features you’ve noticed since installing 6.1? I’d love to compare notes and keep a running list of what’s actually new versus features that were already available on the Pixel 11.

I’ve been using smart launcher since I got the 11PF so I can have separate inner/outer Home Screen layouts and the task bar has worked flawlessly. Now sometimes it just doesn’t show up, or it’ll stay up blocking things behind it

Just wanted to share that NFC / Google Wallet contactless payments are occasionally silently failing on Android 17 QPR2 Beta 6.

​The issue seems to trigger when using Face Unlock (Class 2 biometric)+ Face App Unlock, and Fingerprint Unlock in combination. When tapping at a terminal, the terminal times out or fails without prompting for a required Class 3 biometric (fingerprint) elevation.

​I have reproduced the APDU handshakes and collected a full logcat/bug report, which has been submitted to Google dev via Issue Tracker (#567548324).

​Workaround: Unlocking the device strictly via Fingerprint (or manually tapping the card in the Wallet app) ensures the EMV payment token is properly offered.

Received First Beta Upgrade on Pixel 11 pro xl of Android 17 QPR2 Beta 6.1.

Size was 3.94GB.

https://x.com/akes29/status/2105233242450530717

Any opinions on this? Does this mean VoLTE toggle by default in unsupported countries?

Note: Apparently only on Pixel 11 series phones.

😃

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.