"Unfortunately, Launcher3 Has Stopped": How to Fix It (Including After an Android Update)

Quick answer: “Unfortunately, Launcher3 has stopped” means the app that draws your home screen crashed.

It is a software fault in one app — not a virus, and not a sign that your photos, messages, or accounts are gone.

Restart your phone first.

If the error returns, clear the launcher’s cache (harmless), and only then clear its data (which resets your home screen layout but does not uninstall your apps).

Your phone is still working underneath the error.

The launcher is a single app, and when it crashes, everything else — your files, your accounts, your installed apps — stays intact.

Most people fix this in the first two steps below.

Before you touch anything: take a photo of your home screen with another device, or screenshot each page if you still can.

Some fixes further down reset your icon and widget arrangement, and a reference photo turns a 30-minute rebuild into a 3-minute one.

Quick fixes to try first

Work down this list in order and stop as soon as the error goes away.

The steps are deliberately ordered from zero-risk to higher-risk.

Restart the phone — clears the crashed process; fixes most one-off crashes.
Nothing is lost.
Dismiss the dialog and open the notification shade — swipe down from the top; if it opens, tap the gear to reach Settings.
Install pending system and app updates — a follow-up patch may already exist, especially after an upgrade.
Clear the launcher’s cache — temporary files only; your layout survives.
Force stop the launcher — then press home to relaunch it cleanly.
No data is affected.
Clear the launcher’s data — fixes persistent crashes; resets layout, folders, and widgets (apps stay installed).

If you got here from a search and just needed the fix, that list is the whole answer.

The next section explains why it happens so you can jump straight to the step that matches your situation — after that comes the full background: what Launcher3 actually is, what to do when the crash loop blocks Settings entirely, and how to handle the specific case where everything worked fine until an Android upgrade.

Diagnose it in 60 seconds

Three quick checks tell you exactly where to focus — so you fix the right thing instead of trying everything.

Check 1: Is it your launcher, or Android System UI?

The home screen and the system chrome around it are drawn by two different apps, and they fail differently.

Android System UI (com.android.systemui) is a separate, persistent system process that provides the status bar, the notification shade, the lock screen, and the navigation bar.

Your launcher provides the home screen, app drawer, and home-screen widgets.

Fixing one will not fix the other.

What you observe	Most likely culprit	Where to focus
Home screen goes black or blank, icons and widgets vanish, but the status bar and notification shade still work	Launcher	Follow this guide
Status bar disappears, notification shade won’t pull down, navigation gestures or buttons die, lock screen misbehaves	Android System UI	Troubleshoot System UI, not the launcher
Error names your launcher explicitly (“Launcher3,” “One UI Home,” “System Launcher”)	Launcher	Follow this guide
Error says “System UI isn’t responding” or “com.android.systemui has stopped”	Android System UI	Troubleshoot System UI, not the launcher
Both fail together, phone reboots on its own, crashes appear across many unrelated apps	Wider system or storage problem	Check storage first, then update status

If the table points you at System UI, clearing launcher data will not help and will cost you your home screen layout for nothing.

Stop here and troubleshoot the right component.

Check 2: Which of these five causes matches?

Every launcher crash is one of a small set of underlying problems:

Corrupted launcher data. The home-screen database the launcher reads on startup is damaged — the single most common cause, and the reason clearing data fixes so many cases.
Very low free storage. A launcher that can’t write its own database crashes on load, every time, no matter what else you try.
A conflicting third-party app. Icon packs, theme engines, widget suites, and live wallpapers hook directly into the launcher; a second launcher app fighting for the home-screen role does the same.
Stale data after an Android upgrade. The new launcher version chokes on a database written by the old one — the classic “worked fine until the update” case.
A bug in the shipped build. Least common, but real — especially in early rollouts on devices outside the manufacturer’s main test matrix.

Matched your situation? Jump straight there: corrupted data → Step 5; low storage → Step 6; conflicting app → Step 7; second launcher conflict → Step 8; started after an upgrade → the after-update section.

Check 3: Where are you in the process?

