How to disable optimization of applications 1 of 1 on Android

Users of devices based on Android often encounter the annoying message “Optimizing application 1 of 1” (or “2 of 1”) every time the system starts. This phenomenon not only slows down the loading of the smartphone, but also indicates deeper problems in the operation of the operating system. This usually happens after an unsuccessful update, a settings reset, or a conflict in file system access rights.

There are several ways to solve this problem: from standard settings in the developer menu to using advanced command line tools via a computer. In this article we will analyze in detail all the methods for eliminating the annoying optimization loop. You will learn how to return fast startup to your gadget and why the system behaves this way.

Optimizing applications is the process of compiling bytecode into native machine code for a specific processor. If this process runs endlessly, it means that the system cannot save the results of its work or believes that the application files are damaged.

Why Android constantly optimizes applications

The main reason for the process looping is a violation of access rights to system partitions. The operating system Android uses a mechanism SELinux to control security. If the rights to folders /data or /system are lost, the system sees “clean” files every time it reboots and starts the optimization procedure again.

This often happens after installing custom firmware or receiving root-rights. Incorrectly configured recovery or an incorrect module Magisk can change the attributes of files so that the system no longer recognizes them as trusted. As a result, instead of just running the application, Android is forced to rebuild it every time.

⚠️ Attention: Constant optimization can lead to rapid wear of the device's flash memory due to a large number of write operations. Do not ignore this problem.

Sometimes the culprit is a specific application that was installed incorrectly or is incompatible with the current OS version. The system tries to optimize it, fails, resets the status and starts again with the next application in the queue, creating the illusion of an endless loop.

Preparing the device to fix the problem

Before taking active steps, you need to make sure that the device is ready to make system changes. The first step should always be to check if there is available space. If the internal memory is full to capacity, the system simply has nowhere to write optimized files (ODex/Vdex).

Clear the application cache and delete unnecessary files. Go to Settings → Memory and make sure that at least 10-15% of the total volume is available. This is critical for stable operation of the file system.

It is also recommended to perform a soft reboot. Sometimes a simple on/off cycle can clear temporary Task Scheduler errors. Hold down the power button and select Reboot, avoiding the "Quick Start" function, if available in your launcher.

If the problem persists after a reboot, move on to deeper settings. It is important to understand that further steps will require interaction with hidden system menus.

Disable via the developer menu

The most accessible way to influence the optimization process is to use the developer menu. This section is hidden by default, but its activation does not require connecting to a computer. Go to Settings → About phone and quickly click 7 times on the item Build number.

After the message “You have become a developer” appears, return to the main settings menu. Find the new section For developers. Here we are interested in settings related to background processes and memory optimization.

• 🔍 Find the "Don't save actions" option and make sure it is turned off.
• 🚀 Disable the "Background" option for all applications if it is active globally.
• 🛠 Check the Background Process Limit settings - set to the default value.

Although directly disabling optimization here is not always represented by an explicit checkmark, resetting these settings often helps the system “understand” that resources are available. Some shells (for example MIUI or ColorOS) may have additional startup controls that are also worth checking.

After changing the settings, be sure to restart the device. If the “1 of 1” message appears again, then the problem lies deeper than the standard interface settings.

Using ADB to force a reset

The most effective method of solving the problem is to use a tool ADB (Android Debug Bridge) from your computer. This method allows you to send a command to the system to force a reset of the package optimization state. You will need a PC, a USB cable and installed device drivers.

Connect your smartphone to the computer in USB debugging mode. Open a command prompt or terminal on your PC in the ADB tools folder. Enter the command to check the connection:

adb devices

If the device is displayed in the list, you can proceed to the main command. It instructs the system to rebuild the Dalvik and ART cache without the need for manual clearing through recovery.

adb shell pm write-settings package_verifier_enable 0

However, a more radical and effective method is a command that forces the package manager to rescan all installed applications and reset their optimization status once so that the system writes the correct data:

adb shell pm clear com.android.packageinstaller

Sometimes you need to run a command to reset the cache compiler:

adb shell cmd package compile -f -m speed-profile all

⚠️ Attention: Executing commands via ADB requires caution. Incorrect input may lead to factory reset or data deletion.

What to do if ADB does not see the device?

Make sure that a window asking for debugging permission appears on the phone screen. Click Allow. Also try a different USB cable or USB 2.0 port instead of 3.0.

After completing the commands, unplug the device and perform a hard reboot. In most cases, this breaks the endless loop.

Comparison of methods for eliminating the failure

Different methods have varying degrees of effectiveness and complexity. It is important for users to choose the option that matches their level of training and the state of the device.

Method	Difficulty	Efficiency	Risk of data loss
Clearing the cache in menu	Low	Low	No
Developer settings	Medium	Medium	No
ADB commands	High	High	Minimum
Factory reset	High	100%	Total loss

As can be seen from the table, use ADB is the golden mean between safety and result. Resetting to factory settings should be used only as a last resort, when nothing else helps.

If you are not confident in your abilities when working with the command line, it is better to limit yourself to software methods within the interface or contact a service center. Improper tampering with system files can lead to bootloop (cyclic reboot).

Radical measures: resetting and flashing

If none of the soft methods helped, the damage to the file system is probably too serious. In this case, the only option is a complete data reset (Wipe Data/Factory Reset). This will delete all applications, photos and contacts, but return the system to a clean state.

To perform a reset via the Recovery menu: turn off the phone, hold down the button combination (usually Volume up + Power), wait for the logo to appear and select Wipe data/factory reset using the volume buttons.

In situations where even a reset does not help (the message appears immediately after the first boot of a clean system), the problem may be hardware or related to the firmware itself. Perhaps the system image was recorded with errors or the device memory has bad sectors.

⚠️ Attention: Before resetting, be sure to back up your important data to the cloud or to your computer. It will be impossible to restore them after formatting. Owners of devices with an unlocked bootloader should consider flashing the stock version using tools like (for Samsung) or (for Pixel and others). This will replace all system partitions with known working ones.

Owners of devices with an unlocked bootloader should consider flashing the stock version Android through tools like Odin (for Samsung) or Fastboot (for Pixel and others). This will replace all system partitions with known working ones.

Preventing problems

To avoid repeating the situation with endless optimization, you should follow certain rules for using your smartphone. Do not install applications from dubious sources that may request excessive access rights to system folders.

Update your operating system regularly. Developers Google and device manufacturers constantly release patches that correct errors in the operating mechanism ART compiler. Ignoring security updates can lead to the accumulation of system errors.

• 📲 Install applications only from the official store Google Play.
• 🧹 Once a month, clear the cache of system applications through the settings.
• 🔋 Follow depending on the state of the battery - voltage surges can damage data in memory.

It is also not recommended to frequently change launchers or themes that are deeply integrated into the system if you are not sure of their compatibility with your version Android.

Is it safe to disable application optimization?

Completely disabling optimization is impossible and unnecessary, since this will slow down all apps. It's about eliminating the failure when the process gets stuck in a loop. Correcting this error is safe and necessary for normal operation.

Why does the message appear after updating Android?

When the system is updated, the compiler version changes. Old optimized files become invalid, and the system is forced to recreate them for all applications at once. This usually happens once.

Can a virus cause constant optimization?

Yes, malware can intentionally change system file attributes or create process conflicts, causing optimization services to constantly restart. Check your device with an antivirus.

How long should normal optimization take?

The normal optimization process after an update or reset takes from 2 to 10 minutes, depending on the number of installed applications and memory speed. If it lasts longer than 15 minutes, it’s a failure.

Does this problem affect the speed of games?

Yes, if the system spends processor resources on background optimization every time it starts, games may experience freezing, stuttering, and rapid battery drain.