Xiaomi and the Autostart Setting That Breaks Notifications

You set up a messaging app on a new Xiaomi phone, grant every permission it asks for, and for the first day notifications land exactly on time. Then, a few days later, they stop. Not all at once and not with any warning: a message sits in the thread for hours before you open the app yourself and see it was already there. Nothing in the app's own settings looks wrong. The channel is on, the permission list is green, Do Not Disturb never ran. Miui notifications not working this way, quietly and only after a delay, almost always traces back to one setting that has nothing to do with notifications in its name at all: autostart.

Here is what autostart actually controls, the two settings that sit next to it and cause the same symptom, and why this is one of the rare cases where the app you are troubleshooting genuinely cannot fix itself.

Autostart, the permission nobody grants

MIUI and HyperOS run their own process management on top of standard Android, and autostart is the gate it puts in front of every app. An app without autostart permission is allowed to run while you have it open, but once you close it, swipe it away, or the phone reboots, the system will not relaunch it on its own. For most apps that is invisible, because most apps only need to run while you are looking at them. A notification listener is different: its entire job is to stay running quietly in the background so it can hear a message the moment it arrives, and without autostart, Xiaomi's process manager treats it the same as any other closed app and leaves it closed.

The setting defaults to off for almost everything you install, which is the opposite of how most Android permissions behave. You find it under Settings, then Apps, then Permissions, then Autostart, sometimes reached instead through the Security app's own permissions screen depending on the MIUI or HyperOS version. It is a flat list of every installed app with a toggle next to each one, and on a phone that has never been opened, the vast majority of that list is switched off.

Battery saver set to no restrictions

Autostart controls whether the app can start again at all. A separate setting controls how much it is allowed to do once it has started, and that one lives under Settings, Battery and performance, App battery saver. Each app sits in one of three states: battery saver, which restricts background activity on a schedule the system decides, restricted, which blocks background activity almost entirely, and no restrictions, which leaves the app alone. An app can have autostart enabled and still go quiet for hours if battery saver here is left on its default setting rather than switched to no restrictions.

This is the same standby bucket mechanism described in more detail when looking at how OEM battery managers delay or kill background apps generally, except Xiaomi runs its own stricter version underneath the standard Android one, which is why fixing the Android-level setting alone is not always enough on this brand specifically. Both the autostart toggle and the battery saver level need to be checked, and checking only one explains why a fix that worked for a friend's phone sometimes does nothing on yours.

Lock the app in recents

The third piece is the recent apps view. MIUI periodically clears background apps from memory, including ones with autostart and unrestricted battery access, and it is more aggressive about this than the standard Android task switcher. Open the recent apps screen, find the app's card, and tap the small padlock icon at the top of that card, usually revealed by tapping the app's icon within the card rather than the card itself depending on the version. A locked app is excluded from MIUI's automatic memory cleanup, which on a phone with many apps open at once can be the difference between a background listener that survives the afternoon and one that gets swept away with everything else the moment memory gets tight.

None of these three settings substitutes for the other two. Autostart without battery saver set to no restrictions still gets throttled. Both without the recents lock can still get cleared the next time MIUI decides memory is low. The combination is what keeps a background service alive.

Why the app cannot fix this for you

It is worth being direct about why a notification history app, or any app whose job depends on running quietly in the background, cannot simply turn these settings on itself. Autostart and battery restrictions exist specifically to limit what an app is allowed to do without you noticing. If an app could flip its own autostart permission or exempt itself from battery restrictions, the setting would stop meaning anything, for this app or for every other app that might try the same thing. Android and MIUI both withhold that control from apps on purpose, which is also why the fix always looks the same regardless of which app is affected: open the settings, find the app, change the toggle yourself.

Samsung phones run into a related version of this with their own sleeping apps list, covered in more detail in why Samsung notifications arrive hours late, and the underlying shape is identical across both brands: a manufacturer layer sits above standard Android, restricts background apps more tightly than Android does on its own, and only the person holding the phone can grant the exception. An app built well still depends on you doing this once, on this device, after you install it.

A checklist you can run in two minutes

In order, on the app whose notifications are arriving late or not at all:

• Settings, Apps, Permissions, Autostart: find the app and switch it on.
• Settings, Battery and performance, App battery saver: find the app and set it to no restrictions.
• Recent apps view: open the app's card and tap the padlock icon to lock it.
• Close the app and leave the phone with the screen off for a few minutes before testing, since a change made while the app is open does not always apply until the next time it starts.

After making the change, the real test is not waiting for the next message to arrive on its own. Send yourself a test notification through the app and see whether it shows up within a few seconds rather than only once you unlock the phone later. If it still arrives late, Android's own notification log can confirm the exact time something actually landed, as long as the phone has not rebooted since, which helps separate a delay from a notification that silently never arrived at all.

ReNotify walks through autostart and battery saver for your specific device the first time you open it, because on Xiaomi and HyperOS phones a listener that is not exempted from both will eventually miss something no matter how well the app itself is built. Getting the setting right once, on this phone, is what keeps the history it builds complete.