Android notification issues? Try these simple 16 fixes

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

Android notifications can be blocked, delayed, silenced, hidden, or never delivered. The quickest fix is to identify which of those symptoms you have instead of changing every setting at once. Start by turning off any active mode or Do Not Disturb schedule, checking the affected app’s notification permission, and using Notification history to determine whether Android received the alert.

The paths below use current Pixel and stock Android labels. Menu names differ by Android version, manufacturer, region, launcher, and carrier; Samsung Galaxy alternatives are included where they matter. Android 17 documentation is available, but not every phone receives Android 17 at the same time. If a path differs, search Settings for terms such as notifications, notification history, battery usage, Data Saver, or sleeping apps. See Google’s Android update guidance for device and carrier availability.

First, identify what is actually failing

Android notification problems usually occur at one of four layers:

1. Delivery: The app, its account, or its server does not generate or deliver the alert.
2. Permission and categories: Android allows the app to send some notifications but blocks the app or a specific notification category.
3. Background execution: Battery restrictions, Data Saver, Doze, an OEM sleeping-app feature, or a network problem delays background work.
4. Presentation: Android receives the notification, but it is silent, hidden from the lock screen, grouped, minimized, organized, or dismissed before you notice it.

This distinction matters. If an alert appears in Settings > Notifications > Notification history, Android received it. Investigate lock-screen visibility, silent categories, notification cooldown, notification organization, and dismissal behavior. If it never appears in history, investigate the app, its account, connectivity, permissions, and background restrictions. Notification history is not available on every device and generally must be enabled before the missing notification occurs, so turn it on while troubleshooting. Google explains these controls in its Android notification settings guide.

What you see	Most likely checks	Do not do first
No apps notify	Modes or Do Not Disturb, Airplane mode, network, Battery Saver, system notification settings	Reinstall every app
Only one app fails	App permission, notification category, in-app settings, account state, battery and background access	Factory-reset the phone
Notifications appear only after opening the app	Battery restrictions, sleeping apps, Data Saver, VPN, background data, app-server or account problems	Disable all battery optimization globally
The phone makes a sound or vibrates, but nothing is visible	Notification history, lock-screen settings, silent or minimized categories, notification organizer	Assume the app failed to deliver
The alert is in the shade but has no sound	Notification category set to Silent, Ring & notification volume, vibration, cooldown	Clear app data
The alert is in the shade but not on the lock screen	Lock-screen notification visibility and sensitive-content settings	Reinstall the app
Only a watch, car, tablet, or desktop misses alerts	Companion-app notification access and device-specific mirroring settings	Reset the phone

Three fast checks before the 16 fixes

1. Turn off active Modes or Do Not Disturb. Swipe down twice, tap Modes on a Pixel, and turn off Do Not Disturb or another active mode. On a Galaxy, disable Do not disturb in Quick Settings.
2. Check the affected app’s permission. Go to Settings > Notifications > App notifications > [app] and turn on the app’s notifications.
3. Enable Notification history. Go to Settings > Notifications > Notification history, enable it if available, and test with a new message or reminder.

Use a second phone, a test email, or another safe test account to generate a fresh alert. Testing with a new event is more useful than waiting for an old notification that may already have been dismissed or grouped.

The 16 fixes, in the safest diagnostic order

1. Turn off Modes, Do Not Disturb, and scheduled silencing

Try this when: Several or all apps have stopped making sounds, showing banners, or appearing prominently, especially at certain times of day.

Pixel and stock Android:

1. Swipe down twice to open Quick Settings.
2. Tap Modes.
3. Turn off Do Not Disturb and any active custom mode.
4. Open Settings > Modes and inspect schedules, including driving, bedtime, and custom modes.

Current Pixel Modes can filter people, apps, alarms, reminders, calendar events, and other interruptions. A schedule can reactivate Do Not Disturb after you manually turn it off. On Samsung, use Settings > Notifications > Do not disturb to inspect schedules and allowed-app exceptions. Google’s Pixel Modes and Do Not Disturb documentation describes the available filters.

Test: Lock the phone and send a message from another device. Do Not Disturb normally suppresses interruptions; it does not necessarily mean the app failed to deliver the notification.

2. Check the affected app’s notification permission

Try this when: One app has no alerts at all, particularly after it was newly installed, reinstalled, restored from backup, or migrated to a new phone.

