Interactive Troubleshooter

Published: Sep 17, 2026

Slack Notifications Delayed on Android 15: Deep Diagnostics & Fixes

Time: 15 mins Level: Beginner

By StepDiag Engineering Team

Reviewed by Ibraheem Taofeeq Opeyemi

Delayed push alerts in Slack running on Android 15 stem from aggressive Doze mode maintenance windows, Firebase Cloud Messaging (FCM) high-priority quota throttling, or App Standby Bucket demotions. This diagnostic tree isolates core system power limits, network socket drops, and notification permission channels to restore real-time message delivery.

Full Diagnostic Tree & Step-by-Step Overview

When and under what specific device condition do Slack notifications experience delays on Android 15?

Notifications arrive only when turning the screen on or opening the Slack app after lock state
Notifications arrive in bulk batches every 15-30 minutes instead of real-time alerts
Notifications are delayed specifically when connected to Wi-Fi or when transitioning to Mobile Data
Slack status shows active, but sound/vibration fails or alerts drop silently without system logs

What specific system mechanism is triggering the delay during device sleep or screen-off state?

Android 15 Doze Mode maintenance window is deferring FCM high-priority execution
App Standby Bucket is restricted to 'RARE' or 'RESTRICTED' via Adaptive Battery
OEM-specific aggressive battery management (e.g., Samsung Device Care, Xiaomi MIUI/HyperOS) kills background sockets
Android 15 Foreground Service type restriction terminates Slack's background listener service

Exempt Slack from Android 15 Doze Mode Power Restrictions

Solution:

Root Cause: Deep Doze State Deferring Low-Priority FCM Messages

Android 15 enforces strict idle execution limits. When a device is stationary with the screen off, the OS enters Deep Doze mode. Standard Firebase Cloud Messaging (FCM) tokens or high-priority messages that exceed their network quota are pushed into periodic maintenance windows, delaying alerts until the device awakes or the maintenance window opens.

# Diagnostic Verification:

Verify Doze state and check if Slack is optimized via ADB:

bash
adb shell dumpsys deviceidle whitelist | grep com.Slack

If no result is returned, Slack is subject to Doze mode network gating.

# Step-by-Step Fix:

1. Open system Settings > Apps > See all apps > Slack.
2. Tap App battery usage.
3. Change the setting from Optimized to Unrestricted.
4. To override via ADB directly (requires USB Debugging enabled in Developer Options):

bash
   adb shell cmd deviceidle whitelist +com.Slack

5. Verify that Slack is now listed in the power whitelist:

bash
   adb shell dumpsys deviceidle whitelist | grep com.Slack

# Prevention & Long-Term Monitoring:

Re-check this setting following major Android system updates, as system optimizations may reset app battery permissions to 'Optimized'.

Reset App Standby Bucket and Disable Adaptive Battery Suppression

Solution:

Root Cause: App Standby Bucket Demotion to RARE or RESTRICTED

Android 15 uses machine learning to assign applications to Standby Buckets (ACTIVE, WORKING_SET, FREQUENT, RARE, RESTRICTED). If Slack remains untouched in the foreground for several days, the OS demotes its standby bucket, strictly throttling network access windows and job scheduler execution.

# Diagnostic Verification:

Query Slack's current App Standby Bucket allocation using ADB:

bash
adb shell am get-standby-bucket com.Slack

If the returned value is 40 (RARE) or 45 (RESTRICTED), notification job dispatching is throttled by the OS.

# Step-by-Step Fix:

1. Open Settings > Battery > Adaptive preferences (or Adaptive Battery).
2. Disable Use Adaptive Battery to prevent automatic background bucket demotions.
3. Force Slack into the ACTIVE bucket using ADB:

bash
   adb shell am set-standby-bucket com.Slack active

4. Confirm the bucket change:

bash
   adb shell am get-standby-bucket com.Slack

The terminal should return 10 (ACTIVE).

# Prevention & Long-Term Monitoring:

Launch Slack at least once daily or set it to 'Unrestricted' battery mode to prevent the Android machine learning runtime from lowering its priority.

Disable OEM Battery Optimizations and Custom System Killers

Solution:

Root Cause: Vendor-Specific Process Management Restrictions

Hardware vendors (such as Samsung, Xiaomi, OnePlus, and Asus) layer proprietary background process killers over Android 15. These services enforce aggressive kill signals on cached background processes, destroying the persistent TCP/TLS FCM socket maintained by Google Play Services.

# Diagnostic Verification:

Inspect system logcat output for force-stop events triggered by OEM system services:

bash
adb logcat -d | grep -E "am_kill|ProcessCleaner|phantom_proc"

Look for entries terminating com.Slack or com.google.android.gms due to memory management policy.

# Step-by-Step Fix:

1. Samsung One UI: Go to Settings > Battery > Background usage limits > Never auto-sleeping apps > Add Slack.
2. Xiaomi (MIUI/HyperOS): Go to Settings > Apps > Manage Apps > Slack > Enable Autostart, and set Battery saver to No restrictions.
3. OnePlus/Realme (ColorOS): Go to Settings > Apps > App management > Slack > Battery usage > Enable Allow background activity and Allow auto-launch.
4. Disable Phantom Process Killer system-wide via ADB if running advanced workloads:

bash
   adb shell device_config put activity_manager max_phantom_processes 2147483647

# Prevention & Long-Term Monitoring:

Exclude both Slack and Google Play Services from any third-party or native vendor cleaner tools.

Update App Permissions for Android 15 Foreground Service Changes

Solution:

Root Cause: Android 15 Foreground Service (FGS) Type Runtime Exceptions

Android 15 introduces strict runtime requirements for Foreground Service types (dataSync, remoteMessaging). If Slack attempts to start a background service without explicit user context or required runtime permissions, Android 15 throws a ForegroundServiceStartNotAllowedException, terminating the sync operation.

# Diagnostic Verification:

Review system crash logs for foreground service security exceptions:

bash
adb logcat -d | grep "ForegroundServiceStartNotAllowedException"

# Step-by-Step Fix:

1. Ensure Slack is updated to the latest build supporting Android 15 API level target (API 35).
2. Reset runtime permission toggles for Slack:

bash
   adb shell pm reset-permissions com.Slack

3. Launch Slack, go to Settings > Apps > Slack > Permissions, and grant all requested access (specifically Notifications and Pause app activity if unused = DISABLED).
4. Clear application cache:

bash
   adb shell pm clear com.Slack

5. Re-login to Slack to force full registration of current Android 15 system services.

# Prevention & Long-Term Monitoring:

Keep Slack updated through the Google Play Store to receive targeted compatibility patches for Android 15 OS runtime changes.

What is the primary indicator of batched or delayed FCM push notifications?

FCM high-priority quota for Slack is exhausted, falling back to low-priority delivery
Google Play Services Push Connection socket is stale or dropped by network router
Slack internal FCM token is corrupt or unregistered in Google Cloud Messaging servers
Android Notification Channel priority is set to 'Silent' or 'Low' in system settings

Reset Firebase Cloud Messaging High-Priority Push Quotas

Solution:

Root Cause: FCM High-Priority Push Quota Depletion

Google Cloud Messaging limits the number of high-priority push messages an app can receive while the device is in a background/idle state. If a busy Slack workspace generates dozens of channel notifications per minute, Android 15 degrades subsequent FCM messages to 'normal priority', queuing them until the next maintenance window.

# Diagnostic Verification:

Dump the FCM push notification log for Google Play Services using ADB:

bash
adb shell dumpsys activity service com.google.android.gms/.gcm.GcmService

Look for entries indicating HIGH_PRIORITY_QUOTA_EXCEEDED or drop-down logs showing message priority demotion.

# Step-by-Step Fix:

1. Open Slack, tap your profile icon at the bottom right, and select Notifications.
2. Change Notify me about to Direct messages, mentions & keywords (reducing unnecessary high-priority channel traffic).
3. In Slack's internal settings, navigate to Troubleshooting > Reset Notification Settings.
4. Tap Send Test Notification to force FCM token re-negotiation with Google servers.
5. Restart Google Play Services using ADB:

bash
   adb shell am force-stop com.google.android.gms

# Prevention & Long-Term Monitoring:

Mute high-volume public channels in large Slack workspaces to avoid exceeding the daily FCM high-priority message budget.

Re-establish Stale FCM TCP Connection Sockets in Google Play Services

Solution:

Root Cause: Silent TCP Socket Timeouts on the GCM/FCM Multiplex Engine

Google Play Services maintains a persistent TCP connection on port 5228/5229 (mtalk.google.com) for all push notifications. Mobile networks or aggressive Wi-Fi routers with short NAT keep-alive timeouts often silently drop this socket without sending a FIN or RST packet. Android 15 remains unaware the socket is dead, leading to missed alerts.

# Diagnostic Verification:

Check the active connection state of the Google push service socket:

bash
adb shell netstat -anp | grep 5228