You can’t reach Settings at all → use these routes back in, starting with the notification shade.
Safe Mode is stable but normal mode isn’t → a downloaded app is responsible.
Remove recent installs one at a time, starting with icon packs, themes, widgets, and cleaners.
Safe Mode crashes too → not a third-party app.
Focus on storage, system updates, and the launcher itself (Step 6, Step 2).
Clearing data fixed it, but only temporarily → something is re-corrupting the launcher.
Check free storage, then test Safe Mode to find the conflicting app.
Clearing data fixed it but reset your home screen → expected outcome.
Rebuild from your photo and watch for a week before concluding it is solved.
A restart fixed it → nothing further needed.
Install pending updates and monitor — a single crash is not a pattern.
Otherwise → work the 10 steps in order, stopping as soon as the crash is gone.
Nothing has worked → back up fully, then read the factory-reset section and contact your manufacturer’s support.

What “Launcher3” actually is

A launcher is an ordinary Android app with one job: draw the home screen, the app drawer, the wallpaper, and the widgets that sit on your home pages.

Android does not hard-code a home screen.

It hands that role to whichever app is registered as the default home app.

Launcher3 is one specific implementation of that app.

It lives in the Android Open Source Project as the package com.android.launcher3, and its source is published openly in Google’s AOSP repository.

Its build configuration explicitly declares that it overrides the older Home and Launcher2 packages — it is the modern AOSP reference launcher that replaced them.

Why this matters:

Not every Android phone uses Launcher3. Manufacturers are free to ship their own launcher instead, and most large ones do.
A Samsung Galaxy typically runs One UI Home.

A Google Pixel runs the Pixel Launcher.

Motorola, Xiaomi, and OnePlus devices ship their own home-screen apps under their own names.
Seeing the literal name “Launcher3” is itself a clue. The unmodified AOSP name most often surfaces on devices running an AOSP-based or lightly customized build: custom ROMs, some budget and regional handsets, Android tablets and TV boxes from smaller manufacturers, emulators, and developer builds.
If your error says something else — “Unfortunately, Launcher has stopped,” “One UI Home keeps stopping,” “Pixel Launcher isn’t responding,” “System Launcher has stopped” — you have the same class of problem with a different launcher app.
Every fix in this guide still applies; only the app name you look for in Settings changes.

How to tell which launcher your phone actually uses

Open your Settings app and look for the default home app.

Depending on your phone and Android version, the option may be under Settings > Apps > Default apps, Settings > Apps & notifications > Default apps, Settings > Home screen, or a similarly named menu.

These paths move between versions — Google’s Pixel docs note some appear only on Android 14 and later.

Whatever name appears as the current Home app is the app you will be clearing the cache and data for in the steps below.

Tip: Launchers are often hidden as system apps — on Samsung tap Filter and sort > Show system apps; other brands hide it behind a three-dot “Show system apps/processes” menu.

Will any of this delete my data?

Read this before running the steps: these six actions sound similar but differ enormously in consequence.

Action	What it actually does	Risk level
Restart	Shuts down and relaunches every running process. Changes no stored data at all.	None
Force stop	Kills the app and its background services immediately. Settings and saved data are untouched; the app simply starts fresh next time.	None
Clear cache	Deletes the app’s temporary working files. Google describes this as removing temporary data that the app will rebuild on its own.	None to your content
Clear data / Clear storage	Resets that one app to its factory state. Samsung’s documentation puts it plainly: the app returns to default settings and personal settings saved in the app are removed. For a launcher, that means home-screen layout, folders, widget placement, icon arrangement, and launcher preferences.	Resets launcher settings only
Reset app preferences	System-wide reset of app preferences, not app content. The on-screen confirmation dialog lists exactly what it covers on your device — typically disabled apps, disabled notifications, default apps for actions, and background-data and permission restrictions — and states that no app data is lost.	Low; resets defaults you may need to re-pick
Factory reset	Erases the entire device. Google states directly that a factory data reset removes all data from your phone and uninstalls all apps and their associated data.	Total data loss — back up first

Two points worth stating explicitly, because the internet routinely gets them wrong:

