Notifications not arriving on Android: why apps go quiet

The opposite problem from notification overload is worse: the app you need — messages, banking codes, the delivery window — has gone silent. Missed notifications usually aren't one bug; they're one of five layers swallowing the alert. Work them in order, because each is cheaper to check than the next.

1. The app's notification channels got switched off

Android apps post notifications through channels — categories you can control separately (messages versus promotions versus silent updates). An app can be "allowed" while its important channel is muted, and some apps start with channels off by default. Settings, then Apps, then the app, then Notifications: check each channel, and while there, confirm the app isn't in a paused or "silent" notification state. This is the mirror image of the tuning pass in silencing the noise properly — same controls, opposite direction.

2. Battery optimisation is strangling the app

The most common culprit on phones that "miss" messages overnight: aggressive battery management puts rarely-opened apps into deep sleep, blocking their background push. Settings, then Apps, then the app, then Battery: set it to Unrestricted (or exempt it from optimisation) for anything whose notifications matter — messaging, authenticators, delivery trackers. The trade is honest: unrestricted background means some battery cost, and the battery-drain picture is where to check you haven't over-granted. Some manufacturers ship extra-aggressive "battery savers" with their own per-app kill lists — check the phone's own battery app for a "sleeping apps" list and move your critical apps out of it.

3. Data restrictions cut the app's lifeline

Push notifications ride data. Three data-side switches silence apps: Data Saver mode (Settings, then Network) blocks background data globally except for exempted apps — exempt the critical ones; per-app background data restrictions (App info, then Mobile data); and plain old "mobile data off" with apps that have no Wi-Fi fallback. If notifications flow on Wi-Fi but die on the road, it's this layer — and if all data is dead outside Wi-Fi, that's the mobile-data diagnosis, not a notification problem.

4. The moment-of-truth checks

Notifications arriving only when you open the app is the signature of background push being blocked (layers 2–3) — the app learns of the message fresh each launch. Notifications that buzz but show nothing is channel content-hidden (layer 1) or the lock-screen setting hiding content (the privacy pass sets that deliberately). And a phone whose notifications stall everywhere, for every app, until you unlock it: that's USB/debugging mode or an aggressive third-party cleaner app — uninstall the cleaner; Android does not need one, and the crash-triage piece explains the harm category they live in.

5. When it's the sender, not the phone

One app silent everywhere — on your phone, a partner's phone, after a clean reinstall with notifications verified on? The app's own push infrastructure is the failing layer, and no phone setting fixes that: report via the store listing and wait out the fix. The quick cross-check that proves it: does the same category of alert arrive from a different app on the same phone? If yes, your phone is fine and the developer owns the bug — which is a diagnosis worth having before the tenth reinstall.