How to disable automatic launch of applications on Android

Many smartphone users are faced with a situation where the device starts to work slower, and the battery charge melts before our eyes for no apparent reason. Often the culprits of this behavior are apps that launch immediately after turning on the phone and continue to run in the background, consuming valuable processor and RAM resources. Understanding how to manage this process is the key to optimizing the performance of your gadget.

Modern operating systems Android have powerful power management mechanisms, but they do not always work as the user would like. Manufacturers of shells, such as MIUI, OneUI or ColorOS, often add their own algorithms that can either block necessary notifications or, conversely, keep too many unnecessary processes in memory. In this article, we will analyze in detail all the available ways to restrict autorun.

There are several levels of prohibition: from standard system settings to using special administrator rights. The choice of a specific method depends on what phone model and software version you have. Manual control Processes give maximum control, but require care not to disable critical system services.

Standard autorun controls in settings

In most modern smartphones The autostart control function is already built into the system, although its location may vary depending on the manufacturer. Typically this section is hidden in the application management menu or in special battery settings. To get started, you should look for item Settings → Applications → Autorun or a similar one.

If you are the owner of a device from Xiaomi or Redmi, then you are the luckiest: in shell MIUI there is a separate “Security” application, where autorun control is placed at the top level. Here you can simply switch the toggle switch opposite the unnecessary app, and it will no longer start when you turn on the phone. This is the easiest and safest method for beginners.

On devices Samsung with a shell OneUI the situation is a little more complicated, since there may not be an explicit “Autorun” switch. Here the system relies on power saving and sleep modes for applications. You need to go to the battery settings and add problematic apps to the list of those that are put into sleep mode. Deep sleep completely prohibits the application from running in the background until you open it.

⚠️ Attention: Do not disable autorun for system applications such as Phone, Messages, Contacts, or Google Play Services. This can lead to incorrect operation of the smartphone, loss of notifications and failures in data synchronization.

Owners of “pure” Android (for example, Google Pixel or Motorola) will have to look for settings in the “Digital Well-Being” section or in the advanced battery settings. Often there is no direct ban on start, but there are restrictions on background activity, which are similar in effect to disabling autorun.

Using the mode developer to limit processes

If the standard settings do not give the desired result, you can use the hidden menu for developers. This section provides access to deeper system settings, allowing you to limit the number of background processes globally. To get there, you need to click seven times on the build number in the “About phone” section.

In the developers menu, find the item Background process limit. By default, there is “Standard limit”, but you can select the option “No background processes” or limit their number, for example, to two. This will force the system to force close applications as soon as you switch to another task.

This approach is radical solutionwhich can significantly speed up older devices with low amounts of RAM. However, keep in mind that instant messengers and email clients may stop receiving real-time notifications, as their processes will be killed by the system instantly.

Also in this section there is an option Do not save actionsthat forces the system to destroy application activity immediately after the user leaves it. This is useful for testing, but in everyday use it will make multitasking almost impossible.

Force stop and limit background activity

Another effective method, available on any version Android is a manual forced stop and prohibition of working in the background for specific applications. This method requires an individual approach to each app that bothers you.

Go to application settings, select the desired app and find the “Stop” or “Force Stop” button. This will instantly kill the current process. However, to prevent it from starting again, you must also disable permission to run in the background.

• 📱 Go to Settings → Applications → Select application.
• 🔋 Find the item “Battery” or “Charge Consumption.”
• 🚫 Select the "Restricted" or "Prohibit background activity" mode.
• ✅ Confirm the action in the dialog box that appears.

After completing these steps, the application will only be able to work when it is open on the screen. As soon as you minimize it, the system will block its activity. This is ideal for rarely used apps that you do not want to completely remove.

Why might the Stop button be grayed out?

If the Force Stop button is grayed out, it means that the application is a system application or has device administrator rights. In this case, you first need to revoke administrator rights in the security settings, and then try to stop the service again.

Managing autorun via ADB commands