Clearing launcher data does not uninstall your apps. They stay installed in the app drawer — you lose only the arrangement: icon positions, folders, widgets.
Photos, messages, contacts, accounts, and logins are unaffected.
Clearing launcher data is not risk-free either. Years of curation deserve a photo first.
One exception: Samsung notes some system apps can’t have data cleared — a greyed-out Clear data button is expected behavior on some devices, not a fault.

Skip ahead.

Step-by-step fixes, safest first

Paths below are patterns, not exact taps — settings differ by manufacturer and version, and your manufacturer is the authority for your device.

Step 1: Restart the phone

Hold the power button and choose Restart, or hold power until the device cycles.

On many recent phones the power menu needs Power + Volume up instead, since a short press triggers the assistant.

Do this first, every time — a cleanly restarted process often never crashes again.

If the error is gone, jump to prevention.

Step 2: Check for system and app updates

Especially valuable after an upgrade — manufacturers often ship a follow-up patch within days of a major release.

System update: look under Settings for System update, Software update, or a similarly named entry.
The location varies — it may sit under System, About phone, or at the top level.
App updates: open the Google Play Store, tap your profile icon, then Manage apps & devices, and update anything pending.
Pay particular attention to Android System WebView, Google Play services, and the Google app — all three render content inside other apps and are common sources of downstream instability.

Step 3: Clear the launcher’s cache

The lowest-risk targeted fix.

Find your launcher (enable “Show system apps” if needed), open its storage screen, and clear the cache — on Pixel: Settings > Apps > See all apps > [the app] > Storage and cache > Clear cache; on Galaxy: Settings > Apps > [the app] > Storage > Clear cache.

Restart and test.

Step 4: Force stop the launcher

On the same app info screen, tap Force stop — this kills the app and any background services stuck in a bad state.

Press home to relaunch it cleanly.

Step 5: Clear the launcher’s data

The fix for most stubborn crashes — and the first step with a real cost.

A corrupted home-screen database classically crashes the launcher the instant it loads, and wiping that database is precisely what this does.

Photograph your home screen first, then choose Clear storage or Clear data on the same screen and confirm.

Expect a default home screen afterward: your apps are all still installed; you’re rebuilding the arrangement, nothing more.

Restart the phone.

Step 6: Check your available storage

A nearly full device causes crashes that look like app bugs — Google’s Pixel docs warn problems begin below 10% free storage.

Check Settings > Storage; if you’re under that, clear space (large videos, unused apps, downloads) and retest.

A launcher that can’t write its own database keeps crashing no matter how often you clear it.

Step 7: Look at recently installed or updated apps

Some app categories hook directly into the home screen and destabilize launchers: icon packs, theme engines, widget suites, live wallpapers, and “cleaner”/“booster” utilities that aggressively kill background processes.

If the crash began within a day or two of installing or updating one, uninstall it and retest first.

Step 8: Check for a second or disabled launcher

If two apps both think they’re the home screen, they fight — and the loser crashes.

A real, community-verified cause almost no guide mentions: a manufacturer launcher conflicting with a second launcher (carrier app, setup leftover, “Google Now”-style app).

Re-enabling or removing the spare stops the crashes.

In Settings > Apps > Default apps > Home app, confirm exactly one launcher is default.

Then scan the full app list (show system apps) for any other launcher — disable one you don’t use, or uninstall its updates.

Conversely, if a “cleaner” or debloater disabled your preferred launcher, re-enable it here: a disabled home app produces exactly this crash loop.

Step 9: Reset app preferences

For when the launcher seems fine but the system won’t reliably launch it — e.g., the home button does nothing, or the wrong app keeps claiming the home role.

Find Reset app preferences in the Apps screen’s three-dot menu and read the confirmation dialog first.

You’ll re-pick defaults (browser, dialer) afterward.

Step 10: Switch to a different launcher

If the launcher is genuinely broken with no patch in sight, a different one restores a working home screen immediately.

Install a well-reviewed launcher from the Play Store (Nova, Niagara, and Microsoft Launcher are well-known options), press home, and select it — or set it under Settings > Apps > Default apps > Home app.

This is a workaround, not a repair: a usable phone today while you wait for a manufacturer fix.

If crashes started right after installing a third-party launcher, you may not need a new one: in its app info choose “Clear defaults” (or uninstall it), then re-set your built-in launcher as default.

