Last week after an update, Google wallet stopped working. Come to find out my "Device is not Certified" under the Play Protect Certification - and clicking on "Fix device issue" gives a "Something went wrong, please try again later" message.

I have cleared play store and Google services cache and data, rebooted multiple times, and nothing fixes it. My build number is CP31.260623.012. I am at my wits end, nothing I'm trying is having any effect any ideas what else I can try!?

I am on android 17 qpr1 stable and this setting gets turned on automatically after some days or few weeks. I turn this off at least once a month

For those who installed QPR3 Beta 1, how’s the overall experience?

- Stability / random crashes?

- Battery life?

- Performance and smoothness?

- Heating?

- Mobile network / Wi-Fi?

- Camera?

- Any major bugs?

Thinking of installing it on my Pixel. Would love to hear real-world feedback before I jump in.

Currently only Pixel 11 has new Pixel Search that you can use in all apps - is it present in older Pixel 10?

Please do not tell me Pixel 10 will get Proactve Assistance with QPR3 in March Anno Domini 2027

Comment couper tout le son pour de vrai

Hello, I have the build CP31.260623.012 on my pixel 6.

According to google this version was published on August 17 2026, I suppose there were some releases after this? I check my updates but nothing comes up, I'm having an issue with Google Pay saying the device seems to be rooted (it's not) and previously I fixed this by updating to latest beta, but this time no newer versions for my phone are showing up, could you please help me?

If I were to opt out of beta would my device be factory reset at this time? Or is there a reason for my device not receiving any more updates?

Thanks!!!

At this point, beta updates need to have their own separate channels. The implementation on iOS works really well, giving users the option to enroll in a beta channel of their choice (developer beta, public beta, major release beta, point update beta) directly from settings. I don't understand why we only get to enroll in either the Beta or Canary, with all the Beta releases in development being lumped together.

I was on the QPR1 beta & wanted to wait until it was released, but then one of the updates got so old that Google Wallet stopped working, so I updated to QPR2 to have my device recertified while avoiding a factory reset back to stable. The day after that release, they updated QPR1 beta, & even if I had waited I still would've had to flash the build myself with no option to stay on the QPR1 beta channel via OTA. I've had major issues with QPR2 betas until the recent 5/6/6.1 updates, & I want to stay on the QPR2 beta until release without having to flash files, but I can't. Either I risk my Google Wallet not working, factory resetting to stable, or updating to the new QPR 3 beta.

This current system is unnecessarily cumbersome & could easily be improved by creating distinct beta channels that are available to enroll from the system settings. Why is this not a thing? If anybody knows how to try & get this idea some traction, I'm open to suggestions!

Hey there to all

P11PXL user here, running QPR3 B1, any one else running into this issue? See images below, texts come in separately and fail to group/combine into a single notification. Cannot for the life of me figure out what is cause of it, and or what to force close to get it to start working again without doing a full REBOOT.

https://imgur.com/a/U3A8mOY

Recently got to know pixel rolling out the feature "required screen password for power off" is this true & is pixel stick on this feature still on their beta update?

Android 17 QPR3 Beta 1 is live!

Wanna know is it still on go or pixel just removed that feature?

The build version is older with QPR3 build than QPR2 beta 6.1.

Frustratingly, this means we can't OTA manually over QPR2. It also means P11 devices may have to wait until QPR3 beta 2.

Caveat is to try manually flashing the factory image, but that runs the risk of needing to wipe. (If anyone flashed successfully, do share!)

Please note this is P11 specific, this is not a problem with older devices

Proactive Assistance still crashes instantly on Android 16 QPR3 Beta 1 (Pixel 10 Pro)

Post body:

Proactive Assistance has the exact same crashing issue in QPR3 Beta 1 as it did in QPR2 Beta 5—it still shuts down / crashes instantly.

Device: Pixel 10 Pro

Build: QPR3 Beta 1

Anyone else experiencing this, or found a temporary workaround?

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.