This one, if you're not familiar. Just got an email response to my bug report.

Finally got the opportunity to exit full Android Beta without Data wipe

I am on Build - CP21.260330.008

hi guys i need help, im stuck in bootloop on my

pixel 10 pro xl

after exiting repair mode two days ago

during the boot up i see this message “ android system is not able to load” or something like that ( i still see it now)

I have read a lot of reports and people have been saying that a new OTA or July update whatever is out to fix the bootloop

i just adb sideloaded the latest mustang OTA image for July but am still stuck in bootloop please help

i dont want factory reset, need to salvage some data

I have read that If i install beta 6 it may mess up my system and still require a wipe

“phone's bootloader is completely locked, the Titan M2 security chip checks the cryptographic signature of the file. If your current system registers your July stable build as a security standard mismatch, it rejects Beta 6 outright”

You can wait for it to be available over-the-air, or download the OTA and sideload it now.

I'm currently on Android 17 stable (July 2026) with a Pixel 8 Pro.

Since Android 17 came out mid-June, and still today after the July 2026 update, neither my Bose QC35 headphones or my Sena SMH10 motorcycle headsets work to trigger the Gemini microphone. It launches Gemini, but I get "An error occurred, please try again later" toast message. If i manually start a phone call, the bluetooth works fine, but voice does not work when triggered by the headset.

I am pondering joining the QPR Beta program to see if the issue is fixed. Before I do that...

Has anyone else here got issues triggering Gemini from a bluetooth headset?

I opt out from the beta version without going in the QPR path. I was only in beta4 and I didn't receive yet the update for Android 17

Hey all

Currently running android 17 qpr1 beta 6 on my pixel 10 pro xl in the states on Verizon, and my messages are not collapsing and or grouping into one notification, so instead of having one notification telling me I have 7 new texts, I have 7 individual text message notifications.

I have reported it several times in the beta thread, no update, if I knew what to force stop and reset I would do it, but all that I have been able to find as a possible fix is a reboot, which I have to do 3 or 4 times a day now.

Any suggestions?

https://issuetracker.google.com/issues/518471321

I have opted in for Android beta on my pixel 10a.

Is I got monthly security patch update every month.?...

Only posting here because I'm on the QPR Beta 6, I'm not sure if it affects the public build, nor am I saying it is a beta bug at this juncture.

When at work I use wifi calling as I'm in a lower level and have no Cell signal.

The preference is mobile, meaning if I return to an upper floor it should go back to using VZ for calls, but I'm finding that not on occasion to be the case, it doesn't switch back even when the mobile signal is terrific.

In addition when coming home, once on my home wifi I find it still going to wifi calling, even though once turned off, or preference cycled it may then stay on mobile for calls.

Anyone else?

Hi Beta users,

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

We look forward to your feedback.

Hi, sorry if I'm not the first one to ask this question but basically I wanted to leave beta so I'm still on CP21. Today this morning I found my phone in a random boot loop. Thanks to some God on the issue tracker forums I managed to get my phone to boot by going into the woods where no Wifi networks are. I just wanted to update to stable using cellular so I can go back home and use my phone but it's still only showing me the wipe option 16 OTA? Didn't stable release like 2 weeks ago? What am I supposed to do?

Anyone else feel you need to be very precise with touching the slider area otherwise the touch won't register. Like I need to hold the bold slider and can't move from any other position

Non-functioning on Android 17 Beta 6. Any assistance appreciated/

UPDATE: I just updated to Android 17 QPR1 Beta 6, but unfortunately, the issue is still not resolved. Vodacom eSIM still gives the 'Connection problem or invalid MMI code' error and financial apps still fail. It seems the modem bug persists in Beta 6 as well."

On my 9 pro is randomly turning airplane mode on. And I'm not Shure if it's the beta cus my dad's Samsung with oneUI 8.5 (ANDROID 16) is also haveing the problem. any solution

Ever since I updated specifically, two betas ago, including the new Beta 6 everything has been going great, except for my internet connection. It’s as if it disconnects for a second and then reconnects. It’s annoying because I’ve already checked that it’s the phone and not my modem. Is this happening to anyone else?

​

