Samsung has started rolling out the One UI 6.1 update to the Galaxy devices, and as predetermined, the company gradually expanded the update to last year’s flagship devices, which include the Galaxy S23, Galaxy S23 FE, Galaxy Z Fold 5, Galaxy Z Flip 5, and Galaxy Tab S9 series.
With the One UI 6.1 update, there are several new features that have boosted the overall performance and user experience of the existing functions as well as brought some innovative functions, some of which are AI-powered ones. However, at the same time, some new issues are spotted that are running the performance experience of some good lock functionalities.
Good Lock issues arrived after One UI 6.1
According to the official in charge of Good Lock, Galaxy device users are having some issues while using different Good Lock functions. Let’s check them out.
After installing One UI 6.1, the NotoisTar UI element gets disturbed, and when using the transparent hints, it creates an issue with the keys, which are not working on the AI introduction screen starting with One UI 6.1. The screen hides the navigation bar and display buttons, but this conflicts with the Navistar option, and the area overlaps, causing a problem.
The AOD clock is now integrated with the locked screen clock and cannot be set separately, while the manual brightness setting is also removed from AOS settings, so for users who prefer separate AOS and lock screen settings, Good Lock will provide a solution through the Upcoin Always on Display and LockStar updates.
Good Lock is also not working on the flip cover screen; when the user taps the cover screen, it doesn’t get the proper response from the Good Lock function. To get rid of this problem, Good Lock Head has confirmed that it will be fixed in the next update.
With the enhancement in dictation performance, new keyboard buttons have been introduced to enable easier voice input, but at the same time, some users are reporting missing voice buttons, leaving a space instead. Samsung is actively working to replicate and resolve this issue internally.
For a temporary solution, you can disable “the keyboard buttons in navigation bar” option in the default and additional keyboard settings.