How to set up startup of applications on Android: 5 proven methods

Autoloading applications on Android is a mechanism that allows apps to start automatically when the device is turned on or after a reboot. For some users this is a convenient feature (for example, for instant messengers or antivirus apps), but for others it is a source of irritation if unnecessary applications slow down the system. In this article, we will look at all the ways to manage startup: from built-in settings to hidden commands for experienced users.

It is important to understand that smartphone manufacturers (Samsung, Xiaomi, Huawei etc.) often modify Android, so the menu layout may differ. We will look at universal methods that work on most devices, and also indicate features for popular brands. If your model was released before Android 10, some functions may be missing - this is due to the policy Google to limit background activity.

Before you start setting up, check which applications have already been added to startup. Often not only system utilities end up there, but also games, social networks or advertising modules. Disabling them can significantly speed up the device startup and save battery power.

1. Standard startup settings in Android

On pure Android (for example, on devices Google Pixel or Nokia) the startup function is hidden from the user. However, manufacturers often add it to branded shells. Here's where to look:

• 📱 Samsung (One UI): Settings → Applications → ⋮ (three dots) → Autorun. Here you can disable unnecessary apps.
• 📱 Xiaomi (MIUI): Settings → Applications → Manage applications → Autorun. In MIUI 14+ the path may differ.
• 📱 Huawei (EMUI): Settings → Applications → Application settings → Autorun. On new versions, permission to change system settings is required.
• 📱 Realme/Oppo (ColorOS): Settings → Applications → Permissions → Autorun.

If your firmware does not have such an item, this does not mean that Autoload is disabled. It may be controlled through ADB or third-party applications. We'll talk about this further.

⚠️ Attention: Disabling autoloading for system applications (for example, com.android.phone) can lead to malfunctions of the phone. Do not change the settings if you are not sure of their purpose.

2. Using ADB to manage startup

If the menu does not have the necessary options, you can use Android Debug Bridge (ADB) a debugging tool that allows you to manage hidden settings. This method is suitable for advanced users.

First enable Developer mode:

1. Go to Settings → About phone → Build number.
2. Click Build number 7 times until a notification appears You have become a developer!.
3. Go back to Settings → System → For developers and activate USB debugging.

Now connect the phone to the PC and run the commands:

adb shell pm list packages -f | grep "BOOT_COMPLETED"

This command will show all applications that have permission to autoload. To disable unnecessary things, use:

adb shell pm revoke PACKAGE_NAME android.permission.RECEIVE_BOOT_COMPLETED

For example, to disable autoloading Facebook:

adb shell pm revoke com.facebook.katana android.permission.RECEIVE_BOOT_COMPLETED

⚠️ Attention: After updating the firmware, permissions may be reset. Also, some applications (for example, WhatsApp or Telegram) may request permission again.

Install drivers for your device on your PC

Download the ADB platform from the official Google website

Enable USB debugging on the phone

Connect the phone to the PC and confirm trust in the computer

-->

3. Third-party applications for managing startup

If you don’t want to tinker with ADB, you can use specialized utilities. They provide a convenient interface for managing autorun, but require root access or accessibility permissions.

For example, in Greenify you can add an application to the hibernation list, and it will not start when the system starts. A MacroDroid allows you to create rules like: If the device has booted → Launch application X.

Please note that Google Play limites the capabilities of applications without root. For example, Autostarts will show a list of startup apps, but not all of them can disable them.

4. Startup via Tasker (for advanced users)

Tasker is a powerful automation tool that allows you to create complex scripts, including managing startup. For example, you can set it to start Spotify only on weekdays or disable autostart Facebook when the battery is low.

Here is a simple example of setting up autostart for the messenger:

1. Open Tasker and create a new profile (+ → Status → System → Loaded).
2. Add a task (+ → Application → Launch application) and select the desired messenger.
3. Save the profile. Now the application will launch every time the device boots.

To disable autoloading for a specific application, you can create a task that will kill the process when the system starts:

Profile: Loaded
Task: Kill the application → Select the target application

Tasker supports conditional logic. For example, you can configure autoloading Google Maps only when connected to a car Bluetoothdevice. To do this, add a condition Status → Bluetooth → in the profile. Connected → [device name].

5. Cleaning startup from viruses and advertising

Sometimes malicious or advertising modules are added to startup. They can disguise themselves as system processes. (for example, com.android.system with extra characters). To detect them:

• 🔍 Check the startup list through ADB or Autostarts. Pay attention to unknown packages.
• 🛡️ Scan device antivirus (Malwarebytes, Dr.Web).
• 📦 Remove suspicious applications or disable their permissions.
• 🔄 If the virus is deeply embedded, you may need reset to factory settings.

Advertising modules are especially common in firmware from little-known brands (for example, Doogee, Ulefone) They can add services like com.ads.service or com.push.moduleto startup. Such processes can be disabled via ADB:

adb shell pm uninstall -k --user 0 PACKAGE_NAME

If deletion is impossible, try freezing the application using Titanium Backup (required root) or App Quarantine.

⚠️ Attention: Some viruses block access to startup settings. In this case, only flashing the device or using Safe Mode (hold the power button → hold Turn off → select Safe Mode).

6. Optimizing startup to save battery

Each application in startup consumes resources: CPU, RAM and battery. To extend the operating time of the device, follow these tips:

• 🔋 Disable autoloading for social networks (Facebook, Instagram, TikTok) - they actively use the Internet in the background.
• 📱 Leave only critical applications in autoloading: instant messengers (WhatsApp, Telegram), antivirus, synchronizers (Google Drive).
• ⚡ Use Greenify or Battery Optimizer to hibernate unnecessary processes.
• 🔄 Check the startup list regularly - after updates, applications may be added there automatically.

On devices with Android 12+ there is a function Adaptive batterythat limits the background activity of rarely used applications. To enable it:

1. Go to Settings → Battery → Adaptive preferences.
2. Activate the option Adaptive battery.
3. In the section Background limitation manually add applications that should not work in background.

On some devices (for example, Samsung Galaxy S22+) the adaptive battery conflicts with auto-loading of instant messengers. If notifications arrive with a delay, add the application to exceptions.

7. Autoloading on custom firmware (LineageOS, Pixel Experience)

If you use custom firmware (for example, LineageOS, Pixel Experience or Resurrection Remix), autoload control can differ. In most cases, you need to:

1. Install Magisk to obtain root access.
2. Use modules like App Systemizer or BootManager.
3. Configure startup via Tasker or ADB (as described above).

For example, in LineageOS you can disable autoloading of system applications via Settings → Applications → ⋮ → Show system → [select application] → DisableHowever, this may lead to unstable operation.

For firmware based on Android 13+ it is recommended to use the module Universal Boot Manager for Magisk. It allows you to flexibly manage autostart without manually editing configuration files.

⚠️ Attention: On custom firmware, disabling critical system processes (for example, com.android.server.telecom) can lead to bootloop (loop reboot). data-i="217">before experiments. TWRP before experiments.

FAQ: Frequently asked questions about autoloading on Android

adb shell pm grant PACKAGE_NAME android.permission.RECEIVE_BOOT_COMPLETED