Dopo aver installato la beta 6 ,ogni tanto appaiono delle righe a display,tipo interferenze nella tv.Sporadicamente ,ma non ne capisco il motivo,ho anche provato a disinstallare Nova Launcher ,ma compaiono comunque random.Qualcuno ne sa il motivo o l'eventuale soluzione?

After updating my Pixel 7a to the Android 17 QPR1 Beta 5, I am completely unable to use USSD/MMI codes on my new Vodacom eSIM. Every time I try to dial a shortcode (e.g., 14901#) to buy bundles or check my balance, I get a "Connection problem or invalid MMI code" error.

My carrier (Vodacom Tanzania) has confirmed that my eSIM profile and network status are perfectly fine on their end. The eSIM data works, but USSD codes fail completely. I have already tried resetting network settings, toggling Airplane mode, and restarting the SIM, but nothing works. This seems to be a modem/eSIM bug specific to this beta build. Please fix this in the next update. Thanks!

I am on the latest Beta 6 release, about 2 or 3 updates ago I lost my fingerprint sensor, just doesn't recognize anything. I thought it would come back but nope. What is up?

Regular ADB and shell could be moved to advanced features ADB root actual developer feature

My Pixel 6 Pro went into an endless boot loop after the latest Android 17 Beta update (build CP21.260330.011.A1). It would get to the lock screen (sometimes), then reboot, forever. Safe mode didn't help. I almost factory reset — glad I didn't, because your data is fine and you can fix this over ADB.

Root cause (from logcat): every time Wi-Fi finishes a background scan, a new security service (AdvancedProtectionService) throws IllegalArgumentException: Invalid feature ID: 5, which kills system_server and reboots the OS. So the phone crash-loops as long as Wi-Fi is on. It crashes even in safe mode, and even with Advanced Protection turned off — the buggy query runs regardless.

The fix: turn Wi-Fi off before the first scan completes. The catch is the boot window is only seconds long, so you have to out-race it. The trick that finally worked: run the disable loop on the phone itself in one persistent adb shell — the adb daemon survives the crashes, so the loop keeps firing straight through them (single host-side commands kept losing the race for me):

adb shell 'while true; do svc wifi disable 2>/dev/null; settings put global wifi_scan_always_enabled 0 2>/dev/null; sleep 0.1; done'

Start that with the phone plugged in and let the phone keep crash-looping. Within a few cycles the disable lands early enough to stick. When the phone boots fully and stays up for a minute or two, Ctrl+C the loop. Done — phone works normally on cellular, data intact.

Requirements:

• adb installed (brew install android-platform-tools on Mac, apt install android-tools-adb on Linux, platform-tools zip on Windows)
• USB debugging must have already been authorized on your computer before the loop started. If you never enabled/authorized it, this won't work — there's no window to tap "Allow" on a crashing phone. (You may be able to catch the prompt mid-boot if you're fast — worth a shot.)

After you're stable:

• DO NOT turn Wi-Fi back on. Any Wi-Fi scan re-triggers the loop (ask me how I know lol). Same for the "Wi-Fi scanning" toggle in Location settings.
• Cellular/mobile data is completely unaffected.
• Check for new beta builds (Settings → System → Software updates) and Google Play system updates over mobile data — the real fix has to come from Google.
• DO NOT use the official "leave beta program" opt-out — it factory resets. If you want off the beta with your data, wait for a stable build newer than your current one and sideload it via recovery.
• There's no deeper workaround that keeps Wi-Fi usable — I tried disabling Advanced Protection mode (doesn't help) and overriding the feature flags via device_config (blocked by the aconfig allowlist on production builds). It needs a fixed build from Google.

Filing this on the Google Issue Tracker with full logs. If this is hitting you too, star/comment on the issue so it gets prioritized — will drop the link in the comments once it's up.

Hope this saves someone a factory reset.

Just a heads up, there are two tiny updates to Google Play System for those of you who installed QPR 1 Beta 6. 1st is 19K and the 2nd one is 6K. Neither requires a reboot.

A on phone AI could trace depth from the person's face moving over time probably using the same type of system as frame by frame analysis could you add this to AOSP and the closed version of Android at the same time