Android notifications arriving late, silently or not at all

The delay is a design decision before it is a fault. Android ships two power-saving features that manage how apps behave off a charger: Doze, which defers background CPU and network activity once the device has been unused a while, and App Standby, which defers background network activity for apps with no recent user activity. Google's Pixel help page says the same of the layer above them: Adaptive Battery may reduce performance and delay notifications to extend battery life. The job is to find which system is holding your alerts, because every exemption you hand out is battery you spend.

Under Doze the system suspends network access, ignores wake locks and defers alarms, jobs and syncs, surfacing periodically for a maintenance window in which the pending work runs. The longer the phone sits untouched, the rarer those windows get.

That is where the unlock symptom comes from. Most apps do not hold their own connection open: Android points developers at Firebase Cloud Messaging, one shared connection to the cloud, and Firebase's setup guide has apps check for a compatible Google Play services package first. A high priority message wakes the app even in Doze. A normal priority one waits for a maintenance window, or until you wake the device.

Android 9 and later also sort apps into standby buckets, from active down to rare, with a stricter restricted bucket added in Android 12, and the bucket sets how often an app's jobs and alarms run.

Split the problem. Nothing at all from one app points at a switch: a muted category, a permission never granted, an app put to sleep. Late, then several at once points at power management.

The cheapest test is a charger. Google states the standby restrictions apply only on battery power, so an app prompt on the cable and slow off it is behaving as documented.

• Google says to keep Adaptive Battery and battery optimisation on, both on by default: an app on Optimized is ordinary, not a finding.
• A category set to Silent still delivers: no sound or vibration, but it appears when you swipe down.
• Notification cooldown quietens a burst of notifications, as after Airplane mode goes off, excepting calls, alarms and emergency alerts.

Aim at two or three apps. A page full of optimised apps is a healthy phone.

This is the section that fixes most delays, and the one that bills you. Google's warning comes first: with battery optimisation off an app runs more while unused, and can use more battery than needed.

So pick the app first. On a Pixel: Settings, Apps, See all apps, the app, App battery usage, Allow background usage. Android's standby documentation calls this designating an app to provide unrestricted functionality in system settings.

That designation does more than it sounds. On Android 13 and higher an app falls into the restricted bucket after eight days without interaction, then runs jobs once a day in a ten-minute batched session. Unrestricted apps are exempt.

Which is why installing a helper usually hurts. Our roundup of battery saver apps for Android is plain: an app that cannot run in the background cannot deliver your messages.

Since Android 8.0 every notification belongs to a channel, and Android's documentation names the detail that catches people out: the interface calls channels categories. An app switch can be on while the category you want is off.

Google's path is Settings, Notifications, App notifications, where you can turn everything off or choose from specific categories.

Android 13 and higher added a runtime permission an app must hold before it can post notifications, so a recent install can be silent because it never got one. The Pause app activity if unused toggle sits further down that app's info screen, under Unused app settings, and the app permissions guide explains what that toggle switches off.

That toggle has a documented name: hibernation. An app targeting Android 11 or higher and untouched for months is hibernated, and on Android 12 and higher it then cannot receive push notifications, including high-priority Firebase ones. Opening it ends hibernation; the permissions are not restored.

Modes are easy to leave running. Google documents Do Not Disturb, Bedtime, Driving and custom modes under Settings, Modes, and flags that some steps need Android 14 or later; our guide to updating your Android version shows where to check.

Inside a mode, Notification filters decide what gets through: People for calls and messages, Apps for which apps may notify you, and alarms and other interruptions. Critical notifications still show; system security notifications cannot be blocked.

Focus mode lives somewhere else, and that is where a check quietly goes wrong. It sits under Settings, Digital Wellbeing and parental controls, Focus mode, and Google's description leaves no room: you choose which apps to pause, and while it is on you get no notifications from them. Clearing every mode tells you nothing about it.

If you want apps silenced on purpose, our guide to choosing an app blocker for Android covers that.

One network setting breaks push. Android's documentation says that with Data Saver on and the device on a metered network, the system blocks background data usage. Delays only on unmetered Wi-Fi are probably not this. The master switch is the wrong fix: Data Saver caps roaming and end-of-cycle data, and single apps can be allowed background metered data while it stays on. If nothing loads at all, that is a connection fault: see mobile data not working on Android.

Many phones run more than stock Android. DontKillMyApp, a community-run project documenting vendor behaviour, says manufacturers prefer battery life over proper functionality of your apps. Its scoreboard, read 4 August 2026, scores Xiaomi, Samsung, OnePlus and Huawei worst, and stock Android, Pixel, Nokia and HTC zero.

Its Samsung page calls Put unused apps to sleep the major headache: a feature absent from stock Android that restricts an app unused for a few days, and re-sleeps apps you wake by hand unless it is off. The lists sit under Battery, Background usage limits. Switching it off costs battery, the trade this page describes.

• Xiaomi. No APIs and no documentation for the vendor's extensions, plus a per-app Background autostart permission on MIUI 14.
• OnePlus. A sleep standby optimisation that cuts network connections when it judges you are asleep, which the page says prevents push notifications arriving.
• Huawei. A bundled task killer, PowerGenie, said to kill everything not whitelisted.

That is a volunteer-edited project, not manufacturer documentation. It also carries a July 2024 statement it attributes to Samsung, that since One UI 6.0 foreground services targeting Android 14 are expected to work as intended.

Two patterns mean the per-app hunt is wrong. If several unrelated apps are crashing as well as going quiet, the shared layer beneath them is the suspect, and our guide to an Android app that keeps stopping covers that, Google Play services included. A force-stopped app needs opening by hand before background work resumes.

The honest limit: you trade battery for punctuality, one app at a time. Two or three exemptions is a working phone; a page of them is a phone that dies by six.

Which is where the other half lives. If your alerts now arrive on time and the battery no longer lasts the day, that is the same machinery from the other end: Android battery draining fast has the per-app battery screens for Pixel and Samsung, and its own warning about deep-sleeping the apps you need alerts from.