Android Message Not Delivered | Fixes That Work Fast

Guide / By

Most android message not delivered errors come from signal gaps, carrier limits, or messaging settings, and a short set of checks often gets texts sending again.

Seeing “Not delivered” can feel like your phone just ignored you. In most cases it’s a routing problem. The message tried to leave, something blocked the route, then your app showed the last status it received.

The fastest fix is to match your troubleshooting to the lane your message used. SMS, MMS, and RCS each travel differently. Once you know the lane, you can stop guessing and run a small checklist that fits.

What “Not Delivered” Means On Android

Your Android can send messages through more than one system. The same “Not delivered” label can show up for different reasons, so it helps to know what you’re actually sending.

SMS

SMS is the classic carrier text. It doesn’t rely on Wi-Fi or mobile data, yet it does rely on a working cellular connection and a line that can send texts. When SMS fails, the cause is often weak signal, a carrier sending block, or a SIM/line provisioning issue.

MMS

MMS handles photos, videos, and many group texts. MMS usually needs mobile data and correct APN settings. The Google Messages sending/receiving help page points to mobile data checks and APN resets when MMS won’t send.

RCS

RCS (chat features) is the internet-based upgrade used by Google Messages and some other apps. It can show delivery and read states. It needs mobile data or Wi-Fi, plus a working registration. Google’s RCS chats setup page notes that RCS can be disabled by your carrier, which blocks setup until the carrier clears it.

If you aren’t sure which lane you’re in, check out the thread. Plain text with no media is often SMS. Photos and many group chats are often MMS. Threads that show “Chat message,” typing dots, or read receipts are usually RCS.

What You See Likely Cause Try This First
Not delivered when bars are low Weak cellular link Toggle Airplane mode, resend
Photo or group message fails Mobile data or APN issue Turn on data, reset APN
RCS stuck on “Sending” Chat features not connected Reconnect chat features
Fails only to one person Blocked, wrong number, thread glitch Verify number, start new thread
Works on Wi-Fi, fails on data Carrier data session issue Toggle data, reboot
Works on data, fails on Wi-Fi Wi-Fi login page, DNS, or VPN Disable VPN, try another Wi-Fi

Android Message Not Delivered Fixes You Can Try First

Start with the fast checks. They fix a lot of delivery failures and take minutes.

  • Toggle Airplane mode — Turn it on for 10 seconds, then turn it off so the phone re-registers on the network.
  • Restart the phone — A full restart clears stuck radio states and background hangs.
  • Send a plain SMS — Remove photos and links, then send a short text to test the simplest lane.
  • Try a second recipient — Text another number to see if the problem is global or tied to one thread.
  • Check plan limits — Some carriers block outgoing texts on low balance, expired packs, or roaming limits.
  • Turn off Wi-Fi calling — If Wi-Fi calling is on and Wi-Fi is unstable, switch it off and retry.

If sending starts working after this list, keep going with your day. If it doesn’t, the next sections narrow it down by network, carrier, and app settings.

Network And Carrier Checks That Often Fix Delivery

Texting still rides on your carrier line, even when you use modern messaging. A small carrier-side hiccup can look like a phone problem.

Reset the connection cleanly

Airplane mode is the quickest reset, yet a few other toggles can help when the radio is half-connected.

  • Toggle mobile data — Turn mobile data off for 10 seconds, then on, then try sending again.
  • Disable VPN or private DNS — These can block RCS traffic on some networks, then messages stall.
  • Switch network mode once — If your phone lets you pick LTE/3G/2G, switch once and switch back to force a fresh registration.

Check roaming and short-code settings

Roaming can limit outgoing SMS. Carriers can also block certain destinations such as short codes or paid SMS. If you can text friends but not banks or ride apps, ask your carrier to check short-code and paid messaging settings on your line.

Reset APN when MMS fails

If photos or group texts fail, APN settings are a common cause. MMS depends on the carrier data gateway, so the fix often lives in your SIM network settings.

  • Open APN settings — Go to Settings, then Network & Internet, then SIMs, then Access Point Names.
  • Reset APN to default — Use the reset option, then reboot the phone.
  • Test on mobile data — Turn off Wi-Fi for the test so MMS runs through carrier data.

Do a quick SIM check

