In this guide, we will show you the steps to fix the issue of the Back and Home buttons not working in the Samsung Galaxy S21 series after the One UI 4.1 update. The South Korean conglomerate has recently rolled out a new software upgrade on top of their Android 12 update. This 4.1 version brings in a slew of new and intriguing features in comparison with its counterpart (4.0).
These include the likes of Smart calendar, Smart Widgets, more additions to Samsung Pay, the ability to choose how much virtual RAM you want, and the ability to use all rear camera lenses in Pro mode. However, on the flip side, this update also seems to have bought in quite a few bugs and issues, especially with the twenty-first iteration of the devices.
Many Galaxy S21 series users have voiced their concern that the Back and Home buttons not working right after they had installed the One UI 4.1 update. Add to the misery, some have also said that their device gets stuck on the black screen, and there seem to be a few missing shortcuts as well. Well, as far as the Back and Home button bug is concerned, there is a workaround that shall help you rectify this issue once and for all. So without any further ado, let’s check it out.
Fix Galaxy S21 One UI 4.1: Back and Home buttons not working
- To begin with, head over to the Settings menu on your device.
- Then go to Apps > Choose Default Apps and select One UI from the list.
- This is needed because for some users Mobile Services Manager was set as the default Home app.
- Moving on, head over to Settings > Apps and select Mobile Services Manager.
- Then hit Force Stop > OK in the confirmation dialog box.
- After that, go to its Storage section and tap Clear Data > OK to confirm.
- Once the data has been deleted, go to its Permission section.
- Finally, remove its permission for Phone and that’s it. It should resolve the issue.
These were the steps to fix the issue of the Back and Home buttons not working in the Samsung Galaxy S21 series after the One UI 4.1 update. As far as the official stance on this matter is concerned, the developers are yet to acknowledge this issue, let alone give out any ETA for the rollout of a fix. As and when any of these two things happen, we will update this guide accordingly. In the meantime, the aforementioned workaround is your best bet.