To Fix The Problem Of “Unfortunately, TouchWiz Home has stopped”
Samsung has been facing a lot of complaints about their TouchWiz Home launcher which has been slowing down their devices. The TouchWiz Home tends to lag and is not very responsive.
A common issue that happens with the TouchWiz Home Launcher is what is known as force stop error. When you get the force stop error, you will get a message that “Unfortunately, TouchWiz Home has stopped.” If this happens, your device hangs and you’re going to need to restart it.
The simplest solution to get rid force stop error and the other issues is to get rid of TouchWiz and just find and use another launcher from the Google Play Store, but if you do that you will lose the stock touch, feel and look of your Samsung device.
If you don’t feel like getting rid of TouchWiz, we have a fix you can use for the force stop error. The solution we’re going to give you will work on all of Samsung’s Galaxy Devices regardless of whether it is running Android Gingerbread, JellyBean, KitKat or Lollipop.
Fix “Unfortunately, TouchWiz Home has stopped” On Samsung Galaxy
- Boot your device into safe mode. To do so, first turn off it of completely then turn it back on while keeping the volume down button pressed. When your phone boots up completely, let go of the volume down button.
- On the bottom left, you will find “Safe Mode” notification. Now that you are in safe mode, tap the app drawer and go to settings app.
- Open the application manager and then go to Open all applications > TouchWizHome.
- You will now be in TouchWiz Home settings. Wipe data and cache.
- Reboot device.
If the first method does not work for you, try this second method which requires you to wipe your device cache.
- Turn your device off.
- Turn it back down by first pressing and holding down the volume up, home and power keys. When the device boots up let go of the three keys.
- Use volume up and down to go to the Wipe Cache Partition and select it by using the power key. This will wipe it.
- When the wipe is through, reboot your device.
Have you fixed this issue in your Galaxy device?
Share your experience in the comments box below.