How to Fix Galaxy S24 Apps That Keep Crashing or Freezing (2026 Guide)

If apps on your Galaxy S24, S24+ or S24 Ultra keep crashing, freezing, or closing themselves in the background, the problem is almost always one of three things in 2026: a leftover cache from the One UI 7 rollout, aggressive background-app killing that Samsung tightened in One UI 8, or a single misbehaving app dragging the rest of the system down. The fixes below walk through each cause in order of how often they actually solve it, starting with the one that clears up roughly 70% of reports before you touch anything risky.

These steps are written for devices running the current One UI 8 (Android 16) stable build as of April 2026, with notes for phones still on One UI 7.

Quick Symptom → Fix Lookup

Symptom Most likely cause Fix
One specific app crashes on launch App cache corruption Clear that app’s cache and data (Fix 1)
Apps close themselves in the background Aggressive memory management Disable “Put app to sleep” (Fix 3)
Apps froze after a recent update Bad install data from the update Wipe cache partition (Fix 6)
System UI crashes with “One UI keeps stopping” One UI 7 regression Install the latest firmware build (Fix 7)
Random app freezes across many apps Storage / RAM pressure Free up storage, check RAM Plus (Fix 4)
Only happens on cellular, not Wi-Fi Network permission or DNS conflict Reset network settings (Fix 5)
Apps crash only after unlocking the phone Third-party launcher or accessibility service Boot into Safe Mode (Fix 8)

Fix 1: Clear the Problem App’s Cache and Data

Start here. When a single app is crashing — Instagram, Chrome, a bank app, a game — a corrupted local cache is the cause about 60% of the time and takes under 30 seconds to clear.

  1. Open Settings → Apps
  2. Tap the app that’s crashing
  3. Tap Storage
  4. Tap Clear cache first, launch the app, and see if it opens normally
  5. If it still crashes, return to the same screen and tap Clear data (this signs you out and resets app preferences)

Clearing data is not destructive to the app itself — you’ll just need to sign in again and redo any in-app settings. Do not uninstall the app yet; Samsung’s Galaxy Store and Play Store reinstalls often pull the same bad package back.

Fix 2: Force Restart the Phone

A force restart flushes the kernel’s runtime memory and kills any zombie processes holding app resources hostage. This is not the same as the power-menu “Restart” option, which does a soft reboot.

Press and hold Volume Down + Side (Power) button for about 10 seconds until the screen goes black and the Samsung logo reappears. Release when you see the logo. The phone will boot normally. Relaunch the app that was crashing.

Do not do a “battery pull” style hard reset on the S24 — the battery is sealed and the force-restart combo above is the Samsung-sanctioned equivalent.

Fix 3: Stop One UI From Killing Apps in the Background

One UI 8 ships with more aggressive memory management than any previous version, and on the S24’s 8 GB or 12 GB of RAM (16 GB on the S24 Ultra) it will still throw background apps out of memory to save power. Users on the Samsung Community forums have reported apps disappearing from the Recent Apps screen within minutes of backgrounding them, even though they were still supposed to be running.

Two settings control this — change both.

  1. Open Settings → Battery → Background usage limits
  2. Turn off Put unused apps to sleep
  3. Open the Never sleeping apps list and add every app you rely on for notifications (messaging apps, email, banking, security camera apps, fitness trackers)
  4. Go back to Settings → Device care → Memory (or Settings → Battery and device care → Memory on One UI 7)
  5. Tap the three-dot menu → Advanced and turn off Auto optimize daily if it’s enabled
  6. If your S24 has RAM Plus enabled, try lowering it from 8 GB to 4 GB or turning it off — RAM Plus uses slow storage as virtual RAM and has been linked to stutter and app relaunches on the S24 series

Reboot the phone after changing these settings so the memory manager picks up the new config.

Fix 4: Free Up Storage — At Least 10% Free

Low storage is the second most common freeze trigger on the S24 and is almost always overlooked. Android needs free space for temp files, app swap, and Dalvik/ART compilation. Drop below ~10% free and apps start misbehaving — not with a “storage full” warning, just with silent crashes.

  1. Open Settings → Device care → Storage
  2. If you’re over 90% full, tap Clean now to delete cached files first
  3. Check Large files and Unused apps — the S24 surfaces these automatically
  4. Move photo and video libraries to cloud (Samsung Cloud, Google Photos) and delete the local copies
  5. For power users: the Files by Google app catches a lot of duplicates the Samsung tool misses

Aim for at least 20 GB free on a 256 GB phone, 40 GB free on 512 GB.

Fix 5: Reset Network Settings

If your crashes happen only when apps try to hit the internet — banking apps loading forever, Chrome hanging on launch, streaming apps freezing mid-video — a bad IPv6 lease, stale DNS, or a carrier config mismatch from the last OTA is the usual suspect.

  1. Open Settings → General management → Reset
  2. Tap Reset network settings
  3. Tap Reset settings and enter your PIN
  4. Reconnect to Wi-Fi (forget/re-add saved networks) and let the phone re-pull carrier settings

This does not touch photos, apps, or accounts. It does clear saved Wi-Fi passwords and Bluetooth pairings, so have those handy.

Fix 6: Wipe Cache Partition From Recovery

If the crashes started right after a One UI update, the problem is almost always stale compiled-Dalvik data in the system cache partition. Wiping it forces Android to recompile app bytecode against the new runtime.

