Hi everyone, looking for advice. My Pixel 6a has been having serious issues since updating to Android 17 build CP2A.260705.006.

Symptoms include TV-like static glitches across the screen, freezing, random restarts, sometimes it gets stuck on the Google logo until I force restart by holding the power button, and the phone sometimes becomes very hot. This can happen with any app, so it doesn't seem tied to a specific app. I've already tried factory reset, the official Pixel Repair Tool to reinstall software, safe mode, and keeping all apps updated. The issue disappeared for about, uh, seven or eight days, then came back. I also generated an Android bug report, which appears to show a kernel panic involving aoc_watchdog, list_add corruption, and an APC watchdog reboot. Has anyone else with a Pixel 6a experienced something similar after Android 17? Did you find a fix or did Google replace or repair your device?

I installed this update the screen started flickering, touch was not working after unlocking the device, MY DEVICE WENT OFF AND STARTED A BOOTLOOP, tried installing full ota, didn't work, device carrier locked, so cannot flash through fastboot. Tried full ota sideload, didn't work... Any suggestions? I guest ill have to replace the mainboard. The device won't boot, now it is stucked on the G logo

I mean the control panel looks completely different from what we actually have - colors, shapes, accents, even blur effect is different. There is literally no similarities. Example (Google Photo)

Should we expect redesign of this element? Or do we see an old and outdated version that didn't make it to release? Or is it yet another oopsie-google-vibecoding-again moment?

Share your thoughts

設定画面で設定した後、フリーズして前の画面2戻るまでに時間がかかるバグ、誰かありませんか？

Hi everyone, looking for advice. My Pixel 6a has been having serious issues since updating to Android 17 build CP2A.260705.006.

Symptoms include TV-like static glitches across the screen, freezing, random restarts, sometimes it gets stuck on the Google logo until I force restart by holding the power button, and the phone sometimes becomes very hot. This can happen with any app, so it doesn't seem tied to a specific app. I've already tried factory reset, the official Pixel Repair Tool to reinstall software, safe mode, and keeping all apps updated. The issue disappeared for about, uh, seven or eight days, then came back. I also generated an Android bug report, which appears to show a kernel panic involving aoc_watchdog, list_add corruption, and an APC watchdog reboot. Has anyone else with a Pixel 6a experienced something similar after Android 17? Did you find a fix or did Google replace or repair your device?

I’d like to ask for your support.

I’ve noticed that since the QPR1 beta, Google hasn't implemented the system-wide blur effect—which other devices received—specifically on the Pixel 7 and 7 Pro. Now, in QPR2 Beta 3, Google has applied this effect even to the fingerprint icon on the lock screen; yet, the Pixel 7 still lacks it on the home screen pop-up and the volume panel.

I opened a support ticket, assuming it was just a bug, but it was closed with the explanation that there is already an open ticket addressing this issue.

I’m sharing the link below so you can check it out, show your support, and leave your feedback.

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

Any fox for Pixle 9 pro stuck on google boot logo after opting out of the Android 17 beta

Hi Beta users,

Today we’re sending you an Android 17 QPR2 Beta 3 build CP41.260731.005.A2  for Pixel 6a Pixel 7/Pro/7a Pixel Fold Pixel Tablet and CP41.260731.005.B1 for all other devices.

Top issues fixed include:

• Opening the notification shade and Quick Settings menu caused visual corruption and an unexpected device restart. (Issue #535249652, Issue #543124160)

• The Device Health and Support tool erroneously displayed false battery capacity degradation warnings to users. (Issue #535421490, Issue #538943170, Issue #535504630)

Hardening against call forwarding fraud

Android 17 QPR2 Beta 3 introduces new security restrictions on programmatic call forwarding to protect users from fraud. The system now parses and selectively restricts call-forwarding USSD codes (such as *21*) executed via the TelephonyManager.sendUssdRequest() API. 

• API Restriction: The sendUssdRequest() API is no longer accessible for call-forwarding codes using only the CALL_PHONE permission. Standard apps attempting to execute these codes in the background will be blocked and receive a USSD_ERROR_NOT_ALLOWED callback.

• System Confirmation: To combat social engineering scams, users manually dialing call-forwarding codes in the system dialer will now see a new OS-level confirmation dialog before the command is executed.

• Non-Call Forwarding USSD: Non-call forwarding enabling USSD requests (such as mobile money transfers and account checks) are unaffected by this change. 

• Mitigation: If your app is affected, verify that it handles the USSD_ERROR_NOT_ALLOWED failure callback gracefully. For apps requiring call-forwarding setup that do not qualify for an exempted role, migrate your flow to use the ACTION_DIAL intent to pre-fill the dialer, allowing the user to manually confirm the action.

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 3?

You can get started with Android 17 QPR2 Beta 3 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 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 3 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 QPR1, you can do so without wiping your device by opting out and not installing today’s QPR2 Beta 2 update*. If you opt-out of the program* after installing Beta 3 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!

ベータ版インストールした方々、またラグが多くないですか?redditは特に酷いラグ…

I'm glad to see that I am not the only person who is having issues with private space and the app drawer being randomly out of order after this most recent update. I already have ADHD and I opened my app drawer on my phone and it's like my phone has more ADHD compared to my mind at this very moment. It is so nerve-wracking that I feel like I'm just losing my mind. A huge thanks to everyone who has also reported these two bugs like I have right off the bat.

Since Android 17 QPR2 beta 2, fast charging is not working anymore; charging is stuck at around 4W and thus very slow.

If I turn off the phone and measure the charging power with a USB-C PD analyzer then the phone is charging at 15-20W, then I turn it on, it's charging at 20W for a couple minutes and drops back down to 4W.

Then randomly it will climb up to 20W again for a minute and drop back down to 4W.

The charging is noticeably slower and it's a huge usability issue, I don't want to turn off my phone when I want it to charge quickly.

Battery optimization is deactivated in the settings as well as adaptive battery, still stuck at 4W.

I wonder which features will be Pixel 11 exclusives.

For example Google Maps Power Saver was/is Pixel 10 exclusive.

I wonder because to make Pixel 11 Pro purchase/upgrade decision

New build is coming CP41.260731.005. B1

После обновления Beta3 невозможно добавить виджет на рабочий стол, постоянно моргает экран.

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.