A loose SIM, an aging SIM, or a recent phone swap can cause random sending failures. If you changed phones recently, your carrier may need to re-provision messaging on the line.

  • Reseat the SIM — Power off, remove the tray, wipe dust, then reinsert firmly.
  • Try the SIM in another phone — If texts fail there too, the line is the likely source.
  • Request a line refresh — Carriers can resend provisioning to clear silent blocks.

Google Messages And RCS Settings That Affect Delivery

If you use Google Messages or another RCS app, delivery trouble can come from chat features state, background data rules, or carrier eligibility.

Check whether chat features are connected

In Google Messages, open settings and check RCS chats status. If it isn’t connected, RCS messages may sit on “Sending” until registration completes.

  • Confirm the status — Open Messages settings, then RCS chats, and look for a connected status.
  • Toggle chat features — Turn it off, wait a minute, then turn it on to re-register.
  • Resend as SMS — Long-press the stuck message if you see an option to send as SMS/MMS.

Make sure data isn’t blocked for Messages

RCS needs data in the background. If you restrict background data or use strict data saver rules, chat features can drop while the app is idle.

  • Allow background data — In App info for Messages, allow mobile data and Wi-Fi in background.
  • Pause Data Saver — Disable it for a quick test message, then turn it back on if you want it.
  • Allow battery use — If battery rules stop background work, RCS can disconnect.

Know when RCS won’t fall back

RCS doesn’t always drop to SMS when data is shaky. If time matters, resend as SMS now instead.

App And Phone Fixes When Sending Still Fails

If network checks look fine and messages still fail, the issue may live inside the app, its storage, or the phone’s system services.

Confirm your default SMS app

Two messaging apps on one phone can compete for permissions and routing. Pick one as default and keep it there while you test.

  • Set the default SMS app — In Settings, open Apps, then Default apps, then SMS app, and choose one.
  • Disable the unused app — Turn it off for a day so it can’t grab messaging intents.
  • Start a fresh thread — New threads force the app to re-check contact data and routing.

Clear cache and restart the app

Cache corruption can break sending, especially after a system update. Clearing cache is low risk. Clearing storage is a bigger move since it resets settings.

  • Force stop Messages — Open App info, tap Force stop, then reopen Messages.
  • Clear cache — In Storage & cache, clear cache, then try a plain SMS.
  • Update Messages — Install the latest version from Play Store, then test again.

Free space if your phone is near full

Low storage can cause messaging to misbehave, including delayed sends and failed downloads. The Google Messages help page notes that Messages may not send or receive until enough space is available.

  • Delete large files — Clear old videos, duplicate photos, and oversized downloads.
  • Remove old message media — Delete large attachments from old threads you don’t need.
  • Restart after cleanup — A restart helps the system tidy caches and indexes.

Check date and time settings

Wrong time settings can break secure connections used by chat features. Set date and time to network-provided, reboot, then test again.

Test without blocker apps

Call blockers, firewalls, and battery manager apps can stop background messaging. If you use any, pause them for a short test. If sending returns, turn features back on one at a time until you find the one that breaks messaging.

When It’s The Recipient Or The Thread

Sometimes your phone is fine and the failure is on the other end. A few checks can tell you that fast.

Verify the number and country code

A contact saved with the wrong number, a missing country code, or an old line can cause repeated failures. The Google Messages help page suggests verifying the phone number and adding a country code when needed.

  • Check the contact card — Confirm the number matches what the person uses now.
  • Save the number with + code — Add the country code, then resend from a new thread.
  • Delete and re-add the contact — This can clear a broken entry linked to the thread.

Check block lists on both sides

If the failure happens only with one person, check your blocked numbers list in the messaging app and in system settings. If you’re blocked on their side, you may not get a clear warning each time.

Rebuild the conversation

Threads can get stuck after number changes, SIM swaps, or a long run of failed sends. A new thread forces the app to re-resolve the contact and message path.

  • Copy the number into a new chat — Avoid tapping the old thread for the first test.
  • Send one short message — Keep it plain so you can test SMS first.
  • Add media after success — Once SMS works, test MMS or RCS next.

Know what to tell your carrier

If nothing above changes the result, your carrier can check outgoing SMS blocks, provisioning errors, and network-side logs. Share the time of a failed send, the destination number, and whether it was SMS, MMS, or RCS.

If you see android message not delivered across many recipients for hours, test a phone call, reboot once more, then contact your carrier. If the issue is limited to RCS, use the official Google Messages pages on sending issues and RCS chats while you work through settings.

Useful Official References