For advanced users who want to gain full control over the system without obtaining root access, Android Debug Bridge (ADB)will be an excellent tool. This method allows you to disable application components at the system level, making them invisible to the task scheduler.

To work, you will need a computer with installed drivers and platform tools ADB, as well as USB debugging enabled on your smartphone. By connecting your phone to a PC, you can send commands that will block autorun even for those applications that do not have such a setting in the interface.

adb shell pm disable-user --user 0 com.package.name

Instead com.package.name you need to substitute the real package name of the application that you want to disable. You can find it out using special utilities or the command adb shell pm list packages. After executing the command, the application will disappear from the launcher and will no longer launch automatically.

ADB Command	Action	Risk
pm disable-user	Disables the application for the current user	Low (can be enabled back)
pm clear	Clears application data and cache	Medium (loss of settings)
am stop-service	Stops a specific service	Medium (service may restart)
pm uninstall	Complete removal of a system application	High (possible instability)

It is important to understand that use ADB commands requires caution. Disabling critical system components may result in a bootloop (cyclic reboot) or loss of network connection. Always check the purpose of the package before disabling it.

Third-party utilities for controlling autorun

If you don’t want to tinker with the settings and command line, specialized applications from the store will come to the rescue. Google Play. There are many optimizers that automatically find startup apps and offer to disable them with one click.

Popular solutions like Greenify or All-In-One Toolbox use their own algorithms to “put to sleep” applications. They not only prohibit the start, but also monitor the behavior of the app, blocking its “awakening” by other processes. This is especially true for social networks, which often try to run through each other.

However, it is worth considering that installing another application to combat other applications may itself consume resources. Choose only proven utilities with high ratings and a large number of reviews. Avoid "cleaners" that promise incredible speedup, but in reality only show ads.

⚠️ Warning: Many modern versions of Android aggressively limit the ability of third-party applications to manage other processes. Utilities may work unstable on Android 12 and higher without providing special permissions via ADB.

Some antiviruses, such as Kaspersky or ESET, also have autorun control modules in their functionality. If you already have a similar security system installed, check its settings; you may not need additional software.

Features of disabling autorun on different versions of Android

The logic of the operating system has changed with each major version, and what worked on Android 8may not be available or work differently on Android 14. Google is constantly tightening the rules for background work to save energy.

On versions before Android 9 Pie applications had much more freedom of action. They could use services to hang in the memory permanently. Beginning Android 10, strict restrictions on location access and background activity have been implemented. Android 12 a feature called “Suspend cached applications” has appeared, which freezes processes when they are not in use.

On the latest versions of the system, the emphasis has shifted from completely prohibiting autorun for intelligent control. The system decides when to launch the application based on your usage habits. Therefore, manual intervention is required less and less, but for specific tasks it is still necessary.

How to find out which application is loading the system at startup?

To do this, you can use the built-in battery monitoring or third-party utilities like BetterBatteryStats. They will show which processes were activated most often and how long they were awake in the background. Often the culprits are not the applications themselves, but their support services.

Does disabling autorun affect the receipt of notifications?

Yes, it does directly. If you prevent a messenger (WhatsApp, Telegram) from starting automatically or running in the background, you will not receive a message until you open the application yourself. For email clients, you can set up a synchronization schedule so that the compromise is less noticeable.

Is it possible to restore an application deleted via ADB?

Yes, if you used the command disable-userthe application is simply hidden. To return, use the command adb shell pm enable com.package.name. If a complete removal of the system package was performed without a backup, a flashing or reset to factory settings will be required.

Why are autorun settings reset after a reboot?

Some manufacturers deliberately reset background process restrictions after a reboot to ensure system stability. This can also happen after a firmware update. In this case, you will have to reapply the settings or use more robust methods via ADB.

Do you need to disable autorun for widgets?

Desktop widgets by their nature require constant updating of data, so they often have their own autorun services. Disabling these services will cause the widget to stop displaying current information (weather, exchange rates, news) and will show old data or an error.