The short answer: Work down five layers in order — the app’s notification channel, Android’s battery optimisation, your manufacturer’s own background limits, Do Not Disturb, and any app permission that silently lapsed. The classic symptom of the middle two is notifications that all arrive at once the moment you open the app. That is not a network problem; it is your phone having suspended the app until you looked at it.
Notifications failing is rarely one dramatic bug. It is usually a stack of independent systems, each of which is allowed to suppress an alert on its own, and any one of which can be the reason.
Working down them in order is faster than guessing, because the fixes get progressively more obscure and the first two account for most cases.
1. The notification channel, not the app
Since Android 8, every app splits its notifications into channels — “Messages”, “Group chats”, “Calls”, “Updates” — and each channel carries its own importance, sound and behaviour. An app can be fully enabled while one of its channels is set to silent.
Settings → Apps → [the app] → Notifications
You will see the channel list. For each one that matters, check that it is on, and open it to check its importance level. Anything set to Silent or Low will not make a sound or appear as a banner — it goes quietly into the tray, which is very often exactly the complaint.
This is also the layer where a sound goes missing while the notification itself still arrives. If alerts appear but never make a noise, you are almost certainly looking at a channel set to Silent rather than at anything deeper.
2. Battery optimisation
This is the most common cause of late notifications, as opposed to missing ones.
Android puts apps it considers idle into buckets and restricts how often they may wake, run background work, or reach the network. An app in a restricted bucket may not be told about a message until something wakes it — which is why the notifications land in a burst the instant you open the app.
Settings → Apps → [the app] → Battery → Unrestricted
Do this for the handful of apps that genuinely matter — messaging apps, calendar, anything on-call. It is not a setting worth applying to everything, because the trade is real battery life.
3. Your manufacturer’s own layer
This is the part that catches people out, because it is entirely separate from Android’s own battery settings and it usually wins.
Xiaomi, Samsung, Oppo, Vivo, OnePlus, Huawei and others ship additional background-management systems. Turning off Android’s battery optimisation does not turn theirs off, and they are considerably more aggressive.
- Xiaomi / Redmi / POCO (MIUI, HyperOS): the important one is Autostart. Settings → Apps → Manage apps → [app] → Autostart on, and set Battery saver to No restrictions on the same screen. Without Autostart, MIUI will refuse to let the app restart after it has been killed — including when you swipe it out of Recents.
- Samsung (One UI): Settings → Battery → Background usage limits — make sure the app is not in Sleeping apps or Deep sleeping apps. Also turn off Put unused apps to sleep.
- Oppo / Realme / OnePlus (ColorOS/OxygenOS): Settings → Battery → the app → allow background running and auto-launch.
- Vivo / iQOO (Funtouch): Settings → Battery → High background power consumption, plus the separate autostart list.
Xiaomi devices deserve a specific warning: clearing an app from the Recents screen there is a hard kill, and without Autostart enabled the system will actively reject the app’s attempts to start itself again. Nothing in the app can work around that, which is why apps on those phones so often seem to work fine until the first time you tidy your Recents.
4. Do Not Disturb and the modes around it
Worth ruling out quickly, because the notification is arriving perfectly — you just are not being told.
Check Do Not Disturb’s schedule (many phones enable it overnight by default), Bedtime mode, Focus modes, and any driving mode. Each has its own allow-list, and each can silence an app without appearing to be “off”.
Also check the volume the alert actually uses. Android has separate streams for ring, media, notifications and alarms, and it is entirely possible to have notification volume at zero while music plays at full.
5. A permission that quietly stopped working
If the app whose notifications fail is one that reads other apps’ notifications — a notification saver, a smartwatch companion, a car head-unit app, an automation tool — there is a sixth failure mode specific to it: notification access can stop working without being switched off.
Two situations cause it. Updating the app can leave the system’s connection to it unbound until something reconnects it, so the toggle still reads “on” while nothing is actually being delivered. And an aggressive manufacturer layer that kills the app can prevent it rebinding at all.
The fix is the same in both cases: Settings → Notifications → Notification access (on some phones, Settings → Apps → Special app access → Notification access), turn the app off and back on. That forces a fresh bind. Then handle the manufacturer settings in section 3, or it will happen again the next time the app is killed.
One chronological panel of everything that was captured, unread marked — useful for confirming whether an alert actually arrived and was missed, or never arrived at all.
If you want to know whether notifications are genuinely not arriving or merely not being noticed, this is the distinction worth establishing early. An app that keeps a record of everything it received answers it directly: if the alert is in the record, the delivery worked and the problem is sound or visibility; if it is absent, the problem is upstream in one of the layers above.
When notifications arrive but get lost anyway
Not every version of this problem is technical. If a phone posts several hundred notifications a day, individually working alerts still add up to a tray you clear without reading.
Two things help more than any setting. Turn off notifications for the apps that never earn one — the channel screen in section 1 is the fastest route. And make the alerts that matter sound different from the ones that do not, so an important sender is identifiable without unlocking anything — the same applies to a ringtone per caller for app calls.
If the failure mode is that you cleared something before reading it, that is a different fix again: a notification saver keeps a copy after the tray is emptied.
Common questions
Why do all my notifications arrive at once when I open the app?
Classic battery-restriction symptom. The app was suspended and was not permitted to wake for incoming messages; opening it lifts the restriction and the backlog delivers at once. Sections 2 and 3 are the fix.
I fixed everything and one app still fails. Now what?
Check whether that app has its own in-app notification settings — most messaging apps do, and they sit on top of Android’s. After that, clear the app’s cache, then reinstall. Reinstalling resets every bucket and restriction the system had applied to it.
Does clearing apps from Recents cause this?
On stock Android, not much. On Xiaomi, Samsung and several other skins, yes, materially — it is a hard stop, and on MIUI the app cannot restart afterwards without Autostart enabled.
Are notifications delayed on Wi-Fi only?
If so, check for a router or network-level blocker, and check whether your phone sleeps Wi-Fi when the screen is off. Some power-saving modes drop the persistent connection push relies on.
Does a VPN or private DNS break notifications?
It can. Both change how the persistent push connection is made, and some configurations break it outright. Turn either off temporarily as a test.
Why did this start after a system update?
Updates commonly reset per-app battery exemptions and can unbind special permissions such as notification access. Re-check sections 2, 3 and 5 after any major update.
The order matters more than the individual steps. Channels and battery settings account for the overwhelming majority of these cases, the manufacturer layer accounts for most of what is left, and the special-permission failure in section 5 is the one that looks like nothing is wrong at all — because every toggle you can see still says it is on.