Message Not Sent: Service Not Activated on Network

If Android shows “Message not sent: service not activated on network”, first identify the transport and line that actually failed. Plain SMS, carrier MMS and RCS are different paths; a group conversation can use RCS or fall back to MMS depending on participants/settings. On dual-SIM phones, also prove which SIM is selected for messaging and mobile data before changing APN or resetting the phone.

Android · SMS/MMSCarrier · APNLast reviewed Sep 27, 2026

🎯 This guide matches when:

Google Messages or another Android messaging flow shows “service not activated on network.”SMS may work while a photo, attachment or group MMS fails.The problem appeared after a SIM/eSIM, carrier, plan, port, APN or messaging-app change.

Start with what actually fails

Photos fail / group conversation failsIdentify whether the failed send is MMS or RCS/fallback first. If it is MMS, trace selected SIM → mobile data → carrier APN/provisioning.

Plain SMS also failsCheck the selected messaging SIM, signal, active line, plan/credit and carrier activation before focusing on MMS settings.

Dual-SIM / eSIM + physical SIMRecord which SIM sends SMS and which SIM provides mobile data; a working second line does not prove the failing line is provisioned.

RCS/chat fails but SMS worksSeparate RCS status from SMS/MMS. Do not assume an RCS problem proves the SIM is inactive.

Only one contact failsCheck the number, country code and blocked-contact state before changing network settings.

🔎 Quick Check — is this specifically an MMS failure?

Send one short plain-text message to a known working number, then send one small photo to the same number. Record the SIM/line used. For a group conversation, check whether Messages labels/handles it as RCS/chat or SMS/MMS instead of assuming every group send is MMS.

Verify: Record the selected line and whether plain SMS, photo MMS and RCS/group messaging succeed or fail separately. If transport changes through fallback, diagnose the transport that actually produced the error.

Diagnose the transport before changing settings

Use the result of the quick check to identify the failing transport. If plain SMS works but a photo or group message fails, the strongest first branch is MMS/mobile data/APN. If SMS also fails, move first to SIM, signal, line activation and carrier support. If only RCS fails, keep that separate from carrier SMS/MMS.

Verify: You should be able to state one precise failure pattern—SMS, MMS, RCS, one contact, or all messaging—before changing any network setting.

Fix path #1 — prove mobile data works on the relevant line

Google’s current Messages troubleshooting says MMS requires a data connection. Android Help also recommends checking mobile data and switching between Wi-Fi and cellular data when diagnosing connectivity.

Temporarily turn Wi-Fi off, confirm mobile data is enabled, and load a normal webpage over cellular data. On dual-SIM devices, record which SIM is currently selected for mobile data and which SIM is sending the message. If roaming, also record whether data roaming/carrier policy applies. This is a diagnostic test—not a claim that Wi-Fi itself causes the error.

Verify: Cellular data should work in the relevant carrier/line context. If data works only through the other SIM, do not treat that as proof the failing line's MMS path is healthy.

Fix path #2 — compare APN, then restore carrier defaults when appropriate

For a confirmed MMS branch, record the current APN and carrier/SIM first, then compare it with the carrier's current supported configuration. Google recommends resetting APN settings to default for MMS failures, but APN values are carrier-specific and a reset can also affect mobile-data/tethering behavior. Avoid copying random APN values from forums.

For example, T-Mobile’s current BYOD documentation includes an MMS-capable APN type and tells users to test data and/or MMS after saving the supported configuration. Other carriers can use different values.

Verify: After an intentional carrier-supported APN restore/reset, restart only if instructed, confirm cellular data still works, then test one small MMS on the same line. Do not change APN, SIM selection and app data simultaneously.

Fix path #3 — check SIM, line activation and messaging support

Google’s Messages guidance says to verify the SIM is inserted properly, the carrier supports SMS/MMS/RCS, the account has sufficient plan or credit, the phone has signal, and airplane mode is off. If both SMS and MMS fail, these checks move ahead of app-specific troubleshooting.

If you recently ported the number, replaced the SIM, activated an eSIM, changed plans or restored service, ask the carrier to verify that the line is fully activated and that SMS/MMS provisioning is enabled. Android Help directs activation and cellular-service problems to the mobile carrier.

Verify: Ask for a concrete test: can the line send a plain SMS and an MMS after provisioning is confirmed? Record which one still fails.

Fix path #4 — separate RCS from SMS/MMS

Google Messages can use RCS chats in addition to carrier SMS/MMS. If RCS is unavailable, that does not automatically mean MMS is unavailable; likewise, a working RCS conversation does not prove the carrier MMS path is correct.

If you recently changed messaging apps or phones, follow Google’s current Messages guidance for RCS/chat transitions rather than repeatedly toggling unrelated network settings.

Verify: Test a plain SMS and photo/group MMS independently of the RCS indicator. Continue with the transport that actually fails.

Fix path #5 — if only Google Messages fails

If the same SIM and carrier can send MMS from another supported messaging app but Google Messages alone fails, the evidence shifts toward the app/configuration layer. First update Google Messages and confirm it is the default texting app, both steps included in Google’s official troubleshooting.

Do not clear all phone data as an early experiment. Preserve the simpler comparison—same line, same APN, different app—because it is useful evidence if you need to report the issue.

Verify: Re-test the same recipient and same small attachment after updating/default-app checks. If only one app still fails, document the app version and send feedback through that app’s support path.

If only one contact fails

Google recommends checking that the contact is not blocked, the number is correct, and the required country code is present. A single-contact failure is weak evidence for resetting APN or carrier provisioning.

Verify: Send a plain SMS to another known working number. If other recipients work, stay on the contact/number branch.

What not to do first

Do not factory-reset the phone before separating SMS, MMS and RCS failures.Do not copy APN values from an unrelated carrier or an old forum post.Do not assume good Wi-Fi proves the cellular MMS path is healthy.Do not delete the eSIM or discard the SIM before the carrier verifies line provisioning.Do not change APN, app data, SIM and network settings simultaneously—you lose the evidence showing which change mattered.Do not assume every group conversation is MMS; confirm whether the failed send used RCS/chat or SMS/MMS fallback.Do not treat cellular data working on SIM 2 as proof that MMS provisioning on SIM 1 is healthy.Do not reset APNs before recording the current carrier/SIM configuration, especially when mobile data or tethering currently works.Do not enable roaming or incur roaming data charges merely as a troubleshooting experiment without understanding your carrier plan.

Still seeing “service not activated on network”?

Collect enough evidence for the carrier or app support team to distinguish provisioning from device/app behavior.

Capture before escalating:phone model and Android versioncarrier/MVNO and whether the SIM/eSIM or plan changed recentlywhether plain SMS workswhether photo MMS and group MMS workwhether cellular data works with Wi-Fi offGoogle Messages version and whether it is the default appwhether the APN was reset to carrier defaultswhether the failure affects every recipient or only oneapproximate time the failure started and any port/activation changewhich SIM/eSIM is selected for messaging and which is selected for mobile datawhether the failed group send was RCS/chat, MMS or a fallback attemptwhether roaming is involved and whether the issue follows one line/SIM

Official / primary references

Still stuck? Ask the community

Share the phone model, Android version, carrier, whether SMS works, whether MMS fails, and whether cellular data works. Those details are more useful than “messages do not work.”

Keep it safe: never post your full phone number, SIM/ICCID, IMEI, account PIN, activation QR code or carrier login credentials.

Loading community discussion…