Pixel and stock Android: Open Settings > Notifications > App notifications > [app]. Turn on All [app] notifications, then check the individual notification types below it.

Samsung: Use Settings > Notifications > App notifications > [app]. The labels may differ slightly by One UI version.

On Android 13 and newer, most ordinary app notifications require the POST_NOTIFICATIONS runtime permission. A user who selected Don’t allow may need to enable notifications manually in Settings; reinstalling is not the preferred first step. The Android developer documentation explains the permission and its exemptions at POST_NOTIFICATIONS notification permission.

You can also touch and hold an existing notification from the app, tap its settings icon, and inspect the controls shown there. Reinstalling may display the permission prompt again, but it can sign you out, delete local data, or remove offline content.

3. Re-enable the specific notification category or channel

Try this when: Some alerts from an app work but messages, calls, reminders, direct messages, promotions, or another type do not. Also use it when a notification appears but is silent or has no banner.

1. Open Settings > Notifications > App notifications > [app].
2. Tap the relevant notification category or type.
3. Turn it on.
4. Choose Alerting rather than Silent if sound or vibration is required.
5. Enable Pop on screen, Show as pop-up, or a similar option if a banner is required.

Android has used notification channels since Android 8.0. Samsung and some other interfaces call them notification categories. The global app switch can therefore be on while an individual category is disabled or silent. Channels are controlled separately after an app creates them; Google’s technical explanation is available in its documentation on notification channels.

Long-pressing a notification from the same app and opening its settings is often the fastest way to jump to the exact category that controls it.

4. Inspect the app’s own notification settings

Try this when: Android settings look correct but one app, account, conversation, workspace, or contact remains quiet.

Open the app and look for Settings, Notifications, Privacy, or account-specific controls. Check for:

• Muted chats, contacts, channels, servers, workspaces, or groups.
• Quiet hours, paused notifications, or sleep schedules.
• Per-contact notification overrides.
• Options such as Notify me about, message previews, or selected folders and labels.
• A logged-out account, expired session, disabled sync, or an account signed into a different profile.
• Separate controls for email, mentions, calls, promotions, security alerts, and reminders.

This second notification system is common in messaging, email, social, work, banking, security-camera, delivery, and authenticator apps. Android cannot restore an alert that the app itself has been configured not to generate.

5. Restore lock-screen notification visibility

Try this when: Notifications appear after unlocking or in the notification shade but not on the lock screen.

1. Open Settings > Notifications.
2. Tap Notifications on lock screen or the equivalent setting.
3. Choose an option equivalent to Show alerting and silent notifications or Show all notification content.
4. Check whether Sensitive notifications or sensitive content is hidden.
5. If available, inspect the affected app’s individual lock-screen setting.

Depending on the phone, you may be able to show full content, show only notification icons, hide sensitive details, or hide lock-screen notifications altogether. These controls change presentation and privacy; they do not necessarily prevent delivery. Review Google’s notification and lock-screen settings before changing privacy options on a shared or visible device.

6. Disable Battery Saver temporarily

Try this when: Notifications are delayed while the phone is locked, the battery is low, or the problem begins whenever Battery Saver activates.

Swipe down twice and turn off Battery Saver, or open Settings > Battery > Battery Saver. Check whether automatic activation at a battery threshold is turning it back on.

Battery Saver can restrict background activity and delay some alerts; it is not proof that the app or phone is defective. Test with the phone locked and send a new alert. If notifications return, decide whether timely alerts justify changing the Battery Saver schedule. Leaving it disabled can reduce battery life, so treat this as a diagnostic step rather than a universal recommendation. Google documents the interaction in its Pixel battery and notification guidance.

7. Review per-app battery usage instead of disabling Adaptive Battery globally

Try this when: One app delivers only when opened, or alerts become unreliable after the app has been idle for a while.

On a Pixel, open Settings > Apps > See all apps > [app] > App battery usage. Under background usage, compare Optimized with Unrestricted.

Use Unrestricted only for an app where immediate background delivery is important and the battery cost is acceptable. Google generally recommends keeping Adaptive Battery and battery optimization enabled, although these features can reduce background activity and delay some notifications. The appropriate fix is an app-specific test, not automatically disabling Adaptive Battery for the entire phone. See Google’s Adaptive Battery and background usage guidance.

This setting cannot repair an app server outage, an invalid account session, poor connectivity, or a disabled notification category. Return the app to Optimized if changing it makes no difference or causes excessive battery drain.