If the connection status shows CLOSE_WAIT, LAST_ACK, or produces no output, the push tunnel is broken.

# Step-by-Step Fix:

1. Force Google Play Services to rebuild its notification network sockets:

bash
   adb shell am force-stop com.google.android.gms

2. Dial *#*#426#*#* (*#*#GCM#*#*) in the phone dialer app to open the GCM Diagnostics interface.
3. Tap EVENTS and then tap RECONNECT at the top right to force an immediate socket handshake with mtalk.google.com.
4. Verify the state changes to CONNECTED.

# Prevention & Long-Term Monitoring:

If using custom firewalls or VPNs, ensure outbound TCP ports 5228, 5229, and 5230 are unblocked.

Force Regeneration of Slack FCM Device Registration Token

Solution:

Root Cause: Invalid or Stale Firebase Registration Token

During app updates or OS upgrades (e.g., updating to Android 15), the unique FCM registration token assigned to Slack can become desynchronized between the client device and Slack's backend dispatch servers. Push payloads sent by Slack's server fail at the FCM gateway due to invalid token registration.

# Diagnostic Verification:

Examine logcat output while sending a test notification from Slack:

bash
adb logcat | grep -i "FCM"

Look for error strings such as MismatchSenderId, InvalidRegistration, or NotRegistered.

# Step-by-Step Fix:

1. Open Slack and tap You > Preferences > Advanced.
2. Scroll to the bottom and tap Clear Cache.
3. Force stop the Slack process via shell:

bash
   adb shell am force-stop com.Slack

4. Re-open Slack, go to You > Notifications > Troubleshoot Notifications.
5. Let the diagnostic runner complete all checks (it will unregister and request a brand-new FCM token from Google Servers).

# Prevention & Long-Term Monitoring:

Use the built-in Slack notification troubleshooting tool whenever transferring your account to a new device.

Re-configure Android 15 Notification Channels and Priority Levels

Solution:

Root Cause: Misconfigured Android Notification Channel Importance

Android 15 segregates app notifications into granular channels (e.g., 'Messages', 'Mentions', 'Thread Replies'). If an individual notification channel is demoted to 'Silent' or 'Low Importance', Android suppresses head-up banners, lock screen popups, and auditory cues even if the push payload is delivered instantly.

# Diagnostic Verification:

Check notification channel importance settings using ADB dump:

bash
adb shell dumpsys notification | grep -A 10 "com.Slack"

Look for channel importance ratings (importance=2 indicates LOW/SILENT, importance=4 indicates HIGH/ALERTING).

# Step-by-Step Fix:

1. Go to Settings > Apps > See all apps > Slack > Notifications.
2. Ensure Allow notifications master toggle is ON.
3. Tap directly on the text (not the toggle) for Messages and Mentions to open the channel properties.
4. Select Default or Priority (ensuring Pop on screen is toggled ON).
5. Repeat this check for the Calls and Thread Replies channels.

# Prevention & Long-Term Monitoring:

Avoid long-pressing incoming Slack banners to silently dismiss them, as Android 15 may interpret this as an intent to lower channel priority.

Which network layer or interface state is causing push socket drops?

Wi-Fi Network power-save mode (IEEE 802.11ps) drops TCP keep-alive packets
Private DNS (DoH/DoT) or ad-blocking DNS blocks FCM backend servers
Data Saver mode or background data usage restrictions block Slack background traffic
Seamless Wi-Fi to Mobile Data switching drops active TCP sockets during network handoff

Disable Wi-Fi MAC/IP Power Save Mode via Android Developer Options

Solution:

Root Cause: Wi-Fi Access Point IEEE 802.11ps Sleep Cycles

When connected to Wi-Fi, Android 15 negotiates power-saving sleep cycles with the wireless router. Certain consumer routers aggressively drop inactive TCP sockets during Wi-Fi power-save sleep intervals, severing the FCM push connection without notifying the device kernel.

# Diagnostic Verification:

Ping the mobile device from an external local machine while the phone screen is off:

bash
ping <ANDROID_DEVICE_IP>

If packet loss exceeds 50% or latency spikes over 1000ms during screen-off states, Wi-Fi Power Save is dropping inbound traffic.

# Step-by-Step Fix:

1. Enable Developer Options: Go to Settings > About phone and tap Build number 7 times.
2. Go to Settings > System > Developer options.
3. Scroll down to Networking and enable Wi-Fi non-persistent MAC randomization or disable Wi-Fi Power Save (if exposed by OEM build).
4. Enable Mobile data always active in Developer Options:

