La The battery remains the biggest headache For many Android users. In Spain, and in practically any country, one of the most common reasons for retiring a mobile phone isn't that it lacks power, but that the battery life can no longer keep up with daily use. We use our phones to pay, to carry boarding passes, to authenticate ourselves on services… and when the percentage drops into the red, the cold sweats begin.
It doesn't make much sense to buy one powerful mobile and then become obsessed with not using it. That's why it's key. Learn how to control what Android does when we're not looking at the screenThis includes understanding which apps remain active, which services stay running, and how the system manages background battery usage. A solid grasp of this concept, along with modern Android restrictions and available settings, allows you to extend battery life by many hours without significantly compromising the user experience.
What does “background battery usage” really mean?
When we talk about background battery usage, we are referring to everything that apps do when you're not visibly using themThat is, when the screen is off or you have another app in the foreground, but the system still allows certain processes to run in the background.
Many apps of social networks, games, messaging and utilities They maintain data connections, synchronize information, schedule tasks, or receive notifications even when the phone is locked. Some truly need this (for example, the service that links your smartwatch or the email app), but others perform continuous activity without providing a proportional benefit.
This seemingly innocent behavior causes the battery to drain little by little: a constant trickle of energy consumption You don't see it, but it makes a difference at the end of the day. Android groups it in the menus as "background usage" or "background activity," and that's precisely where we can intervene.
Since Android 7.0 and, especially, from Android 8 and 9 onwards, Google has been imposing increasingly strict restrictions on background processes to protect both battery life and device performance. This explains why many older apps have had to adapt using APIs like JobScheduler or WorkManager instead of relying on long-running services or implicit streams.
In practice, all this means that the system decides quite intelligently which apps can continue working in the background and which cannot, but the user still has the final say through battery usage settings.
How to see and control which apps are using battery in the background
The first step to bringing order and reduce battery consumption It's about identifying which apps are draining the battery, both when actively running and in the background. Android offers a fairly comprehensive panel in the system settings.
On most mobile devices the path is similar: enter Settings > Battery > Battery usageThere you'll see a list of apps ordered by usage. Think of it as a ranking of those that have used the most energy in the analyzed period (usually the last 24 hours, although some manufacturers let you change the interval).
When you tap on an app, Android will show how much battery it has used. in the foreground (when you had it open) And how much in the background. If you see an app that you hardly use, but it has a significant amount of data usage in the background, it's a clear candidate for having your freedoms restricted.
Within each application's information sheet, you should find a section called something like this: “Background battery usage”, “Background activity” or “Battery optimization”The exact names and menus change depending on the interface (Samsung, Xiaomi, Pixel, etc.), but the options are usually divided into three main groups:
- No restrictions: The app can run background tasks with almost no limits. It will consume more battery, but it will always function at its best.
- Optimized (default option): Android uses smart algorithms to allow or cut off background activity based on how you use that app.
- Restricted: The system prevents the app from running in the background. It will only be able to do things when you open it or in very specific scenarios.
If you mark an app as restricted, It stops being able to launch jobs, background services, or alarms when you're not using it. In Android 9 and later, this means, for example, that it can't start foreground services, its alarms won't go off, and its JobScheduler jobs won't run while it remains in that state.
Note an interesting nuance: if an application is marked as “Restricted” but you open it manually, Android temporarily treats it as if it were in "Optimized" modeAs soon as you switch to another app or lock your phone, it reverts to restricted mode. This prevents it from completely breaking down when you actually want to use it.
Automatic restrictions when an app misbehaves
In addition to what you manually adjust, Android has a surveillance system called Android vitals and other internal mechanisms that detect apps that abuse battery or resource usage. When the system detects something unusual, it can suggest that the user limit that app.
For example, if an app maintains a partial wakelock (activation lock) for too long with the screen off, or if it runs background services excessively (especially in older apps targeting APIs below 26), Android considers that it is overstepping the mark.
In those cases, the system usually displays a notification of the type “This app is using too much battery”with a button to restrict it. If the user accepts, the mobile phone puts the app in a "restricted" state for background battery usage.
When an app is in that restrictive state on Android 9 or higher, the limitations are significant: You cannot start new foreground servicesThose that were already active may lose foreground status, their JobScheduler jobs will not run, and their alarms will stop going off.
In more recent versions, such as Android 13, it goes even further: if the app is restricted, It does not receive critical transmissions such as BOOT_COMPLETED or LOCKED_BOOT_COMPLETED until the user opens it for some other reason. This prevents it from restarting on its own after a reboot and draining the battery again without permission.
Manufacturers can add their own layer of restrictions (some are very aggressive), so the exact behavior changes from model to model, but the common philosophy is the same: If an app is a battery vampire, Android encourages you to muzzle it..
What has Android technically changed to save battery in the background?
From a developer's perspective, Android has been phasing out many older techniques that caused a lot of background processes. All of this directly impacts... Today the battery lasts longer without the user having to perform any acrobatics..
In Android 7.0 (API 24), Google restricted, for example, implicit transmission CONNECTIVITY_ACTION registered in the manifest. Previously, every network change (WiFi, data, etc.) could wake up half a dozen apps that wanted to know, starting processes even if they barely did anything afterward. That behavior was lethal for the battery.
Since that version, apps targeting API 24 or higher no longer receive that transmission if they declared it in the manifest, and their processes do not start for that reason. The official solution is to use JobScheduler or WorkManagerwhich allow scheduling network tasks when certain conditions are met, for example "only on WiFi" (NETWORK_TYPE_UNMETERED) and "while the device is charging".
JobScheduler is object-based JobInfowhere the developer specifies the job requirements: network type, whether it requires load, whether it should wait until a specific date, etc. When these conditions are met, the system executes the code in a JobService, grouping tasks from many apps to reduce the number of times the CPU wakes up.
WorkManager is a more modern and flexible layer: It ensures the completion of background tasks even if the app process dies.It internally decides whether to use JobScheduler, AlarmManager, or third-party solutions depending on the Android version, and offers advanced features such as job chaining or checking the status of each task.
Another major change in Android 7.0 was the removal of streaming. ACTION_NEW_PICTURE and ACTION_NEW_VIDEO to notify that a new photo or video had been created. These broadcasts could wake up many apps at once, with the resulting impact on performance and battery life. In return, the system extended JobInfo and JobParameters with methods to trigger jobs when specific content URIs were modified.
This is how classes like JobInfo.TriggerContentUri and methods like addTriggerContentUri(), which allow apps to react in a delayed and controlled manner when something changes in a content database (for example, the gallery). The system monitors these URIs through a ContentObserver and triggers the job only when truly necessary.
In addition, JobParameters incorporates methods for asking which URIs or content authorities have triggered a job (getTriggeredContentUris() and getTriggeredContentAuthorities()), so that the app can act in a granular way without having to redo its entire database.
How to monitor and adjust consumption from the user's point of view
All this technical stuff is fine and dandy, but as a user, what you're interested in is something much more direct: Check the battery statistics from time to time and react in timeAndroid offers several panels and options that are worth reviewing from time to time.
In the system battery section you will see a graph of usage over time, along with a list of apps and their relative power consumption. Look at the ones that appear too high up Even if you don't use them that much. If they have a high percentage of background usage, it's a clear warning sign.
Some manufacturers allow you to change the view to see consumption over the last 24 or 48 hours, or since the last full charge. This is useful for detecting continuous drainage patternsFor example, an app that uses up a good chunk of energy every night without you doing anything.
When you detect a habitual suspect, check their permissions and internal settings. Often, that's all it takes. Disable automatic syncing, real-time location scanning, or unnecessary notifications so that the impact on the battery drops sharply without losing important functionalities.
Additionally, there are third-party apps like GSam Battery Monitor or similar that act as a "magnifying glass" for battery consumption, for example AccuBattery or Battery GuruHowever, nowadays, with Android's native tools, most users have more than enough to manage battery life without installing anything extra.
Key configurations to reduce spending without sacrificing too much
In addition to fine-tuning control over each app, there are a number of system options that, when adjusted judiciously, allow Significantly improve battery life without compromising the phone's comfort.It's not about living in permanent airplane mode, but about avoiding waste.
The screen is usually the component that consumes the most power. Reduce the brightness manually and, if possible, disable automatic brightness in stable environments This can lead to significant savings. On OLED panels, using the dark mode You can further reduce energy consumption in apps and the system interface, especially if you spend many hours reading.
Connectivity also plays a significant role. In areas with poor coverage, the mobile phone increases its antenna power and It uses a lot of battery trying to maintain the signal.Whenever possible, relying on a stable Wi-Fi connection helps to limit battery life. And if you don't need mobile data for an extended period (for example, while you sleep), turning it off can extend battery life by several hours.
Regarding GPS, WiFi and Bluetooth, the golden rule is simple: Don't leave them on "just because"Android manages these modules quite well nowadays, but continuing to scan for nearby networks or devices when you're not going to use them adds little usefulness and does represent a constant drain on energy.
Another ally is the Battery saving modeThis feature is available in Settings > Battery. When enabled, the system reduces background activity, limits some processes, lowers maximum processor performance, and restricts certain syncs. It's perfect for times when you know you won't be able to charge for many hours.
What doesn't make sense is installing "miracle apps" that promise to double battery life or aggressively close processes. Most They don't contribute anything real and, sometimes, even worsen consumption by fighting with the operating system's own optimizations. The key lies in real adjustments, not magic tricks.
WiFi, Bluetooth and background location management
Something that often goes unnoticed is that, even when you disable Wi-Fi or Bluetooth from the quick settings panel, many phones keep certain internal functions active. search for networks and devices to improve localization accuracy.
This helps your phone better understand your location by using databases of nearby networks, but it means the antenna continues to perform periodic scans. If you want to minimize this usage, you can go to Settings > Location > Location Services (or Location Settings) and disable options such as “Search for Wi-Fi networks” and “Search for Bluetooth devices”.
In some models, there is also an option called something like “Automatic WiFi activation” Within Settings > Network & Internet > Internet > Network Preferences, you can find an option that reactivates Wi-Fi when it detects known networks in frequently visited areas. Convenient, yes, but it also adds a small amount of data usage.
By disabling these types of searches, the phone stops periodically scanning its surroundings, which It reduces both battery usage and the amount of geolocation data that is sent.The price to pay is that positioning may be slightly less accurate or slower in certain apps, although for most users it's not a big deal.
Automatic updates and other processes that "sneak" behind the scenes
Another classic example of background consumption is... automatic app updatesGoogle Play Store, by default, usually updates apps as soon as it can, sometimes even using mobile data, which in addition to draining battery, also eats up your data allowance.
To adjust this behavior, open the Google Play Store, tap your profile icon (top right), and go to Settings > Network Preferences > Automatically Update AppsThe most sensible option for most people is to choose "Wi-Fi only", or even "Don't automatically update apps" if you prefer to do it manually from time to time.
By reducing the frequency and context of these updates, you achieve that There will be fewer installation, verification, and download processes running in the background.This is especially noticeable in more modest mobile phones.
In addition, it's worth checking which apps have permission to perform constant synchronizations (email, social media, cloud storage, etc.). It's not the same for an app to check something every minute as it is to check it every hour. Adjust those intervals with a little common sense can score several percentage points by the end of the day.
It's also important to understand that closing apps indiscriminately from the recent apps view isn't a solution. Android is designed to automatically manage memory and processesAnd when you force the closure of an app that the system wanted to keep cached, you often end up relaunching it from scratch shortly afterwards, wasting more energy than necessary.
On mobile devices intended for testing or in the development environment, there is even the possibility of simulating extreme background constraints using ADB commands such as RUN_IN_BACKGROUND ignore/allow The `RUN_ANY_IN_BACKGROUND deny` command lets you see how an app behaves when it's prevented from running in the background. For the average user, these commands are useless, but they're there to help future apps be more battery-friendly.
With all these adjustments and the restrictions that Android already applies by default, The best way to take care of the battery is still to rely on the operating system's own toolsCheck the statistics from time to time, and don't be swayed by magic solutions. With a little care, even phones that aren't known for their battery life, like some Pixel models, can easily last through the workday; and those with good battery life can practically last a day and a half without worrying too much about needing to plug them in.
