We’ve been early adopters of the One UI 7.0 beta, which started rolling out earlier this month in select markets. In fact, we installed the first beta the moment it became available. We followed the same course during the One UI 7.0 beta 2 rollout. This approach helps us discover all the new features (and bugs) before the stable version rolls out.
Bugs are to be expected, of course — after all, it’s still beta software. One issue that stood out is a lock screen widget bug we encountered in One UI 7.0 beta 2. This indeed affects usability and throws off the aesthetics. It’s still too soon to blame Samsung, and we’re hopeful that this lock screen bug will be ironed out by the time the stable One UI 7.0 release.
There’s a weird lock screen bug in One UI 7.0 beta 2 messing with aesthetics and usability
In One UI 7.0 beta 2, there seems a bug when interacting with the lock screen: the widgets sometimes blend into the wallpaper. This creates a messy, unpolished look that throws off the overall aesthetics. The blending effect also makes it hard to distinguish the widgets from the background. Interestingly, this problem wasn’t present in One UI 7.0 beta 1, so it was likely unintentionally introduced with the second beta rollout.
But the problems don’t stop there. The fingerprint sensor icon and lock screen message (for displaying custom text or contact info) don’t properly adapt to light mode. This is a pretty big oversight, even for a beta version. Ideally, these elements should turn white to better match the lock screen’s theme.
Minor quirks, but they matter
These might seem like minor quirks, but in the grand scheme of things, inconsistencies like this can spoil the experience — especially when you’re running a beta on your primary Galaxy device. I’ve said it before: it’s usually not worth the hassle to swap out your phone’s stable OS for a beta.
However, if you’ve taken the plunge, be sure to report the issue using the Samsung Members app. In addition, provide detailed feedback so that Samsung knows exactly what went wrong in the latest beta.
