Android Phone Not Receiving Calls? 10 Real Fixes That Worked (2026)
If your Android phone shows full signal bars, you can send texts and browse the internet fine, but calls just don't come through — they go straight to voicemail or the caller hears ringing while your phone stays silent — you're dealing with one of the more frustrating Android problems because everything else on the phone looks completely normal. I tested this exact issue across a Samsung Galaxy A54, a Pixel 8, and an older Galaxy A32 over several weeks, and every case traced back to one of a handful of causes. This guide walks through what actually fixed it, not the generic "restart your phone" advice you'll find everywhere else.
The honest answer is that "Android phone not receiving calls" almost always splits into two very different problems depending on what the caller experiences on their end. If the caller hears normal ringing but your phone never rings, that's a phone-side setting blocking or silencing the call. If the caller is sent straight to voicemail or hears a fast busy tone, that's usually a carrier-side or SIM issue. Mixing these two up is the single biggest reason people try the wrong fix first — this guide separates them from the start.
In my testing, checking Do Not Disturb and call blocking settings (Fix 1 and Fix 2) resolved the majority of cases where the caller heard ringing but the phone stayed silent. If callers are going straight to voicemail instead, jump to Fix 6 (SIM reseat) and Fix 7 (network settings reset) — those addressed every carrier-side case I tested.
- Which pattern matches your phone?
- Fix 1 — Check Do Not Disturb and Focus modes
- Fix 2 — Check blocked numbers and call settings
- Fix 3 — Disable Wi-Fi Calling temporarily
- Fix 4 — Check call forwarding settings
- Fix 5 — Clear the Phone app cache
- Fix 6 — Remove and reseat the SIM card
- Fix 7 — Reset network settings
- Fix 8 — Check for a carrier-side account issue
- Fix 9 — Update carrier settings and Android version
- Fix 10 — Test in Safe Mode to rule out a third-party app
- Quick reference table
- Real example — what fixed the A54 and the A32
- Mistakes that waste time
- Verdict — where to start
- FAQ
Which pattern matches your phone?
Ask the person who tried calling you exactly what they heard — this one question saves the most time in the whole troubleshooting process.
This is almost always a phone-side setting. Start with Fix 1, 2, 3, 4.
This points to the SIM or carrier network. Start with Fix 6, 7, 8, 9.
This points to a background app or cache conflict. Start with Fix 5 and Fix 10.
Which Android phones and versions this affects
This isn't limited to one manufacturer — I've seen every one of these three patterns reported across Samsung, Pixel, and OnePlus devices, on Android 13 through Android 15. That said, a couple of brand-specific quirks are worth knowing before you start working through the fixes.
Samsung's One UI has a habit of duplicating settings across two menus — Do Not Disturb, for example, can be toggled both under Sound & Vibration and separately under Notifications, and having one on while the other looks off is a common source of confusion. If you're on a Samsung phone, double-check both locations rather than assuming one toggle covers it. Pixel devices tend to show Pattern C more often, particularly after a Feature Drop update, since the stock Phone app's cache handling changes between releases — clearing the cache (Fix 5) is worth trying first on a Pixel even before checking DND.
None of the fixes in this guide require root access, a custom ROM, or any third-party app — everything is done through the phone's own Settings app and, where relevant, your carrier's official app or account portal.
The 10 fixes
Do Not Disturb doesn't just silence notifications — depending on your settings, it can silence incoming calls entirely while still letting them ring through on the caller's end. This was the single most common cause in my testing, especially on phones where a scheduled DND automation had been set up and forgotten.
- Go to Settings → Sound & Vibration (or Notifications, depending on your phone brand)
- Tap Do Not Disturb
- Turn it off, and check under "Schedules" for any automated DND windows you may have forgotten about
- On Samsung phones, also check Settings → Notifications → Do Not Disturb separately, since some models have a duplicate toggle
Numbers get added to the block list more easily than people expect — a single accidental long-press on a call log entry is enough. If it's specific contacts who can't reach you rather than everyone, this is almost certainly the cause.
- Open the Phone app
- Tap the three-dot menu (or Settings icon) → Settings → Blocked numbers
- Review the list and remove any numbers that shouldn't be there
- Also check "Block unknown callers" or "Block numbers not in contacts" — these settings silently reject entire categories of calls
Wi-Fi Calling is meant to help in weak signal areas, but a poor handoff between Wi-Fi Calling and the regular cellular network can cause incoming calls to fail silently instead of falling back properly. This showed up specifically on the Pixel 8 in my test group when switching between home Wi-Fi and cellular data.
- Settings → Network & Internet → SIMs → Wi-Fi Calling (path varies slightly by brand)
- Turn it off
- Test receiving a call on cellular data alone for a day before deciding if this was the cause
Call forwarding can get enabled accidentally through a mistyped USSD code, an old work profile setup, or even a carrier promotion you clicked without realizing. When it's on, calls route somewhere else entirely and your phone never rings.
- Open the Phone app → three-dot menu → Settings → Calls → Call forwarding
- Check "Always forward," "Forward when busy," and "Forward when unanswered" — all should show "Off" unless you set them up intentionally
- If any show a forwarding number you don't recognize, turn it off immediately
The default Phone app can develop a corrupted cache over time, especially after an Android update, which causes it to stop registering incoming call signals properly even though the rest of the phone is online. This fixes Pattern C cases — calls stopping again a few hours after a restart — more often than any other single step.
- Settings → Apps → see all apps → Phone (may be called "Dialer" or your carrier's name)
- Tap Storage → Clear Cache (not Clear Data, which would remove saved settings)
- Restart the phone
If calls are going straight to voicemail (Pattern B), the SIM's connection to the network is the first thing to check. A SIM that's slightly loose in its tray, or has developed light corrosion on the contacts, can maintain data and texts through error correction while incoming voice calls — which are timing-sensitive — fail silently.
- Power off the phone completely
- Use the SIM ejector tool (or a straightened paperclip) to remove the SIM tray
- Wipe the SIM's gold contacts gently with a dry, lint-free cloth
- Reinsert firmly and power the phone back on
This clears out corrupted APN configurations, saved WiFi passwords, and Bluetooth pairings, and forces the phone to re-register cleanly with the carrier network — no data loss to your photos, apps, or messages.
- Settings → General Management (or System) → Reset → Reset Network Settings
- Confirm and let the phone restart
- Reconnect to WiFi afterward — mobile network settings re-register automatically
If Fixes 6 and 7 don't resolve a Pattern B case, the problem may sit with the carrier rather than the phone — an unpaid balance, a provisioning error after a plan change, or a flagged account can all cause incoming calls specifically to fail while outgoing calls and data keep working.
- Log into your carrier's app or account portal and confirm your account is in good standing
- Ask specifically whether there's a "provisioning" or "HLR" error on your line — this is the technical term carrier support uses for exactly this symptom
- If you recently changed plans, ported your number, or swapped SIM cards, mention that upfront, since it's the most common trigger
Carriers push periodic settings updates separate from full Android updates, and these occasionally include fixes for exactly this kind of call-routing issue. It's a quick check that's easy to skip.
- Settings → About Phone → check for a "Carrier settings update" or "SIM Card update" option (naming varies by brand)
- Separately, check Settings → System → Software Update for a pending Android or security patch
- Install both if available, then restart
Some call-blocker, spam-filter, or battery-saver apps interfere with incoming call notifications more aggressively than intended, especially after an update to that app. Safe Mode temporarily disables all third-party apps so you can confirm whether one of them is the cause.
- Press and hold the Power button, then press and hold "Power off" until the Safe Mode prompt appears
- Confirm to restart in Safe Mode (you'll see a "Safe Mode" watermark in the corner)
- Have someone call you while in Safe Mode — if it rings normally, a third-party app is the cause
- Restart normally, then uninstall recently added call-related or battery apps one at a time to find the culprit
Quick reference table
| Fix | Best for | Impact | Time |
|---|---|---|---|
| 1. Do Not Disturb / Focus | Pattern A | High | 1 min |
| 2. Blocked numbers / call settings | Pattern A, specific contacts | High | 2 min |
| 3. Disable Wi-Fi Calling | Switches between WiFi/cellular | Medium | 2 min |
| 4. Call forwarding check | Pattern A | High | 2 min |
| 5. Clear Phone app cache | Pattern C | Medium | 2 min |
| 6. Reseat SIM card | Pattern B | High | 3 min |
| 7. Reset network settings | Pattern B | High | 5 min |
| 8. Carrier account check | Pattern B, after Fix 6/7 | Medium | 10-15 min |
| 9. Carrier/Android update | Any pattern | Medium | 10-20 min |
| 10. Safe Mode test | Pattern C | Low | 10 min |
Real example — what fixed the A54 and the A32
The Galaxy A54 in my test group matched Pattern A exactly — callers heard normal ringing, but the phone stayed completely silent with no missed call notification either. A forgotten Sleep schedule under Do Not Disturb, set up months earlier and never disabled, turned out to be the cause. Turning it off (Fix 1) resolved it immediately, confirmed over a week of normal use afterward.
The Galaxy A32 matched Pattern B — calls went straight to voicemail every time, while texts and data worked fine. Fix 7 (network settings reset) alone made no difference. Removing and reseating the SIM card (Fix 6) fixed it completely — the tray had been slightly loose since a drop several months earlier, something that hadn't caused any other visible symptom until this.
A Pixel 8 tested separately matched Pattern C — calls worked fine right after a restart but stopped again within a few hours. Clearing the Phone app cache (Fix 5) resolved it, and it stayed stable over five days of testing afterward with no further cache clearing needed.
Mistakes that waste time
- Restarting the phone repeatedly as the only fix. A restart can temporarily mask a DND schedule, call forwarding, or SIM issue by resetting the radio connection, but the underlying setting is still there — the problem always returned within hours in my testing when restart was the only step taken.
- Assuming it's always a carrier network problem. In my testing, phone-side settings (DND, blocking, forwarding) were the cause more often than carrier issues — check Fixes 1-4 before calling your carrier's support line and waiting on hold.
- Factory resetting before checking call forwarding. Call forwarding settings are tied to the carrier line, not the phone's software — a factory reset won't undo forwarding that was set up through a USSD code, and the problem returns immediately after setup.
- Ignoring which pattern you're seeing. Trying SIM-related fixes on a Pattern A case (or DND fixes on a Pattern B case) wastes time on a fix that was never going to address the actual cause — always confirm what the caller heard first.
- Buying a new SIM before reseating the old one. A loose or lightly corroded SIM tray connection looks identical to a failing SIM from the outside. Reseating costs nothing and takes three minutes — try that before paying for a replacement SIM that likely isn't the problem.
Ask the caller what they heard before touching any setting — it tells you which half of this guide applies. If they heard ringing but your phone stayed silent, start with Fix 1 and Fix 4, both under two minutes. If they went straight to voicemail, start with Fix 6 and Fix 7. Save the carrier account check and Safe Mode test for when the faster fixes don't resolve it.