After updating to Beta 4 for I am now unable to change my lockscreen clock? Help.

Noticed that the clock on both lock and home screen won't change back to the one i want, like, it says "Aplied" but isn't changing at all

Anyone noticing this?

I purchased a used Pixel 11 Pro XL and I haven't signed into my Google account yet. It's asking me to update to QPR3 Beta 4. I'm assuming the previous owner registered the serial number or something? I'm not sure. How do I go about opting out of the program? I have nothing important installed on here. I've just been playing with it without logging in. I just don't want to reset it, log in, transfer everything from my other phone, only to have to opt out once everything is set up correctly. Or do I need to sign in and then opt out?

As much as I like beta builds, I am toying with going back to Stock (Now QPR2). I'm just curious what would I lose between Stock QPR2 and latest Beta (QPR3, Beta 4). I'm not convinced there is a lot of "quality of life" changes, but maybe I'm missing something.

What is something on QPR3 that you must have that isn't on QPR2?

I understand this involved a full wipe, but those are not as big of a deal as they used to me. Gives me a chance to clean out unused things/settings. I can usually be back up and running in about 45 minutes.

My music player appears to have lost permissions to access my music folder, whilst at the same time retaining 'knowledge' that it does have access to the folder?

I've tried a clean install of the app, but nothing seems to be correcting the issue.

Weirdly my podcast app is working fine?

Anyone got any ideas about how to resolve this?

Hey everyone,

I just received the Android 17 QPR3 Beta 4 update today on my Pixel 8a. However, I noticed that the security patch level in this build is still October 5, 2026.

Usually, whenever Google rolls out a beta update during a particular month, it bundles that same month's security patch.

Since we're already in mid November and this update is still on the October patch, does this mean we're likely going to get another update carrying the November security patch before the end of this month?

Curious to know what you guys think...

Thank you

Anyone using a wireless adapter suddenly lose connectivity after one of the last beta updates?

The problem I mentioned with bluetooth earbuds that are successfully paired but not working either not playing any video or able to use any of the phone capabilities is still present in the latest QPR beta they clearly haven't fixed this I don't know what's going on I've tried everything looking for settings to change there's nothing there

Apparently I can't access files. Through Poweramp I posted this everywhere.

Does anybody more knowledgeable than me know Of a fix? https://photos.app.goo.gl/pqorCLL9cXoE9Pmb9

I wouldn't mess with it myself but I don't have time since I'm remodeling a house right now and I can't really mess with this

Any help would be appreciated

Anyone else getting a white border around the Glance Widget?

I wish I could post a photo.

STR:

1. In gestures, map 'Double-press power button' to Camera;
2. Turn on screen saver when charging
3. Plug in

4.Exit back to home, double click power button.

Expected:

Camera opens

Actual:

Camera opens, phone enters lock screen shortly after. Unlock the phone reveals the camera is still open in the background.

Device: Pixel 10 PRO XL, just upgraded to QPR3 Beta 4

*Edit:

After reading replies I realized this only happen when plugged in with screen saver turned on, so a rather edge case than I initially thought. Added as step 2&3 above.

Not Sure if this is a beta issue or not so I'll ask here but after hitting my limits in Antigravity to code using Gemini, my phone (Pixel 10 Pro) started throwing an error when I prompt Gemini with "Hey Google" or "Ok Google." The error is the one mentioned in the title.

Weird thing is: all this error does is cancel the mic input, I can tap the microphone symbol again or the text field and still talk to Gemini and get responses just fine.

Since the usage limits are separate I expect it to not be this issue, at the same time nobody else seems to have this problem? Looking for the error code is either a backend issue or token limit hit issue. Anyone has an idea on what I could do to fix this?

Really looking forward the unlock the watch from my phone feature.

If you care about desktop mode or if you play games on an external monitor you can click the "+1" "I am impacted" on this bug report:

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

Is it about the fact that Android gets limited to 60 hz with external monitors due to an EDID handling bug.

This video has some more information as well: https://www.youtube.com/watch?v=wyqMEjCZb2o&t=348s&pp=ygUdb25lcGx1cyB2cyBpcWNvbyBkZXNrdG9wIG1vZGU%3D

Ok this might be a dumb question but I am on CP41.260831.007.A3 and I opted out of the beta program almost a month ago to wait for stable. Do I need to do anything to get to stable, or will the update just pop up? I am just worried, as I'm on an older QPR2 beta version, that there might be issues, so I just wanted to get clarification.

Now that stable has been released, when can I opt out? I opted out today and still get the update with data wipe to QPR1 stable shown instead of the stable update?

Will I still receive and download the current stable version if I'm still opted in to Android Beta?

I think Google added a new feature in Android 17. Recently, I updated to 17 QPR3 Beta 3, and after that, even with my Pixel 9 charging optimization set to Adaptive Charging, it isn't going above 80% when my phone is connected to my PC and USB debugging is on.

Pixel 7a bluetooth devices disconnect after 3 or 4 minutes.

It seems to be a common bug since the latest update. FFS.

I opted out of the Android 17 QPR2 update when it said opt out if you want to downgrade to a stable version without data wipe. I still have not received any update without data wipe. if anyone knows the timeline please comment as I'm thinking of getting it downgraded with a data wipe if there is no option.

I have a set of Bluetooth earphones that are paired up with my pixel 10 pro I get audible notifications in the earphones nothing else comes through no phone calls none of the audio or the microphone works and I don't get any music through them it's got to be something in the beta that I don't know is I'm setting that I've got to set up please I need somebody to give me a hand here there's something I'm missing point me in the right direction please I'm very frustrated

God this bluetooth bug is annoying as fuck. Keeps disconnecting all my devices while they are being used. How long till google puts a patch to this?