8. Turn off Pause app activity if unused

Try this when: A rarely opened app stopped notifying after months of disuse or after Android marked it as unused.

1. Open Settings > Apps.
2. Select the affected app.
3. Open Unused apps or App unused settings.
4. Turn off Pause app activity if unused.

Android’s unused-app optimization can revoke permissions, stop background activity, and stop notifications for apps that have not been used for a long time. Google describes the feature at Manage unused apps.

On Samsung, the comparable cause may be an app in the sleeping or deep-sleeping lists. Other manufacturers use different labels, such as background restrictions, auto-launch, autostart, or app hibernation.

9. Remove the app from Samsung sleeping or deep-sleeping lists

Try this when: A Galaxy phone receives alerts only while an app is open or after the phone has been idle.

1. Open Settings > Battery.
2. Tap Background usage limits.
3. Open Sleeping apps and Deep sleeping apps.
4. Remove the affected app from those lists.
5. If necessary, add it to Never sleeping apps.

Samsung states that sleeping and deep-sleeping apps may not perform background activities, including notifications. Adding an app to Never sleeping apps can increase battery use, so reserve it for apps that need timely delivery. See Samsung’s guidance for app notification troubleshooting and sleeping and deep-sleeping apps.

Do not apply this Pixel-specific path to Xiaomi, OnePlus, Oppo, Vivo, Huawei, Motorola, or other phones. Search the manufacturer’s Settings for sleeping apps, background usage, autostart, or background launch.

10. Allow background data and bypass Data Saver for the app

Try this when: Notifications disappear only on mobile data, only while Data Saver is on, or only when the app is not open.

On stock Android, open Settings > Network & internet > Data Saver. Turn Data Saver off temporarily, or tap Unrestricted data and allow the affected app. Also check Settings > Apps > [app] > Mobile data & Wi-Fi and enable background data if that control is present.

Data Saver generally limits background mobile data. Wi-Fi and mobile-data behavior can differ, so test both networks separately. If alerts work on Wi-Fi but not mobile data, investigate the carrier, VPN, firewall, private DNS, or mobile-data restriction instead of repeatedly changing notification permissions. Google explains unrestricted data in its Data Saver guidance.

There is a trade-off: allowing unrestricted background data can increase mobile-data use. Use it for apps that genuinely need background connectivity, such as messaging, work, security, or time-sensitive delivery apps.

11. Check connectivity, Airplane mode, VPN, and date and time

Try this when: Alerts are missing on one network, all apps are delayed, or the problem started after enabling a VPN, firewall, ad blocker, or private DNS service.

1. Confirm Airplane mode is off.
2. Load a webpage to verify that the phone is actually online.
3. Switch from Wi-Fi to mobile data, then test in the opposite direction.
4. Temporarily disconnect a VPN, firewall, ad blocker, or private DNS service.
5. Open date and time settings and enable automatic date, time, and time zone.
6. Restart the phone and generate a new test notification.

Push delivery depends on network access and functioning background services. Google’s general app troubleshooting guidance also recommends restarting and updating when an app behaves incorrectly.

Do not assume a weak signal is always the cause. If every other app notifies normally and only one app fails, the app’s account, server, or internal settings are more likely than the phone’s network connection.

12. Check Focus mode and Bedtime mode

Try this when: Notifications stop during work, school, sleep, or another recurring period, or a particular app appears to be paused.

For Focus mode, open Settings > Digital Wellbeing & parental controls > Focus mode. Turn it off, remove the affected app from the paused-app list, and inspect its schedule. When Focus mode is active, selected apps cannot be used normally and do not send notifications. Google’s Focus mode help explains the behavior.

For Bedtime mode, open Settings > Modes > Bedtime on current Pixel software, or look under Digital Wellbeing on phones with older or customized menus. Inspect the schedule and notification filters. Pixel’s Modes documentation covers Bedtime and other notification filters.

13. Disable Pixel Flip to Shhh if it is silencing the phone

Try this when: A supported Pixel enters Do Not Disturb when placed face down, causing alerts to become quiet unexpectedly.

1. Open Settings > System > Gestures > Flip to Shhh.
2. Turn off Use Flip to Shhh.
3. Also inspect Do Not Disturb schedules under Settings > Modes.