Safe Mode disables third-party launchers — which is why the crash often vanishes there and returns on normal boot.

Warning: install launchers only from the Play Store or another trusted official store — never sideload a launcher APK from a random site.

A home-screen replacement runs with broad access to your phone usage; an untrustworthy one is far worse than the crash.

Why this often starts right after an Android update

Many people searching this error add “after update” — the pattern is real enough for its own section.

But timing is a hint, not proof: an upgrade changes many things at once, and it’s also when latent problems (full disk, abandoned apps, aging theme engines) finally surface.

Plausible mechanisms, in rough order of how often they explain the symptom:

Stale launcher data against new code. The upgraded launcher reads a home-screen database written by the previous version.
If a migration handles some edge case badly, the launcher can crash on load, every time, until that data is cleared.

This is why Step 5 resolves so many post-update cases.
Storage pressure during the upgrade. Major updates consume significant space and leave residue behind.
A device that was comfortable before can be over the line afterward.
Third-party apps built against the old version. Icon packs, theme engines, and widget providers integrate tightly with the launcher, and are the most likely to break against a new major release — especially if the developer has stopped maintaining them.
Updated shared system components. Android System WebView, Google Play services, and the Google app update independently of the OS.
A mismatch immediately after an upgrade can destabilize apps that depend on them.
A genuine bug in the shipped build. It happens, particularly in early rollouts of a major version and on devices outside the manufacturer’s primary test matrix.

In order: check for a follow-up system update; update WebView, Play services, and the Google app; clear launcher cache, then data; check free storage; test Safe Mode.

If the build is recent and nothing works, search your manufacturer’s support site and forums for your exact model and build number — a widely reported bug will be visible there, and the right move is waiting for the patch while using a different launcher.

What to do if you can’t open Settings

The hardest version: the launcher crashes on load, so there’s no home screen to tap Settings from.

Try these routes in order (availability varies by device).

The notification shade. Swipe down from the very top of the screen.
It is drawn by System UI, not your launcher, so it usually still works.

Tap the gear icon to open Settings directly.
Quick Settings. Swipe down twice for the full panel.
Long-pressing certain tiles jumps straight into the matching Settings page.
Recent apps. Swipe up and hold from the bottom, or press the recents button.
If Settings was open recently, resume it from there.
Via the Play Store. If you can open the Play Store, search for the launcher, and its store page may offer a route into app info.
You can also install an alternative launcher from here, which gives you a working home screen immediately even if you fix nothing else.
Safe Mode. Third-party apps are disabled, which frequently produces a stable enough home screen to reach Settings and do the real work.
See the next section.
Dismiss and move fast. If the dialog reappears on a timer, tap OK and immediately swipe down — you often have a usable second or two per cycle.

If none of these work and the device is unusable, contacting your manufacturer’s support is the right call — not a last resort.

Using Safe Mode to find a conflicting app

Safe Mode starts Android with only preinstalled software — everything you installed is temporarily disabled.

If the issue disappears in Safe Mode, a downloaded app is the likely cause (per Motorola’s support docs).

It’s a diagnostic, not a repair:

Crash stops in Safe Mode → a downloaded app is implicated.
Exit, then uninstall recently added or updated apps one at a time, restarting and testing after each.

Start with icon packs, themes, widgets, live wallpapers, and cleaner utilities.
Crash continues in Safe Mode → third-party apps are not the cause.
The problem is in the launcher itself, in system components, or in storage.

Return to Steps 3 through 6.

Important for launcher problems specifically: Google’s documentation notes that Safe Mode removes some home-screen widgets, and recommends screenshotting your layout beforehand so you can restore it.

That warning matters more here than in most troubleshooting, since your home screen is the thing you are trying to save.

No universal method exists — these are documented brand-specific examples:

Samsung Galaxy (per Samsung’s US support): press and hold the Power and Volume down buttons together, then touch and hold Power off and tap Safe mode.
Xiaomi and Redmi (per Xiaomi’s support FAQ): power the device off, press and hold power to start it, and when the logo appears, release power and hold Volume down until it finishes booting.
“Safe mode” appears in the lower-left corner.
Motorola (per Motorola’s US support): Motorola publishes a dedicated Safe Mode page for its devices; to exit, hold Power + Volume up and tap Restart.
Google Pixel: Google publishes step-by-step Safe Mode instructions in Pixel Help.

