Carrier Services Keeps Stopping? 9 Fixes That Work (2026)

If your Android phone keeps popping up “Carrier Services keeps stopping” — often while you’re texting — here’s the short answer: Carrier Services is a Google system app that powers carrier features like RCS chat in Google Messages and helps with calling features. When it crashes, it’s almost always a corrupted cache, an outdated app version, or an RCS registration hiccup, not a hardware fault. Clearing its cache and updating it fixes the vast majority of cases in minutes.

This guide explains what Carrier Services is, why it keeps stopping, and nine fixes ordered from quickest to last resort.

What is Carrier Services?

Carrier Services is a Google-made system app that acts as the bridge between your phone and your mobile carrier’s network features. Its biggest job is enabling RCS (Rich Communication Services) — the modern messaging standard behind features in Google Messages like typing indicators, read receipts, high-resolution photos, and chat over Wi‑Fi. It also helps support calling features such as VoLTE and Wi‑Fi calling on some devices.

It is a legitimate Google system app, not a virus. You usually never notice it — until it crashes and starts interrupting your texting. The “keeps stopping” message means the app failed and Android is relaunching it, which is annoying but almost always fixable with the steps below.

Why does Carrier Services keep stopping?

The crash typically traces back to one of these:

A corrupted cache or data. Damaged temporary files are the most common cause and the easiest to clear.
An outdated Carrier Services version. An old build can be unstable with current Messages or Android versions.
An RCS registration problem. If RCS chat features are stuck trying to connect or re-register, Carrier Services can crash repeatedly.
A Google Messages conflict. Because Carrier Services works hand-in-hand with Messages, a problem in one can destabilize the other.
Network or SIM issues. A flaky connection or SIM problem can interrupt the carrier handshake.
A software bug after an update. A new Android version or app update can carry a temporary bug.

The fixes below are ordered to catch the easy, common causes first.

What breaks when Carrier Services crashes?

Because Carrier Services underpins RCS, a crash usually shows up as messaging problems: chat features turning off in Google Messages, messages reverting to plain SMS/MMS, read receipts and typing indicators disappearing, or media sending in low quality. On some phones, calling features like Wi‑Fi calling may also be affected. If your texting suddenly “downgraded” alongside the crash pop-ups, Carrier Services is the likely cause.

How to fix “Carrier Services keeps stopping”

Work through these in order and stop at the first fix that works.

1. Restart your phone

A restart clears stuck states and temporary memory, resolving the crash loop in many cases. Hold the power button, tap Restart, and let the phone fully boot before testing Messages.

2. Clear the Carrier Services cache

This is the most effective single fix:

Open Settings → Apps.
Enable Show system apps from the menu.
Open Carrier Services.
Tap Storage → Clear cache, then restart.

Clearing the cache removes only temporary files — no personal data is touched.

3. Clear Carrier Services data

If cache alone doesn’t help, tap Clear data in the same Storage screen. This resets Carrier Services and forces RCS to re-register cleanly, which clears deeper corruption. Your messages and contacts are unaffected; RCS chat features may take a little while to reconnect afterward.

4. Update Carrier Services

An outdated version is a frequent trigger. Open the Play Store, search for Carrier Services, and tap Update. Keeping it current often resolves crashes permanently.

5. Update Google Messages

Because the two work together, update Messages in the Play Store as well, then restart. Mismatched versions of Messages and Carrier Services are a common source of instability.

6. Toggle RCS chat features off and on

Resetting RCS often stops the crash loop. In Google Messages → Settings → RCS chats (or “Chat features”), turn chat features off, restart, then turn them back on and let them re-verify your number. If verification gets stuck, clearing Carrier Services data (step 3) first usually helps.

7. Clear the Google Messages cache

A corrupted Messages cache can drag Carrier Services down with it. Go to Settings → Apps → Messages → Storage → Clear cache, then restart and test.

8. Check your network and SIM

A weak signal or seated-SIM issue can interrupt the carrier handshake. Toggle Airplane mode on and off, try a different location, and reseat your SIM if needed. If you use an eSIM, make sure the line is active.

9. Update Android, then reset as a last resort

Install any pending software update (Settings → Software update / System update). If crashes persist, reset settings without deleting data (Reset → Reset all settings / Reset network settings). Only as a final resort, back up and factory reset; if Carrier Services still crashes on a clean device, contact your carrier or device maker.

Carrier Services vs Carrier Hub: don’t confuse them

A common mix-up: Carrier Services (by Google) is not the same as Carrier Hub (used by some carriers, notably T‑Mobile/Sprint, for network features and Wi‑Fi calling). If your error says “Carrier Hub keeps stopping” rather than Carrier Services, the fixes are similar — clear cache/data and update — but it’s a different app tied to your specific carrier. Check the exact name in the error message so you troubleshoot the right one. For Google’s Carrier Services, the steps in this guide apply; for Carrier Hub, you may also need to contact your carrier if clearing its cache and data doesn’t help.

Should you disable Carrier Services?

