r/android_beta

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!

​

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?

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

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.

What has happened?! Running A17 beta 6 on P6P and lately after beta 3 it seems gboard vtt has been absolutely slow and horrible. Makes tons of mistakes more than before.

Anyone else experiencing similar things?

Hi Beta users,

Today we’re sending you an Android 17 QPR1 Beta 6 build CP31.260618.005 for all devices. Android 17 QPR1 has reached Platform Stability as of Beta 6. The API surface is
locked, the API diff report reflects the final changes, and you can now incorporate new Android 17 QPR1 capabilities into your apps.

Top issues fixed include:

• Users were unable to select multiple spell checker languages. (Issue #147312111)
• Pressing the device volume buttons within the Clock app failed to trigger the expected user interface actions. (Issue #527400457, Issue #527395501, Issue #524895625)
• Rapidly swiping through the media carousel caused visual glitches in the Quick Settings layout and settings icon by improving animation and layout state handling during rapid transitions. (Issue #514947195)
• An issue in WindowManagerGlobal that resulted in app crashes. (Issue #516639947)
• Enabling the Wi-Fi hotspot displayed a generic default SSID instead of the user's saved custom name. (Issue #485168823)

Please review the latest release notes for limitations and general advisories before installing the update. In addition, see top open issues for the latest list of top open issues that have been reported by developers and users.

How do I get Android 17 QPR1 Beta 6?

You can get started with Android 17 QPR1 Beta 6 today by enrolling your Pixel device. Eligible devices include Pixel 6, 6 Pro, 6a, 7, 7 Pro, 7a, 8, 8 Pro, 8a, 9, 9 Pro, 9a, Pixel 10, 10 Pro, 10 Pro XL, 10 Pro Fold, 10a, Pixel Tablet series devices. Once enrolled, eligible devices will receive an over-the-air (OTA) update to the latest Beta versions. If you were previously enrolled in Android 17 Beta (and have not opted-out), you will automatically receive QPR1 Beta 6 and any future Beta updates. 

Important for those currently enrolled in Android 17 Beta:  

• If you prefer to leave the Beta program and receive the public stable release of Android 17, you can do so without wiping your device by opting out and not installing today’s QPR1 Beta 6 update. If you opt-out of the program after installing Beta 6 or any future updates, all user data on the device will get wiped per usual program guidelines. Opting out will trigger a ‘Downgrade’ OTA. Ignore this update and wait for the Android 17 public release instead.

 

Tell us what you think

Your feedback is incredibly valuable to us. Please share your thoughts through the following channels:

• Use the Android Beta Feedback app included in Beta builds. This is the preferred method if you want to report a user-facing bug. 
• Post your comments here on our official Android Beta Program subreddit. We may not respond to posts individually, but we are actively monitoring the feedback. We’ll reach out to you directly if we need additional information.

Happy Beta testing!

I believe Android 17 supports 16kb pages but it hasn't been enabled by default by Google, likely for compatibility reasons. Rumor was that the Pixel 11 series would enable it by default from the start.

After installing QPR1 beta 6 on my Pixel 10 Pro XL though, I'm noticing a very significant improvement in app launch times and overall system response so I'm wondering if this update finally enabled it?

Is there a way to check if it's enabled, and what are your thoughts? Is anyone else noticing an abnormal improvement in snappiness and response?

None are working for me after the update, before you updated keep that in mind for those who use pixel ims

Just a new pixel factory image detected

How many of y'all are missing these features? Is there anyone on 7 that has those?

Is it just me or is beta 6 much better than 5 and 4 in terms of performance battery and heat?

windows phone link (as bad as it is) stopped updating, phone black screens on text messages or opening settings, shows (wait of cancel) timeouts on both, the settings are a web app? wtf did you bros break?

I used to be able to swipe down on the quick panel and swipe right fast it worked just fine before, I dont mine new animations at all but can we at least have interruptible animations or Parallel animations whatever they are called! I shouldn't wait for the animation to finish before I can swipe

My wife and I have PIxel 8 Pros, I'm on the 17 beta track and shes on regular stable releases. But both our devices are shutting off the wifi and not giving available network options when toggling it back on. If you toggle it on, back out of that screen and go back the wifi toggle is disabled again. What's the deal? Anyone else face this and have a solution? I did start a brief issue for it (529681541) if you want to upvote it if you have it too.

Hi everyone,

I’m using a Google Pixel 8a, and I had been enrolled in the Android Beta Program. I opted out because I want to return to the stable public version while keeping my data.

The problem is that my phone is still only offering me this update:

Android Beta Exit with Data Wipe

The update screen says it will install the latest public version of Android 16 and that all data stored on my device will be lost. The update size is 1.19 GB.

I have not installed this update because I do not want to factory reset or lose my data.

As far as I understand, Android 17 stable has now been released for supported Pixel devices, including the Pixel 8a. I was expecting the update screen to eventually change to a no-wipe stable exit update, or something like “Android Beta Exit No Data Wipe”, but it is now 1 July, and the phone is still showing the same “Data Wipe” update.

What I’ve tried:

I opted out of the Android Beta Program.

I have checked the system update several times.

I have restarted the phone.

I have not downloaded or installed the wipe update.

I have not installed any newer beta updates after opting out.

My question is:

Is my Pixel 8a stuck on the beta-exit wipe update, or do I just need to keep waiting for the stable no-wipe exit update to appear?

I would really appreciate advice on how to safely get to stable Android 17 without wiping my phone.

Thanks.

For folks who are rooted, did RCS conk out on you with the keybox bans?

It looks like on the most recent beta build, without STRONG integrity, RCS is dead, and shows the "Not Sent"

Update: The problem was beta 5, this is fixed in beta 6

I have a Pixel 10 Pro XL, and today i was going to reset mobile network settings, but it's empty.

From settings phone app, then system and reset options, there's nothing there to reset, only settings in uper left corner. Can someone test it please? Thats the only issue i have, phone is faster and smooth and no other bugs.

I have reported this bug through Android beta feedback app to the developers. Issue nº [529809848]

Thanks.