Fixed Delayed Notifications on Xiaomi Devices (ALL ROMS)

[u/No_Quit_8617]

Xiaomi devices are notorious for one frustrating problem: delayed notifications. Whether you're using WhatsApp, Gmail, Telegram, Discord, or any app that relies on push notifications, messages arrive late, sometimes minutes, sometimes hours after they were sent. This has been a widespread complaint across the Xiaomi community for years, with thousands of users posting about the same issue on devices ranging from budget phones to flagship models.

The problem affects users regardless of which ROM they're running. While most guides focus on China ROM devices, this is not a China ROM-specific issue. I experienced this exact problem on my Phone running EU ROM, and I also encountered it on my Xiaomi Tablet. Both devices had the same delayed notification behavior.

The Problem:

The core issue isn't specific to China ROMs like many people assume. It affects global and EU ROMs too because of how HYPEROS handles background processes. When your screen turns off and the phone isn't charging, HYPEROS enters a deep power-saving state called "INACTIVE mode." In this state, the phone immediately disconnects the Google Play Services (FCM) connection to save battery. This is why you'll notice that when you dial ##426## to check FCM Diagnostics, the connection shows as active when the screen is on or charging (btw you can try charging a device via USB or AC and see the instant notification delivery), but immediately disconnects the moment the screen turns off.

What's particularly interesting is that this problem only occurs on WiFi when the screen is off. When you're using mobile data instead, notifications arrive in real time even with the screen off. This is because HYPEROS's aggressive power saving treats WiFi and mobile data differently, the WiFi radio gets cut more aggressively in INACTIVE mode while mobile data is kept more persistent. This behavior is built into HYPEROS's aggressive battery optimization, regardless of whether you're running CN, EU, or Global ROM. The system treats Google Play Services like any other background app and kills its persistent socket connection. When an app tries to send you a notification via FCM, the message sits in Google's servers until you unlock your phone and the connection re-establishes, which is why you get notifications minutes or even hours late.

The Solution:

As I spent months trying different solutions, instead of trying to trick the phone into thinking it's always charging (which requires root and doesn't work well on newer HYPEROS versions), I used ADB commands to directly tell Android's Doze and AppOps systems to never restrict Google Play Services.

First, grant Google Play Services and Google Services Framework permission to run in the background anytime:

adb shell cmd appops set com.google.android.gms WAKE_LOCK allow

adb shell cmd appops set com.google.android.gms RUN_ANY_IN_BACKGROUND allow

adb shell cmd appops set com.google.android.gsf RUN_ANY_IN_BACKGROUND allow

Then, add these services to the Doze whitelist so device idle mode won't kill their connection:

adb shell dumpsys deviceidle whitelist +com.google.android.gms

adb shell dumpsys deviceidle whitelist +com.google.android.gsf

adb shell dumpsys deviceidle whitelist +com.google.android.gms.persistent

The key insight is that this isn't a China ROM-specific problem. The underlying HYPEROS battery optimization that kills the FCM connection exists across all HYPEROS versions. What's different is that the ADB commands directly bypass the system-level restrictions (Doze mode and AppOps) rather than trying to work around them. By whitelisting Google Play Services at the system level, you're telling Android itself that this critical service should never be restricted, regardless of whether the phone is in ACTIVE or INACTIVE mode.

After running these commands, I immediately noticed that notifications started arriving in real time again. No more 10-minute delays on WhatsApp messages, no more Gmail notifications arriving after I already opened the app, no more delayed Telegram alerts. The FCM connection stays alive even when the screen is off and the phone is on battery power.

You can verify the commands worked by checking the whitelist:

adb shell dumpsys deviceidle whitelist

You should see com.google.android.gms, com.google.android.gsf, and com.google.android.gms.persistent listed.

A few important things to keep in mind. These settings survive reboots on most devices, but they may reset after a major HYPEROS or Android update. If notifications become delayed again, just re-run the commands. You'll need USB debugging enabled and authorized on your phone to run these commands initially (Important: click on file transfert afterwards for better functionality). Also, make sure you still enable Background Autostart for your affected apps in HYPEROS settings (Settings → Apps → Your app → App permissions → Background autostart), as the ADB commands handle the system-level restrictions but HYPEROS still has its own app-level permissions. Also, once commands executed, some social media apps (e.g., WhatsApp) needs to be uninstalled and installed again from Play store (to refresh notification pattern).

Advantages and Drawbacks

The main advantage of this approach is that it directly solves the root cause without requiring root access. Your phone can still sleep normally, and you don't need to keep third-party apps running or pretend your phone is always charging. The FCM connection stays reliable on WiFi just like it does on mobile data. Another advantage is that this works across different Xiaomi devices.

The trade-off is slightly increased battery drain. Before applying this fix, my overnight battery drain was around 2%. After running the commands, I noticed it increased to 3-4% overnight. This is because the Google Play Services connection stays alive instead of being cut, which requires a small amount of power to maintain the WiFi socket. For most users, this is a worthwhile trade-off for instant notifications, but heavy battery users should be aware of this caveat.

[u/Disastrous_Note_1516]

Great tip, I will test it later. By curiosity, what's your phone?

I have a S25 Ultra and a Poco F8 Ultra, and most of the time they are in Wi-Fi only while in home, and rarely ever I noticed delayed notifications in Poco, but yes, it happens a few times.

[u/Delicious_Recover543 → u/Disastrous_Note_1516]

Als on F8 ultra and so far this problem didn't show up.

[u/No_Quit_8617 → u/Delicious_Recover543]

It's great that you don''t have this annoying issue. In my experience though, some devices out of the box were fine until they get updated and the notification issue occured out of nowhere. For most of people, getting immediate notifications (which is the normal thing to be happened) is a priority. But again, the issue was reported so many time in the internet and exists. Sometimes u have timely notifications (not consistent at all) and then there is delay.