How to save battery on your Android by configuring standby applications

Share it:

With Android 9 Pie, a new energy saving system arrived, the Standby Buckets App. The literal translation of this function is "Application cubes in Standby" (although it has arrived in Spain as "Applications on hold") and, as its name indicates, is responsible for manage the behavior of what applications can do and not in the background.

Today we will explain where is this setting located, how can you modify it and what is the use of changing its modes, since it is a fairly hidden function among the system settings, although it is enough to follow a few simple steps to find it.

Configuring Standby Buckets App or standby applications

This setting is within the developer options. To activate them, you must click seven times on the build number from your phone This, is in the section of phone information. Once these options are activated, in the section on system you can find standby applications.

Standby Applications

Now, touch navigate these options, which are not precisely grim reapers. We must go down the list until we find the subsection of Applications. In it, we will see the option of standby applications. Click here.

There are five standby application modes. The deeper each one of them is, the more restrictions the system imposes on the app, and more battery savings

App Wait

This section of apps on hold is the reference to the Standby Buckets App, so let's remind you what does each of the modes we find here mean. You can also find this information on the Android page itself.

  • Active / Active: This includes applications that are in use or that have been used recently. These applications have no restrictions of any kind.

  • Working Set / Set of tasks: applications that are used regularly. These types of applications have slight restrictions, focusing on the ability to activate alarms, execute tasks, etc.

  • Frequent / Frequent: applications that are used frequently, but not on a daily basis. These applications have stronger limitations, including limiting FCM (Firebase Cloud Messaging) / Notifications messages.

  • Rare / Uncommon: applications that are not used frequently. These applications have even greater limitations than Frequent, among which is the ability of the app to connect to the internet.

Screenshot 20191204 132358 2

In addition to these four "cubes", we find a fifth called 'Never' or 'Never', which includes quite aggressive limits for these applications.

Having seen this, we can appreciate that the system, on paper, is quite efficient, making the applications that we use the most have less restrictions, and those that we use less, are more capable. However, being able to configure this section manually can help us save battery power.

Active Many games, for example, are set to 'Working Set'. By passing them to 'Frequent' or 'Rare' we can save battery. This example is extrapolated to other apps.

For example, we have observed that it is very simple that the games are included in the Working Set or Frequent categories, depending on the use we give it. Proposals such as Call Of Duty Mobile or PUBG Mobile, for example, often send notifications on a constant basis, so sending them to "Rare" is a good option to save battery power.

Keep in mind that if you restrict apps you use daily, you may lose notifications and background features. This method is designed to save battery power with those apps that we don't need to be constantly running.

Similarly, you can perform the process with any other application you want to limit. The more "deep" the cube, the less energy consumption the app will have when it is not used in the foreground. Note that if you restrict applications you use daily, you will lose notifications and background features, so we recommend configuring only those apps whose full functions we do not need throughout the day.

Share it: