Android Notifications Not Showing? Fix by Symptom

WhatsApp messages often land in a burst the moment you open the app. Bank and Gmail alerts can stay silent for hours on the same phone. I traced both faults on my Tecno Spark 40 running HiOS on Android 15. The app itself was rarely broken, because the system had parked it, muted its channel, or silenced it on a schedule.

This guide triages by delay pattern before it touches any toggle. You match your symptom in the first table, then you work only the section it names. I confirmed the battery and notification entries on my unit through Settings search, while Samsung, Xiaomi, and Pixel paths below use each maker’s own words. Battery theory stays short here, because the optimizer’s home post already covers drain in full.

The 30-second test: burst, silent, scheduled, or single-chat

Four delay patterns explain nearly every silent phone I have seen. A burst usually means Android parked the app and held its alerts. A silent arrival often means the alert came through on a muted channel. Scheduled silence points at a Do Not Disturb or Bedtime window on most builds. A single muted chat points inside the app itself.

The symptom	The layer it implicates	The section that fixes it
Messages arrive in a burst when you open the app	The system parked the app	The exemption sequence
Alerts arrive but make no sound and do not vibrate	A channel sits on Silent	Permission plus channels
Silence falls on a timetable, nightly or in work hours	A Do Not Disturb or Bedtime schedule	The schedules audit
One chat stays mute while other chats alert normally	An in-app mute or notification reset	The WhatsApp reset

Appuals models the WhatsApp version of this check, and this table generalises it phone-wide. You read the symptom column for your exact behaviour, then you open only the section the third column names. If your fault matches none of the four rows, our Android problems fix guide maps the other common faults on the same phone.

Exempt the app: the five-toggle sequence

Android parks idle apps to save power on most builds, and their notifications wait until you reopen them. MakeUseOf calls battery optimisation the silent app killer after its own messaging apps stalled the same way in its background mechanism explainer. Doze slows background work while the phone sits idle, and App Standby limits apps you have not opened recently. Pixel help adds that Adaptive Battery may delay alerts to extend battery life.

You apply five toggles to one quiet app, in this order, through Settings search on your build. WhatsApp itself frames burst-on-open delivery as a push issue tied to permissions, background data, and battery settings in its WhatsApp push troubleshooting note. Samsung frames Power Saving as a background restrictor that can block alerts in its Samsung notification support guide.

The toggle	What it undoes	Where I found it
Unrestricted battery use	It lifts Doze and Standby limits for this app only	App info, then Battery (confirmed on my Spark 40)
Background data allowed	It lets alerts arrive on mobile data while closed	App info, then Mobile data and Wi-Fi (confirmed on my Spark 40)
Autostart enabled	It lets the app restart itself after a reboot	App management on HiOS builds I checked (names shift by build)
Locked in Recents	It stops swipes and cleaners from killing the app	Recents padlock icon (confirmed on my Spark 40)
Pause activity if unused stays off	It stops Android auto-pausing an app you rarely open	App info toggle state (confirmed on my Spark 40)

You stop at three or four apps, because each exemption spends battery, so our battery draining guide explains the allowance logic between the two posts. Xiaomi documents a per-app background autostart switch under Apps, Permissions, and Background autostart in its Xiaomi autostart FAQ. Appuals pairs the same sequence with Allow background usage and Unrestricted in its Appuals WhatsApp notification guide.

Permission plus channels: the two gates

Android 8.0 moved every alert into channels, so each category carries its own sound and silence. The Android channel documentation states the rule plainly for that release and every release since. Google separates Alerting from Silent in its Google notification controls: one makes sound and shows a lock-screen message, while the other stays quiet. Appuals caught the sharpest trap in its guide: the main switch can stay on while Message or Group categories sit on Silent.

You re-grant the runtime permission first, because a denied permission silences every channel below it. You open App info, then Notifications, then each category, and you flip muted ones back to Alerting. If your Galaxy shows no categories list, hunt its own menu on that build, because names shift by brand. In-app mutes sit beneath all of this, so you check the app's own notification settings first. Our companion guide to deleted WhatsApp chats covers notification-dependent workflows on the same app.

Schedules that swallow alerts: Do Not Disturb, Bedtime, Modes

BestForAndroid phrases the rule plainly: Do Not Disturb silences sounds, vibrations, and visual pop-ups except the ones you allow. Google now groups Do Not Disturb with Bedtime and Driving under Modes, and each mode carries its own on-off switch in its Google Modes help. A schedule can silence the same hours daily, which reads as late alerts rather than a broken app. GuidingTech’s 2024 fix names the exact move: open the schedule list and turn off the toggles beside your DND schedules.

