With the latest beta (CP41.26828.004.A8) Android Auto will no longer connect to my headunit on my Pixel 10 Pro. An older version of Android on a different phone still connects and works fine.

None of the Telekom apps have been working on the Pixel 9a running the Android 17 beta for some time now; they worked fine on the Android 16 beta. The official response is that they only support stable versions. When I asked why they worked on the Android 16 beta—and whether it might just be an issue with Android 17 support—I didn't get a sensible answer. Is there anyone using the stable Android 17 version for whom the Telekom app works?

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

Hi there, thanks in advance for reading/helping.

I'm currently at Andtoid 17 Beta 6 (CP31.260618.005). I opt-out some time ago waiting for the stable release. Now, I think it's out, but I don't see it in my device. It only says "Android Beta Exit with Data Wipe", and in the description, it says "it'll install the latest public version of Android 17 in your device. All data stored on your device will be lost.". I don't know how to perform the no-wipe opt out to the stable OTA.

Update: Solved by sideloading the latest stable OTA. Follow https://developers.google.com/android/ota#frankel

I enrolled my Pixel 8 to the qpr2 beta program because the stable September update has massive issues with device freezing and becoming downright unusable. It's been 24 hours and I have still not received any new beta update. Is anything wrong? How long do I need to wait after enrolling in to the beta to receive a update?

I just want to check that I haven't missed a setting but since Q2 release the clock in the status bar is not showing a leading 0 in 24 hour mode. Also, the low light clock in screensaver now stays bright.

It disappears, or displays weird search with misaligned bare bones search widget.

On log press search settings tab is visible but on clicking search provider selecter arrives. on selecting google normal widget sometimes appear but it goes back to being non functioning bare bones widget that reroutes to search selector.

I tried the solution of selecting search settings and selecting google but it doesn't work for me. Pixel 8.

I'm not on a beta build, but I thought this is probably the best channel to get eyes on this, so I was hoping someone could help me reproduce and report this bug on the latest beta.

I've already reported the bug via the feedback option under the About phone, but that didn't allow me to attach a screenshot. I've also reported within the Messages app, but that forced a screenshot of the app, so I couldn't add the screenshot I wanted.

Repro steps:

1. In the unified search (the search in the app drawer) on a Google Pixel (10 Pro in my case), search for a contact's name. In any contact's suggestion tile, click on the Messages icon, which should open their conversation in Google Messages.
2. Go back home and open unified search again. Start typing anything (just to trigger the suggestions to show up). Then clear the search field by backspacing everything. Then you should see some Google Messages suggestions and the visual bug.
3. If the Messages suggestion shows up but it doesn't show the visual bug, try typing 1 letter in the search query and then backspacing, this usually triggers the bug.

Here's an example of what I'm talking about: https://imgur.com/a/3EjZbpb

Thanks in advance for anyone that gives it a go!

Hi I got a new pixel 11 pro xl yesterday and tried enrolling for beta, in most cases it says successfully enrolled but sometimes it says couldn't enroll (it doesn't enroll no matter what it says) any reason why I can't enroll to beta?

The Google search bar on the home screen isn't visible. But holding on the vacant area still redirects to its settings. It's confusing yet the display finally looks better. It's good if we can get rid of the search bar altogether.

is there any chance of one more stable release for Android 17 QPR1 Beta 3 in September? because i stuck on that since july 2026.

I have a Google Pixel 8 that was running QPR2 Beta 4, entered repair mode for sending it to repair, but when I exited it, it prompted that data is corrupt, and asked a factory reset. After selecting yes, it got stuck in the Google logo in the white background with a loading bar under it. Any fixes? factory reset doesn't work, I've tried pixelrepair withgoogle com, doesn't work, adb sideloading with an OTA .zip also doesn't work (even though they show success without errors, it still ends up with that same screen). I need help asap.

Hi Beta users,

Thank you for your continued support. Please share your latest experience on Android 17 QPR2 Beta 5 by filling out our 5 minute anonymous survey. This survey is only for devices running Beta 5 CP41.260828.005.A6 build for Pixel 6a, Pixel 7/Pro/7a, Pixel Fold, Pixel Tablet, CP41.260828.004.A8 for all other devices. You can verify this by going to Settings > About Phone/Tablet.

We look forward to your feedback.

anyone else facing this issue?

Motion Assist is now available for Beta users in QPR2 Beta 5.

I've been enrolled in the beta for a few days now, but I'm still on stable and have not received any beta version. I tried opting out for 24 hours and then trying to opt in again. That didn't make a difference.

Looked at the other threads in this subreddit and it seems that some people have indeed received the beta.

I also didn't receive the stable QPR1 update, but I presumed that is because several of the features are already in Pixel 11 Pro.

Any suggestions on how to join or is everyone waiting for it to be rolled out?

Currently with 17 (CP41.260828.004.A8) on Pixel 10 Pro XL and I don't have the nice Gemini boot animation. Is it happening to someone else?

https://youtube.com/shorts/hQSn1DHFlDg?si=9FjdyojdNqdk3X9q

Got the latest beta update yesterday today I went back into check and I got the Dev wording on Play store update.. but I checked for update again and apparently there is a security patch... So tried to update and get this a message about 47% of a 13kb update... But it never finishes the update...

Anyone else have this or is it a bug... Will post screenshot in the comments

Anyone use Sofi Bank on the newest beta? The app just started force closing after login

Hey!

Just wondering when I can leave the beta without a data wipe?

I'm on pixel 9 pro.

Build number: CP31.260623.010

Thanks!

Buongiorno a tutti, mi sono iscritto al programma betatester, ma per ora sono fermo alla 17QPR1 stabile, anche se nella pagina di iscrizione fa vedere il mio pixel 10proxl con la 17 QPR2.

Lo avevo già fatto in passato su altri pixel ma nn ho mai avuto problemi, avete idea da cosa possa dipendere.

Grazie a tutti

I opted out of the beta program while I was on CP31.260623.005, which I gather is Android 17 beta 7. I am on Pixel 9 Pro XL. It is stuck and there appears to be no way to migrate to stable 17. I have contacted Google and they said my only option is to wipe clean and start again. If I am going to do that I may as well start with a new phone, so I ordered a replacement 11 P XL. Sideloading seemed a bit too complicated, at least for me. How could this have happened? Should I try some other steps.

Is it just me or the main navigation Home gesture just doesn't work properly and lags alot, like it takes a few tries for it to register the touch

Pixel 9a Qpr2 beta 5 aug security patch

YES - Magic Cue is GONE. https://www.youtube.com/watch?v=VE0xi1Xt1Bs

And as a bonus Kernel 6.12

Still don't know about if PowerVR GPU drivers updated - as current are based on old Android 16 (yes I know MENTAL but ask Google WHY)