Android notifications missing or delayed

• Estimated time: 5 min
• Easy
• Low risk

Absence, silence, and delay need different tests.

1. Open the notification shade and compare it with the lock screen. Note the app, expected time, arrival time, and whether the phone was locked. Use a non-private test notification you can repeat without incurring charges.

2. If the notice is in the shade without sound, follow silence. If absent, distinguish one app from several and observe whether opening the app makes it appear. If the app crashes or will not open, use the app guide; do not confuse execution failure with notification permission.

• Estimated time: 5 min
• Easy
• Low risk

Changing background activity does not explain a notice that is already visible.

1. In the app’s notification settings, check whether that category is alerting or silent. Also check Do Not Disturb or the equivalent active mode. Names and controls depend on the manufacturer; do not assume every phone follows a Pixel path.

2. Change only the control explaining the silence and repeat the same notice. If it now sounds, do not change battery settings. If nothing changes, retain the observation and check that category/app’s own options.

• Estimated time: 5 min
• Easy
• Low risk

A blocked category can leave other categories working.

1. Find Notifications in Settings, select the app, and check whether they are allowed. Review the expected notice’s category and in-app settings, including the correct account. Do not enable unwanted categories just to test.

2. Repeat the notice after correcting a block. If it stays absent but appears when opened, continue with background behavior. If only that app fails with correct permissions, its developer can investigate delivery/account state; do not clear its data.

• Estimated time: 15 min
• Easy
• Low risk

The pattern justifies testing one option, not globally disabling power saving.

1. If the manufacturer offers a per-app activity or battery control and documents its effect, record the original value and temporarily allow the required activity for that app only. Keep the same connection and compare a notification with the phone locked for a similar interval. If the option does not exist, do not use ADB or developer options to manufacture it.

2. A repeatable improvement gives background management more weight; it does not prove a universal cause. With no change, restore the original value and leave that hypothesis. An app still delayed with unrestricted usage needs delivery investigation, not more system features disabled.

• Estimated time: 10 min
• Easy
• Low risk

A shared pattern makes an environment comparison more useful.

1. Note whether delays occur only on Wi-Fi, cellular data, or while locked. Compare another authorized connection while keeping other settings unchanged. If browsing also fails, use the Wi-Fi or mobile-data guide; do not change every app’s permissions.

2. If changing networks improves delivery, report the difference to the network owner. If several apps remain affected across connections, give the manufacturer timing and power-state observations; do not declare Doze responsible or reset the phone.

• Estimated time: 5 min
• Easy
• Low risk

Hidden content can be a privacy choice rather than a delivery failure.

1. If the notice is in the shade after unlocking, review app and system lock-screen options. Decide whether to show notices or sensitive content; a managed device may have a restriction.

2. Check again with the phone locked. If arrival in the shade is also delayed, it is no longer just visibility: use the delay branch.