When the person you text says they are not receiving your messages on Android, it is frustrating—especially because everything looks normal on your side. This issue is usually caused by delivery settings, blocked or filtered numbers, incorrect message app defaults, or a temporary network problem. Below are practical checks to help you pinpoint the cause and get your texts delivered again.
As an Amazon Associate I earn from qualifying purchases.
Most of the time, Android isn’t delivering your texts because the message is sent in the wrong format (SMS vs RCS/MMS) or the recipient’s phone/carrier isn’t accepting messages from your number. In this guide (updated for how Android messaging works in 2026), we’ll walk through the quickest checks on your Android device so you can pinpoint whether the issue is your settings, the network, or the recipient’s phone.
If you’re messaging a specific person and their phone never shows your texts (or you only see “failed”/no delivery), this applies. It’s also helpful if you can text other people normally and only that one contact seems to miss your messages.
Step 1: Confirm it’s not a simple network/SIM issue
This is the fastest way to rule out the “boring” problems before you dig into RCS settings or app-specific blocks on Android. If delivery fails only for one contact, your carrier routing is less likely—but a shaky connection can still break SMS/MMS delivery in ways that look like a recipient-side issue.
- Make sure your phone isn’t in airplane mode and you have signal (try toggling Mobile Data/Switching networks briefly). If you’re on Wi‑Fi calling for data, temporarily switching to mobile data can clarify whether the problem is network-path related.
- Re-check the recipient number and country code (a “near match” can cause messages to land nowhere). A single-digit typo or missing leading “+” can redirect the message to a different destination you’ll never get feedback from.
- If you’re sending media, confirm whether it’s going through as SMS or MMS (MMS delivery is easier to break than plain text). On Android, the same chat can silently “downgrade” from richer messaging to MMS when RCS isn’t available—then delivery becomes dependent on MMS support and APN configuration.
Step 2: Check whether you’re blocked (or filtered)
If Android messages never arrive for one person but work fine for everyone else, blocking or carrier-side filtering is a common culprit. This step matters because the phone may not tell you “you’re blocked”—it may simply stop delivering.
- Ask yourself: did you ever block that person on your phone, or do they show up in any “blocked numbers” list? Unblock if needed. Also check for “block unknown callers” or “spam protection” features that can be surprisingly aggressive on Android builds.
- If you’re using a different app than you think (Google Messages vs a carrier app), verify the block/report settings inside that app. Android can route messaging through the “default SMS app,” so a block in one app won’t show up if another app is actually sending.
- Look for signs the recipient might be filtering messages (some phones/carriers can auto-filter unknown or suspicious senders). Even if you’re in their contacts, “message request” style filtering can happen on certain devices/carriers if your number was previously flagged.
Quick comparison: RCS vs SMS vs MMS on Android
This helps you understand what “can’t receive from your number” usually looks like when the message type differs.
| Criteria | RCS (Chat) | SMS | MMS |
|---|---|---|---|
| Delivery dependence | Operator data path + RCS support | Mobile signaling path | Carrier MMS gateway + settings |
| Common “silent fail” causes | RCS capability mismatch | Invalid routing, number formatting | APN/MMS not enabled, size limits |
| Media success rate | Usually good when both sides support RCS | Not designed for rich media | More fragile than text/SMS |
| What you often see in Android | “Not delivered” / no updates | “Sent” with no “delivered” | “Failed” for photos/links |
| When it’s best for troubleshooting | Try switching off Chat to test SMS path | Great “ground truth” for text delivery | Use for confirming MMS settings/APN issues |
Step 3: Verify your Android message settings (SMS vs RCS)
Android messaging can route the same conversation through different systems depending on capability. When RCS/Chat is involved, delivery can fail even though your phone shows “sent,” especially if the recipient’s device/app can’t handle RCS reliably.
- Confirm your default messaging app (Android “Default apps”): if the wrong app is handling messages, delivery can behave differently. In Settings > Apps > Default apps (wording varies by manufacturer), ensure the app you expect is set as the SMS app.
- If you use Google Messages Chat/RCS, try switching that conversation to SMS (or temporarily disable Chat/RCS) and resend the same text. If the SMS arrives immediately afterward, you’ve proven the issue is likely RCS capability or account provisioning, not a block.
- For MMS, confirm you have “MMS messaging” enabled in your messaging app settings (if MMS is disabled, images/links may fail). Also confirm mobile data is available when sending MMS—many carriers require data signaling to fetch the media after the MMS is negotiated.
Android messaging reality check (important)
RCS and SMS aren’t the same “channel.” RCS (often called “Chat” in Google Messages) is IP-based messaging that relies on operator provisioning; SMS is a legacy signaling system. MMS is SMS for media, but it requires MMS-specific gateway support and correct configuration. If one person’s phone/carrier handles these differently, you’ll see exactly the “only one contact” symptom.
Step 4: Troubleshoot the send/delivery path on your device
Now you validate what the Android side is actually doing in that moment. This step is about interpreting delivery status correctly and removing formatting/media variables.
- Open the conversation and check delivery status (e.g., “sent,” “delivered,” or “failed”). If it’s “failed,” focus on signal/app settings first; “sent” without “delivered” is often an SMS routing or filtering issue.
- Restart your phone and resend a short plain-text message (this helps rule out formatting/media issues). Sending a two-to-five-word SMS is the cleanest test because it avoids emoji/unicode edge cases and large payloads.
- If it still won’t go through, clear cache for your messaging app (avoid deleting data unless you’re comfortable re-signing into anything tied to the app). Clearing cache is usually safer than “Clear storage,” which can reset RCS setup or notification permissions.
Quick “what I look for” interpretation
From a practical standpoint, these patterns usually isolate the root cause fast on Android:
- Plain text fails too → likely number/formatting, block/filtering, or SMS routing.
- Plain text arrives, media fails → likely MMS settings (or message size/type mismatch).
- Only one contact affected → likely recipient-side support/capability differences (RCS/SMS handling) or their filtering rules.
What can go wrong (common edge cases)
Even if you follow the steps above, Android SMS/MMS behavior can still be confusing due to carrier routing rules, message encoding, and how the other phone handles chat threads.
- Character limits and formatting: very long texts or unusual formatting can fail depending on how your device encodes the message (7-bit GSM vs Unicode). Multipart segmentation can also make some gateways more sensitive.
- Group chats: if only one person is missing, group settings (or their device/app) may handle the thread differently. Sometimes Android devices in the same group switch message types differently per recipient.
- Carrier differences: one carrier may handle SMS/MMS routing more strictly than another, especially for media. It’s why “other contacts work” doesn’t fully rule out a network problem.
- RCS compatibility: if you’re sending via RCS to someone on a device/app that can’t receive RCS, the message type may break or never deliver as expected.
Message length/encoding limits that can break delivery on Android
If your “failed” messages correlate with longer texts, emoji, or links, encoding limits often explain why. According to 3GPP TS 23.040, a standard GSM SMS can carry 160 characters using the GSM 7-bit alphabet (spec describes the 160-character payload, used widely in operator implementations). Similarly, multipart concatenated SMS reduces the per-segment payload to 153 characters under the same encoding scheme (3GPP TS 23.040). And according to 3GPP TS 23.040, when the message requires Unicode (UCS‑2), the typical single-SMS payload is 70 characters and concatenated segments drop to 67 characters.
SMS Payload Limits That Affect Delivery (Operator-Standardized)
| # | SMS encoding / format | Single SMS limit | Multipart per segment | Fragility vs single (spec reduction) |
|---|---|---|---|---|
| 1 | GSM 7-bit (default alphabet) | 160 chars | 153 chars | 0.0% ★★★☆☆ |
| 2 | GSM 7-bit (concatenated) | 160 chars | 153 chars | -4.4% ★★☆☆☆ |
| 3 | UCS‑2 / Unicode (single SMS) | 70 chars | 67 chars | 0.0% ★★★☆☆ |
| 4 | UCS‑2 / Unicode (concatenated) | 70 chars | 67 chars | -4.3% ★★★★★ |
| 5 | 8-bit (binary) payload | 140 bytes | 134 bytes | 0.0% ★★★☆☆ |
| 6 | 8-bit (binary, concatenated) | 140 bytes | 134 bytes | -4.3% ★★★★★ |
| 7 | Concatenation header overhead (UDH) | 6 octets | — | -4.3% ★★★★★ |
Verdict / tip: Use a “narrow test” to find the cause fast
The quickest path is to force the Android side to send the simplest possible message type first—then toggle only one variable at a time. In practice, start by sending a short plain-text message to the same contact, then test again with Chat/RCS off (or resend as SMS), and enable/verify MMS only if you’re sending photos/links.
This narrow test works because it separates three failure classes on Android: (1) number/block/filter issues, (2) RCS capability mismatch issues, and (3) MMS/media path problems. The downside: toggling RCS/Chat can change how the conversation looks and behaves, so it’s best for troubleshooting rather than leaving permanently. Skip this approach if you rely on RCS features daily and don’t want conversation behavior to switch—use it only until delivery is resolved.
Quick checklist (scan/save)
| Check | What to look for | What to do next |
|---|---|---|
| Signal + airplane mode | No bars / message fails | Toggle airplane mode, switch networks |
| Number + contact saved | Wrong digit/country code | Re-enter number or verify contact |
| Block list | Your number is blocked (or you blocked them) | Unblock in messaging app/phone settings |
| Default messaging app | Messages handled by the “wrong” app | Set the correct default app |
| RCS/Chat vs SMS | Only this person never gets it | Temporarily disable/enable Chat and resend |
| MMS enabled | Texts with media never deliver | Turn on MMS messaging in app settings |
Frequently Asked Questions
Why are my texts not showing up on my recipient’s Android phone?
This usually happens when the message isn’t being delivered due to SMS/MMS settings, carrier issues, or a blocked contact. Start by checking that you’re using the correct message type (SMS vs MMS) and that Mobile Data and/or Cellular service are working. Also confirm the recipient hasn’t blocked your number and that you don’t have a conversation showing “Not sent” or “Send failed.”
How can I tell if my Android text is failing delivery or getting blocked?
On many Android phones, failed delivery is indicated by messages showing an error like “Not sent,” a retry prompt, or a different status icon. If your texts appear to send but the recipient reports not receiving them, check whether your number is blocked and whether your carrier shows any messaging outages. You can also test with a different contact or send the same message to another phone to isolate whether the issue is specific to one recipient.
What SMS settings should I check on Android if only one person isn’t receiving my messages?
Verify that your Messaging app is set as the default SMS app and that you have the correct APN and carrier configuration for SMS/MMS. If you’re sending pictures or group messages, confirm MMS is enabled and that your APN supports multimedia messaging. It can also help to turn Wi‑Fi off temporarily (or on, depending on your setup) to ensure cellular messaging is functioning correctly.
Which fixes work best when my Android is not receiving delivery reports or my texts never arrive?
First, restart your phone and toggle Airplane mode briefly to refresh network registration. Then clear the cache of your Messages app and check for software updates, since outdated messaging services can break delivery. If the problem persists, reset your network settings and confirm your carrier messaging center/SMS settings are correct (often restored automatically with the right carrier APN).
Best practices to avoid “message not received” issues when texting Android users?
Use SMS for plain text and confirm MMS is available for media, especially when switching between different carriers or Android-to-Android apps. Keep an eye on your signal strength and avoid sending while your phone is on a weak/unstable network, as that can cause delivery delays or failures. Finally, if someone recently changed phones or numbers, recheck that you’re texting the correct number and not an old contact entry.
📅 Last Updated: November 12, 2026 | Topic: why is someone not receiving my texts android | Content verified for accuracy and freshness.
References
- Text messaging
- SMS
- Short Message service center
- Multimedia Messaging Service
- Rich Communication Services
- Mobile phone spam
- https://en.wikipedia.org/wiki/Call_barring
- https://scholar.google.com/scholar?q=android+sms+not+receiving+troubleshooting Google Scholar
- https://scholar.google.com/scholar?q=rcs+message+delivery+failure+android Google Scholar
- https://scholar.google.com/scholar?q=short+message+service+delivery+failure+causes+carrier+blocking Google Scholar