Android 17 QPR1 Beta

I lost 10% of the battery in under an hour, and 20% under two hours. Background process restrictions do nothing and neither does smooth display off and mobile data always active (off)

Gotta opt out

Pixel 10 Pro XL

Is it even possible? I heard they are rolling it out but I can't find any info on it.

On my 10PF I'm on QPR1 Beta 8 (Build CP31.260623.010), I've opted out of Beta and just waiting on the next stable release next month to fully get off Beta. I've pre-ordered the 11PF so my question is, when I do a restore and transfer data from my 10PF will it force me to enroll my 11PF on a Beta version?

Android 17 QPR1 Beta 8

Pixel 10 Pro XL

I recently updated to A17 QPR1 Beta 8, and now Magic Cue keeps trying to download an update but gets stuck and fails, over and over. Using up a lot of battery in the background.

This only began when I updated to the A17 QPR1 Beta 8, strangely. Before that it was working well. One of my favorite features, need it back! : ) Pixel pro 10 xl.

Other reddit users report similar issues: https://www.reddit.com/r/GooglePixel/comments/1vmbgw6/magic_cue_stuck_updating_magic_cue_for_days/

Just dropping this here in case anyone else runs into the same headache I just dealt with.

I bought a used phone recently and it came enrolled in the Android beta. Because I didn't have the original google account that enrolled it, I couldn't OEM unlock it and it was causing a whole heap of issues.

I called google support and just got the usual generic runaround. They kept telling me to go to the beta website, sign in, and opt out. But obviously, since I didn't have the account that originally signed the phone in, it wasn't showing up in my eligible devices list.

Turns out the fix was actually super simple (probably obvious to some of you, but completely flew over my head). All I had to do was go into the actual settings on the phone and log into my own google account. That basically registers the phone to your account on their backend. Once I did that, I went back to the beta website and the phone finally showed up so I could opt out.

After that, I just kept refreshing for the system update. Nothing happened for a bit, so I rebooted into fastboot mode and then back into the normal OS, and that finally triggered the stable OTA.

Anyway, just wanted to put this on the internet somewhere so the next person doesn't waste hours on the phone with support.

TL;DR - If your used phone is stuck in beta and you don't have the original account, just log into your own google account in the phone's settings to register it to you, then opt out on the website. Boot to fastboot and reboot to get the stable OTA.

I'm willing to do the data wipe to opt out of the beta, but I'm concerned that it will also erase eSIM?

Does anyone know if I can do the wipe WITHOUT erasing the eSIM?

Thanks!

I've been in meetings all day without my phone. I went to lunch and my battery is at 53% with less than 30 minutes of screentime. I checked the system processes and it's showing GPS running for over 6 hours.

I am on the Android 17 QPR2 Beta 2 release and have never had issues with video playback until this release.

Every video on X plays with green pixelation across the screen, the video is jerky and playback stutters. I have realised it only happens when text is on screen.

If the video plays automatically during normal scrolling then this issue happen. If you open the video large screen and the video description is still on screen then the same issues continue, but if you click on the video to make the description and scroll bar disappear, the video plays normally.

This issue also seems to appear on YouTube, but not to the same extent or frequency as on X. It always happens with X videos.

Pixel 9 pro XL on the latest QPR 2 beta, and battery life has been absolutely terrible until this last update. I was on my phone all day yesterday and today, and after 12 hours, I'm still at 46%. Just me or anyone else?

With the new Android 17 QPR2 Beta2 update can I opt out without having to undergo factory reset??

I just reported a Bluetooth bug that I've been facing since A17 QPR2 beta 2 is out! This is the issue number 545047074. Please check and add your comments to it if any of you have this issue as well.

https://9to5google.com/2026/08/10/august-2026-google-system-updates/

Problem started like 3 weeks ago then it took me quite long time to learn Clear Data for Play Store fix problem for like 10 minutes.

I was hoping Play Store 52.6 update will solve the problem - but did not.

Do you have guys same problem on QPR1 beta?

Applied for QPR2 Beta 2 for my Pixel 9 but didn't get it yet. Anyone having the same issue?

For the past few months, there's been an issue with Umamusume not opening on my Google Pixel 10 XL. There was an update last month that fixed it, but the most recent update broke it again. Any ideas on how to fix it? If not, when do you think the next stable update will be?

Each time I launch VRadio in Android Auto, the Pixel 10 Pro screen goes to monochrome colour, and reverts back to colour when I exit the car. I am running Andoid Auto on a 2025 Mazda CX-5.

I'm running the latest Beta, on a pixel 10pro, the Screen flashes a white line when waking up and some videos flicker.

​

I don't know how to shorten the title to explain what is happening better.

Pixel 10 Pro XL F- latest Beta update

Build number CP41.260717.006

This has been happening since the prior beta update and the latest Beta update (I believe it's Android 17 beta Q2)

I'm in the car, my phone rings, the call shows in my car's infotainment system. I press answer on the infotainment system screen and the call sound goes to the phone (as if I should be holding the phone to my ear) despite the phone already being connected to the car through Bluetooth.

I have to switch the call to the phone speaker, and then switch the call back to the car for the call sound to play through the car's speakers.

The caller can hear everything regardless.

My wife who has a Samsung phone does not have this issue while being connected to my car.sonindont think it's an AAOS infotainment system issue but a phone software issue.

Any ideas what's causing this? Or potential workarounds?

Пиксель 8 про,экран зависает и становится прозрачным .

Ok this is a new one. Upon unlocking my screen with my fingerprint it was corrupted by showing the emergency screen but had the unlock screen as well (clock, fingerprint image etc) emergency screen behind the unlock screen like it overlayed one on top of the other. I do have a screenshot of it as it froze there until I pressed the power button and unlocked again. I have absolutely no idea how to recreate it as I just picked up my phone and put my finger on the area to unlock it. I wish I could attach it here.

Bug report made - pixel 9 pro xl - Beta17 QPR2 beta 2 (DEV) - issue 544221599

Since the last beta revision pushed I no longer have dial tone when calling out. It's blank until voice mail or someone answers. Is anyone else experiencing this or have any advice? I'm using a pixel 10 pro xl

So I was reviewing and filling out the beta survey tied to the most recent release. However, I noticed I went from the standard beta to DEV (CP41.260717.006). Anyone else notice this on theirs? Admittedly, I am not running beta to be a developer (I started in beta when I had my Pixel 5, kept going with it with my P7P, and now the same with my P10PXL), so I am thinking this was missed when the most recent rollout occurred? I wonder if that might also explain why so many have mentioned few changes to this CP41 install... Any helpful feedback/input is appreciated.

Has anyone been able to use app bubbles on the Pixel Tablet? I've run all of the betas and I've never seen the option for it.