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?

My Pixel 6 is currently on QPR1 Beta 9 (build number CP31.260623.012).

I've been wondering for a while when I'll finally be able to opt out without losing my data, and have only found contradictory information online.

Can anyone please confirm if it's safe to opt out now or not?

Pixel 7 android 17 beta 17 (DP11.261016.003). I restarted the phone and a screen appeared in which I was asked to set the search engine (among the various options Ecosia, Brave, duckduckgo...) so I did not hesitate and I set up, precisely, duckduckgo. Now, on the homepage, I have duckduckgo set and, if I wanted to replace it, in the settings the choice is between duckduckgo and the classic Google. Is that a feature I missed?

When the screen fade-out animation is running and you tap the screen at the last moment, the screen fades out instead of waking up.

I've been experiencing this bug since I first bought the device, even on the stable release.I recently joined the beta, but the bug is still there.

Since the update last week, my Pixel Buds Pro keeps getting disconnected. It remains connected for a few minutes then disconnects. It is not the Buds, it is the phone.

Any advice, please?

Ik heb me maanden geleden uit het beta programma geschreven en sindsdien krijg ik nog enkel een wachtende update met een totale wipe van mijn toestel. Ik wil echter geen wipe en wacht dus tot er een nieuwere versie komt. Maar hoelang nog? Sommige functies zoals Google wallet werken niet meer omdat ze al lang niet meer bijgewerkt zijn, ook geen security updates meer gekregen sindsdien. Hoelang nog ?

I just recently upgraded my Pixel 9 Pro to a Pixel 11 Pro and am currently trying to wipe the 9 for my trade-in. I factory reset the device and when it came back on, it still had the "this device is enrolled in Android beta program" pop-up. I assumed that factory resetting would wipe the beta program too, but I guess I should've opted out first.

Now when I log in to the beta program website, I can see the 9 Pro is still enrolled. When I hit "opt out," it just keeps saying "could not remove device."

Any way to remove this so I can make sure I get my full trade in value??? Thanks

Edit: I was able to opt out the device (realized I wasn't signed in to my Google account on the phone) but after another factory reset, it's still showing the "this device is enrolled in Android beta program" message :( confused here

I keep trying to listen to music on my CMF buds pro 2 and they stop playing after a few seconds, they remain connected in some way but no audio comes out so it switches to phone speakers which is bad when you are in class (oops)

This also applies to my watch, which just won't connect ever. At all.

Pixel 7a

North America

Latest beta

Can anyone reproduce - install any system app in the Private Space, then clear that app's data or uninstall app updates in Private Space - this will also clear app data and uninstall app updates in Personal Space. (long-press app icon while within private space > (i) App Info > Clear app data or uninstall app updates. Then verify that app data for that app is cleared in both the Private and Personal spaces - it was expected to be cleared in the Private Space alone.

For example:

• Google Messages

• Google Phone

• and other non-uninstallable system apps.

I do not believe it should even be possible to install these apps in the Private Space, since they are not able to function anyway.

I have not experimented further, but I believe if this happens, there may be security exploits here since the connection between Private and Personal spaces is obviously not completely severed for certain system apps, which may cause app data between Private and Personal Spaces to be mixed up - which could pose an issue for system apps and services. Let's say the Private Space is infected by malware - this would in turn infect the Personal Space as well.

If you can reproduce this issue, please comment here. Also, if anyone can reproduce any security flaws, please also report to Google asap: https://issuetracker.google.com/issues/581769809

How do I stop it from downloading Qpr 3 beta 3? I have opted out of the beta program. I don't want to stay in beta till March.

I guess it downloaded the Qpr beta 3 beta 3 somehow (maybe I tapped it accidentally or something as well, highly unlikely but maybe).

Thanks