bash
   adb shell settings put global mobile_data_always_on 1

*This keeps the cellular data channel standing by to receive FCM packets immediately if Wi-Fi drops the socket.*

# Prevention & Long-Term Monitoring:

Ensure home Wi-Fi router firmware is updated and DTIM (Delivery Traffic Indication Message) interval is set to 1 or 2 in router settings.

Whitelist Google FCM Endpoints in Private DNS and Ad-Blockers

Solution:

Root Cause: DNS Filtering Blocking FCM Server Hostnames

Private DNS services (such as NextDNS, AdGuard, or Pi-hole) or local VPN-based ad blockers can inadvertently flag and block Google Cloud Messaging endpoints (mtalk.google.com, alt1-mtalk.google.com, android.clients.google.com), breaking the push socket connection completely.

# Diagnostic Verification:

Test DNS resolution of the primary FCM endpoint on the device via ADB terminal:

bash
adb shell ping -c 2 mtalk.google.com

If the host fails to resolve or returns 127.0.0.1 / 0.0.0.0, DNS filtering is intercepting push traffic.

# Step-by-Step Fix:

1. Go to Settings > Network & internet > Private DNS.
2. Switch from private provider to Automatic or Off temporarily to test.
3. If using NextDNS/Pi-hole, add the following wildcard domains to your whitelist:

text
   *.google.com
   mtalk.google.com
   mtalk4.google.com
   android.clients.google.com

4. Flush the Android DNS cache by toggling Airplane Mode ON for 10 seconds, then OFF.

# Prevention & Long-Term Monitoring:

Review ad-blocker query logs regularly to ensure system-critical push notification services are not blocked.

Grant Unrestricted Background Data Access in Android Data Saver

Solution:

Root Cause: Data Saver Restricting Background TCP Traffic

When Android 15 Data Saver mode is enabled, apps operating in the background are prohibited from consuming cellular or metered Wi-Fi data. Unless Slack is explicitly exempted, all background sync requests and socket negotiations are terminated by the kernel network stack.

# Diagnostic Verification:

Check if Data Saver restriction is active for Slack:

bash
adb shell cmd netpolicy get restrict-background

If output shows true, global background data restrictions are enforced.

# Step-by-Step Fix:

1. Go to Settings > Network & internet > Data Saver.
2. If Data Saver is ON, tap Unrestricted data.
3. Scroll down to Slack and toggle the switch to ON.
4. Alternatively, grant unrestricted background network access via ADB:

bash
   adb shell cmd netpolicy add restrict-background-whitelist com.Slack

5. Verify the policy update:

bash
   adb shell cmd netpolicy get app-idle-whitelist

# Prevention & Long-Term Monitoring:

Always verify background data permissions when enabling metering policies on mobile network connections.

Optimize Cellular Network Handoff and TCP Socket Keep-Alive

Solution:

Root Cause: Socket Destruction During Interface State Handoff

When walking out of Wi-Fi range, Android 15 teardowns the wlan0 network interface and binds traffic to rmnet0 (Cellular). During this transition, active TCP sockets are broken. If Google Play Services does not instantly detect interface re-binding, push notifications are delayed until the next automated socket check-in.

# Diagnostic Verification:

Monitor network interface switching and push socket status using ADB logcat:

bash
adb logcat -b network | grep -i "interface"

Look for orphaned TCP socket errors during network handoff events.

# Step-by-Step Fix:

1. Go to Settings > System > Developer options.
2. Enable Mobile data always active (this maintains an active IP allocation on cellular towers even while connected to Wi-Fi, enabling seamless socket migration).
3. Reset network settings if socket handoffs routinely fail:

Go to Settings > System > Reset options > Reset Bluetooth & Wi-Fi.

4. Restart the device to clear stale routing tables in the cellular baseband modem.

# Prevention & Long-Term Monitoring:

Learn more about system networking and connection management at Android Official Developer Documentation.

What specific system configuration is muting or dropping delivered Slack alerts?

Android 15 Do Not Disturb or Priority Modes are suppressing notification sounds and popups
Slack Multi-Device status suppression (Desktop client active) is holding back mobile alerts
Notification history or channel group settings are automatically auto-dismissing alerts
Corrupted local Slack app database/cache is causing notification thread render drops

Configure Android 15 Do Not Disturb (DND) App Exemptions for Slack

Solution:

Root Cause: DND Mode / Priority Mode Filtering Slack Payloads

