Joe Maring / Android Authority
TL;DR
- Google removed Android 16 QPR2 Beta 3 due to the risk of phones looping with desktop settings enabled.
- Users who have already installed the update are looking for solutions to escape the loop without factory reset.
- A method of plugging and unplugging USB devices has proven to be successful, but can be very slow in achieving results.
Trying beta software means accepting a certain level of risk, but how much do you really hope to risk by running a beta version of Android? Maybe Google Wallet no longer works? Does the fingerprint sensor turn off? A few app crashes, sure, but for the most part, Google still manages to give us largely functional software. That may be true, but this week was seemingly the exception that proves the rule, as Google was forced to hit the brakes on Android 16 QPR2 Beta 3 following reports of serious phone crash issues.
I don’t want to miss the best of Android Authority?
As we shared with you yesterday, QPR2 Beta 3 has a nasty surprise in store for anyone who installs it on a device that has Android desktop mode enabled: if the option is not disabled, it enters a boot loop where SystemUI crashes, preventing users from doing anything. If you haven’t already set up ADB on your PC to remotely change phone settingsit looked like you might be forced to reset your handset (and lose all your data in the process).
If you’ve been stuck in this situation for a day or so and wondering what to do next, we have good news: there is a path forward. It sounds right very boring.
Android beta users on Reddit exchanged strategies and a message from Lyneca highlights what seems to be the best approach so far. The trick is that even in this compromised state, you can briefly turn the phone screen back on by connecting some USB devices.
Specifically, by connecting a USB-C keyboard and pressing Windows key + I, Android will bring up its Settings menu. And at this point, users have to rush to scroll through this list before the screen turns off. They’re looking for the “enable secondary display features” option, and if you can turn that off, you might be able to get out of this mess. But with the screen constantly blank, it could take you an hour or more, according to these reports.
The fact is, though, that it’s possible, and especially if you’ve been a little lax with data backups, it might be time well spent. We just wouldn’t be surprised if you reconsider your interest in Android betas in the future.
Thank you for being part of our community. Read our comments policy before posting.
