Incoming Call Notification Not Showing on Android: Diagnose and Fix

If your Android phone rings but no incoming call screen appears, no caller name shows up, and the answer/decline buttons never slide into view, you are not alone — the symptom looks like a single bug, but it actually maps to half a dozen different root causes across Android versions, OEM skins, and third-party apps. This guide skips the generic checklist and walks you through what each variation of the problem actually means, the 60-second triage that fixes most cases, the universal settings to check, the OEM-specific paths for Samsung, Xiaomi, OPPO, Vivo, and Pixel, and a symptom-to-fix table you can scan in 30 seconds. If a specific app is the culprit rather than the dialer, a Discord badge that won't clear is a common app-level example.

What 'Incoming Call Notification Not Showing' Actually Looks Like

The phrase covers four distinct symptoms, and each one points at a different root cause. Confirm which variation matches your experience before you start changing settings.

• Variation 1: the phone rings audibly but the full-screen call UI never appears. The ringer plays, but you see no caller ID, no answer or decline buttons, and no overlay on top of whatever app was in front. This usually means the heads-up overlay is failing or the Display-over-other-apps permission has been revoked from the dialer.
• Variation 2: the ringer is silent but a missed-call entry shows up later. The call did arrive, but Do Not Disturb, Focus mode, or a Bedtime schedule suppressed both the sound and the visual notification at the same time.
• Variation 3: the call screen only appears after you manually unlock the device. The Phone app process was killed in the background, so the OS could ring but could not draw the lock-screen overlay until you woke the device yourself.
• Variation 4: the problem only happens with specific contacts or only with unknown numbers. A contact-level block, a third-party caller ID filter, or the spam-call setting in the Phone app is intercepting only that subset of calls.

Knowing which row you are in narrows the fix list from a dozen options down to one or two.

60-Second Triage Checklist Before You Change Any Settings

Before you dive into Settings menus, run this 60-second pass — most call-screen failures are transient and clear with a restart or a quick toggle.

1. Force restart the phone. Hold the power and volume-down buttons together until the device reboots. A clean restart clears system UI glitches that can swallow the incoming call screen.
2. Have someone call you right now. Watch the screen with the phone face-up. Does it light up at all? Does the ringer play? Knowing whether the system is firing the call event but failing to draw the UI narrows the root cause dramatically.
3. Check Do Not Disturb. Swipe down to the quick-settings panel and confirm DND is off. A DND profile can ring audibly while still suppressing the heads-up banner.
4. Confirm you are not in Focus, Bedtime, or Driving mode. Each of these can hide the call UI even when the phone is ringing.
5. Toggle airplane mode on, wait five seconds, then off. This resets the cellular radio and re-registers the device with the network.
6. Pull down the notification shade during a test call. If a notification is sitting there, the call event is reaching the OS — only the heads-up overlay is broken.

Root Causes: Why the Call Screen Fails to Appear

The same symptom — a ringing phone with no call UI — has several distinct technical causes. Identifying which one applies saves you from cycling through every fix.

• Battery optimization is killing the Phone app. Aggressive memory management terminates the dialer process in the background, so when a call arrives the system can ring but cannot draw the in-call UI in time.
• Do Not Disturb call exceptions are misconfigured. You may have allowed calls to ring audibly but left the visual notification suppressed — Android treats these as separate switches.
• Heads-up notifications are disabled for the Phone app. Without the pop-up style, you only get a silent banner that never overlays the lock screen.
• Focus mode, Bedtime mode, or Digital Wellbeing schedules can suppress the call UI on a recurring window even when you are actively using the phone.
• 'Display over other apps' permission was revoked. The Phone app needs system-overlay rights to draw the full-screen call interface over whatever you were doing.
• A third-party caller ID app has hijacked the incoming call screen. Truecaller, Hiya, and similar apps replace the native UI — if they crash, the replacement never paints.
• An accessibility service is interfering with the system UI overlay. Screen readers, gesture-control apps, and screen recorders sometimes block the call window from drawing.
• Call forwarding is accidentally enabled. If unconditional forwarding is on, the call is routed away before your device ever shows a screen for it.

