Doubling Standby Time by Blocking Background Data for 90% of Apps on Android

Despite doing nothing with the phone overnight, the battery had dropped to nearly half by morning. As reported by Ali Salman Zia of Android Police, an investigation tracing the cause of this abnormal standby battery drain was featured. The report found that blocking background data for 90% of apps roughly doubled standby battery life. This is not just a simple power-saving trick, but an illuminating case for understanding the relationship between Android’s communication controls and power consumption.

Tracing Why Battery Drains by Half on Standby

According to the report, the author’s device was losing significant battery just by sitting on a desk overnight. An investigation into the cause revealed that numerous apps were regularly communicating, syncing, and updating in the background. This included apps installed from outside the Play Store, but overall, background activity had become the norm.

What is distinctive about standby consumption is that it is caused by communication, not the display or processing performance. The amount of data each app sends is tiny, but the cost of waking the radio from its low-power idle state is high. To send even a small packet, the radio must be powered on, a connection established, and then remain on standby for a period after transmission. Repeating this sequence over and over drains the battery.

Google itself is aware of this problem. Android has automatic power-saving mechanisms such as Doze and App Standby that delay the activity of unused apps. However, they do not fully suppress the behavior of all apps. This leaves room for manual controls to be effective.

The Difference Between Background Data and

Battery Restriction

What is often confused is the restriction of background data and the “Restricted” setting in battery settings. The Android Police article clearly distinguishes the two as separate controls.

Background data prevents an app from using mobile data or Wi-Fi when you’re not actively using it.

Restricting background data is a setting that prevents an app from using mobile data or Wi-Fi when it is not in the foreground. The common method is to select the target app from Settings > Apps and toggle it under “Mobile data & Wi-Fi.” The system-wide “Data Saver” has a similar effect, but differs in usability in that it does not allow per-app exceptions.

In contrast, the “Restricted” setting on the battery side is a control that strictly suppresses background execution itself. It curbs not only communication but also job execution and alarm triggers. It is highly effective, but also has greater side effects such as delayed notifications. Restricting communication is positioned as a more limited measure, specifically focused on reducing the number of times the radio is activated.

How to Identify the Culprits Draining the

Battery and Common Trends

In the test, rather than restricting all apps at once, the approach was to deal with the biggest consumers first. First, the author opened Settings > Battery > Battery usage and sorted to check consumption by app.

At the top were social media apps, free apps with many ads, and apps that use location information. Surprisingly, there were also cases where utility apps that are rarely opened appeared near the top. The picture was that apps that should not have been in use were waking up regularly in the background to acquire location or refresh ads.

Access to location information is cited as one of the main factors driving up battery consumption on standby. Acquiring location involves sensors and communication, which consumes a lot of power. Simply stopping unnecessary apps from using location in the background can change how quickly the battery drains on standby. Restricting communication and restricting location are separate controls, but combining them increases effectiveness.

As covered in Fermata Auto: A Practical Review of Video Playback on Android Auto, in the app ecosystem around Android, there is room for background activity beyond what is officially intended to slip in. Apps designed for in-vehicle use or always-on connectivity tend to have higher background communication frequency in common.

How to Block Background Data and Choose Which

Apps to Restrict

While the exact wording varies by device manufacturer and Android version, the basic flow is the same. Select the target app from Settings > Apps and disable “Background data” under “Mobile data & Wi-Fi.” The system-wide Data Saver is often found under “Network & internet.”

The author of the report ultimately disabled this setting for about 90% of apps. He did not aim for 90% from the start; it was the result of judging each app one by one against the criterion of “does this app need to communicate in the background?” The criteria were clear. Apps that require immediacy, such as messaging, email, and calendar sync, were excluded. On the other hand, social, news, shopping, ad-supported free apps, and utilities that function offline are candidates for restriction.

How to handle exceptions is key to the operation. Data Saver is effective across the board, but does not allow fine-grained exceptions. Per-app settings take time and effort, but allow for more granular control — keeping only the necessary apps alive and stopping unnecessary apps from waking the radio.

Where the OS’s Automatic Power Saving Falls Short

Android’s Doze delays network access and jobs in batches when the device remains stationary with the screen off. App Standby treats apps that have not been used for a while as idle and reduces their opportunities to run. Both are foundational technologies for curbing standby consumption.

However, these automatic controls are not perfect. The article points out cases where Google’s own services’ periodic checks become a source of consumption, and cases where third-party apps have their own sync logic. Apps from outside the Play Store in particular may exhibit behavior that falls outside the OS’s optimizations. Implementations where an ad SDK communicates frequently or acquires location information wake the radio between Doze intervals.

Manual restriction of background data fills the gaps in this automatic control. Because it stops the radio itself from being activated on a per-app basis, it can be expected to cut off the fragmented communications that Doze cannot fully delay. The accumulation of tiny data transmissions results in a large difference in power consumption.

Side Effects to Watch For and How to Avoid Them

The cost of blocking communication is a loss of freshness and immediacy of information. Apps with background communication blocked will only sync when brought to the foreground. This can cause delayed notifications, stale timelines, and widgets that do not update.

Therefore, restrictions should not be applied uniformly, but divided by use case. Means of communication, work chats, authentication apps, and smart home controls that require real-time performance should be excluded from restrictions. Conversely, apps that only need to be opened a few times a day or apps whose main purpose is ad refresh will have little impact on usability even if restricted.

When continuing to operate with these settings, it is effective to periodically check the battery usage screen after applying restrictions and weigh the benefits against side effects. If an app stops receiving notifications after being restricted, revert it to an exception. Conversely, keep apps restricted if you have no trouble after restricting them. By repeating this trial and error, you can find the balance between standby battery life and convenience. The result that standby time roughly doubled in the test can be seen as a reflection of how the accumulation of restrictions significantly reduced the number of times the radio was activated.

Editorial Opinion

In the short term, we expect manual restriction of background data on Android devices to be re-evaluated as a standard method for improving standby time. Rather than relying solely on the OS’s automatic power saving, the process of identifying culprits from the battery usage screen and blocking communication on a per-app basis could spread through how-to articles and device manufacturers’ support information within 3 to 6 months. Dealing with free apps that use ad SDKs and location information in particular is an area where effects are easy to feel immediately.

In the long term, we assess that the tug-of-war between app design and platform-side controls will continue. Apps seek frequent syncing to maintain engagement, while the OS strengthens restrictions to preserve battery life. In 1 to 3 years, we expect progress toward greater visualization of background communication and more granular user permissions. From both privacy and power-saving perspectives, the trend of requiring developers to be accountable for explaining background communication is likely to strengthen.

The question from the editorial team is which to prioritize: convenience or autonomy. How much immediacy of notifications are you willing to sacrifice to extend standby time? Blocking 90% is an extreme choice that is not the right solution for every user. The question is, given your own usage, which apps will you allow to communicate in the background?

References

• “I restricted background data for 90% of my apps; it doubled my standby battery”, by Ali Salman Zia — Android Police, 2026-09-06T12:00:10.000Z (ARR)
• Source URL: https://www.androidpolice.com/restrict-background-data-android-apps-battery-life/