Notifications Not Showing on Android: The Fix Order That Works

The group chat lit up on your friend's phone an hour before it reached yours. A delivery update that should have landed at nine in the morning shows up stamped two in the afternoon, hours after the package was already on the porch. Nothing in your settings looks obviously wrong: sound is on, the app is installed, you never touched Do Not Disturb. Notifications not showing android is rarely one broken setting. It is usually one of a handful stacked on top of each other, and the fastest way through it is checking them in an order that actually finds the culprit instead of guessing.

Here is that order, starting with the setting that overrides everything else on the list.

Start with the switch that overrides everything

Every app on Android has one master notification toggle, under Settings, Apps, the app in question, Notifications. If that switch is off, nothing downstream matters. Battery settings, channel importance, Doze exceptions, none of it runs, because the app is not permitted to post a notification at all. This gets flipped more often than people expect: a system update resets it, an app update re-triggers the permission prompt and gets denied by accident, or a "clean my phone" utility turns it off as part of a supposed optimization.

Check this one first because it explains total silence, not delay. If notifications are merely late rather than completely absent, this switch is already on and the cause is further down the list.

Per channel settings inside the app

Since Android 8, a notification does not belong only to an app. It belongs to a channel inside that app, and the channel, not the app as a whole, decides whether it makes a sound, shows a banner, or shows up at all. A messaging app might have separate channels for direct messages, group chats, and account alerts, each with its own importance level.

Open the app's notification settings and look at the channel list. A channel set to low importance still delivers the notification, but silently and without interrupting the screen, which looks identical to app notifications delayed until you actually go check the shade. A channel set to blocked delivers nothing at all. If one specific type of message is missing while others from the same app arrive fine, this is almost always where the difference lives.

Battery management, the usual culprit

If the app-level and channel-level settings both look correct and notifications are still late or missing, the next suspect is the way OEM battery managers delay or kill background apps to save power. Standard Android's own battery optimization can defer background work for an app it decides is not important enough to run continuously. Manufacturer software goes further: Samsung's sleeping apps list, Xiaomi's autostart permission, and similar features on other brands can stop an app's background listener outright, which means the notification never gets a chance to post until you open the app yourself.

The fix is the same shape everywhere: find the app under battery settings and set it to unrestricted, or remove it from whatever sleep or restriction list the manufacturer maintains. This is the single most common fix for android notifications not working on phones less than a year old, because it is the setting most aggressively defaulted to restrictive out of the box.

Doze, app standby, and why nights are worse

Even with battery optimization turned off for one app, the system-wide Doze mode still applies while the phone is stationary with the screen off for an extended stretch, which in practice means overnight on a nightstand more than any other time. Doze batches network access into short maintenance windows and holds most background work in between them. High-priority messages are meant to break through immediately, but plenty of apps send their notifications as normal-priority messages, which wait for the next window like everything else.

This is why the same delay pattern shows up again and again: fine during the day when the phone moves around and gets picked up, worse overnight, worse still on a phone charging on a nightstand rather than in a pocket. Android also assigns each app a standby bucket based on how often you actually use it. An app you open daily gets frequent maintenance windows. An app you open twice a month gets far fewer, and its notifications inherit that same slow schedule regardless of how urgent any individual message actually is.

Data saver and background restrictions

Two more settings live outside the notification menu entirely and cause the exact same symptom. Data Saver, under Settings, Network, restricts background data for any app not added to its allowed list, which can hold a notification until you open the app on Wi-Fi or add it as an exception. Separately, Settings, Apps, the app, Mobile data and Wi-Fi lets you restrict background data for one app specifically, independent of Data Saver being on at all.

Both are easy to miss because neither one lives anywhere near the notification settings a person checks first, and both produce delay rather than obvious failure, so the notification eventually arrives and the setting never gets suspected.

What to do when nothing above helped

If every setting above checks out and the problem persists, the next question is whether the notification is actually being delayed or was never delivered to the phone at all, and those need different fixes. Android's notification log, reachable through a home screen widget shortcut, records every notification the system received since the last reboot, including ones you swiped away. If an app claims to have sent something and the log has no trace of it at all, the problem sits with the app's own servers, not with your phone's settings, and no local fix will help.

If the log does show the notification, but only after you went looking, the earlier steps in this list are where to keep working. It also helps to have Android's built in notification history switched on before the next gap happens, since the log clears on every reboot and the history, while still limited to roughly a day, at least survives a swipe.

This is also where a dedicated notification history app becomes useful, not as a fix for delayed delivery but as a record of what actually arrived and when, which is often the missing piece when you are trying to tell a Doze delay apart from a channel that got muted by accident. ReNotify keeps that record locally and lets you resend anything still in it, though the original tap target only survives for around six hours and until the next reboot, since that is how long Android keeps the underlying PendingIntent alive. Past that window resending still brings back the full text, just without the link behind it.

Work through the list in order rather than changing several settings at once. Each one produces a slightly different symptom, and knowing which setting actually fixed it is what stops the same notification from going quiet again in a month.