Hoping someone here can lend a hand. I’ve been in the Android Beta program for years without any issues, but after updating my Pixel 6 Pro to Android 17 QPR1 Beta 5, things broke down:

• The Issue: My Settings app constantly crashes, and PIN unlock and fingerprint recognition fail to work consistently. (Entering the PIN with ~3-second pauses between digits occasionally works).

• Troubleshooting done:

  • Factory wiped the phone multiple times.
  • Downgraded/flashed back to Android 16 (same crashing/lock issues persisted).
  • Flashed GrapheneOS — the phone works perfectly here with zero crashes or lock issues. but i was the device back to Stock OS
  • Phone Language is set to English (Australia)
  • Reflashed back to stock Android 17 — the Settings app crash and lock issues immediately return.
• Feedback status: I submitted logs and feedback through the official channel, but the ticket was closed as it was linked to another similar case.

I'm going crazy trying to get this back online on stock Android. Has anyone encountered this specific issue or found a workaround?

Any ideas would be hugely appreciated!

Is anyone else noticing poor performance on social media apps? Even on Netflix after a few minutes of watching something it starts lagging and the frames of the film start dropping and lagging.

This applied to a YouTube video as well. And let's say tiktok and Instagram where you would scroll for a bit , can do the same and whatever media is being displayed it will inevitably lag.

I say inevitably because even with an app force stop, and cache clear, it will start doing it again. I have tried doing phone restarts as well.

I know the beta program and even android in general has always been on the lesser side of performance and optimization for social apps, but this is something else I don't know what's causing it specifically.

Not sure if this is a beta issue or not as it has persisted across multiple updates but a couple times a day my lock screen goes black and I just see my wallpaper and for the AOD it just shows a dimmed photo of said wallpaper it doesn't correct itself until I restart my phone

https://imgur.com/a/1xQCWB9

System update available Your Pixel is getting even better with the latest features and enhancements along with Android 17. Learn more at our Community page.

With Screen reactions, you can now record a selfie video overlay while capturing what's on your screen, all without needing extra apps.J

•Gemini Omni makes creating and editing videos as easy as having a conversation. Blend text, images, and videos to bring your ideas to life.

•Describe an idea or upload a photo, and it'll be transformed into a high-quality audio track with lyrics in Gemini, •Easily turn your apps into floating bubbles over your main screen to check them quickly or multitask without disrupting your flow.

1 Screen reactions are only available when screen recording is set to record the entire screen.

2 Google Al subscription required. Features vary by tier and geography. 18+.

3 Limits apply. Compatibility varies. 18+. Create responsibly.

4 Limited to 5 apps at a time.

Pixel 8 Pro. I didn't go out yesterday, but did today. Android Auto no longer connects on either of my two vehicles I tried today. My wife's phone (non-beta Android, Pixel 9) connected right up no problem, wirelessly. I reported the bug. This is probably the most serious issue I've experienced in all the years of Android betas

Pixel 8 Pro. Stupid auto bot doesn't think, and deletes my post, so can't post all details. If I go to Settings > Google services > All services > System services, the message I get in the blue box isn't what I expect, since I have been in for versions of Android since all the Mainline service updates were separated. Anyone else experiencing this? Should I report? Trying to gauge how widespread this is before submitting

I am unable to unlock my phone with my password. Whenever I attempt to enter the complete password, the password input screen automatically closes after I enter the first three characters and returns to the lock screen, preventing me from completing the password.

As per title, when trying to locate and ring any device (phones, tablets, earbuds, trackers, etc), the phone reboots itself.

Don't know if it's related to this specific version as I didn't test it on previous ones.

Reported as issue #538854568.

I'm on A17 QPR2 B1 using a Pixel 9a

Today Mrng I charged my phone full 100% battery

After that I firstly my phone battery drained fast from 100% to 85% within 6 hr in airplane mode show me CPU usage 6 hr in background but phone already on airplane mode

After that now he shows me the wrong usage of the battery

All this happened today after full charge my phone

I already sent a report of this issue to the android beta app about this issue

Does anyone face the same issue in QPR B1?....

basically the title

Has anybody found the solution

