Owners of Xiaomi smartphones with a MIUI shell or HyperOS often face a situation where applications are “unloaded” from memory before they have time to finish playing a track or finish downloading a file. In search of a solution, users stumble upon a hidden setting “Limit of background processes.” This is an Android system feature that allows you to rigidly adjust the number of simultaneously running applications that are not visible to the user at the moment.
By default, this option is often hidden from the eyes of the average user, as the system itself tries to balance between performance and autonomy. However, interfering with this parameter can dramatically change the behavior of your device. Understanding how memory management works at the kernel level of the system will help you decide whether to limit processes manually or trust the shell optimization algorithms.
In this article, we will take a closer look at the mechanics of background services, analyze the impact of speed and autonomy restrictions, and provide step-by-step configuration instructions for different scenarios of using your gadget.
Mechanics of background processes in Android
Android is built on the principle of multitasking, where each application can consist of several components. When you fold a program, it does not disappear completely, but goes into a state of "background activity." This allows you to instantly deploy the application when you re-task and ensures that notifications work, email and music synchronize, but each process consumes RAM and CPU time.
The system task manager constantly monitors the load. If free memory becomes critically scarce, Android begins to force shutdown processes, starting with those that have not been used for a long time. On Xiaomi devices, this process is complemented by aggressive work of the MIUI shell, which seeks to extend battery life, often at the expense of the background activity of the messengers you need.
Background Process Limit gives the user the ability to redefine the standard behavior of the system, so you can specify hard how many applications are allowed to be in memory at once, and it works like a windshield wiper: once the number of processes exceeds the set limit, the old ones are instantly destroyed, freeing up resources for the current task.
Technical detail
How to find and activate hidden menus
The limit management option is in the Developer Menu, which is hidden by default in the system settings. To access it, you need to perform a few simple actions. Find the About Phone menu and click 7 times in a row on either the MIUI version or the OS version.
Once you've become a developer, go back to the main settings menu, go to "Additional" or "Extended Settings" where a new "Developers" item appears. Inside this menu, scroll down to the "Applications" section, and you'll find the "Background Process Limit" line.
It's important to understand that changing these settings takes effect immediately. You don't have to reboot the device to see the result. However, if you set too tight limits, the system can start to run unstable, so experiment with caution.
☑️ Activation of the Developer Menu
Impact of Battery and RAM Restrictions
Many users mistakenly believe that limiting background processes always saves battery life. The logic seems simple: less programs run, less power is wasted. But in reality, it's more complicated. When you tightly limit the number of processes, the system has to constantly restart the applications that you need right now.
The process of “cold start” an application (when it is booted from scratch, rather than from memory) requires significantly more processor resources and power than simply switching between tasks already running. If you set a limit “No background processes”, your phone will constantly expend energy on initializing services, which can eventually even increase battery life.
On the other hand, on older devices with low RAM (2-3 GB), a limitation can help, prevent RAM overflows that cause interface lags and system hangs, in which case the sacrifice of background synchronization for smooth interface operation is justified.
Use cases: when to limit
There are specific situations where manually setting limits is really beneficial, especially for older smartphones that are used as navigators or music players in the car, in which case you only need one application (such as Yandex.Navigator or Spotify) to work, and the rest do not distract resources.
The second scenario is high-demand games, where if you run heavy games at the limit of iron, the background processes can eat away at precious megabytes of memory, causing friezes. Setting a limit of 1 or 2 processes before launching a game can stabilize FPS.
The third is kiosk mode, or handing over the device to a child, and by limiting the background, you ensure that the application you are running will not be interrupted by the system, and the child will not be able to accidentally switch to other programs, consuming traffic or making purchases.
💡
If you use your phone as a navigator, set a limit of 1 process and add a navigator to battery exclusions, which will prevent the screen from turning off and voice prompts from stopping.
Comparison of Limits Options
You'll see several different values in the settings menu, and understanding the difference is critical to the proper functioning of the system. Standard value usually means that the system decides how many processes to store based on the current load.
The numbers (1, 2, 3, 4) are hard to pinpoint the number of background applications. If you choose "No background processes," the system will kill everything immediately after folding, a radical measure that turns a smartphone into a device with the functionality of a push-button phone in terms of multitasking.
Below is a table showing the impact of different settings on system behavior:
| Setting up | System behaviour | Impact on the battery | Recommendation |
|---|---|---|---|
| Standard limit | Dynamic management | Optimal. | For all users |
| No background processes | Instant closure | High consumption (constant start) | Only for games. |
| Maximum 1 process | All that remains is active. | Medium. | For navigation/music |
| Maximum 4 of the process | Moderate cleaning | Low. | For old devices. |
⚠️ Note: Setting a "No Background Processes" value can result in loss of unsaved data in applications and disruptions to system services such as telephony or Wi-Fi.
Problems with notifications and their resolution
The most common complaint after changing limits is that notifications from instant messengers (Telegram, WhatsApp, Viber) stop coming in.