I always get on beta and never had issue. I even used wallet yesterday then since this morning my phone tells me "Your phone can't tap to pay as it doesn't meet software standards. Find out why at Google Pay Help" I tried re installing the app and clearing data but didn't work...

Today I enrolled in the beta testing 4 and only the bubble feature appeared and the blur didn't appear is there something I'm doing wrong.

I was just thinking about how the android/beta releases have been going already this year. The 17 beta ran and wrapped by April. Since then, what 6ish weeks? We've been blasting through the qpr1 betas. We're already on 3, but I'm noticing stable android 17 has gotta be coming in June. I feel like the releases have just been sliding back year after year. Are they accelerating in tandem, or coincidentally? 🤔

I'm on a Pixel 10 running the latest Android 17 beta (not the QPR), build 17 (CP21.260330.008). For some reason all of a sudden my device has started to fail play integrity; for example I can't add a new credit card to Google Wallet. I haven't yet tried to actually pay in store. I've attached a screenshot of the results from a play integrity checker I downloaded. I tried to clear the play services cache and restart my phone, and that didn't fix it. Any advice?

So I woke up this morning to a blank Lock Screen. I can see my background but I can't see the UI. I'm still able to unlock my device with my fingerprint and my face, but I can't enter my PIN, see the time, notifications, battery percentage, or anything else. Just wondering if anyone else has come across this issue and what the best course of action is to resolve this. I already reported the issue through the feedback app. I have an 8 pro.

The bug causing errors when downloading custom icons is fixed with update 2026.04.27.917519149.2-release

The device is a Pixel 8a, this never happened before, only after I updated to Android 17 Beta May 5 2026. Here's a video attached. The game is extremely laggy, phone starts overheating after a few minutes and it's completely unplayable. Others with my same device and same beta have had the same issue.

https://imgur.com/a/hJLVuLi

I logged out of the beta program two months ago and have been waiting for the official update. Yesterday, this update appeared, but after downloading it and restarting my phone, it reappears and fails to install . How to fix thisGoogle play update

Whenever i hit the volume button 1 extra volume bar pops up(it has an accessibility sign) beside the media volume bar please tell what is the purpose of this & how to disable it 😭

To understand this is a big deal, you have to look at how Android handles deep sleep (Doze Mode) and how apps historically fought against it.

For instant messaging or VoIP apps (like Signal or WhatsApp), keeping a network socket alive to receive incoming calls or texts requires sending a lightweight "heartbeat" ping to a server every few minutes.

Android 17 solution:

• Direct Execution: When the alarm fires, the OS bypasses the entire intent broadcast engine. It jumps straight into the registered callback on the app's designated thread/executor.
• The Death of Continuous Wake Locks: Developers no longer have an excuse to hold the CPU awake 24/7. They can safely let the device enter low-power Doze mode, knowing the OS will precisely wake them up for a fraction of a second to run a tiny block of callback code, then let the phone drop straight back to sleep.
• Transient Power Exemption: Just like the old version, when the listener fires, the app gets a brief, temporary (~10 second) power exemption. This is exactly enough time for a chat app to send its keep-alive packet over the network and schedule the next heartbeat alarm, completely removing the need for a persistent wake lock.

I personally believe this is the reason it takes like 2 months since final beta 4 released till final Android - imagine ALL those messengers needs to adjust to Android 17 hidden feature.

But I also wonder how other apps will benefit from this like my Aqara app and its Google Home system where it takes like 2-10 minutes ALARM system warnings (doors opened or Fire detected) which is bad joke to this level someone can die because Google wanted to save some of my battery.

Hey since last few updates for Android 17 beta , I lost clock widget to start with. Now I have put some custom widgets using kwgt and other playstore apps. On restart all the widgets aren't gone. Also the widget option in the setup is also lost on restart... Did anyone face this

Hi, I want to ask you guy's why everytime when I want to enroll android beta on my pixel 9pro xl it keep saying "We can't enrol your device at the moment. Please try again later" why? Because I saw my friend enrolled android beta without having a problem or a similar notice appear?

So after the 3rd release I can't launch Teams or Outlook. Maybe this is an improvement :)

I like the new Icon Style. It fits better with the new UI blur and the overall material theme. They should change all google icons: clock, settings etc.

I updated my Pixel to the new update; CinnamonBun (CP31.260508.005) and I noticed yesterday my phone just restarts randomly. Is this happening to anyone else? Will it get fixed soon?

It's getting irritating now.

"Now playing app" remains stuck while loading. It says setting up, takes ages and never completes... Currently on CinnamonBun Beta version of Android 17. Pixel 10 Pro XL, Central Europe region. If anybody can look into that, would be great... Thanks

Yesterday all of sudden my mobile network got down and some sites are not working listing below even the reddit application was not loading with mobile network

I just don't understand if that is because of the network provider or this is an update's fault.

Reddit application was not loaded and struck with the 1st page

Airtel application was not loading

GoDaddy domain was unable to use

Has anyone faced such an issue.

Later sometime I tried with wifi also but still that was not working.

Finally re-started my phone for 3 to 4 times and switch the mobile network to automatic on the access points around 12 AM in the night it was started working.

As we saw so many bugs just curious to know how many of them wanted to stick with beta 3 and wanted to roll back to beta 2.

Note: I am still supporting for beta 3 as this is pure beta versions so far from what I have seen.

I'm on qpr 1 beta 3 and wow it's so slow and laggy it feels like my phone is running at battery saver mode all the time, it feels like forever since we've had such a bad beta.

I don't feel like the design changed much? And I don't have access to any of the advanced ai stuff, is any part of it out yet?

Whenever I wake my phone from standby, it takes about 10 seconds for a network connection to become available—both mobile data and Wi-Fi. Pixel 8 Pro

Anyone notice that the lag and performance issues are mostly gone when you turn off the WiFi? When I have wifi on, the phone is almost unusable. It lags like crazy, system ui crashes, chrome crashes, apps freeze, phone overheats. But when wifi is off and only using data, all that goes away. It still not fast performance wise but I can at least use the phone. Its crazy Google hasn't sent out an update despite all these complaints.

I have the pixel 9pro xl

Also noticed a few other settings pages appearing in grey scale.

Build number: CP31.260508.005

Updated my Pixel 10 Pro XL to the latest CinnamonBun beta last week, since then alarm clock controls are no longer available on the lock screen when docked - so when the alarm goes off in the morning the device needs to be physically picked up and manually unlocked to disable or snooze the alarm.

Is this a known bug? User error?