Flip to Shhh activates Do Not Disturb when a supported Pixel is placed face down. It is not a universal Android feature and is not available on every Pixel model. Google lists supported devices and behavior in its Flip to Shhh help page. A case, desk surface, or proximity-sensor behavior can also make the gesture seem unpredictable.

14. Restart, then update the app, Android, security components, and Google Play system

Try this when: Notifications broke after an update, the phone has been running for a long time, or the behavior is inconsistent across apps.

Restart first. A restart reloads system and app processes, so it is a low-risk diagnostic, not a guaranteed repair. Then check each update channel:

• Apps: Open Play Store, tap your profile picture, then Manage apps & device > Updates available.
• Android and manufacturer software: Open Settings > System > Software update, or use Samsung’s Settings > Software update.
• Security and Google Play system: On newer Android versions, check Settings > Security and privacy > System and updates.

Restart again when an update requests it. Google says app updates improve stability and security, while system-update availability depends on the device, manufacturer, and carrier. See Google’s app update instructions and Android update information.

If the issue began immediately after an Android, One UI, or app update, record the phone model, software version, app version, and exact symptom before changing many settings. The timing may indicate a regression, but it does not prove that the update caused it.

15. Force-stop the app, clear its cache, or reinstall it

Try this when: The app appears stuck, its notification process is malfunctioning, or other settings are correct.

1. Open Settings > Apps > [app].
2. Tap Force stop, then open the app and test it.
3. Tap Storage & cache > Clear cache.
4. Sign in again if the app requests it and generate a fresh test alert.
5. Reinstall only after confirming that the account is backed up and you know the login details.

Clearing cache removes temporary files. Clear storage, Clear data, and reinstalling can remove local settings, downloads, offline content, or account sessions. They are not equivalent to clearing cache. Google distinguishes these actions in its app troubleshooting instructions.

For messaging apps, verify that chats and media are backed up before clearing data or reinstalling. If only one app remains broken after a clean sign-in, contact that app’s developer; Android settings cannot fix a server-side account or delivery problem.

16. Reset app preferences, test Safe Mode, and escalate carefully

Try this when: Notification behavior remains broken across apps after the ordinary checks, or you suspect an app-level default was changed.

On Pixel and many stock Android phones, try Settings > System > Reset options > Reset app preferences. Read the confirmation screen because the exact effects vary by manufacturer. This is not a factory reset, but it can restore disabled apps, default app choices, permissions behavior, and other app-level defaults. You may need to recheck notification permissions and defaults afterward.

Next, test in Safe Mode. The method varies by phone; on many Android devices, open the power menu, touch and hold Power off, and confirm Safe Mode. If notifications work in Safe Mode, uninstall recently added utilities one at a time, especially:

• Battery managers and cleaner apps.
• Launchers and notification organizers.
• VPNs, firewalls, ad blockers, and private DNS tools.
• Automation apps and accessibility tools that modify notifications.

If notifications still fail in Safe Mode, the cause is less likely to be a third-party app. Contact the phone manufacturer for a system-wide issue or the app developer for a single-app issue. Google’s Pixel troubleshooting guidance places factory reset later in the process because it erases device data. Never factory-reset until you have a verified backup, access to your accounts, and recovery information for two-factor authentication.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Modern Android features that can look like failures

Notification history: the delivery test

Enable Settings > Notifications > Notification history before running your test. On supported devices, it can show recently dismissed alerts and the day’s notification history. If the missing alert is listed, Android received it and the failure is probably presentation, dismissal, grouping, privacy, or sound. If it is absent, continue with permission, app, network, and background-delivery checks.

History is not a permanent record of every notification on every Android phone. Some devices do not provide it, and enabling it after an event generally cannot recover that earlier event. Google’s notification help explains the feature and related controls.

Notification cooldown: later alerts may be quieter

On supported current Android and Pixel software, Settings > Notifications > Notification cooldown can reduce sound and pop-up interruptions when many notifications arrive in a short period. This can explain why the first message makes a sound but later messages are quiet. Turn it off temporarily while testing. Calls, alarms, priority conversations, and emergency alerts can be treated differently. Availability and behavior depend on the software version.

Notification Organizer: an alert may be grouped or silenced

