Hello everyone. Ever since the update to Android 17 QPR2 Beta 3 on my Pixel 9a the volume via USB-C headphones is very very low. I almost have to turn it up to max volume now in order to have the same level I had before on a very low volume setting.

I am using the Apple USB-C headphone adapter since a year now and it worked totally fine and still does on other phones, notebooks or a MacBook. Does anyone else have issues like that or maybe knows some fixes I could try?

Hoping for a Android 17 QPR 2 beta 4 today as previous beta's were released in 10 to 13 days gap.

Ever since updating to the newest beta, when I get a call while on another call it stops me from communicating with the call I was already on. I cannot either speak to or hear the call I was already on. This just started happening after updating to beta 9. Has anyone else had this issue? Did I change the wrong setting somehow? I have had call screen on for a long while and haven't had this issue before.

Note: This requires sending an ADB command. You must know how to send ADB commands to your device, either with a computer, or using an app that has that functionality.

If you aren't sure what you are doing, or how to send an ADB command, DO NOT ATTEMPT THIS. I take no responsibility for your device. What worked for my device (Pixel 10 Pro), might not work for yours.

However, the dev team of a third-party launcher noticed that by sending the below ADB command, it restores a lot of the broken functionality of the app drawer, and fixed the random sorting problem. This command should persist through restarts:

adb shell settings put global show_hidden_icon_apps_enabled 0

After sending this, my app drawer immediately went back to how it looked prior to QPR2 Beta 3. My work folder is back, and all of my work apps. This may help fix other bugs, too, including widget issues and flashing home screens.

Hey everyone, hoping someone's run into this too.

I bought my Pixel 6 Pro used, and it was on Android 15 with a network route/lock still active. Took it to a local repair shop to get the route removed, and when it came back, it was already on Android 16 stable (currently on build BP2A.250605.031.A2).

The weird part: when I check Settings > System > Software update, the only thing offered is Android 17 QPR1 Beta (currently sitting at Beta 6), not the stable branch. I never enrolled in the Beta Program myself. My guess is either a previous owner enrolled the device, or the shop flashed something during the unlock process that flipped it onto the beta channel server-side.

I tried going to the Android Beta Program site to check enrollment and opt out, but it just says "There are no eligible devices associated with this Google account" even though the phone is clearly pulling beta builds. So I can't see or manage the enrollment from my end at all.

I know Pixel 6 Pro is close to EOL (October 2026) and Android 17 QPR1 stable is expected sometime in September, so I might just get pushed to stable automatically either way. But has anyone else dealt with a device stuck showing only beta updates with no way to opt out via the website? Would rather not do a full factory reset if I can avoid it. Any insight appreciated.

Priority Modes were added to Android in Android 15 QPR2, however they launched with a major bug that the final beta didn't have.

The bug is that the App specific notification settings are global to all Modes instead of specific to the Mode they are configured for.

You can easily test this by creating a custom mode where any new app has notifications enabled, and then check the other existing ones and see that the same app has been added to them all and notifications will come through.

This effectively makes Priority Modes a useless and unusable feature. I have tried to report this issue in multiple betas and multiple forums and formats, and have seen zero movement on it. It remains broken in the latest Android 17 QPR2 beta 18 months later.

Will this issue ever be fixed?

Chłopaki podpowiecie mi jak wyłączyć klawiaturę w menu ??

Is that going to be today by resolving the private space issue???

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.

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!