Android 15 features enhanced Do Not Disturb rules and Focus modes. If Slack is not added to the explicit DND exception list, push notifications are delivered silently to the shade without turning on the screen, vibrating, or emitting a sound ringtone.

# Diagnostic Verification:

Check if system Zen Mode (DND) is suppressing Slack alerts:

bash
adb shell dumpsys notification | grep -i "mZenMode"

If mZenMode is set to 1 (IMPORTANT_INTERRUPTIONS) or 2 (NO_INTERRUPTIONS), DND filtering is active.

# Step-by-Step Fix:

1. Open Settings > Sound & vibration > Do Not Disturb.
2. Tap Apps under 'What can interrupt Do Not Disturb'.
3. Tap Add apps, select Slack, and check Allow all notifications.
4. Ensure Bypass Do Not Disturb is toggled ON for critical channels in Slack App Settings > Notifications > Channels.

# Prevention & Long-Term Monitoring:

Review scheduled DND and Focus Mode rules to ensure business-critical communication channels are permitted during working hours.

Adjust Slack Desktop Presence and Mobile Push Timing Delay Settings

Solution:

Root Cause: Slack Desktop Active Status Notification Suppression

By default, Slack suppresses mobile push notifications whenever your Slack account is detected as 'Active' on a desktop client (macOS/Windows/Linux/Web). If you leave Slack open on a desktop computer, mobile alerts are intentionally delayed by 2 to 5 minutes to prevent duplicate notifications.

# Diagnostic Verification:

Check Slack's notification timing preferences via the Slack mobile app (You > Notifications > Send notifications on mobile).

# Step-by-Step Fix:

1. Open Slack on your Android device.
2. Tap You (profile tab) at the bottom right > Notifications.
3. Tap Send notifications on mobile.
4. Change the setting from On a delay (default) to As soon as I'm inactive or Always, even if I'm active.
5. Ensure your desktop client is closed or explicitly set to 'Away' when stepping away from your workspace.

# Prevention & Long-Term Monitoring:

Setting mobile delivery to 'Always' completely eliminates desktop presence detection delays across all platforms.

Re-enable Notification Banners and Check Android Notification History

Solution:

Root Cause: Android System UI Heads-Up Notification Suppression

If the 'Heads-up' display flag is toggled off globally or per-channel, incoming notifications land silently in the drop-down notification shade without popping up over active apps or waking the lock screen.

# Diagnostic Verification:

Verify incoming notification events via Android Notification History:
1. Go to Settings > Notifications > Notification history.
2. Look for recent Slack entries. If listed here but no sound/popup occurred, UI rendering is suppressed.

# Step-by-Step Fix:

1. Go to Settings > Apps > See all apps > Slack > Notifications.
2. Tap on the Messages and Mentions channel.
3. Toggle Pop on screen to ON.
4. Ensure Lock screen notifications is set to Show all notification content.
5. Toggle Allow notification dot to ON.

# Prevention & Long-Term Monitoring:

Use Android Notification History as a quick diagnostic tool to confirm whether alerts are reaching the system or failing at the network level.

Perform Full Application Reset and Re-index Local Storage

Solution:

Root Cause: Corrupted Local SQLite Database or Cache Locks

Slack uses an internal SQLite database to store channel messages, user states, and push payload logs locally. If an unexpected app crash occurs during an in-app database migration on Android 15, thread rendering stalls, causing incoming push payloads to be discarded by the client app UI thread.

# Diagnostic Verification:

Check logcat for database execution errors within the Slack process space:

bash
adb logcat -d | grep -i "android.database.sqlite"

# Step-by-Step Fix:

1. Force stop Slack:

bash
   adb shell am force-stop com.Slack

2. Clear app cache and local data storage:

bash
   adb shell pm clear com.Slack

3. Uninstall the Slack app:

bash
   adb uninstall com.Slack

4. Re-install the latest version of Slack from the Google Play Store.
5. Log into your Slack workspace and re-run You > Notifications > Troubleshoot Notifications to register clean state pointers.

# Prevention & Long-Term Monitoring:

Periodically clear app cache via Slack's internal settings menu to prevent database fragment inflation.

Related Diagnostic Guides

Notion Offline Mode Data Lost: Version History & Cache Recovery Guide

Excel File Crashes on Open: Safe Mode and Add-ins Recovery Guide

Google Calendar Not Syncing to Outlook: Complete Fix Guide

Home Assistant Database Corrupted After Power Loss: Recovery Guide

PDF Won't Print: Font Embedding and Driver Fix Guide

Subscribe to StepDiag

Embed Guide on Your Website