When Your Android Phone Stops Receiving MMS: A Step-by-Step Diagnostic Guide

Your phone sends texts fine. It even sends the occasional photo. But somewhere along the way, incoming picture messages, group chats, or SMS with emoji started vanishing—or arriving hours late, or not at all. The sender sees a delivered receipt. Your phone shows nothing. This is one of the more frustrating Android failures because it sits at the intersection of your device, your messaging app, and your carrier's network configuration, and each party is quick to blame the other two.

The good news is that the failure pattern is common enough that carriers, community forums, and support threads have documented a fairly reliable sequence of fixes. The bad news is that no single step resolves every case, and some of the most commonly repeated advice—install this app, reset your phone—can waste days before you land on the actual cause. What follows is an ordered diagnostic path, from least invasive to most, with guidance on what to do when each step fails.

Before starting, confirm the symptom precisely. Can you receive plain SMS? Can you send MMS but not receive them? Does the failure affect one contact, one group chat, or everyone? A Samsung Galaxy S25+ owner on AT&T reported that the problem affected both group chats and one-to-one threads, and that SMS containing emoji also failed—a pattern that points toward a carrier or APN issue rather than a single corrupted conversation ^¹. If your failure is similarly broad, start at step one. If it is isolated to one thread, deleting that conversation may be enough, and the steps below are overkill.

1. Restart the phone and toggle Airplane Mode. Power the device off completely, wait a few seconds, and power it back on. This clears transient radio and messaging-service states. If that does not help, toggle Airplane Mode on for thirty seconds and off again to force a fresh network registration. This step is the standard first move in carrier troubleshooting guides and costs nothing ^².

2. Confirm MMS is actually enabled and set to auto-download. In Google Messages, open your profile picture, go to Messages settings, then Advanced, and verify that auto-download MMS is on and that group messaging is set to send an MMS reply to all recipients. Manufacturers sometimes bury these toggles in different places, so the exact path varies, but the settings themselves are standard. If auto-download is off, incoming MMS may sit in limbo until you manually retrieve it—or never arrive if the retrieval window expires.

3. Check whether the Carrier Services app is installed and up to date. This is the step most likely to be skipped and most likely to matter. Carrier Services provides the background services that support RCS messaging in Google Messages, and a Google Fi community response noted that nine out of ten times a Samsung device fails to receive MMS, the cause is that Carrier Services is missing ^³. The same thread includes a user who was told by support to install the app, refused because they believed it was unnecessary, and later found that the standard steps—which included ensuring Carrier Services was present—resolved the problem without any separate third-party app. If you use Samsung's proprietary messaging app rather than Google Messages, Carrier Services may still be relevant to RCS functionality, but the dependency is less direct. Check the Play Store for the app, install or update it, then restart the phone and test again.

4. Reset the APN settings. The Access Point Name configuration tells your phone how to connect to mobile data, and MMS rides on that connection. A carrier support guide recommends resetting APN settings to restore the carrier's defaults as a standard troubleshooting step. On most Android phones this lives under Settings, Network and Internet, Mobile network, Access Point Names, with a reset option in the overflow menu. After resetting, restart the phone and send yourself a test MMS from another device.

5. If the reset APN does not work, compare against a known-good device on the same carrier. This is the step that broke the case open for the AT&T user on the Samsung community forum. After two store visits, six calls to technical support, a factory reset, and a warranty replacement phone—none of which fixed the issue—the user researched an alternate AT&T APN and compared settings against a Pixel 10 Pro on the same network that was not experiencing the problem. Combining a few settings from that comparison produced a working configuration. The same user noted the issue had followed them across an S22 and a new S26, reinforcing that the problem was not device-specific. The practical takeaway: if a factory reset and a new phone did not fix it, the problem is almost certainly in the APN or the carrier provisioning, not the hardware.

6. Switch messaging apps as a diagnostic, not a permanent fix. The AT&T user had always used Textra but switched to Google Messages while troubleshooting, and ultimately accepted Google Messages with RCS enabled as part of the working solution. This does not mean Google Messages is inherently more reliable—it means that if a third-party app is handling MMS through its own APN or service configuration, switching to the stock app can isolate whether the problem lives in the app or beneath it. If MMS works in Google Messages but not in your preferred app, the issue is app-level configuration. If it fails in both, return to the APN and carrier steps.

7. Contact the carrier with specifics. Generic "MMS not working" tickets tend to produce generic responses. Instead, report what you have already tried, whether the failure affects SMS as well as MMS, whether it persists after an APN reset, and whether a known-good device on the same account works. The AT&T user's experience suggests carriers may replace hardware before diagnosing provisioning, so arriving with evidence that a second phone failed identically can redirect the conversation.

What to do when a step fails: if steps one through four do not resolve the issue, do not factory reset yet. A factory reset erases data and, as the AT&T case demonstrates, may not fix a carrier-side problem at all. Move to the APN comparison in step five first. If you cannot find a known-good device to compare against, ask your carrier for the current MMS APN values in writing and verify each field—MMSC, MMS proxy, MMS port, and APN type—against what is on your phone. If the carrier cannot or will not provide them, that is itself useful information.

One persistent confusion deserves clarification. RCS, the successor to SMS and MMS, uses mobile data or Wi-Fi rather than the traditional carrier messaging channel, and troubleshooting guides for RCS differ from those for MMS. If your phone has RCS enabled and the failure involves chat features rather than picture messages, you may be troubleshooting the wrong service. Check whether the failing messages are green (SMS/MMS) or blue/chat-style (RCS) in your messaging app before proceeding.

What remains genuinely unresolved is why certain carrier provisioning changes cause MMS failures on specific accounts while leaving others untouched. The AT&T user concluded that the carrier or Google "obviously changed something," but no source confirms a specific cause or a formal carrier acknowledgment. That ambiguity is exactly why the diagnostic sequence matters: when the root cause is opaque, the only reliable path is to eliminate variables one at a time, starting with the cheapest and least destructive.

Sources

1. ¹ Re: Carrier is ATT. Unable to reliably receive MMS messages or any messages wi.. - I am using an S25+ us.community.samsung.com
2. ² Troubleshooting your Texts (SMS) and MMS help.smartlessmobile.com
3. ³ This is not a question - it's a PSA: if Android phone messenger app fails to receive texts - Send feedback on support.google.com