Fix “Unfortunately the Process.com.android.phone Has Stopped” (2026)

The error “Unfortunately, the process com.android.phone has stopped” means the system Phone/Telephony process on your Android has crashed. It’s almost always caused by a corrupted cache in the Phone app or SIM Toolkit, a bad SIM read, or a failed migration after a system update — not a broken handset. As of 2026, the fixes below work on Android 12 through Android 15 (One UI 5 through One UI 7, Pixel stock Android, and most carrier skins).

Start with the fastest fixes at the top. If one works, you can stop — you don’t need to run the rest.

What com.android.phone actually is

com.android.phone is the system-level process that handles cellular calls, SIM reads, radio state, and emergency dialer hooks. When it crashes, you typically lose the ability to make calls, see signal bars flicker, or get the error popup repeatedly even when you’re not in the Phone app. It is not the same as the Google Phone app (com.google.android.dialer) or Samsung Phone (com.samsung.android.dialer) — those are the dialer UIs that sit on top of the telephony process.

Because this is a system process, most user-facing troubleshooting (like uninstalling the Phone app) doesn’t apply. You need to target the underlying telephony and SIM Toolkit services.

Common triggers

• A system update or security patch that didn’t migrate SIM/radio settings cleanly
• A flaky or physically damaged SIM, or a SIM that’s mis-seated in the tray
• A corrupted Contacts database after importing a large vCard
• Carrier Services or Google Play Services falling behind their required version
• On Samsung: a failed Galaxy Store “auto-install” during overnight updates
• A third-party call-recorder, dialer, or dual-SIM app with root hooks

Fix 1: Force stop and restart the Phone process

This clears the running state without touching any data. It solves the issue for roughly 4 in 10 users.

1. Open Settings → Apps (on Samsung: Settings → Apps; on Pixel: Settings → Apps → See all apps).
2. Tap the three-dot menu → Show system apps (or Show system).
3. Scroll to Phone (package name com.android.phone, not the Google Phone dialer).
4. Tap Force stop → OK.
5. Reboot the phone.

Fix 2: Clear the cache of Phone and SIM Toolkit

If force-stopping didn’t stick, clear the cached state for both the telephony process and the SIM Toolkit. Cache-clear is safe — it does not delete contacts, call log, or messages.

1. Go to Settings → Apps → See all apps → three-dot menu → Show system.
2. Tap Phone → Storage & cache → Clear cache.
3. Back out, then tap SIM Toolkit (may appear as STK, SIM Menu, or carrier-branded like Verizon SIM Toolkit) → Storage & cache → Clear cache.
4. If the error keeps popping, repeat the above but use Clear storage (or Clear data). This resets telephony preferences only — you’ll need to re-enable things like call-forwarding or voicemail shortcuts.
5. Reboot.

On dual-SIM phones, you may see two SIM Toolkit entries (SIM Toolkit 1 and SIM Toolkit 2). Clear both.

Fix 3: Pull and reseat the SIM

A SIM that isn’t making full contact will throw this error intermittently — especially on phones that have been dropped or travel through temperature swings. This is particularly common with physical SIMs on Samsung Galaxy A-series, Pixel 6/7/8, and older Motorola handsets.

1. Power the phone off.
2. Eject the SIM tray with the included pin. If you don’t have one, a straightened paperclip works.
3. Wipe the gold contacts of the SIM with a lint-free cloth. Do not use alcohol or water.
4. Check the tray for dust or a bent retainer. Reseat the SIM firmly.
5. Power on and test.

If you’re on an eSIM and can’t physically check a card, go to Settings → Network & internet → SIMs, toggle the eSIM off, reboot, and toggle it back on. On Pixel, this forces a fresh provisioning handshake with the carrier.

Fix 4: Boot into Safe Mode to rule out a third-party app

Safe Mode disables every app you installed yourself. If the error disappears in Safe Mode, one of your installed apps is triggering it — most often a call recorder, dual-SIM manager, or a launcher that replaces the dialer.

Samsung Galaxy: Press and hold Power → long-press Power off until the Safe mode prompt appears → tap it.

Pixel: Press and hold Power → long-press Power off until you see Reboot to safe mode → tap OK.

Other stock Android: Same gesture as Pixel works on most OnePlus, Motorola, and Nothing devices running Android 13 or later.

If the error stops in Safe Mode, reboot normally and uninstall recently-added apps one at a time. Start with anything that asked for Phone, Contacts, or Accessibility permission.

Fix 5: Update Carrier Services and Google Play Services

Carrier Services (com.google.android.ims) handles RCS, VoLTE handoffs, and SIM profile updates. When it falls behind Android’s required version, the telephony process starts crashing on SIM reads. This is the single most common cause on Pixel phones in 2026.

1. Open the Play Store → tap your profile icon → Manage apps & device → Updates available.
2. Look for Carrier Services and Google Play Services. Update both.
3. If they don’t appear under “Updates available,” search the store for each and tap Update directly.
4. Reboot.

Fix 6: Reset app preferences

This restores default handlers, notification permissions, and background restrictions for every app without deleting data. It fixes scenarios where a third-party app has taken over as the default dialer and is interfering with com.android.phone.

1. Go to Settings → Apps → See all apps.
2. Tap the three-dot menu → Reset app preferences → Reset apps.
3. Reboot.