If your brand isn’t listed, search your manufacturer’s support site for “safe mode” plus your model.

Don’t guess forum button combos — some open recovery or a factory-reset prompt instead.

Exit by restarting normally.

Manufacturer differences that change these steps

Settings vary by phone — your manufacturer is the authority for your device.

Here’s what changes between brands:

Device family	Typical launcher	What tends to differ
AOSP-based builds, custom ROMs, some budget and regional devices	Launcher3 (com.android.launcher3)	The one place the literal “Launcher3” name commonly appears. Menus follow near-stock Android naming.
Google Pixel	Pixel Launcher	Storage screen is labeled “Storage and cache,” with “Clear storage” rather than “Clear data.”
Samsung Galaxy (One UI)	One UI Home	Storage screen labeled “Storage,” with “Clear data.” System apps hidden behind Filter and sort > Show system apps.
Motorola	Motorola’s own home app	Close to stock Android naming. Motorola publishes per-model help pages, so check the page for your exact device.
Xiaomi / Redmi (HyperOS, MIUI)	Xiaomi’s own launcher	Settings organization diverges noticeably from stock Android; app management often sits under a dedicated Apps section.
OnePlus (OxygenOS)	OnePlus’s own launcher	Frequently listed as a system app, requiring “show system apps” before it appears in the app list.

Match the concept, not the wording: every device can show an app’s storage screen and clear its cache and data — only labels and paths differ.

When a factory reset is actually justified

The most common bad advice for this error — occasionally correct, usually premature.

Google is unambiguous: a factory reset removes all data and uninstalls all apps and their data.

Synced data can be restored; device-only data cannot.

A factory reset is reasonable only when all of the following are true:

You have worked through every step above, including clearing launcher data and testing Safe Mode.
Installing a different launcher did not give you a usable home screen either — which points at something broader than one broken app.
No system update is pending, and no manufacturer patch is known to be coming.
You have a verified, completed backup of your photos, messages, contacts, files, and two-factor authentication apps.

Back up before you reset, not after deciding to: confirm photos uploaded, contacts synced, and — critically — authenticator apps migrated (a Google backup often won’t restore those codes).

If the crash survives a reset, it’s likely firmware or hardware — a support case, not a settings problem.

Mistakes and myths

The same bad ideas appear in almost every thread about this error — each row covers both the mistake and the myth:

Mistake / Myth	Why it hurts / What’s actually true
Jumping straight to a factory reset — “it’s the reliable fix”	The most destructive option is rarely the necessary one. Most launcher crashes resolve in the first five steps.
Clearing data without knowing what it clears — “it uninstalls my apps”	Thirty seconds of reading — or one photo of your home screen — prevents an avoidable loss. Clearing data resets the launcher layout, not your app library; apps stay installed.
Installing a “phone cleaner” or “system repair” app — “it will fix the crashing launcher”	These have no privileged access to system components. Aggressive process-killing can cause launcher instability rather than resolve it.
Sideloading APKs from untrusted websites	Especially dangerous when the APK claims to be a launcher or system component — it runs with broad access to how you use your phone.
Assuming it’s malware — “Launcher3 has stopped means a virus”	A named app crashing is ordinary software failure. Launcher3 is published open-source code in AOSP.
Assuming every Android phone has Launcher3	Most major manufacturers ship their own launcher instead. Following Launcher3-specific advice on a Galaxy or Pixel wastes time looking for an app that isn’t there.
“Clearing cache and clearing data are the same thing”	They are different actions with different consequences. Cache holds temporary files the app rebuilds; data holds your settings and, for a launcher, your home-screen layout.
Repeating the same fix without changing anything	Clearing cache four times will not work if it did not work once. Move down the escalation path.
Ignoring free storage	Cheap to check, and it invalidates every other fix when it is the real cause.
“If the crash started after an update, the update definitely caused it”	The timing is suggestive, not conclusive. Upgrades also expose pre-existing issues such as low storage or abandoned third-party apps.
Not backing up before destructive steps	The moment you are considering a factory reset is already too late to start.

