Fix Samsung: Cannot Go Back to Original DPI/Leave Tablet Mode

I thought of bragging about my tech skills within my tech group, and it backfired in some style! One of my colleagues had a Galaxy S24 Ultra, so I asked him if I could convert his device to tablet mode, to which he straightaway replied NO. They have this weird impression about me that I am a guy who always carries out weird stuff on mobile phones [for the tech geeks, this weird stuff simply translates to flashing custom ROMs, rooting devices, using Fastboot Commands, etc].

Anyways, I managed to convince him and showed him each and every step of what I was doing. He was simply impressed the moment I enabled Developer Options [he was like “our device has this hidden menu with so many features!”]. Then I scrolled to the Minimum DPI section and first took the screenshot of the default DPI [which was 411 if I’m not mistaken]. Then I changed the value to 600, and the UI straightaway changed to the tablet mode. For once, he was genuinely impressed.

However, the issue with this mode is that only the Settings menu is usable; the rest of the stuff is unreadable. So after using it for 10-15 minutes, he requested me to change the UI back to its default state. So I went to the Developer Mode and changed the Minimum DPI back to the default 411. And that’s it. The UI should be back to the original one. Or so I thought. Even after I set the default DPI, the device was still in tablet mode.

This surprised me because I have changed DPI across numerous devices [OnePlus, Pixel, Xiaomi, and Nothing], and they all reverted to their default value as soon as I changed the DPI value. But Samsung refused to do so. Well, these types of issues have one single fix: device restart. But I was wrong once again. Even after a restart, the device was still in tablet mode. Although the DPI was showing as 411, it was still respecting the 600.

dpi changed 411 but samsung still in tablet mode - 2

DPI Changed Back to Default 411, but Tablet Mode is Still Enabled

Truth be told, this was something new for me as well, and while I was intrigued to have a new issue at my hands, he was clearly infuriated. So the time was clearly running out. Whatever fix I had to find should be done in the next 5-1 minutes. So I went through all the menus in his device and finally found out the root cause of this problem as well as the fix! And since I might not be the only one who could face this issue, I thought of documenting my findings here so that any other affected user could be helped out by this guide. So with that in mind, let’s get started.