Fix 7: Wipe the cache partition (recovery mode)

If the error started right after a system update, the Dalvik/ART cache from the old build is probably stale. Wiping the cache partition forces Android to rebuild it on the next boot. It does not delete your files, photos, or accounts.

Samsung Galaxy S-series, Note, Z Flip/Fold:

1. Power off.
2. Plug the phone into a Windows or macOS computer via USB-C.
3. Hold Volume Up + Power + Side key (on models with a Bixby button, substitute Bixby for Side) until the Samsung logo appears, then release.
4. Navigate with Volume keys to Wipe cache partition → Power to select → Yes.
5. Reboot system now.

Pixel 6/7/8/9: Google removed the cache-partition wipe from stock recovery starting with Pixel 6. The equivalent fix is Settings → System → Reset options → Reset Wi-Fi, mobile & Bluetooth, which rebuilds network and telephony state without touching personal data.

Fix 8: Disable Google Contacts sync, then re-enable

A corrupted single contact — typically one imported from an old vCard or from a carrier’s cloud — can repeatedly crash the telephony process when it tries to resolve a caller. Toggling sync off forces a clean re-pull on re-enable.

1. Go to Settings → Passwords & accounts (Samsung: Accounts and backup → Manage accounts).
2. Tap your Google account → Account sync.
3. Toggle Contacts off. Wait 30 seconds.
4. Toggle it back on. Let the sync finish — it can take 2-5 minutes for large address books.
5. Reboot.

Fix 9: Disable Play Store auto-update

If the crash happens once or twice a day and correlates with overnight hours, the Play Store is probably auto-updating the dialer package while something else is trying to read from it. Flipping auto-update to “Over Wi-Fi only” — or to “Don’t auto-update” — stops the mid-session updates.

1. Open the Play Store → tap your profile icon → Settings → Network preferences → Auto-update apps.
2. Select Over Wi-Fi only (recommended) or Don’t auto-update apps.

Fix 10: Factory reset

If every fix above fails, the error is almost always tied to a corrupted system partition from a failed update or an interrupted flash. A factory reset rebuilds it. Back up first — the reset wipes all user data, installed apps, and internal storage.

1. Back up to Google One, Samsung Cloud, or a local computer.
2. Go to Settings → System → Reset options → Erase all data (factory reset).
3. Confirm. The phone reboots into setup on completion.
4. When restoring, choose Set up as new for at least the first 24 hours of use to confirm the error is gone. If it returns after restoring a backup, the backup itself contains the corrupted contact or setting.

Related variants of the same error

The com.android.phone crash shares a root cause with several sibling errors. If you see any of these, the fixes above apply equally:

Error Message	Most Common Cause	Go to Fix
“process com.android.phone has stopped”	Corrupted SIM Toolkit or Carrier Services cache	Fix 2, Fix 5
“com.android.phone keeps stopping”	Auto-update collision or bad SIM seat	Fix 3, Fix 9
“Unfortunately, Phone has stopped”	Dialer UI, not the telephony process — clear the Google/Samsung Phone app cache	Settings → Apps → Phone → Clear cache
“process com.android.systemui has stopped” at same time	System-wide update corruption	Fix 7, Fix 10
Error only when dialing a specific contact	Corrupted contact entry	Fix 8

When it’s a hardware problem

If you’ve done Fix 1 through Fix 10 and the error keeps returning within hours of a reboot, the SIM reader itself may be failing. Signs of a bad reader:

• “No SIM” or “Emergency calls only” alternating with the error even with a known-good SIM
• The tray feels loose or doesn’t click into place
• The phone has been dropped, submerged, or stored in a very humid environment

SIM reader replacement is a board-level repair on most modern phones (it’s soldered to the motherboard) and isn’t economical on devices older than the Galaxy S22 or Pixel 6. Get a repair quote before committing.

Warranty and support contacts

If your phone is under warranty and the error persists after a factory reset, contact the manufacturer rather than paying for a paid repair.

• Samsung US Support: 1-800-726-7864 (7 days, 8am-12am ET). Have your IMEI ready — Settings → About phone → Status information.
• Google Pixel Support: Pixel phones include a 1-year limited warranty; contact via the Google Store app → Help, or call 1-855-836-3987.
• Motorola US Support: 1-800-734-5870.
• OnePlus US Support: 1-833-777-8881.
• Your carrier: Verizon, T-Mobile, and AT&T will replace a defective SIM for free at any retail store within 15 minutes. This is worth trying before paying for a phone repair — a fresh SIM fixes this error for a surprising number of people.

Prevention

Once the error is gone, these habits keep it from coming back:

• Install system updates on Wi-Fi with at least 50% battery, and leave the phone alone for 10 minutes after the reboot so Android can rebuild its caches.
• Don’t install two dialer or call-recorder apps at the same time. Pick one.
• Clean out orphaned contacts every 6 months — open Google Contacts → Fix & manage → Merge & fix.
• If you use a dual-SIM or eSIM, periodically check Settings → Network & internet → SIMs to confirm both profiles are still active. Carriers sometimes silently deprovision unused eSIMs.

For 90%+ of users, Fix 2 (clearing Phone and SIM Toolkit cache) solves this error permanently. If you’ve worked down to Fix 7 or beyond, save yourself time and go straight to the factory reset — the recovery wipe and cache-partition tricks rarely help once software-side fixes have failed.