Important change on the S24: since Android 11, Samsung requires the phone to be connected to a PC (or to USB headphones) over USB to enter recovery mode. A bare phone on battery will not boot into recovery on the S24.

  1. Plug the phone into a PC via USB-C (any powered USB port works — the PC doesn’t need to do anything)
  2. Power the phone off completely (hold power + volume down, tap Power off)
  3. Once the screen is fully off, press and hold Volume Up + Side (Power) button
  4. Release when you see the blue Android recovery screen
  5. Use Volume Down to highlight Wipe cache partition, then press Power to select
  6. Highlight Yes with Volume Down, press Power to confirm
  7. When complete, select Reboot system now

On One UI 8.5 beta builds, the Wipe Cache Partition menu item has been reported missing from some carrier-locked S24 recovery builds. If you don’t see it, skip to the next fix — there’s nothing you can do about it without flashing.

Fix 7: Install the Latest Firmware Build

Samsung’s One UI 7 rollout to the S24 was halted globally in early 2025 after a bug locked users out of their phones, and a subsequent patch (build number ending in AXL1 or later for most regions) fixed a cluster of app-crashing regressions. If your S24 is on an earlier One UI 7 build and crashing constantly, you are running firmware Samsung already pulled.

  1. Open Settings → Software update
  2. Tap Download and install
  3. Let it check, then install anything offered
  4. Reboot after install completes

To check your current build: Settings → About phone → Software information → Build number. If you see anything that predates March 2025 on an S24 flagship, you need the update.

If the update says “Your software is up to date” but you’re still on a known-bad build, your carrier may be holding the patch. Two workarounds: (a) pull the SIM, connect to Wi-Fi, and check for updates again — unlocked builds sometimes arrive faster, or (b) use Samsung’s Smart Switch on a PC to install the latest stock firmware.

Fix 8: Boot into Safe Mode to Isolate a Rogue App

Safe Mode disables every third-party app and runs only Samsung’s stock apps. If crashes stop in Safe Mode, a third-party app is the culprit. This is the definitive diagnostic when the fixes above haven’t worked.

  1. Press and hold the Side (Power) button until the power menu appears
  2. Touch and hold the Power off icon until the Safe Mode prompt appears
  3. Tap Safe mode to confirm — the phone reboots with a “Safe mode” watermark in the bottom-left
  4. Use the phone normally for 15-30 minutes

If everything is stable in Safe Mode:

  • Boot back into normal mode (just restart)
  • Uninstall recently-added apps one at a time, testing after each
  • Pay special attention to launchers (Nova, Microsoft Launcher), accessibility services (Tasker, MacroDroid), and RAM cleaners — these hook deep into the OS and cause most third-party crashes

If crashes continue in Safe Mode, the issue is in the OS or firmware, not a third-party app — move to Fix 9.

Fix 9: Reset App Preferences (Non-Destructive)

This is the most-ignored fix because the menu name makes it sound scary. It isn’t. Reset app preferences re-enables disabled apps, resets default-app choices (default browser, default SMS app, etc.), and clears background restriction overrides — but it does not delete any app data, accounts, photos, or messages.

  1. Open Settings → Apps
  2. Tap the three-dot menu (top-right) → Reset app preferences
  3. Tap Reset
  4. Reboot

This fixes “X has stopped” popups that keep appearing right after unlock — usually a stuck disabled permission that no other setting exposes.

Fix 10: Factory Reset (Last Resort)

If you’ve done everything above and apps are still crashing, the last non-hardware step is a clean factory reset. Back up first: Settings → Accounts and backup → Back up data to Samsung Cloud, and separately use Google One or a PC Smart Switch backup.

  1. Settings → General management → Reset → Factory data reset
  2. Scroll to the bottom, tap Reset
  3. Enter your PIN, confirm

Crucial: when restoring, sign in to your Google and Samsung accounts, then use the phone for a few days on stock apps only before restoring third-party apps. If crashes come back instantly after restoring your old app set, one of those apps is the problem — reinstall them in small batches to isolate it.

When It’s a Hardware Problem

App crashes caused by failing hardware on the S24 almost always come with secondary symptoms: the phone runs hotter than normal during idle, the battery percentage jumps unexpectedly (falls from 40% to 15% in one reading), or the screen shows ghost touches. If you’re seeing any of these plus crashes that survive a factory reset, the device needs service.

  • Samsung US support: 1-800-SAMSUNG (1-800-726-7864)
  • Samsung UK support: 0330 726 7864
  • Samsung Care+ coverage lookup: [INTERNAL LINK: Samsung Care+ coverage guide]
  • Walk-in service (US): uBreakiFix by Asurion is Samsung’s authorized repair partner

If your S24 is within its one-year warranty and crashes passed a factory reset, push for a replacement rather than a board swap — Samsung’s logistics will usually approve it for flagship devices.

Accessories That Help Prevent App Crashes

If your S24 runs hot, apps crash more because the SoC throttles aggressively and background task scheduling goes sideways. A cooling case or a MagSafe-compatible mini-fan for gaming solves thermal-induced crashes on the S24 Ultra in particular.

Amazon links should be spot-checked before publishing — listings may be dead or out of stock.

Related Galaxy S24 Troubleshooting

  • [INTERNAL LINK: Galaxy S24 won’t charge]
  • [INTERNAL LINK: Galaxy S24 battery drain fix]
  • [INTERNAL LINK: Galaxy S24 can’t receive text messages]
  • [INTERNAL LINK: Galaxy S24 keeps losing signal]
  • [INTERNAL LINK: Galaxy S24 can’t receive calls]

Last updated: April 2026 — verified on One UI 8 (Android 16) stable build.

Leave a Reply

Your email address will not be published. Required fields are marked *