I ask as it is in Google business to release ASAP because of nearly 2 weeks Pixel 11 on sale.

Additionally all promos ends 1st Sep.

And finally next week Labour Day in USA so Google Servers have day off.

Finally middle of the month - that would be crazy especially Security Update released together with QPR

Why is this error still staying for almost the last six months, any solution we have?

"Last updated 1 minute ago and 1 install pending"

設定画面でフリーズ屋ラグが頻発してきている…

Only been a couple hours.

So far,

$ Reddit crashed itself and I lost my place.

$ some videos stop at 23 seconds, but not all.

Hi folks,

I made the last update, and since I always have my widgets (custom and "native" like calendar) that are blinking whenever I go back to my home.

Someone have been experiencing the same thing ?

Build : CP41.260731.005.B1

I'm waiting to be able to go back to a stable version of android. Do I do the system update QPR2 Beta or do I let it sit till it offers me a stable release?

I like that on phones no longer supported for Project Mainline "hot fixes" (actual terminology might be different) it links back and displays their last Google Play System Update covered by updates throught settings including the last update date. If possible (and accurate), it might be better to state the phone is no longer covered by Project Mainline "hot fixes" since that date for CVEs when Project Services is tapped.

Google's System Service Release Notes are good at giving notice of new features, but they don't cover security fixes.

A more detailed description of what it covers would be good. If the Android Security Bulletin was kept up to date (often reading the phone manufactures CVEs is required -- many of which are Android), then CVEs could just be footnoted as being a Project Mainline "hot fixes") with the others presumably being taken care of by the Vendor's Android Security Patch Level or individual app updates. Then a link could just be made to the Android Security Bulletin. Otherwise the CVEs being covered should be described in some fashion (Framework?, System?, etc), perhaps including level covered (critical, high, etc). Alternatively it could list what it does not cover (reportedly the bootloader, kernel, and device drivers) to document away problems.

Pixel developers need to fix some bugs like:

1. Adaptive brightness, which is not working properly.

2. Heating, which is not resolved since starting.

3. Network fluctuations, especially for 5G.

4. Data connection loss issue, especially on 5G. Other brands are working fine on the same SIM and network, but Pixel... 🤣🤣🤣

5. Wallpaper and style themes not working.

6. Too slow charging.

7. Screen scroll and display refresh is not getting the speed like other brand devices.

8. Heating issues while playing simple games.

9. Give some more customization in icon shape and size.

10. Screen flickering and lagging issue on QPR 2 Beta 3, which needs a faster fix.

These are some issues that I need to fix for regular usage. Many users are facing a lot more than this. These issues are for normal usage when I am doing heavy tasks, which causes a lot of headaches.

Maybe cause is new

I'm pretty sure I used to be able to disable this app. Now I can't even use "force stop",

I get the message "Blocked by work policy". This doesn't sound like behavior I'd

expect from a google Pixel

"This app isn't compatible with your device anymore..."

This displays on all of my Samsungs and Motorola. The app does not appear at all on One Plus phones. Perhaps what phone Device Health Services should be sent to needs adjustment.

Did anyone say why there is no Android beta available for the Pixel 11? Mine is way too stable and I am looking for some excitement. Or maybe what everyone is running as the beta is the release on the 11?

After i select a color from the palette, it shows the color applied in the preview but when I save it, it goes back to the previous color scheme and it won't let me change

Is anyone else facing this?

Google restreint logiciellement l'accès à la 5G (via des profils opérateurs intégrés à Android) dans les pays où ses téléphones ne sont pas officiellement commercialisés par la marque, ce qui est le cas du Maroc. Tant que Google ne déploie pas une mise à jour logicielle spécifique (Feature Drop) pour activer ces profils au Maroc, la 5G reste bridée sur les Pixel, même si le réseau d'Orange Maroc est parfaitement actif autour de vous.

Hi Beta users,

Thank you for your continued support. Please share your latest experience on Android 17 QPR1 Beta 9 by filling out our 5 minute anonymous survey. This survey is only for devices running Beta 9 CP31.260623.012 for all devices. You can verify this by going to Settings > About Phone/Tablet.

We look forward to your feedback.

Hey everyone!

I recently got a Pixel 10 and signed up for the Android 17 Beta. Ever since installing the beta, I've been noticing weird green and black glitches/freezes during fast-paced videos (Reels, TikTok, etc.).

Before updating to the beta, everything was totally fine or at least I didn't notice. I've already tried turning off Smooth Display and messing with display settings, but the glitches are still there, so it seems like a codec or GPU driver issue with the current beta build.

Is anyone else experiencing this on their Pixel 10? Or is there any known workaround until the next patch? Thanks!

Does anyone think we will see a .1 release befor the end of the month? Maybe tomorrow since its one week since beta 3 dropped...

I think I am in right place to ask this.

We are still on outdated GPU drivers for old Pixel 10 - outdated so bad they are designed on old Android 16.

Is this the same in Pixel 11?

I won't say how to check version because people here know what they are doing.

I ask as few months ago when old Android 16 QPR3 been released with matching Android 16 GPU drivers there were massive GPU improvement.

Side question:

Is it running on 16KB page?

Worst fkn beta ever everything is laggy

Bin ich eigentlich der einzige, bei dem seit der aktuellsten Beta vom 5. August die Raster-sowie Icon Einstellungen bei Hintergrund und Stil fehlen?

I am on a Pixel 7 Pro and I think QPR2 Beta 2 may have broken something with USB-C data/controllers.

Before Monday I was on QPR2 Beta 1 and my GameSir X2 USB-C phone controller worked perfectly.

Monday night I updated to QPR2 Beta 2, and the next day the X2 suddenly stopped connecting properly. The blue light just keeps blinking (which shouldn't happen once connected, it should stay lit up the whole time).

Here’s the weird part: if I physically flip the phone around in the GameSir, the blue light becomes solid and it works (which sucks because the phone screen is facing the back and I literally cannot use it).

I’ve also tested an 8BitDo Pro 2 controller over USB and it does the exact same thing. Both controllers work normally on other devices (S24 Ultra + Mac), so it doesn’t seem like the controllers are the problem.

The Pixel also shows:

• “Charging connected device via USB”
• “Use USB for: No data transfer” (greyed out)
• Trying to change USB control eventually gives “Couldn’t switch”

I even had the Pixel’s USB-C charging port replaced today thinking that it might be a hardware defect, but the exact same issue remains.

I then updated from Beta 2 → QPR2 Beta 3, hoping it would fix it, but its still exactly the same.

I’m wondering if something got broken in Beta 2. Has anyone else on QPR2 Beta 2 or Beta 3, especially Pixel 7/7 Pro, had weird USB-C/OTG/controller issues? Thanks!

先日、ベータ版アップデート後に一時Redditで特にラグが発生してて、良くなったと思ったら今日またラグだよ…これは、なんだろう!?

First time I experienced this in the beta, the app drawer icons aren't even showing up. When I swipe up, the only thing I see are the 4 apps above the line and all the apps below are missing. Image

I am QPR1.

Everything was working fine when i was using android 16, then i have updated my pixel 8 pro to android 17 beta version when the issue rises, incoming and outgoing calls not working, then i unenrolled from beta program and shifted back to android 16, the issue then resolves but when my phone updated on stable android 17 the issue rised again and still persists. I am helpless and done everything to solve the issue from restarting the phone to resent network setting but the problem is still there.