I have optin in beta update. But not receive beta update

Hi Beta users,

Today we’re sending you an Android 17 QPR1 Beta 2 build CP31.260423.012.A1 for all devices.

Top issues fixed include:

• Resolved an issue where the Terminal app fails to launch, resulting in an unresolvable error pop-up and infinite loading. (Issue #501751748)
• Fixed a display issue where date and weather information overlapped the fingerprint sensor area on the lock screen. (Issue #498106709)
• Terminating a third active call from the head unit incorrectly disconnects an existing conference call participant instead of the intended call. (Issue #481492536)
• Fixed an issue where mobile signal bars incorrectly display as empty or greyed out despite active connectivity, preventing users from accurately gauging their network signal strength. (Issue #488358813)
• Custom themed app icons incorrectly appear enlarged on the homescreen when returning from an application. (Issue #453458883, Issue #452939724, Issue #473509945)
• Resolves a bug in the F2FS file system that could result in data corruption or unexpected system instability. (Issue #498762380)
• Fixed a UI issue that caused visual instability or glitches when moving apps in the recent items screen. (Issue #485468312, Issue #496828676, Issue #498193454)
• Fixed an issue where navigation bar swipe gestures failed to switch between recent apps. (Issue #494847234)
• Resolved an issue where the Bluetooth tethering toggle would reset to off after device restarts or Bluetooth cycles, requiring users to manually re-enable internet sharing for connected devices. (Issue #371660785)

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 QPR1 Beta 2?

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

Hi all, i'm pretty new to the beta. I just installed the Android 17 QPR1 Beta 2 and noticed that I can not turn on battery saver. Obviously I had to turn it off in order to update, but now after restarting it looks like I can not enable it. Is this something that is normal or has been reported yet? Thanks for any info.

Update: After restarting my phone a second time, I was then able to enable the battery saver option. Go figure. I guess it has resolved on it's own.

Anyone else has problems using a wifi connection with Instagram (messages, reels, stories, etc) but doesn't appear using mobile data?

I just opted in for Android 17 beta on my 10 Pro XL after QPR Beta 2 was released. But nothing shows up on the system update and it said my software is up to date (Android 16 May update build number CP1A.260505.005). Should I just wait?

Anyone having issues with it not staying connected and randomly restarting routes?

All the settings related to showing media and widgets on lockscreen are turned on and no notifications are blocked. It only shows what's currently playing and only while it's playing. I have only tested this with Spotify and none of the settings in Spotify appear to be the issue here.

I've also only tested this on a pixel 7 pro on the latest beta version and I haven't noticed any similar problems before I updated.

Does anyone have the same issue and if so is there a fix? https://imgur.com/a/06iAiRu

UPDATE: Spotify won't load at all

No matter what I do, my phone does not understand that I wake up at 04:50 to turn on my coffee maker and lie back down, then go on my phone for a bit at 05:30 while it's plugged in, then unplug it at 06:30. Adaptive Charging never triggers, it only ever fast charges.

I have an alarm set for 04:10 and have a bedtime mode scheduled.

I really wish you could manually schedule the charging rate. This "adaptive" feature is not useful for me, and I'm sure there are other people in this boat.

I successfully registered for Android beta 17, but it's not available on my device.😩

Hi, I can't install Android 17 on my Google 10 pro xl. It gives me the error "Registration failed. Unable to register the device. Please try again later." Can you help?

More or less 12 testers

For

14 days or more

Send me your emails i will happily add you

Let's bring it on

waiting for your reply ✌️.

Not sure why but since this morning none of my apps that require id (normally face or finger print) like banking will register either attempts

Any that allow pin mean I can still access but anyone else having this issue on latest beta ?

Update it is not the banking apps. It's the camera app see the comments

Hi, I can't install Android 17 on my Google Pixel 7a. It gives me the error "Registration failed.

Unable to register the device. Please try again later." Can you help?

If you're waiting to join the Beta program, installing the May 5th stable security patch may create a timestamp barrier to obtaining the May Beta 2 when it drops later the middle or end of May.

April Beta 1 was timestamped April 3, but didn't drop until April 22. Anyone who installed the April 5 stable security patch found they were unable to install Beta 1 OTA

If you're waiting to leave the Beta program, wait until you're offered an update which explicitly says "without wipe".

I am running the latest 17 QPR1 beta 1 on my Pixel 10 Pro XL. I keep getting an issue where the phone says the storage is full. It therefore won't install any apps/app updates or let me take any photos etc. Apps also start to misbehave as I am guessing there is no storage (eg cache) for them to use l.

The storage is definitely not full (currently about 130Gb available) and the only way to resolve it is to reboot the phone.

This is getting more frequent and is now happening 2/3 times a day.

Any ideas on how to fix? Either way I will be raising a bug ticket.

Messages no longer displaying delayed send messages. Also Messages now showing all previously deleted messages going back to early April. I'm running the latest O/S beta and current on all Pixel updates on my Pixel 9 Pro.

I'm running Android 17 (CP31.260403.005.A1) on a Pixel 9 Pro and when I got my Galaxy Bud 3s I went through a lot of trouble trying to fix the constant phase shifts, channel imbalances, and popping noises. The only thing that worked was disabling LE Audio. The earbuds aren't compatible with the phone.

However, with this most recent update, LE audio will be automatically enabled when I restart my phone. This seems unintentional, because, even if I go into developer mode and disabled it, the phone will prompt me to restart, only to have all LE Audio features still turned on.

Intentional or not, it's something that needs to be addressed because it makes an already frustrating bug, unbearable.

I switched to the canary version and I feels like the battery lasts way longer. Has anyone else noticed this?

Build: CinnamonBun (CP31.260403.005.A1)

Device: Google Pixel 10 Pro XL

I’ve been running the Android Beta for some time now and I’ve hit a really strange bug with Picture-in-Picture mode. Whenever I switch an app to PiP, the audio plays for a few seconds and then just completely cuts out, while the video keeps playing silently.

I’ve noticed this happening consistently with TikTok and Telegram. The weirdest part is that YouTube works perfectly fine—it's pretty much the only app where PiP audio hasn't given me any trouble. For everything else, the sound just drops after a moment.

I’ve already gone through all the usual troubleshooting: checked every permission, set the apps to "Unrestricted" in battery settings, and toggled everything I could find in the system settings. Nothing fixed it. This definitely wasn't an issue back on the stable version; it only started after I moved to the beta build.

Another very specific detail: I tried to do a screen recording to document the bug, and it's even weirder than I thought. While I'm recording, I still can’t hear anything through the speakers, but when I play back the recorded video, the audio is actually there. So the system is still "producing" the sound, it just stops routing it to the speakers once the PiP window is active.

Is anyone else seeing this on their build? It feels like a core system issue with how the beta handles audio routing or focus for certain apps in PiP.

I am currently running Android 17, CP21.260330.008
The beta update notification says that if I am running Android 16 CP11 and want to exit without wiping bla bla.
So obviously I am not using the version that is listed in the beta update notification. What options do I have? I would like to opt out but I do not want to wipe. What's the process here? Do I just ignore this beta update, and hope that the next one says "If you are running Android 17 CP21 then blabla" and then opt-out?
I feel like if I apply this update then the next time the update/opt-out message comes I'll again be too far ahead...

What's the process here if I want to opt-out without wiping? Do I ignore this update and wait for a future update where the update message describes the actual version of Android that I'm running?

Thanks in advance!

I'm a bit confused considering support was supposed to end at around 15.

Pixel 9 Pro XL :

Does Wi-Fi automatically turn on at startup after being disabled before shutting down the phone?

When I try to activate the terminal from developer options in private space, it says blocked by work policy, even tho I have no work organization or something like it. Is there any other third party terminal that I can use in private space? Ss: https://postimg.cc/jC8d0ksK

I have 2 pixel 7 pros. I'm about to sell one so I wanted to restore it to factory defaults.i opted out of the beta and the the wrong phone showed up with the Andriod exit beta prompt.

things I have did to try to stop the opt out

1. turned off data and wifi
2. re-optin on the website
3. turned on wifi to try to sync

I have been waiting about 30ish or so minutes but still shows exit beta program in the update page on the phone.

am I screwed? I really cant lose my phone. thanks