How to check autorun on Android: a complete guide

Modern smartphones based on the operating system Android have impressive characteristics, but over time, users often notice a decrease in performance and rapid battery drain. One of the main reasons for this behavior is the uncontrolled autorun of apps that are activated immediately after the device is turned on or rebooted. These processes can run in the background, consuming RAM and processor resources, even if you are not using them.

Understanding which services start automatically is critical to optimizing the operation of your gadget. Many smartphone manufacturers, such as Xiaomi, Samsung or Huawei, hide standard startup lists deep in the system settings so as not to overload the average user's interface with unnecessary information. However, access to this data is necessary for advanced users who want to take full control of their device.

In this article we will examine in detail methods for detecting hidden processes, ranging from built-in system tools to the use of specialized software. You'll learn to differentiate between system services that are required for your phone to function and third-party apps that can be safely disabled. This will not only speed up the startup of your smartphone, but also significantly extend its battery life.

Built-in application controls

The first and safest step is to check the default settings of your smartphone. In most modern shells, such as One UI from Samsung or MIUI from Xiaomi, there is an application management section where you can view the permissions and behavior of apps. However, it is worth understanding that a direct “Autostart” list in its pure form is rare; More often than not, this function is disguised as permission management or battery optimization.

First you need to go to the Settings → Applications → Application managementsection. Here you will see a complete list of installed software. Select the suspicious application and go to its detailed description. Pay attention to item Permissions or Run in the background. If the switch is active, the app has the right to start along with the system without your knowledge.

Some manufacturers have moved autorun management to separate optimization menus. For example, on Honor or Huawei devices you need to look for the Battery → Launching applicationssection. Here the system itself offers to control which apps can run in the background. Disabling this option for instant messengers may delay notifications, so proceed with caution.

⚠️ Warning: Disabling system services with names containing the words "System", "Framework" or "Google" may result in unstable operation of the operating system or loss of synchronization data.

If you do not find an explicit autorun switch, check the section Special features. Often malware or aggressive optimizers disguise themselves as accessibility services in order to gain permanent operating privileges. There should be no apps unknown to you in the list of active services.

Using developer mode and statistics

A more in-depth analysis method is to use a hidden menu for developers. This section provides access to technical process statistics that are not visible in the regular interface. To activate this mode, you need to click 7 times on the build number in the section About phone, after which a new item will appear in the main settings For developers.

Inside this menu we are interested in the section Running services or Process statistics. This displays a list of all currently active services and the amount of RAM they occupy. Although this is not a direct startup list, it allows you to identify applications that start first and occupy memory immediately after the system boots.

You can also find an item in the developer menu Background process limit. By default, it is usually set to "Standard Limit". Changing this setting to "No more than 1 process" or "No background processes" will forcefully prevent most apps from running in the background. This is a drastic measure that can be useful for testing, but inconvenient for everyday use.

• 📱 Battery statistics: Shows which applications are consuming energy in the background.
• ⚙️ USB debugging: Necessary for connecting to a computer and using ADB.
• 🚫 Do not kill activities: An option that prevents the system from closing background processes.

Pay attention to the parameter Time spent working in the background. If an application that you have not used for several days has a long active time, it means that it has successfully registered itself in startup and bypasses standard system restrictions. Such apps are candidates for removal or forced stop.

Checking via a computer using ADB

The most accurate and A professional way to check autorun is to use tools Android Debug Bridge (ADB). This method requires connecting the smartphone to the computer via a USB cable and having the device driver installed. ADB allows you to send commands directly to the system, bypassing the limitations of the GUI.

To get started, you need to enable USB debugging in developer mode, which was mentioned earlier. Once connected to your PC, open a command prompt or terminal in your ADB tools folder. The first command should always be to check the connection: adb devices. If a device with status deviceappears in the list, you can begin diagnostics.

To see a list of all installed packages, including system ones, use the command:

adb shell pm list packages

However, this command produces too much information. We are specifically interested in those components that respond to the system boot event. To do this, you can use the command to view the broadcast receivers that respond to BOOT_COMPLETED:

adb shell dumpsys package | grep -A 5 "android.intent.action.BOOT_COMPLETED"

The result of this command will show a list of packages that are registered to run when the device is turned on. This is the most comprehensive startup list available at the system level. You will see package names such as com.facebook.katana or com.google.android.gms.

⚠️ Note: The command line interface does not have a Cancel button. Be extremely careful when entering commands that remove or disable system packages, as this can turn the phone into a “brick”.

Third-party monitoring utilities

If working with the command line seems too complicated to you, specialized applications from the store will come to your aid. There are a number of utilities developed by enthusiasts that visualize hidden startup processes. One of the most popular and reliable apps in this category is Google Play. There are a number of utilities developed by enthusiasts that visualize hidden startup processes. One of the most popular and reliable apps in this category is Autostarts.

