How to turn off annoying low battery notifications on Android

Every smartphone owner has encountered a situation where the device literally starts “screaming” about the need to charge, even if you are ten meters from the outlet or simply cannot connect the cable right now. These system alerts, although intended for the good purpose of saving your data from a sudden power outage, often become a source of serious irritation. This is especially true for users who use old batteries or specific operating scenarios where constant vibrations and sound signals interfere with work or rest.

Unfortunately, the standard interface Android does not provide a simple checkbox “Disable low battery warning.” Operating system developers consider this function critical for the security of the device and the safety of user data. However, there are a number of workarounds, from simple power saving mode settings to advanced methods using USB debugging. In this article, we will analyze in detail all the available ways to solve this problem, assess their risks and effectiveness.

Before taking radical measures, it is necessary to understand the nature of these notifications. They are generated by a system process BatteryServicethat constantly monitors the voltage at the battery terminals. When the value falls below a certain threshold (usually 15% or 5%), the trigger activates a standard dialog box. You can bypass this mechanism, but this will require either superuser rights or the use of special debugging tools.

Standard settings and power saving mode

The safest and most accessible method, which does not require root access or connecting to a computer, is to manipulate the power saving mode. On many modern shells, such as MIUI, OneUI or ColorOS, the notification logic is closely related to active power profiles. Try going to the section Settings → Battery and forcefully enable the power saving mode.

In some firmware versions, activating this mode changes the threshold value at which the system starts sounding the alarm. Instead of the standard 15%, the notification can appear only at 10% or 5%, which significantly reduces the frequency of annoying signals. However, this method has a downside: it limits the background activity of applications and the refresh rate of the processor.

It is also worth checking the sound and vibration settings. Go to Settings → Sound and vibration → Advanced → System notifications. Here you can try to turn off the sound specifically for system warnings, although the visual window (pop-up) will still appear on the screen. This solution is suitable for those who are concerned about acoustic discomfort, and not the very presence of the icon in the status bar.

It is important to note that manufacturers are constantly changing the location of these menu items. What worked on Android 10may not be available on Android 13. If you do not find the necessary switches, this means that your firmware version strictly regulates the behavior of the battery at the system kernel level.

⚠️ Attention: Disabling the sound will not prevent the smartphone from suddenly turning off. You may lose unsaved data if you miss the visual warning and your phone dies at the wrong time.

Using the menu for developers

A deeper level of control over the system is revealed through the hidden menu for developers. This interface is intended for debugging applications and testing functions, but sometimes contains options that affect the behavior of the system as a whole. To enter this menu, you need to click 7 times on the build number in the section About phone.

After activation, go to System → For developers. Here we are interested in the section related to monitoring or background processes. Although there is no direct “Disable Battery Notification” button, you can try limiting the background activity of system services. Find the item Background process limit and set the value to "No more than 1 process" or "No background processes."

This measure may indirectly affect the operation BatteryServiceby forcing It is less likely to poll the battery status or delay sending a notification. However, the effect is not guaranteed and depends on the specific firmware implementation. On devices Samsung or Google Pixel this method is often useless, since system services have high priority.

Another parameter that is worth checking is the animation settings. Reducing the window animation scale, transition animation, and animator duration to 0.5x or Off may make the notification appear less noticeable, although it will not completely remove it. This is more of a cosmetic measure than a full solution to the problem.

Disablement via ADB (without root access)

The most effective way, which does not require hacking the system, is to use tools Android Debug Bridge (ADB). This method allows you to send commands directly to the system, disabling specific notification components. You will need a computer with ADB drivers installed and a cable to connect your smartphone.

First, enable USB debugging in the developer menu and connect your phone to the PC. Open a command line or terminal on your computer and enter the command to test the connection:

adb devices

If the device appears in the list with a status device, you can start turning off notifications. The command may vary depending on the Android version, but the universal option for hiding notifications from the system UI is as follows:

adb shell pm disable-user --user 0 com.android.systemui

However, stopping completely com.android.systemui will cause the status bar and navigation buttons to disappear, rendering the phone unusable. A more specific command disables only the battery notification channel:

adb shell settings put global low_battery_warning_level 0

This command sets the warning threshold to 0%, which effectively disables it. In some cases, you need to use a command to block a specific notification channel via notification_listener, but this requires more complex manipulations with access rights.

Methods for users with root access

