JUMP TO SOLUTION Solved

Original topic:

One Home UI launcher keeps crashing

(Topic created: a week ago)
228 Views
Jin9
Asteroid
Options
Tablets

Information

  • Galaxy Tab S8 Ultra (SM-X900)
  • One UI version 6.1.1
  • Android version 14
  • Security Patch Level: October 1, 2024
  • Problem: One Home UI launcher

After I have installed the latest update for my tablet, the launcher keeps crashing and it's getting pretty annoying that I don't want to use the tablet.

Things I tired

  • Restarting the tablet.
  • Force Stop, Clear Data & Cache.
  • Tried another launcher (keeps crashing in the baggrund)
  • Updated everything available in Store.

Help

6 Replies
Robin621k
Honored Contributor
Options
Tablets
Have you tried a wipe cache partition?.
Power off phone, while phone is off press the power button and volume up button simultaneously. When you feel the phone vibrate let go of the buttons. You will now be the bootloader menu. Using volume buttons for navigation, power button for Yes. Scroll to wipe cache partition, press power key, scroll to yes, press power button, reboot, press power button.

Hope this helps
0 Likes
Jin9
Asteroid
Options
Tablets

It's not a phone, it's a tablet.

It won't let me access the bootloader, it just reboots again.

0 Likes
Robin621k
Honored Contributor
Options
Tablets
Absolutely, you can wipe cache partition on the Tab S8+ in the same way you do it on your phone. I do it on ny Tab S9+ all the time.
0 Likes
Jin9
Asteroid
Options
Tablets

Maybe there is a language barrier

already tried accessing the bootloader, but that device just reboots again and skips the bootloader, there for I cannot access it like do on my phone.

 

 

0 Likes
Robin621k
Honored Contributor
Options
Tablets
I don't understand why they would allow it on a Tab 9+ and not a Tab 8+!
It doesn't make sense, considering some people who own tablets, don't own a computer!
0 Likes
Solution
Jin9
Asteroid
Options
Tablets

Apparently You need to connect a PC to your Samsung before trying accessing the bootloader.

I wiped the cache partition and it seems to have fixed the problem.