Fix Android Notification Badges Not Updating

1. Verify the app’s notification permission

1. Open Settings → Apps & notifications → See all apps.
2. Select the app that shows a wrong badge.
3. Tap Notifications. Ensure the master toggle is On and that the relevant notification channels (e.g., “Messages”, “Updates”) are also enabled.
4. If you see a “Blocked” label, turn it on and confirm any pop‑up asking for permission.

Why this matters: Android will not forward a notification to the launcher if the system blocks it at the source.

2. Check launcher badge settings

Different launchers expose badge controls in different places. Below are the most common paths.

• Pixel Launcher / Google One UI: Settings → Apps & notifications → Notifications → App icon badges. Make sure the global toggle is On.
• Nova Launcher: Long‑press the home screen → Settings → Notification badges. Enable Show notification count and optionally Badge style.
• Microsoft Launcher: Settings → Personalization → App icon badges. Turn on Show badge on app icons.

If you recently switched launchers, the new launcher may have its badge feature disabled by default.

3. Disable battery optimisation for the affected app

1. Open Settings → Battery → Battery optimisation (or Battery usage → Optimisation).
2. Tap the drop‑down menu and select All apps.
3. Find the app and set it to Don’t optimise.

Why this matters: When Android puts an app in Doze mode, its background service that informs the launcher of new notifications may be paused, leaving the badge stale.

4. Clear the launcher’s cache and data

Sometimes the launcher’s internal badge cache becomes corrupt.

1. Open Settings → Apps & notifications → See all apps.
2. Tap the three‑dot menu → Show system (if needed).
3. Locate your launcher (e.g., Pixel Launcher, Nova Launcher).
4. Tap Storage & cache → Clear cache. If the badge still misbehaves, also tap Clear storage. Warning: clearing storage resets your home‑screen layout, widgets, and folder structure.
5. Restart the device.

After the reboot the launcher rebuilds its badge database from fresh notification events.

5. Reset the notification listener service (ADB optional)

If the above steps did not revive the badge, you can force Android to re‑register the notification listener that feeds badge data.

Prerequisite: A computer with adb installed and USB‑debugging enabled (Settings > Developer options > USB debugging).

1. Connect the phone via USB and verify the connection with adb devices.
2. Run the following command to toggle the listener off and on:

   adb shell settings put secure enabled_notification_listeners ""
   adb shell settings put secure enabled_notification_listeners "$(adb shell settings get secure enabled_notification_listeners)"

3. Reboot the device (or simply press the power button and select Restart).

What this does: Android clears the list of apps that have permission to read notifications, then restores it, forcing a fresh registration.

6. Update or reinstall the problematic app

Some apps ship buggy badge implementations that are fixed in newer releases.

1. Open the Play Store, search for the app, and tap Update if available.
2. If no update exists, uninstall the app (Settings → Apps → Uninstall) and reinstall it from a trusted source.

Reinstalling also clears any stale internal badge state the app may keep.

7. Verify the fix with a test notification

1. Open a messaging app (e.g., Messages, WhatsApp) that you know supports badges.
2. Ask a friend to send you a message, or send yourself a test message using the app’s “self‑chat” feature.
3. Observe the app icon on the home screen. The badge should appear instantly (or within a few seconds).

If the badge appears, the problem is solved. If not, proceed to the troubleshooting section.