Some people try to stop the crashes by disabling Carrier Services. You can, but it’s a trade-off: disabling it turns off RCS chat features, so Google Messages falls back to basic SMS/MMS — no typing indicators, read receipts, Wi‑Fi messaging, or high-quality media. If you rely on those, don’t disable it; fix the crash instead using the steps above. If you genuinely never use RCS and just want the pop-ups to stop, disabling it is a valid (if feature-reducing) option. For most people, clearing the cache and updating is the better path because it keeps the features working.

Carrier Services crashes after an update or switching carriers

When the crashes started narrows the cause. If they began right after a system update, Carrier Services or Google Messages is likely out of date relative to the new software — update both in the Play Store and clear the Carrier Services cache. If they began after switching carriers, plans, or SIMs, RCS is trying to re-register on a new network and may be stuck: toggle chat features off and on, and clear Carrier Services data so registration restarts cleanly. Give RCS a little time to re-verify your number on the new network — verification can take a few minutes to a few hours — before assuming something is broken. Matching the crash to its trigger lets you skip straight to the fix that matters.

Does Carrier Services use a lot of battery or data?

Normally, no. Carrier Services sips power and data while keeping RCS connected in the background. If you notice it sitting high in your Battery or Cellular data stats, it’s almost always because it’s stuck retrying registration — the very same thing that causes the crash pop-ups. In other words, high battery/data use and the “keeps stopping” message usually share one root cause, so fixing the crash (clear cache, update Carrier Services and Messages, re-toggle RCS) also resolves the elevated usage. There’s no need to restrict the app on a healthy phone; only investigate if its usage is abnormally high and paired with crashes.

How to stop Carrier Services crashes from returning

A few habits prevent repeats. Keep Carrier Services and Google Messages updated through the Play Store, since most crashes come from outdated or mismatched versions. Keep Android itself updated. Avoid repeatedly toggling RCS on and off, which can leave registration in a stuck state. And maintain a stable network connection during RCS verification. These steps prevent the large majority of recurrences.

Key takeaways

Carrier Services is a Google system app that powers RCS chat features in Google Messages and supports some calling features — not a virus and not normally something to remove.
The most common causes are a corrupted cache, an outdated version, or a stuck RCS registration.
Clearing the cache (then data, if needed) and updating Carrier Services and Messages fix the large majority of cases — without deleting personal data.
Toggling RCS chat features off and on forces a clean re-registration that often stops the crashes.
Don’t confuse Carrier Services (Google) with Carrier Hub (carrier-specific) — check the exact error name.

Frequently asked questions

Is Carrier Services a virus or spyware?

No. Carrier Services is an official Google system app that enables RCS messaging and carrier features. The “keeps stopping” message just means the app crashed — it’s not malware, and clearing its cache usually fixes it.

Will clearing Carrier Services data delete my texts?

No. Clearing its cache or data only resets the app’s own temporary files and forces RCS to re-register. Your SMS/MMS messages, RCS conversations, and contacts are stored elsewhere and are unaffected.

Why does Carrier Services keep stopping when I text?

Because it powers RCS chat in Google Messages, so it’s most active while you’re messaging. A stuck RCS registration or a corrupted cache makes it crash at that moment. Clearing the cache and toggling RCS off and on usually fixes it.

Can I just disable Carrier Services to stop the pop-ups?

You can, but you’ll lose RCS chat features (typing indicators, read receipts, Wi‑Fi messaging, high-quality media) and drop back to basic SMS/MMS. Fixing the crash is the better option unless you never use RCS.

Is Carrier Services the same as Carrier Hub?

No. Carrier Services is Google’s app for RCS and carrier features; Carrier Hub is a separate app some carriers (like T‑Mobile) use. Check your error message for the exact name and troubleshoot accordingly.

How long does RCS take to reconnect after clearing data?

Usually a few minutes, but it can take up to several hours depending on your carrier and network. After clearing Carrier Services data or toggling chat features, give Google Messages time on a stable connection (Wi‑Fi or good signal) to re-verify your number. If it’s still “connecting” after a day, repeat the toggle and confirm your number is correct in Messages settings.

Does disabling Carrier Services stop me receiving texts?

No. Basic SMS and MMS texts still arrive even if Carrier Services is disabled, because those don’t depend on it. What you lose are the RCS chat features — typing indicators, read receipts, Wi‑Fi messaging, and high-quality media. So you’ll still get messages, just without the modern enhancements.

Conclusion

“Carrier Services keeps stopping” is disruptive because it interrupts your texting, but it’s almost always a simple software issue — a corrupted cache, an outdated app, or a stuck RCS registration. Clearing the cache, updating Carrier Services and Google Messages, and toggling RCS chat features off and on resolves the vast majority of cases without losing any data. Reserve disabling the app for the rare case where you don’t use RCS at all.

If other “keeps stopping” errors are hitting your phone too, our fixes for com.android.systemui keeps stopping, Android System WebView keeps stopping, and Samsung Keyboard keeps stopping cover the most common Android crashes — they often share the same cache-and-update root causes.