Wait — is it really a surprise to find pre-release versions of Android aren't quite perfect yet?
This past week, Samsung surprised many of us by dropping its first One UI 4 beta, based on Android 12, well ahead of the stable code drop from Google. At the time of writing, we're not expecting Pixel phones to get stable Android 12 until early October. As such, the early version available to Galaxy S21 owners right now is ... well, kind of a mess. Performance issues and bugs aplenty reveal that the current One UI 4 build is further away from stable status than previous Samsung betas, which on the whole have been relatively stable. So if you want to try Android 12 on Samsung's best Android phones, you might want to hold off for a more reliable build.
The same pattern is apparent in the Android 12 public beta for Pixel phones. Fairly serious bugs remained right up to the current beta 5 build. And even that version still has obvious user-facing issues, like the broken "at a glance" widget and Bluetooth performance bugs. Previously, betas 3 and 4 featured broken visuals around the Google search bar in the app drawer, becoming a running joke among Android watchers.
It's a far cry from Android 11 and Android 10, which were basically daily-driver-ready around the time of their July betas in previous years. And by the time we got to August, beta program builds were basically release-ready, with the eventual over-the-air updates to stabilize usually weighing in at just a few megabytes.
Android 12 isn't like most Android updates, though. On Pixel phones, it brings the most significant UI overhaul since the introduction of Material Design in 2014. Material You touches every part of the interface on a Pixel phone, and Google also has to update its apps to fit with the new design language. Google is monkeying with the System UI much more than, for example, it did while jumping from Android 9 to Android 10 in 2019. So it stands to reason that more user-facing changes will result in more user-facing bugs.
That said, the beta program has already lasted longer than any recent Android version, and Google has played fast and loose with the definitions of the most recent preview build. Beta 5 is supposed to be a "release candidate," which in software development means it's ready to ship, save for some final testing. Yet this build also comes with a "known issues" section in its release notes, along with the aforementioned UI bugs, which is not something you'd expect to see in a release candidate.
Given that Android 12 on Pixel phones still has stability issues, perhaps we shouldn't be surprised that early builds of One UI based upon it are similarly imperfect.
Anshel Sag, senior analyst at Moor Insights & Strategy, told Android Central we shouldn't read between the lines too much.
"I think it's fine if they drop the betas early, maybe it will help them figure out bugs sooner and not have to fix them at launch," Sag said. "I think that a lot of people's expectations for betas are sometimes too high, and we need to remember that they exist to help work out bugs."
That's particularly true for Android enthusiasts — we often treat the beta program as a convenient way to get to play with new Android features ahead of the masses, without remembering why those features aren't generally available yet. There's an ever-present trade-off between access to cool new stuff early and potential side effects on day-to-day usability, especially if you're installing beta software on your primary (or only) device.
Rumors of an "Android 12.1" coming soon in the wake of regular old Android 12 aren't too much of a surprise either, considering the trajectory of this version of Android. "Point" versions of Android generally mean a new API level from Google — the code targeted by developers when they're making apps. Given Android 12's fairly lengthy development cycle, it's not shocking to find some changes originally planned for version 12 not making the cut.
Nevertheless, if an Android 12.1 does emerge late this year, this would be the first time since 2017 that Google pushed out a point release of the OS. Back then, Android 8.1 Oreo supplemented the significant changes in 8.0, adding APIs for neural networking, wallpaper colors, and shared memory — all relatively minor updates.
While the current Android 12 betas may be far from perfect, that's precisely why they're betas. Google still has a few more weeks to give the new version a final coat of polish, and when it does, that'll be the time to pass the final judgment on Android 12.
Alex is global Executive Editor for Android Central, and is usually found in the UK. He has been blogging since before it was called that, and currently most of his time is spent leading video for AC, which involves pointing a camera at phones and speaking words at a microphone. He would just love to hear your thoughts at email@example.com, or on the social things at @alexdobie.
I've noticed One UI seems very jittery compared to Nova7's relative smoothness in the One UI 4 beta. No real problems on my end. Though pulling down the notification shade looks really jankey. It's only beta 1.
They will iron out some of the bugs using the beta testers er pixel 6 users lol.
So true! Google is nothing but a hugh beta machine. If you don't like being a beta tester, stick with Apple... 🤣
Yeah, iOS never has any issues. /sarcasm
So true! It's not like there was a MASSIVE zero day exploit less than a week ago or anything... Lol.
It's also not like Apple always ends up having to release fifty-eight quick fixes after they launch a new iOS, amirite?
Of course At a Glance and the search bar are going to still be broken, Android 12 is going to bring lots of new functionality to both. The search bar in the app drawer is being changed to a newer one that allows for searching for more stuff in your phone. People with old broken search bar just haven't had their device switch over to the new search bar (most likely due to still trying to do final testing on the new system). I have the new search bar and it's showing up perfectly and works perfectly for me. The same goes for the At a Glance. They're adding the ability for the widget to show a lot more than it can already do, and just isn't fully implemented just yet. While annoying, it's not exactly a huge issue, and will more than likely be fine once full release comes about.
Google makes little to no money from Android per se. Why then do they feel compelled to make a new version every year? How often does Microsoft make a new version of their OS...every ten years or whatever?
Maybe Google should spend some real effort on making the current version BUG FREE before they make a newer, buggier version available!!! This whole update cycle is turning into a very sick joke! The same goes for SOC's too.
Yeah, because Windows is well known for its lack of bugs. Always good to hear from people who don't understand the first thing about computer science, though.
I've been saying this for years. I'll take it a step further and say I don't think they should release a new phone every year. Why not wait till they have new tech to release and not give us minor speck bumps. The market is shifting that way anyway.
I had to uninstall the beta. The graphical inconsistencies aren't the issue. And this article spends a lot of time saying/suggesting those are the only complaints. My phone was soft bricked for hours. Eventually it came back to life on its own at which point I uninstalled the beta immediately. System Process error did it to my device. Pixel 5. Android 12 beta 5. I've been using Android betas for years and never have I seriously thought of uninstalling. No less actually did it. These bugs are SUPER ROUGH for this stage. These are beta 1 type bugs.
Get the best of Android Central in in your inbox, every day!
Thank you for signing up to Android Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.