For owners of smartphones with superuser rights (Root) opens up the widest possibilities for modifying the system. Having Root access allows you to edit system configuration files and use specialized modules for managers like Magisk. This is the most reliable way to remove the notification forever.

One ​​of the popular tools is a module Battery Calibration or similar scripts available in repositories. They allow you not only to calibrate the charge controller, but also to change the warning logic. Installation of such a module usually occurs through an application Magisk Manager in a couple of clicks.

A more advanced method involves editing a file build.prop or using applications like Titanium Backup (for older versions of Android) or System App Remover. With their help, you can “freeze” the component responsible for generating the alert. However, be careful: removing a system component can lead to a cyclic reboot (bootloop).

There are also specialized applications from the store Google Play, such as Battery Charge Limit, which, if you have root access, can control the charging process and turn off notifications, redirecting them to a log file or ignoring them completely. These applications create a profile that automatically applies the desired settings every time the system starts.

⚠️ Attention: Any tampering with system files while you have root access will void the device warranty. Incorrect editing can turn a smartphone into a “brick.”

The table below compares the effectiveness of various methods depending on the availability of access rights:

Method	Requirements	Efficiency	Risk of breakdown
Energy settings	No	Low	None
Developer menu	Mode activation	Medium	Minimal
ADB commands	PC, cable, drivers	High	Medium
Root modules	root access, Magisk	Maximum	High

Automation via Tasker and macros

If you don’t want to get into the system jungle, you can try to intercept the notification using automation applications such as Tasker, MacroDroid or Automate. The principle is to create a script that detects the appearance of a low battery notification and immediately closes it or blocks the sound.

In MacroDroid, for example, you can create a macro: Trigger"Battery level < 15%" → Action"Notification: Close last" or "Sound: Mute". This method does not remove the notification itself from the system, but makes its appearance instantaneous and invisible to the user, since the script runs faster than you can see the dialog box.

For such scripts to work, you need to grant the application permission to “Access notifications”. This is a safe method that does not require root access, although on some shells (for example, Xiaomi MIUI), you may need to additionally configure permissions in the "Autostart" and "Battery Saver" sections for the automation application itself.

Why may macros not work?

On new versions of Android (12+) Google has tightened its background application policies. The system can kill the automation process before it has time to process the notification. In this case, you need to add the application to the battery optimization exclusion list.

The advantage of automation is its flexibility. You can configure the scenario so that the notification is turned off only at night or when the phone is in a certain geolocation zone (for example, at home, where a power outlet is always at hand). This allows you to maintain the warning functionality in critical situations when you are on the go.

Possible risks and alternative solutions

Completely disabling discharge warnings carries certain risks. The main danger is that lithium-ion batteries are sensitive to deep discharge. If the phone turns off completely and remains in this state for a long time, it can lead to irreversible degradation of the battery chemistry and a decrease in its capacity in the future.

In addition, a sudden shutdown can damage the file system. Although modern file systems (ext4, f2fs) are quite robust, an improper shutdown while data is being written can result in loss of information or the need for a factory reset.

Instead of a complete shutdown, consider an alternative: replacing the battery. If notifications appear too often (for example, at 40%), this is a sure sign that the battery is worn out and needs to be replaced. The new battery will solve the problem of frequent warnings naturally, without the need for software interventions.

⚠️ Attention: Interfaces and menu names may differ depending on the Android version and smartphone model. Always consult the manufacturer's official documentation before making changes to system settings.

Frequently Asked Questions (FAQ)

Is it possible to turn off notifications only at night?

Yes, this can be done using automation applications such as MacroDroid. Create a profile that is activated by time (for example, from 23:00 to 07:00) and blocks notifications from the system interface or changes the sound mode to “Mute” during this period.

Why were the settings reset after updating Android?

When updating the operating system, user configurations and access rights are often reset. Previously entered ADB commands can be canceled and developer settings returned to default values. You will have to repeat the setup procedure after each major software update.

Is it safe to use the adb shell pm disable command?

Using this command is only safe if you know exactly the name of the package you are disabling. Disabling critical system components (for example com.android.phone) may result in loss of communication or inability to boot the system. Always use the command pm enable to restore if something goes wrong.

Does disabling notifications affect the warranty?

Using standard settings or developer mode does not affect the warranty. However, obtaining root access and unlocking the Bootloader will almost always void the manufacturer's warranty. Using ADB commands usually does not leave traces that the service center may regard as a violation of the warranty terms if no changes have been made to the system partition.