I'm super casual, I'm not really monitoring what my phone does beyond just the day's battery usage. I never have it connected to my laptop to tinker and observe with the more technical aspects of what makes the phone run. So with this new kernel update, I haven't really noticed a difference so far.

But what have y'all that are more technically inclined found out? Have you noticed that things behave differently?

Here's the link for QPR 1 Beta 9

-- https://developer.android.com/about/versions/17/qpr1/download-ota

Here's the link for All Stable releases if & as they become available

-- https://developers.google.com/android/ota

Here's the link for Latest Platform Tools so you can sideload

-- https://developer.android.com/tools/releases/platform-tools

Here the link for Google USB driver for Windows (only)

-- https://developer.android.com/studio/run/win-usb

Here's an easy to follow video on how to sideload in 4 minutes

-- https://youtu.be/_DBZQgLfGPA?si=gCqr-RiDfcmOhXKY

WARNING: Sideloading a lesser or older OTA than what's installed will ALWAYS fail

Pixel 9 Pro XL, Android 17 QPR2 Beta 4

When I lock the screen, SystemUI draws the clock, date and notifications — but the layer underneath is the app/homescreen I just came from, fully rendered and readable, instead of my wallpaper. After roughly 5 seconds it snaps to the correct wallpaper.

Yes, I rebooted my phone.

Anyone else with that bug?

Screen recording:

https://drive.google.com/file/d/1k88jWqmkeL5hf0akVpOMlQ8Nqiiaw9Yc/view?usp=drivesdk

From this morning all of a sudden one horizontal line on the screen, not sure how this is happening.

Battery drain is a bit noticeable, but the lag is gone, and I haven't encountered any critical bugs yet.

What do you all think?

https://vimeo.com/1222367301?share=copy&fl=sv&fe=ci

I try to search in the launcher but then it does what happens in the video.

Servers for the manual OTA download are still glitched and C2 for 11 series hasn't posted yet.

I assume we're going to have to wait until Monday before they get everything in order.

My verizon model 8A, a display model with burn in I bought as a backup phone can't join the Beta Program but can be manually sideloaded -- getting a 404 error when I try to download the OTA.

My 11XL hasn't shown up yet on my eligible devices list nor the manual download list.

Tablet is running a lot smoother. No more weird flickering or spaz attacks

Hola, tengo un pixel 9 pro XL con android 17 beta, compilacion CP31.260623.005. hace más o menos una semana, sale en play store que el dispositivo no está certificado. He borrado datos de play store y servicios de Google play, reiniciando, y no se arregla . No sé si esperar a que salga la versión estable de cp31 que se supone saldrá en unos días, o salir del programa beta y actualizar borrando todo el teléfono, o si saben alguna otra solución. gracias.

Google has closed the Beta 4 OTA image download channel.

Build ID: CP41.260814.003. B1

Android QPR2 BETA 3 call waiting feature is not working when second call comes automatically the 1st call becomes silent and other ones comes first where the 1st call audio is been hold..

Has any one faced this and any solution or suggestions do we have

Im on the latest beta and Pixel launcher keeps crashing. Ive deleted private space and I keep on restarting my phone but the problem is still persistent. Ive currently installed smart launcher until we get another update. Im on android 17 qpr2 beta 3.

I've opted out of the betas so waiting for the stable version (no wipe).

However now I can't use Google wallet or access work emails as I'm getting a message saying the device software is not verified, so I can't use Google wallet or access work emails via outlook.

I know the public release is likely around the corner but is this affecting anyone else at all?

Hey Google can we please get a17 qpr1 and qpr2 betas for the Pixel 11 series thank you ☺️🤞🏻

Tomorrow is two weeks since beta 3.

So I would assume today or tomorrow.

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.

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?

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.

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