The application Autostarts scans the system and displays a detailed list of all events to which installed applications react. You can filter the list by event Boot Completed (Download complete) and see who exactly starts with the phone. The app interface allows you not only to view, but also to disable unnecessary components without obtaining root access, using special ADB commands inside the application.

Another useful tool is Greenify. Although this app is more focused on putting applications to sleep, it also provides excellent analytics on the behavior of software in the background. Analysis mode will show which applications frequently wake up the system or are launched by other apps. This helps to identify startup chains when one application pulls another.

Utility name	Root required	Main function	Complexity
Autostarts	No (partially)	View and disable autorun	Medium
Greenify	No	Hibernate background processes	Low
System Panel 2	No	Real-time activity monitoring	High
All-In-One Toolbox	No	Comprehensive cleaning and management	Low

It is worth noting that the effectiveness of third-party applications may vary depending on the version Android. Starting with version 8.0 (Oreo), Google introduced strict restrictions on background activity, causing some older methods of controlling startup to stop working or require additional permissions through the computer.

Why can't some apps be disabled?

System apps signed with manufacturer or Google certificates are often protected from being disabled by standard methods. An attempt to remove them without root access will result in an error, and disabling them may cause malfunctions of the phone.

Analysis of energy consumption as an autorun indicator

An indirect, but very effective method of identifying apps registered in startup is to analyze battery consumption statistics. Apps that start automatically and run in the background inevitably consume power, even when the phone screen is turned off. The Android system keeps detailed records of this consumption.

Go to the menu Settings → Battery → Battery consumption. Look at the list of apps sorted by consumption. If you see an application that you haven't used today, but it is in the top 5 for energy consumption, this is a sure sign that it is constantly running in the background. Often such violators are social networks, news aggregators and games.

Pay attention to the category Background activity. In modern versions of Android, the system separately highlights how many percent of the battery was spent exactly when the screen was turned off. If for a particular application this indicator is unreasonably high, it means that it successfully bypasses system restrictions and, most likely, starts when the device starts.

For a more detailed analysis, you can use the ADB command:

adb shell dumpsys batterystats --checkin

This command will download detailed statistics in a form convenient for analysis on a computer. In the report you can find sections describing the time the device wakes up (wakelocks) by specific applications. Frequent awakenings immediately after a reboot indicate active autostart.

⚠️ Attention: Battery statistics are reset when the phone is completely discharged or the statistics are manually reloaded. To get an objective picture, monitor the device for 1-2 days without resetting the data.

Optimization and disabling unnecessary services

After you have identified the list unwanted apps, the question arises of disabling them. The easiest way is to use the button Disable in the application settings. However, for many pre-installed apps (bloatware) this button is inactive. In this case, a deeper approach is required.

If you have root access, you can use managers such as Titanium Backup or System App Remover. They allow you not only to freeze, but also completely remove system applications registered in startup. Freezing is a safer option, as it makes the application invisible to the system, but stores its files on disk in case of recovery.

Without root access, the only option is to use ADB to disable packages for the current user. The command looks like this: adb shell pm disable-user --user 0 package name After executing this command, the application will disappear from the menu and will no longer launch, but will remain in the phone’s memory. This is a reversible procedure: to return the application, you need to enter the command

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

Replace package name to a real name that you recognized earlier (for example, com.facebook.appmanager). After executing this command, the application will disappear from the menu and will no longer launch, but will remain in the phone’s memory. This is a reversible procedure: to return the application, you need to enter the command pm enable package name.

Don't forget to also check the permissions on Overlaying on top of other windows and Access to notifications. Applications often use these rights to maintain their activity in the background, even if direct autorun via BOOT_COMPLETED is blocked by them. A comprehensive approach to disabling rights will give the best result.

What is “freezing” an application?

Freezing is a process in which the system stops seeing an installed application. It does not take up RAM, does not run in the background and is not displayed in the menu, but its installation file remains in the internal memory.

Frequently asked questions (FAQ)

Is it safe to disable system applications via ADB?

You can disable only those applications whose purpose you fully understand. Disabling Google Play services, system interface (SystemUI) or telephony will result in the device not working. Always google the name of the package before disabling it.

Why did the phone perform worse after disabling autorun?

You may have disabled an important system service responsible for synchronization, network operation, or_push_notifications. Some system processes are necessary for other applications to function correctly. Try enabling disabled packages back.

Do you need root access to have full control over autorun?

You do not need Root to view the autorun list. To disable most user applications too. However, for deep cleaning of system garbage and disabling protected pre-installed apps, superuser rights significantly expand the possibilities.

Does autorun affect the speed of turning on the phone?

Yes, directly. The more applications try to start at the same time as the system boots, the longer the processor takes to process task queues. Disabling unnecessary software can reduce boot time by 10-20 seconds.

How to find autorun on older versions of Android (5.0 - 7.0)?

On older versions, background work restrictions were weaker, so autorun was more aggressive. Verification methods via ADB and the application Autostarts work equally effectively on all versions of Android.