I have muscle memory to swipe down twice and tap a certain part of the screen to change my brightness, but instead I end up clicking on an app notification I did not want to click on. Alsp, I use Good Lock so my apps show in the way a tablet normally shows them when I go to my recents menu, but the 4 recent app icons at the bottom are gone. If I disable it, they are back. This is stupid because I want to be able to see the suggested apps because Samsung's learning system was actually good and about 80% of the time the next app I want to use is right there. Also, it broke my Sim card when I updated, now I can't make calls or texts, but somehow mobile data works. I also don't like the extra bouncing in one UI 7. Fix the UI please, or I'm downgrading to Apple.
The lock screen security method should have absolutely nothing to do with navigation bar icons. There is nothing related between them. That it works for you now that you did that may have just been coincidence. Try changing it back to the PIN and see if they go away again.
------------------------------------------------------------- Please mark any response that helped you as your solution. -------------------------------------------------------------
You'll only be able to reproduce this if you have a work profile. The update that was pushed required passwords instead of a pin in order to activate work profile. The bug is that the nav bar/gestures broke even while work profile was off so long as you didn't change lock screen security to password instead of pin. I just didn't realize I needed to do that until I tried to turn on the work profile this morning and got that message.
The pin/password work/personal profiles should still have nothing to do with the nav bar icons, as the two are totally unrelated. You could put in an error report, but in order to do that, you would have to revert back to the PIN, replicate the behavior, take a screen shot and submit the logs and upload the screen shot. You would have to submit the error report immediately after replicating the anomaly, since the logs get overwritten pretty quickly.
However, since the problem appears to have resolved itself for you, you may choose not to bother.
------------------------------------------------------------- Please mark any response that helped you as your solution. -------------------------------------------------------------
