Samsung Android 11 (One UI 3.0) update poor benchmark performance acknowledged, fix allegedly in the works
Samsung has begun rolling out the Android 11 update for several smartphones from its portfolio. The Galaxy S20 series were the first phones from the company to pick up the new Android version.
Following suit, devices such as the Galaxy Note 20, Note 20 Ultra, Galaxy S20 FE, and Galaxy S10 Lite started receiving the One UI 3.0 update based on Android 11.
Recently, the company also kick-started the One UI 3.0 beta for the Galaxy A51 5G in South Korea and the Galaxy M51 in India.
One UI 3.0 based on Android 11 brings a ton of new features and improvements to Samsung phones. Further, the new skin comes with a fresh coat of paint which has left many fans with mixed feelings.
Of course, like most other major software updates, One UI 3.0 also brings a few bugs and issues that may have slipped passed the internal and public testing phases such as the navigation gesture issue.
And now that Samsung has begun rolling out the Android 11 update in multiple regions to the public, it seems some have begun noticing a strange performance issue.
According to users, the benchmark scores are considerably lower for their phones after installing Android 11 on their Samsung phones. We’ve shared an example of this below tested by a user with the Galaxy S20+:
As you can tell from the screenshots above, most benchmark scores are worse on the Samsung Galaxy S20+ running on Android 11 than when the device was running on Android 10.
Naturally, some users have raised concerns on Samsung’s community page and it seems one individual even sent the device logs to Samsung in order to assist the developers in figuring out the issue.
In response to the user’s feedback on the issue, a moderator in charge of system performance has claimed that the internal analysis results point towards the issue being caused by Android 11 itself.
Further, the moderator also mentioned that Samsung will fix the problem and will release an update in the latter half of January.
Matter of fact, a report did highlight the same issue on Google Pixel phones running on Android 11 back in October.
While Google did not issue a statement on the matter publicly, now that Samsung has confirmed the existence of the problem, it’s likely that it may be fixed on all affected devices soon, including non-Samsung phones.
We will continue to track the situation and will post an update once more details are available. In the meantime, you can head here to know more about other bugs and issues that come with the One UI 3.0 update.
Moreover, you can keep an eye on our dedicated tracker to know more about the One UI 3.0 update and its rollout details on all eligible devices by heading here.
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.