Why Android notifications arrive late, and the settings that actually fix it

A message was sent an hour ago and arrives the moment you unlock the phone. Somebody called through an application and the notification appeared after they gave up. On another handset with the same applications, everything is instant. The difference is almost never the network; it is the set of power-management rules the phone applies to background work, and there are more of them than most people realise.

How a notification is supposed to arrive

Applications are not meant to hold their own connection open. A single system service keeps one long-lived connection to a push network, and every application's messages arrive through it. That design is why a phone with fifty applications does not have fifty connections draining the battery. When it works, a message reaches the phone within a second or two of being sent, regardless of how long the application has been closed.

Delays happen when something prevents that shared connection from being maintained, or prevents the application from being woken when a message arrives for it.

The three layers that interfere

• Doze. When the phone is stationary, unplugged and the screen has been off for a while, the system batches background work into periodic windows. Messages flagged as high priority are supposed to pierce this; ordinary ones wait for the next window. This layer is part of Android and behaves consistently.
• Per-application battery optimisation. Each application is either optimised or exempt. The setting is where it should be, in the battery section of the application's information page, and exempting an application is the correct fix for one that genuinely needs to be reachable at any moment.
• The manufacturer's own layer. Several makers add an aggressive process manager on top, which closes background applications on its own schedule and sometimes reverts exemptions after an update or a reboot. This layer is the usual culprit when a phone is noticeably worse than others at the same task, and its settings live outside the standard battery menu — under names like protected applications, auto-launch management or background activity control.

Why it looks random

Because the layers interact. An application exempted from the standard optimisation can still be closed by the manufacturer's manager. An application allowed to run in the background can still be starved of network access in a data saver mode. And an application that has not been opened for weeks may be placed in a restricted bucket automatically, on the entirely reasonable theory that you do not use it.

The order to change things in

Start with the application that is actually late rather than with a global setting. In its information page, allow unrestricted background use and confirm its notification categories are enabled — a category muted at some point in the past will silence a specific kind of alert while everything else works.

Then find the manufacturer's process manager and mark the application as protected there. Check it again after the next system update, because this is the setting most likely to be reset.

Then look at data saver, and at any per-application data restriction on mobile networks. A phone that is instant on a wireless network and late on mobile data is telling you exactly where to look.

Finally, check that the phone is not on a battery saver profile that you enabled once for a long journey and never turned off. Saver modes defer background work by design, and their whole purpose is the behaviour you are complaining about.

What to leave alone

Do not exempt everything. Every exemption is a permission to wake the phone, and a handset with two dozen unrestricted applications will have visibly worse standby time. Three or four applications that genuinely need immediacy is a reasonable number; the rest can wait for the next window without anyone noticing.

And do not install an application that promises to fix notifications. It will ask for extensive permissions in order to keep other applications awake, and the cost lands on the battery while the underlying restriction remains in place. If the battery is the reason the restrictions were tightened in the first place, the real question may be the cell rather than the settings — the way to tell is in reading battery health.