The fix changes meaningfully depending on which of these is responsible, which is why the next two sections walk through the universal sequence first and then map it to your specific phone brand.

Core Fixes That Work on Any Android Version

Run these in order. Stop the moment a test call shows the full call screen again — you do not need to keep applying changes.

1. Re-enable Phone app notifications. Go to Settings → Apps → Phone → Notifications and turn every category on. Pay special attention to the channel labelled Incoming calls — it is often disabled separately from missed calls and voicemail.
2. Set the Incoming calls channel to heads-up / pop-up style. Inside that same Notifications screen, tap the Incoming calls channel and choose Alerting or Pop on screen so the banner overlays whatever app is in focus.
3. Grant Display over other apps to the Phone dialer. Settings → Apps → Special access → Display over other apps → Phone → Allow. Without this, the full-screen call UI cannot paint over the lock screen or the current foreground app.
4. Disable battery optimization for the Phone app. Settings → Apps → Phone → Battery → Unrestricted (or Don't optimize). This stops the OS from killing the dialer process between calls.
5. Clear the Phone app cache — but not its data. Settings → Apps → Phone → Storage → Clear cache. Clearing data wipes call history and settings; clearing cache only resets the UI process.
6. Cancel all call forwarding. Open the dialer and dial ##21# then press call. The network confirms unconditional forwarding has been cleared.
7. Disable or uninstall third-party caller ID apps temporarily. Truecaller, Hiya, CallApp — turn them off one at a time and test. If the native call screen returns, you have your culprit.
8. Reset the default dialer or reinstall the Phone app. If you switched dialers at some point, Settings → Apps → Default apps → Phone app → pick Google or your OEM's native dialer. If you are running Google's Phone app, uninstall its updates from the Play Store and let it reinstall fresh.

OEM-Specific Paths: Samsung, Xiaomi, OPPO/Vivo, and Pixel

Menu paths differ across Android skins, and Chinese OEMs ship with aggressive task-killing enabled by default — that single setting is the most common offender on those devices.

• Samsung One UI. Settings → Apps → Phone → Battery → Unrestricted. Also open Modes and Routines and check that no Driving, Sleep, or Work routine is muting visual call notifications. Settings → Notifications → Advanced settings → Floating notifications → enable Smart pop-up view.
• Xiaomi MIUI / HyperOS. Open the Security app → Permissions → Autostart and enable autostart for the Phone app. Then Settings → Battery → Battery saver → Phone → No restrictions. For lock-screen visibility, Settings → Notifications & Control center → Lock screen notifications → make sure Phone is allowed to show on the lock screen. MIUI's task killer is the single biggest reason call screens fail on Xiaomi.
• OPPO / Vivo ColorOS and FuntouchOS. Settings → Battery → App battery management → Phone → toggle on Allow background activity and Allow auto-launch. Then Settings → Notification & status bar → Notification management → Phone → enable Lock screen notifications and Banner. Both skins also have a Game Mode / Do Not Disturb scheduler — check it isn't running.
• Google Pixel / stock Android. Settings → Apps → Phone → Notifications → Incoming calls → Pop on screen. Settings → Battery → Battery usage → Phone → Unrestricted. Pixels are usually the least aggressive about background restrictions, so if a Pixel is misbehaving, the cause is more likely a third-party app or a DND profile than battery optimization.

If your device is from Huawei, Honor, Realme, or another OEM not listed, look for two settings: an autostart or background-launch toggle for the Phone app, and a battery-restriction exception. Those two together solve the majority of OEM-skin cases.

Symptom-to-Fix Map: Pick the One That Matches Your Case

If you only have time for one fix, match your exact symptom to the row below and apply just that fix first.

Apply the single matching fix, place a test call, and only move on if the symptom returns. For households where missed calls land on a child's phone, NexSpy covers the parent-side call-log mirror that catches the call even when the visual notification fails.

How NexSpy Adds a Parent Safety Net When Calls Keep Slipping Through

This section is for parents reading the article — not because NexSpy fixes the underlying Android bug (the steps above do that), but because once a child's phone has shown it can drop the call screen unpredictably, parents reasonably want a backstop. NexSpy's calls and SMS safety on Android sits next to the OS fix and gives the Parent Dashboard visibility into what calls and texts the child's device is actually receiving, so a missed parent-to-child call is never silently lost in the gap between the network and the UI.

The matched use case here is narrow on purpose. NexSpy is not a system overlay that forces the call UI to appear — Android itself controls that. What NexSpy adds is context: a parent can review the call log from the Parent Dashboard, see whether their own call connected or was missed, and adjust who is allowed to ring through in the first place.

Call log context for parent review

When the call-screen failure intermittently swallows incoming calls on a child's phone, the Parent Dashboard becomes the source of truth. The call log shows who called the child's device, when, and whether the call was answered or missed — so a parent who tried three times to reach their child during the afternoon can confirm whether the calls actually arrived at the device or were dropped before delivery. That distinction matters: a delivery problem is a carrier issue, a UI problem is the Android fix above, and a “she had her ringer on silent” problem is a conversation worth having calmly with the child rather than a settings dive.

Blacklist, whitelist, and automatic spam blocking

Part of why kids learn to ignore the ringer is volume — repeated unknown-number spam trains the child to swipe past every call. NexSpy supports a call blacklist and whitelist on Android, plus automatic spam call blocking from the blacklist. The practical effect is meaningful: junk calls don't ring through, the ringer keeps its meaning, and when a parent does call, the child is more likely to actually pick up. Parents can also whitelist specific family numbers so those calls always break through, even when other call restrictions are in place.

SMS keyword alerts as a backup channel

When the call UI on the child's device misbehaves and a parent cannot get through by voice, SMS often becomes the fallback channel. NexSpy adds real-time keyword alerts on sent or received SMS, so urgent messages containing parent-defined keywords surface in the dashboard immediately rather than waiting for the next sync. Coverage is keyword-based by design — NexSpy is not pulling full chat logs, only flagging on words and phrases the parent configures — which keeps the feature inside lawful parental supervision rather than blanket message reading.

A few honest limits worth naming. Calls and SMS controls in NexSpy are Android-only — they do not work on iOS child devices because Apple does not expose the equivalent APIs. SMS coverage is keyword-based by default, not a full message archive. And exact behavior depends on the Android version on the child device and which permissions the parent grants during setup. The framing throughout is lawful parental supervision of a minor's device — call log context, spam blocking, and keyword alerts on a phone the parent owns and a child uses — not covert wiretapping of an adult's communications.

If you fix the Android call screen this afternoon but want a Parent Dashboard view of the child's call activity so the next intermittent failure doesn't slip past unnoticed, NexSpy is the layer that adds that visibility on Android.

When to Stop Troubleshooting and Contact Support

If you have worked through the universal fixes, the OEM-specific path for your phone, and the symptom-to-fix table without recovering the call screen, the next step is not more settings — it is isolating the layer below.

1. Boot into safe mode. This disables every third-party app. Place a test call. If the screen appears in safe mode, a third-party app is the culprit and you can uninstall recent additions one at a time.
2. Swap in a different SIM if one is available. This isolates carrier-side call delivery from device-side UI rendering.
3. Factory reset only after a full backup. If the call screen still fails after a clean reset, the issue is likely hardware (often the proximity sensor) or carrier provisioning.
4. Escalate. Open a ticket with the OEM (Samsung Members, Mi Community, Pixel Support) or your carrier, and include a 24-hour log of which calls failed, from whom, and on which network.