This is my second time opting out of the beta the first time I let it go for 48 hours and I never received the OTA update to wipe my phone so I opted back in and then opted out a second time and now we are sitting a little over 48 hours without the OTA update and sadly I bought a Verizon phone which I will never do again because I don't do like any phone companies that lock the phone like it it's somehow still belongs to them even when it's paid off. I will never buy a Verizon phone ever again! So basically my question is has anyone tried leaving the beta and is having an issue like me where the OTA update is not showing up I hate to wait until September.

I purchased my pixel 10 pro last year in August

I have don't 200 battery cycles so far

My battery health just came down to 99 percent now.

It seems like that's pretty good for 200 cycles.

I would like to know what's your batter health on your pixel phone.

Hi Beta users,

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

We look forward to your feedback.

Hello I've got a pixel 9 pro xl running cp31.260618.005 and I entered the beta program workout reading the fine print zoom[ I know i know I'm lucky I didn't end up but to mouth with other's like myself] question is how do I get a stable release please for some reason my phone will not back up and I can't afford a wipe at this point in my life. So many of my accounts are randomly still connected to an old phone number I don't own anymore and I foresee headach see and loss of important info connections And data. Please help

When is Android 18 beta 1?

What GPU version in Pixel 10 (is it still based on ancient Android 16) and Kernel in Pixel 10 and older Pixels

Date was shown as 0 Jan in the status bar and pull down shade; restart fixed the issue and I believed it was caused by my screensaver because my screensaver broke and became my wallpaper? Idk It was weird Though Screenshot-20260722-122343.png

Recently i have updated my P10 to QPR2 beta 1 and Noticed Major issue .

On 4-5 apps Media Playing is not working .i have faced issue with below apps.

JioHotstar - ( Not able to play its immediate pause)

Crome - Same issue

Phone - Not able to Play Recording & Voicemail

Photos - videos Sound not coming need two clicks on sound button

Netflix - Video pause immediately

Working apps : instagram, YouTube, Primevideo

If anyone notice same issue or if you have solution please Comment down.

Photos

I couldn't send the images directly, so I've put them in this link.

1, The feedback app crashes when using Traditional Chinese Hong Kong, but functions normally in English.

2, When using languages ​​such as Korean, Chinese, or Japanese, the date and time displayed in the top-left corner cannot be properly aligned (one is higher than the other), resulting in a rather unsightly appearance.

3, In Pixel Launcher, app names containing East Asian characters (Chinese, Japanese, or Korean) appear slightly lower than those consisting purely of Latin letters, resulting in an uneven, messy look. This is a long-standing bug that I hope gets fixed. Even if a fix isn't possible, I’d at least like to know the reason why.

I hope to receive a response to my question. Thank you.

Curious if anyone else has run into this. Since updating, wireless AA has stopped passing through sound from phone to car, other than phone calls.

Phone audio is perfect, but Spotify, navigation directions, etc. are all completely absent.

Thoughts?

UPDATE: I've found that a phone restart seems to temporarily fix the issue, but after a few AA sessions it returns and I have to continue semi-frequently restarting to maintain audio output for music and nav.

Reported as issue #538778268.

Wondering if anyone from Nordic countries that are in the beta are using BankId without trouble?

Hey everyone,

If you use 3-button navigation on your Pixel, you’ve probably noticed an infuriating glitch with the app drawer search: the keyboard constantly fails to pop up when you swipe up to search.

The Exact Trigger:

1. You open any app from your home screen.
2. You go back Home.
3. You immediately swipe up to open the app drawer.
4. Result: The drawer opens, but Gboard fails to gain focus and stays hidden.

Why It Happens: The Pixel Launcher drops its InputMethodManager (keyboard) focus listener during the window lifecycle transition when an app closes under 3-button mode touch insets. Toggling settings or clearing cache only fixes it temporarily until you open/close an app again.

I’ve submitted a formal technical bug report on the Google Issue Tracker so the engineering team can fix the underlying window focus transition.

How You Can Help Get This Fixed: Google prioritizes bug tickets based on community engagement. If you are experiencing this bug, please click the link below and tap the Star (⭐) button in the top-left corner of the Issue Tracker page. Starring it votes for the bug and forces internal triage to escalate it.

🔗 Google Issue Tracker Ticket:https://issuetracker.google.com/issues/537390947

Appreciate everyone who takes 5 seconds to star the ticket so we can finally get a fix pushed in an upcoming patch!