Google has released the new version of Android P Beta today on Google I / O, and it does bring a ton of new features and improvements. While the new gesture-based navigation steals the limelight, Google has also added a bunch of improvements under the hood to improve the user experience. With battery life increasingly demanded by users, Google has promised better and more effective battery management with Android P. While each new version introduces something new regarding battery life, such as Doze, This year with Android P, Google has achieved the Stand Stand Cubes app.With the help of App Standby Buckets, you will be able to take more control over the applications running in the background, which will affect the battery life. But before we talk about how to use it, let's take a look at what exactly App Standby Buckets are:
What are Standby Buckets App?
App Standby Buckets is a new energy saving tool introduced with Android P Developer Preview 2. Basically, it classifies applications according to how often they are used and limits their access to device resources accordingly. This is a dynamic process, and the system assigns each application to a priority group and then reassigns the applications as necessary.
According to Google, there are 4 main Standby Buckets App, namely:
An application is said to be in the active group if the user is currently using the application, for example:
- The application has launched an activity.
- The application is running a foreground service.
- The application has a sync adapter associated with a content provider used by a foreground application
- User clicks on an app notification
As such, if an application is in the active group, the system does not impose any restrictions on the application's FCM jobs, alarms, or messages.
An application is said to be in the working set group if it runs frequently but is not currently active. For example, a social media application that the user starts most days is likely to be in the working set. Applications are also promoted to the working set group if used indirectly. If an application is in the job set, the system imposes slight restrictions on its ability to run jobs and trigger alarms.
An app is said to be in the frequent group if used regularly, but not necessarily every day. For example, an exercise tracking app that the user runs in the gym may be in the frequent bucket. If an application is in the frequent pool, the system imposes greater restrictions on its ability to run jobs and trigger alarms, and also imposes a limit on high-priority FCM messages.
An application is said to be in the rare cube if it is not used frequently. For example, a hotel application that the user only runs while staying at that hotel may be in the exceptional location. If an application is in the exceptional group, the system imposes strict restrictions on its ability to run jobs, trigger alarms, and receive high-priority FCM messages. The system also limits the application's ability to connect to the Internet.
Lastly, there is a special package for applications that have been installed but have never been run. The system imposes severe restrictions on these applications.
The problem of application waiting cubes
In theory, App Standby Buckets sound like a great feature. However, it turns out that there is a catch to it. As stated by Google, "Each manufacturer can set their own criteria for how non-active applications are assigned to compartments." Indeed, each manufacturer can manage the applications and distribute or classify the applications in various compartments according to their design idea. Although Google claims that the process is dynamic and that Android will categorize applications according to user use, it is worth noting that Android will resort to this usage pattern system to determine the location of the application only if the device lacks preloaded software that would otherwise determine where. An application may be placed.
However, users can also manually decide the Waiting Cube for each application, as desired. To do so, keep reading, as we show you how to manually configure the reserve cubes for each application:
How to manually use standby applications
Note : I tried the following method on my Google Pixel 2 XL with Android P Developer Preview 2. The method should remain the same for all other devices with Android P Developer Preview 2.
1. First of all, go to Settings -> System -> About phone .
2. Now press Advanced and scroll down. I touched "Build number" seven times to enable developer options.
3. Once you have done that, go to Configuration -> System -> Advanced -> Developer options.
4. Once here, scroll to the bottom. Click on "Applications on hold" .
5. And that's it. Now see a list of all the applications installed on your device. Just tap on any app you want to change the Waiting Cube from . You should get a list to choose from the 4 main Reserve Cubes mentioned above.
Get a better battery life with standby apps on Android P
Well, like Doze, App Standby Buckets claim to promise a better backup battery. Using the guide above, you should be able to get manual control over assigning apps to your preferred app pools, rather than letting your OEM do it. On the other hand, if you are running Android P on a Pixel device, Android will automatically do the profiling for you. While the actual effect on battery life with App Standby Buckets will only show up after a couple of days of use, the function itself appears to be quite good.