An Android phone may receive messages while showing no banner, badge or lock-screen alert. A notification can be blocked at the app level, suppressed by a single notification channel, delayed by a network connection or quietly grouped by a Focus-like interruption setting. First distinguish missing alerts from late message delivery: open the app and check whether the message was received on time.
Symptoms: what this problem looks like
- One messaging app stays silent while calls and other apps alert normally.
- Notifications appear only after the app is opened or the phone is unlocked.
- Sound is missing but the notification can be seen in notification history.
Why it happens
- Notification permission or an individual channel is disabled.
- Do Not Disturb, Bedtime or a device-specific quiet mode is active.
- Background data or app-specific battery limits defer network activity.
Before making changes
Menu names vary among Pixel, Samsung and other Android devices. Note your settings before changing them; do not install third-party “notification booster” apps or grant accessibility access to unknown tools.
Start with the least disruptive checks, and stop when the original problem is resolved. The Beginner tab below describes the recommended diagnostic sequence. The Advanced tab helps authorized support teams collect evidence without introducing unrelated changes.
Step-by-Step Troubleshooting
Work through the following steps in order. Check the result after each action and preserve a rollback path for any configuration changes.
Prove whether delivery or display is failing
Send a test message from a second account while the phone is locked. Compare the time it arrives inside the app with the time a notification appears. If the message itself is delayed, investigate the app connection and background data; if it arrives immediately without an alert, focus on display settings.
Check app and channel permissions
Open Settings > Apps > the affected app > Notifications. Enable notifications and review categories or channels such as Messages, Direct messages or Calls. A single silent channel can block sound even when the master permission is enabled. Test that exact channel rather than toggling every app.
Review quiet modes and lock-screen behavior
Temporarily leave Do Not Disturb, Bedtime or a scheduled quiet mode and repeat the test. Inspect lock-screen notification visibility and whether the relevant channel is marked Silent. Restore preferred quiet hours after identifying the setting that caused suppression.
Check app account and in-app alerts
Open the app’s own notification settings, verify the signed-in account and confirm the conversation is not muted or archived. Many chat and mail apps maintain their own notification switches independently of Android, so system permission alone may not be enough.
Allow necessary background connectivity
Confirm the app can use background mobile data and Wi-Fi. Inspect its battery usage setting; if it is Restricted and alerts arrive only on launch, test the less restrictive vendor-supported option for this app only. Do not globally disable battery optimization or data-saving controls.
Update and restart without losing data
Install available app updates from the official store and an approved Android system update. Restart the phone, then send two independent test notifications. Avoid clearing app storage or reinstalling before checking whether local messages or authentication data would be lost.
Isolate a device or service fault
Try the same account on a second device if available, or compare another notification-heavy app. If the issue follows only one account, check that provider’s status and support; if multiple apps fail on this phone, collect Android version, OEM skin, timestamps and affected channels.
Correlate the original symptom
Compare the earliest reliable error time with the documented indicators: One messaging app stays silent while calls and other apps alert normally. Collect only masked diagnostic data, and do not infer causation solely from recent changes.
Validate the strongest suspected cause
Focus the authorized test on this possible failure: Do Not Disturb, Bedtime or a device-specific quiet mode is active. Use staging or a secondary test account when feasible and document the exact rollback before any production configuration edit.
Confirm fix and watch for regressions
Send alerts while the screen is on, locked and after several minutes of idle time. Confirm the correct channel displays at the expected time, the chosen sound or vibration works, and quiet hours still behave as you intended. Preserve test evidence and route unresolved issues to the responsible vendor or system owner rather than broadening permissions or disabling protection.
Interpret the results
Use the results of your tests to choose the next action instead of repeating a reset. For this specific issue, compare the following observations with the suspected causes:
- Observation A: One messaging app stays silent while calls and other apps alert normally. This supports checking: Notification permission or an individual channel is disabled. Confirm it with a reversible test before making a lasting change.
- Observation B: Notifications appear only after the app is opened or the phone is unlocked. Compare the affected environment with a known-good case and investigate: Do Not Disturb, Bedtime or a device-specific quiet mode is active.
- Observation C: Sound is missing but the notification can be seen in notification history. If the earlier checks do not change the result, gather stronger evidence around: Background data or app-specific battery limits defer network activity.
How to verify the fix
Send alerts while the screen is on, locked and after several minutes of idle time. Confirm the correct channel displays at the expected time, the chosen sound or vibration works, and quiet hours still behave as you intended.
Common mistakes to avoid
- Clearing app data before checking backup or message sync.
- Turning off battery optimization for every app when only one channel is misconfigured.
- Assuming a visible notification means sound must be enabled.
If the problem is still there
If two networks and multiple apps fail after a system update, record the Android build, device model, app versions and exact delivery times for the manufacturer or app provider. Do not attach authentication tokens or private messages.
Include the specific step that changed the outcome, what you expected, and what actually happened. This allows the next person to continue from evidence instead of repeating the same unsuccessful tests.
Solution Checklist
Official reference
For up-to-date menus, compatibility rules and product-specific support paths, see Google Android: Control notifications. Product menus and support options can change with software versions and regions.
Editorial note: Follow these instructions only for systems and accounts you are authorized to manage. Verify each result before proceeding. This guide does not claim that one fix applies to every configuration.
Disqus hosts the discussion. Comments load automatically as you approach this section and may use cookies.