How to keep this from happening again

Keep 10% or more of your storage free. Google names this threshold explicitly as a point where problems begin.
Keep Android System WebView, Google Play services, and the Google app updated. Other apps depend on all three.
Install system updates, but not necessarily on day one. On a device you depend on, waiting a few days after a major release lets early problems surface publicly first.
Be selective with home-screen customization apps. Icon packs, theme engines, and widget suites hook deepest into the launcher and break most often across major versions.
Prefer actively maintained ones.
Keep a photo of your home screen layout. Costs five seconds; saves the rebuild every time.
Keep backups running. Verify occasionally that photos are actually uploading and contacts are actually syncing.
Skip cleaner and booster apps. Modern Android manages memory itself; aggressive process-killing causes more instability than it prevents.

Frequently asked questions

Why does Launcher3 keep stopping?

It repeatedly fails to start or run — usually corrupted launcher data (often after an upgrade), very low storage, a conflicting third-party app (icon pack, theme engine), or a bug in the shipped build.

Clearing cache, then data, resolves most cases.

Is Launcher3 a virus?

No.

Launcher3 is a legitimate Android home-screen app published as open-source code in the Android Open Source Project under the package name com.android.launcher3.

Seeing it crash indicates a software fault, not an infection.

Can I delete or uninstall Launcher3?

No — and you shouldn’t try.

On most phones the built-in launcher is a system app that can’t be uninstalled, and removing or disabling your only home-screen app leaves you with no home screen at all.

What you can do is replace it: install a different launcher and set it as the default Home app.

That gives you a working home screen without touching the built-in one.

Does clearing Launcher3 data delete my apps?

No.

Clearing launcher data resets the launcher to its default state — home-screen layout, folders, widget placement, and launcher preferences are lost.

Your installed apps remain installed and remain in the app drawer, and your photos, messages, contacts, and accounts are unaffected.

How do I fix Launcher3 without a factory reset?

Restart, install updates, clear cache, force stop, clear data, free up storage, remove recent customization apps, test Safe Mode.

If the build itself is broken, a different launcher from the Play Store restores a working home screen without erasing anything.

Can an Android update cause Launcher3 problems?

It can contribute: stale launcher data, consumed storage, broken third-party apps, or genuine build bugs.

But timing alone doesn’t prove the update was the sole cause.

How do I access Settings if the launcher keeps crashing?

Swipe down the notification shade — it’s drawn by System UI, not the launcher, so it usually works — and tap the gear.

Failing that: recent apps view, Safe Mode, or install another launcher from the Play Store.

What if clearing launcher data doesn’t work?

Check free storage first — a full device re-corrupts data as fast as you clear it.

Then test Safe Mode.

If it persists there with adequate storage, look for a manufacturer patch and use a different launcher meanwhile.

What if I use a third-party launcher?

Same steps, targeting that launcher’s name.

Bonus option: uninstall and reinstall it cleanly — impossible with a built-in launcher.

If it crashes on load, Safe Mode disables it and restores the built-in one.

How do I restart Launcher3?

Force stop it from its app info screen, then press the home button — Android relaunches the home app automatically.

A full device restart accomplishes the same thing and is often easier when the home screen is unstable.

Why does my error say “Launcher has stopped” instead of “Launcher3”?

Your device uses a different launcher (One UI Home, Pixel Launcher, etc.).

Troubleshooting is identical — only the app name in Settings changes.

The short version

“Unfortunately, Launcher3 has stopped” means one app failed — the one drawing your home screen.

Not a failing phone, not malware.

Restart first, clear cache second, clear data third (photograph your layout first; you’ll rebuild the home screen but keep every app and file).

After an upgrade, check for a follow-up patch and update WebView/Play services/the Google app before anything destructive.

If the home screen is inaccessible, use the notification shade or Safe Mode.

If the build itself is broken, a different launcher from the Play Store gets you a working phone today.

Keep the factory reset in reserve — it’s almost never the required step.

Thanks for reading! "Unfortunately, Launcher3 Has Stopped": How to Fix It (Including After an Android Update) you can check out on google.

Go to Link