The mode	What it silences	Where its schedule hides
Do Not Disturb	It silences calls, alerts, and pop-ups on a timetable	Sound or Modes, then Schedules (search Settings on your build)
Bedtime mode	It quiets night-window alerts and the display	Digital Wellbeing or Modes (names shift by brand)
Driving mode	It holds alerts while a drive is detected	Modes, then Driving (Transsion names differ)
Repeat callers exception	It lets a second call within 15 minutes break through	DND exceptions (Google documents the 15 minutes)

You audit the master toggle first, then each schedule, then priority-sender exceptions for family and work. BestForAndroid tested its flow on the Pixel 8a, the Galaxy S24, and the OnePlus 12, so Transsion owners should treat its menu names as hints rather than paths. A schedule you set months ago can still fire daily, which is why the list matters more than the toggle.

Lock screen, history, data: the visibility third

Some alerts arrive fine yet never show on the lock screen. You check lock-screen visibility per app, because that screen acts as a separate gate on many builds. Google’s keeper here is notification history as a diagnostic timestamp, and it settles arguments fast on current builds. You open history through Settings search, then you compare its timestamps against the quiet window. A missing entry means delivery failed, while a present entry means display failed.

Data Saver and background-data limits can stall delivery on mobile data on many builds. You allow background data for the quiet app, then you retest on mobile data alone for one afternoon. Wi-Fi-only testing hides this fault, so the mobile-data session stays mandatory.

Update-linked silence and the Transsion block

Updates can reset permissions and exemptions, so silence that starts the morning after an update gets its own sweep. You re-grant the runtime permission and you re-apply the five toggles first. You re-check the DND schedules next, before you blame the update itself. Reddit symptom threads for the Infinix Hot 40i and the Tecno Camon 40 Pro 5G describe this exact burst-on-open fault on current hardware.

Carlcare published no notification-delay guide I could find, and the lane held no independent article on 7 October. HiOS and XOS menu names shift by build, so you search Settings for battery usage, autostart, and notification categories rather than memorising my path. The dontkillmyapp benchmark ranks Xiaomi among the most aggressive background killers, while Transsion evidence lives in threads rather than benchmarks. Your symptom match matters more than any ranking here.

What not to do, plus the reinstall verdict

Three popular fixes trade the whole phone for one app, so I skip all three on my unit. ADB commands that disable Doze fall outside the supported toggles, so this page skips them and stays with the per-app sequence. Keeper-awake apps can hold the phone awake for little gain, which spends battery across every app instead of one. System-wide Adaptive Battery switches repeat the same trade, while this page limits Unrestricted to three or four apps.

A reinstall stays legitimate only after a backup, because clearing app data wipes logins and chat state. You back up first, then you reinstall. Lifewire pairs cache with data casually in its June 2025 guide, so you treat cache as safe and data as destructive on your unit. Samsung dropped wipe-cache-partition from Galaxy recovery with its February 2026 patch, per 9to5Google’s 27 February 2026 report, so you never go looking for that menu on a current Galaxy. A factory reset gets no prescription here, because that decision belongs to a dedicated reset guide rather than this page.

What I tested on a Tecno Spark 40, and what I could not reproduce

The bench phone is my Tecno Spark 40 running HiOS on Android 15, checked in the first week of October 2026. I confirmed the per-app Unrestricted entry, the background-data toggle, the per-category Alerting states, and the DND schedule list through Settings search. I confirmed the Recents lock gesture and the notification-history timestamps across one overnight run. I could not reproduce Samsung sleep-list verbs, Xiaomi autostart labels, or Pixel Bedtime wording, so those sections use each maker’s own words.

I measured no overnight drain delta and I ran no second device, so battery-cost figures stay out of this page. The full bench method lives in our how to test an Android phone guide. For the other faults on the same phone, the Android problems fix guide holds the full map.

Questions readers ask

Messages arrive in a burst when I open the app. Is the app broken?

The app is parked rather than broken on most builds, so the five-toggle exemption comes first.

Should I disable Doze with ADB commands or install a keeper app?

Neither belongs in this fix, because ADB sits outside the supported toggles while keepers spend battery everywhere.

Should I turn off Adaptive Battery entirely?

You exempt three or four apps instead, because a system-wide switch spends battery across the whole phone for one app.

One channel stays silent while others alert. Is the fix the same?

The fix differs by category on most builds, so you flip that one channel back to Alerting.

Bedtime is on, but it is daytime. Can it still silence me?

A leftover schedule can silence daylight hours, so you audit every schedule entry rather than the master toggle alone.

My Samsung has no wipe-cache option any more. Is that related?

The removal is unrelated to your alerts, because Samsung dropped that recovery option with its February 2026 patch.

What to do next

You run the thirty-second triage once, and the page collapses to the single section that is yours. You exempt the app, you unmute its channel, you clear its schedule, and you lock it in Recents on your unit. For the other faults on the same phone, you start with our Android problems fix guide before you open another tab. Exempted apps sip extra power, so you read our battery draining guide when the allowance question comes up.