On supported Pixel devices and software versions, Settings > Notifications > Notification organizer can group and silence lower-priority categories such as promotions, news, social, or suggested alerts. Availability may depend on the device, region, software release, and staged rollout. Turn it off temporarily or exclude the affected app while testing. The feature primarily changes organization and presentation; it should not be the first explanation for an alert that never appears in Notification history. See Google’s Notification Organizer help.

Special cases: watch, car, work profile, and cloned apps

If notifications work on the phone but not on a connected watch, car, tablet, or desktop, the phone’s ordinary app permission may be fine. Open the companion app and check notification access, allowed apps, mirroring, connected-device permissions, and whether alerts are set to appear on only one device. Some services deliberately suppress a phone alert when a wearable is connected.

Work profiles, managed phones, multiple users, guest mode, Samsung Secure Folder, and cloned or dual-messenger apps can have separate notification settings and accounts. A company administrator may control notification behavior, background activity, or app installation. Check that you are testing the same app instance and profile that receives the message.

Wireless Emergency Alerts have separate controls from ordinary app notifications. Do not use ordinary app-permission troubleshooting to explain every emergency-alert behavior.

When to stop changing settings

Use the pattern of the failure to decide who should help:

• One app fails, but other apps work: After checking Android permission, categories, in-app preferences, account state, battery, and data access, contact the app developer. The app’s server or account may be the source.
• Every app fails after a system update: Check for a manufacturer or carrier update, document the software version, and contact manufacturer support. Do not claim the update caused the problem unless it is reproducible or officially acknowledged.
• Notifications work in Safe Mode: Remove third-party cleaners, battery tools, launchers, VPNs, firewalls, organizers, or automation tools until the culprit is identified.
• Alerts work on Wi-Fi but not mobile data: Investigate mobile-data restrictions, Data Saver, the carrier, VPN, private DNS, and firewall settings.
• Alerts appear in Notification history: Focus on lock-screen visibility, Alerting versus Silent, pop-up settings, notification cooldown, organizer behavior, and whether the shade was cleared.
• Nothing works, including Safe Mode: Manufacturer support is appropriate. A factory reset is a last resort after backup, not a routine notification fix.

When contacting support, provide the phone model, Android and manufacturer-interface version, app version, whether the problem occurs on Wi-Fi, mobile data, or both, whether the alert appears in Notification history, whether Safe Mode changes the result, and when the issue began. Mention any recent update, device migration, profile change, VPN installation, or wearable connection.

Frequently Asked Questions

Why do Android notifications appear only when I open the app?

That pattern usually points to background delivery rather than the visible notification permission. Check Battery Saver, the app’s Settings > Apps > [app] > App battery usage setting, unused-app optimization, Samsung sleeping or deep-sleeping lists, Data Saver, background data, VPNs, and the app’s account session. If the app is absent from Notification history until you open it, also contact the app developer because its server or account may not be delivering the event.

Why does one app show some notifications but not others?

Android controls an app globally and by individual notification channel or category. Go to Settings > Notifications > App notifications > [app] and enable the relevant category. Set it to Alerting if you need sound or vibration. Then check the app’s own settings for muted conversations, quiet hours, disabled folders, or account-specific notification choices.

Why do notifications appear in history but not on my lock screen?

Android received the notification, so delivery is probably working. Check Settings > Notifications > Notifications on lock screen, choose an option that shows alerting notifications, and review sensitive-content privacy settings. Also check whether the category is Silent, notification cooldown is reducing interruptions, or Notification Organizer is grouping the alert.

Should I turn off Adaptive Battery to fix Android notifications?

Usually not globally. Adaptive Battery can reduce background activity and delay some alerts, but Google recommends keeping battery optimization enabled in normal use. Test the affected app specifically under Settings > Apps > [app] > App battery usage. Use Unrestricted only when timely delivery is important and the added battery use is acceptable.

Will clearing app data or reinstalling fix missing notifications?

It can repair damaged local app state, but it is disruptive. Force-stop the app and clear its cache first. Clearing data or reinstalling can sign you out, remove local settings and offline content, and affect unsynced data. Confirm that the account is backed up and that you have the login and two-factor-authentication details before using either option.

The Bottom Line

Start with the smallest diagnostic: disable Modes or Do Not Disturb, verify the app permission and notification category, and check Notification history. If history contains the alert, fix presentation; if it does not, investigate the app, network, permissions, and background execution. Use app-specific battery exceptions rather than disabling optimization everywhere, and reserve reset or factory-reset steps for the point when the evidence justifies them.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.