You miss a message for hours and then a flood of notifications arrives all at once when you open the phone. You were online all day and the sender expected a quick reply. That delay breaks trust because important messages look ignored.
Android delays notifications to save battery by letting apps sleep when the phone is idle. Doze mode batches background work and it can hold notifications until the phone wakes. Aggressive battery optimisation for a messaging app can add hours to that delay. Late notifications have a mirror-image fault in a phone vibrating randomly without notifications, where alerts arrive as buzzes with nothing to explain them.
This guide shows you how to restore timely notifications for the apps that matter while keeping battery saving for other apps. Change settings for one app at a time so you can see what works.
Check Do Not Disturb and notification settings
Open Settings and then open Notifications and check whether Do Not Disturb is on. Do Not Disturb can silence or delay alerts without a clear icon on some phones. Turn it off for a test and see whether notifications arrive promptly.
Open the app notification settings and make sure notifications are allowed and set to a sound or vibration you notice. A silent notification can look delayed when it actually arrived on time. Set important conversations to priority if your phone offers that option.
Check notification history if your phone offers it. History shows when a notification actually arrived versus when you noticed it. That detail separates a delivery delay from a missed alert.
Stop battery optimisation for important apps
Open Settings and then open Apps and then open the delayed app and then open Battery. Set battery usage to unrestricted for messaging apps you need instantly. Unrestricted lets the app run in the background without Doze delays.
Turn off adaptive battery restriction for that app if it appears in settings. Adaptive battery learns usage and it can restrict an app you use rarely but need urgently. A rarely used banking app can suffer long delays for that reason.
Check whether a power saving mode is on all day. Power saving can delay background sync for many apps at once. Turn power saving off for a test day and compare notification timing.
Fix data and background restrictions
Allow background data for the delayed app in its data usage settings. An app blocked from background data cannot fetch new messages until you open it. That restriction looks exactly like a notification delay.
Turn off data saver for a test if it is on. Data saver restricts background data for most apps. If notifications improve without data saver then add the important app to the unrestricted list.
Keep the app out of deep sleep lists on phones that manage sleeping apps. A sleeping app will not wake for notifications until you open it. Remove important messaging apps from any sleep list. If the phone also drops its data link then the steps for resolving mobile data dropping on 4G and 5G can help you check whether the network is delaying delivery.
Test with a controlled message
Ask a friend to send a test message at a set time while the phone screen is off. Note the exact arrival time on the phone and compare it with the send time. A controlled test gives clear evidence instead of guesswork.
Test again after each setting change with a new message. Changing many settings at once hides which change fixed the delay. One change and one test at a time is slower but it gives a reliable answer.
Restart the phone after you finish changing settings. A restart clears stuck background services that can hold notifications. Test once more after the restart to confirm the fix holds.
adb shell dumpsys deviceidle
adb shell dumpsys notification
adb shell cmd appops get com.example.app RUN_IN_BACKGROUND
The commands above were prepared for this guide and they use only standard tools that ship with Android developer tools. They show Doze and notification state for advanced users and they use a placeholder package name that you replace with the real app package.
While you work through these steps it helps to compare symptoms with other fixes in the same area. For example the steps for mobile data dropping problems show how a related fault behaves differently and the steps for endless account notification problems help you rule out a second fault that shares early symptoms.
Common mistakes
One common mistake is setting every app to unrestricted to fix one delayed app. That change drains the battery for all apps and it hides the real culprit. Restrict only the apps you need instantly. Another mistake is blaming the messaging app when Do Not Disturb is on.
Another mistake is testing notifications only while the screen is on. Doze delays appear mainly when the screen is off for a long time. Test with the screen off for an hour for a realistic result.
A third mistake is clearing app data to fix a delay. Clearing data logs you out and it does not change battery optimisation. Check battery settings before clearing data.
A week-long notification test that proves the fix
Ask a friend to send a test message at the same time each day for a week while the phone screen stays off for an hour. Note the delay for each message. A delay that shrinks after you set the app to unrestricted proves battery optimisation caused the delay. A delay that stays long after unrestricted settings points to network or server causes.
Test a second messaging app on day four with the same method. A second app that arrives promptly while the first app delays points to that app settings. Both apps delaying together points to a system or network cause.
Test with power saving off for two days in the second half of the week. A clear improvement without power saving shows that power saving batches notifications on your phone. You can then decide which apps deserve unrestricted status.
Long-term habits that protect timely notifications
Review battery settings for messaging apps after every major update. Updates can restore restrictions that you previously removed. A quick review after an update prevents a return of delays.
Keep important apps out of deep sleep lists as a routine. A sleeping app will not deliver alerts until you open it. That habit matters most for banking and messaging apps that you use rarely but need urgently.
Test notifications with the screen off rather than only while using the phone. Screen-off testing reveals Doze delays that screen-on testing hides. A monthly screen-off test catches new restrictions early.
What to do when notifications still delay after unrestricted settings
Check whether the app itself has an internal notification delay setting. Some messaging apps offer quiet hours or sync intervals inside the app. An internal setting can delay alerts even when system settings allow them.
Test notifications with the app open in the background versus fully closed. An app that delivers promptly when open but delays when closed points to background restrictions. An app that delays even when open points to server or network delays.
Check whether a VPN or a firewall app delays push messages. A VPN that disconnects frequently can interrupt push connections. Disabling the VPN for a test day reveals that pattern.
Contact app support with your test times if delays persist after system fixes. App support can check server delivery logs for your account. A detailed test log helps support find a server-side delay.
Testing notification delivery with a second app and a second time
Test notification delivery in the morning and in the evening on separate days. A time pattern can reveal Doze behaviour that depends on how long the phone has slept. Morning delays after overnight sleep are a classic Doze pattern. Evening delays after daytime use point to other causes.
Test notification delivery with the phone on a charger and on battery. A charger test removes power saving from the results. A prompt delivery on charger with delays on battery points to power management. A delay on both points to app or network causes.
Test notification delivery with Wi-Fi on and with Wi-Fi off. A Wi-Fi test shows whether push delivery depends on a specific network path. A difference between those tests points to a network or firewall issue.
Test notification delivery after a restart and after a full day without restart. A restart test removes stuck push services from the results. A prompt delivery after a restart that degrades later points to a service that stops over time.
Test notification delivery for a group message versus a direct message. A group message test can reveal server batching that direct messages do not show. A difference between those tests points to app server behaviour rather than phone settings.
Keep a log of send time and arrival time for each test message. A log with exact times is far stronger evidence than a feeling that messages arrive late. That log helps app support check server logs for the same times.
Keep the notification test running for a second day after a successful first day. A second day test proves the fix holds beyond a single good day. That confirmation matters before you rely on timely alerts for important messages.
Frequently asked questions
Why do notifications arrive in a batch when I unlock the phone?
Doze batches background work while the phone sleeps and releases it when you wake the phone. That batching saves battery but it delays alerts. Unrestricted battery for an app reduces batching for that app.
Will unrestricted battery drain my phone fast?
Unrestricted battery for one or two messaging apps has a small effect on total battery life. Unrestricted battery for many apps can drain power noticeably. Limit unrestricted status to apps you truly need instantly.
Why are only some apps delayed?
Apps have different background rules and usage patterns. An app you open rarely can be put to sleep while an app you open often stays active. That difference explains why one app delays and another does not.
Conclusion
Delayed notifications usually come from battery optimisation and Doze rather than a broken app. Check Do Not Disturb first and set important apps to unrestricted battery. Allow background data and remove those apps from sleep lists. Test with a controlled message while the screen is off. If delays persist after those steps then check network stability. Start today by setting your main messaging app to unrestricted and sending a test message after one hour with the screen off.
