Some Google Pixel users on Android 12 beta say opening Settings > Accounts page crashes devices, issue escalated

A few days ago, Google introduced us to its next version of Android, Android 12, at Google I/O 2021. However, the swanky new version of Android is still in its infancy.

Now, a bunch of devices across various OEMs in the Android ecosystem are set to take part in the Developer Preview Program and the first build, Developer Preview 1, is available for these devices.

Google Pixel 5

Of course, Google’s own Pixel devices are a few steps deeper into the development cycle with the public beta 1. As expected, this is still a pretty buggy build and might still be missing a number of the features that will end up in the final builds later this year.

That said, these builds are still expected to work to some extent as they should still be usable by developers who need to test out their apps and services for the new version of Android, along with enthusiasts who can’t wait to try out this build, right?

Well, it is coming to light that this initial public beta has a pretty serious issue on Google Pixel devices that makes it impossible to perform certain tasks in the user interface.

Google Pixel Settings - Accounts crashes

A section of Pixel device owners who updated their devices to this Android 12 beta build reports that their devices crash when they go to access Settings > Accounts section on their devices.

I have the same Settings crashing issue and want to add some détails, I Just update to Android 12 SPB1.210331.013 from latest android 11 on my Pixel 4a(5G) Hardware Version MP1.0. I’m using Work Profile, I’ve test with Work profile On and Off -> same issue. I’ve removed all external Apps that can show an account (twitter, Amazon, Github,WhatsApps, etc). I send a logcat file with crash log for settings apps. I’ve also send a crash report from phone.


Interestingly, this issue doesn’t seem to affect all Pixel devices. The majority of the reports are from users of the Pixel 4a (sunfish) and Pixel 5 (redfin) while users of Pixel 4 XL (coral) seem unaffected, at least according to reports.

This has since been brought to the attention of Google in the Issue tracker forum and now, Google says it is looking into this as the development team has been notified.

passed to development team

We have passed this to the development team and will update this issue with more information as it becomes available.

It is commendable to see an OEM swinging to action this fast and we shall continue to keep an eye on this and update as and when we get more info so stay tuned.

NOTE: We have these and many Google stories in our dedicated Google section.

PiunikaWeb started as purely an investigative tech journalism website with main focus on ‘breaking’ or ‘exclusive’ news. In no time, our stories got picked up by the likes of Forbes, Foxnews, Gizmodo, TechCrunch, Engadget, The Verge, Macrumors, and many others. Want to know more about us? Head here.

Want to work for PiunikaWeb and enjoy best-in-industry compensation & benefits? You'll be glad to know we're hiring experienced candidates.

Clinton Madegwa

A cybernaut grasping at all things tech. Lover of Android, Linux, and custom ROMS. A nerd, a writer, an avid reader.