com.android.phone has stopped
iOS/Android
Medium severity
Android — “com.android.phone Has Stopped” (Phone/Dialer Keeps Crashing)
The telephony process crashed — a corrupt cache, a bad update to the Phone app, or a SIM/carrier config problem.
Last reviewed 2026-08-29 by the Tech Issue Guide team.
Symptoms
- Repeated “com.android.phone has stopped” or “Phone keeps stopping” pop-ups.
- Calls drop instantly or the dialer closes when opened.
- It started after a system update, a new SIM, or changing network settings.
What causes com.android.phone has stopped
- Corrupt cache/data in the Phone or SIM Toolkit app.
- A buggy update to the carrier services or Phone app.
- A loose or failing SIM, or an outdated carrier configuration.
- A third-party dialer, call-recorder, or spam-blocker conflicting with the system dialer.
How to fix it — 3 steps
- Settings → Apps → show system apps → Phone → Storage → Clear cache (then Clear storage if needed); do the same for “SIM Toolkit” and “Carrier Services.” Reboot.
- Power off, reseat the SIM card (or try another SIM), power on, and check Settings → About phone → for a carrier settings update.
- Boot into Safe Mode (hold Power → long-press “Power off” → Safe Mode). If the crash stops, uninstall recently added dialer/call apps one by one.
Terminal / CLI command
adb shell pm clear com.android.phoneOptional, via ADB — clears the telephony app’s data. You may need to re-check APN/carrier settings afterwards.
How to confirm the fix: The dialer opens, calls connect and stay connected, and the pop-up no longer appears.
Prevent it from coming back
Install only one dialer/call-management app, and apply carrier settings updates when offered.
Frequently asked questions
Clearing storage on a system app — is that risky?
For the Phone app it is safe; it rebuilds its data. You may need to re-enable call settings like voicemail number or call blocking afterwards.