Understanding Android’s App Standby Buckets

What Are App Standby Buckets?

Since Android 9 (Pie), Google introduced App Standby Buckets as part of its broader effort to manage background activity and preserve battery life. A bucket is essentially a classification that tells the system how frequently an app is expected to run in the background. The OS uses this information to allocate resources such as CPU time, network access, and wake‑locks.

There are five buckets, each representing a different level of expected usage:

• ACTIVE – The app is in the foreground or has recent user interaction.
• WORKING_SET – The app is used regularly (e.g., messaging or navigation apps).
• RECENTLY_USED – The app was used within the last few days but not frequently.
• RARELY_USED – The app hasn’t been used for weeks.
• RESTRICTED – The app is idle for a long period and receives the strictest limits.

These buckets are not static; Android continuously re‑evaluates them based on your interaction patterns.

Why Do Buckets Matter?

Understanding buckets is useful for two main reasons:

1. Battery life: Apps in lower‑priority buckets receive fewer background CPU cycles and network access, which reduces power drain.
2. App performance: If an app you rely on is placed in RARELY_USED or RESTRICTED, you may notice delayed notifications or slower background sync.

While Android does a good job of automating this process, power users often want to verify that critical apps are not being throttled unintentionally.

How Android Determines a Bucket

The system looks at several signals:

• Frequency of app launches.
• Time spent in the foreground.
• Whether the app has a foreground service (e.g., music playback).
• User‑initiated actions such as replying to a notification.
• Battery optimization settings (e.g., apps exempted from Doze).

Developers can also request a higher bucket using the setAppStandbyBucket() API, but the OS may ignore the request if it conflicts with overall power‑saving goals.

Checking an App’s Current Bucket

There are three primary ways to see which bucket an app currently resides in:

1. Using Developer Options

1. Open Settings → About phone and tap Build number seven times to enable Developer Options if you haven’t already.
2. Go back to Settings → System → Advanced → Developer options.
3. Scroll to the Apps section and enable Show app standby buckets.
4. Return to the main Settings screen and open Apps & notifications → See all apps. Each app entry now displays its bucket next to the app name.

2. Using ADB (Android Debug Bridge)

If you prefer a command‑line approach, ADB provides precise information:

adb shell dumpsys deviceidle | grep -i "bucket"

This command lists all packages with their current bucket. To filter for a single app, replace grep with the package name, e.g.:

adb shell dumpsys deviceidle | grep com.whatsapp

3. Using Third‑Party Utilities

Several free apps on the Play Store (e.g., App Standby Buckets or Battery Historian) can read the same system data without requiring ADB. They are convenient for users who do not want to enable Developer Options.

Practical Ways to Influence Buckets

While you cannot directly assign a bucket, you can nudge Android toward a higher‑priority classification through the following methods:

1. Frequent Interaction

Open the app regularly, especially after a device reboot. Even brief foreground sessions (10‑15 seconds) signal to the OS that the app is actively used.

2. Pin the App to the Home Screen

Apps placed on the home screen are more likely to be considered part of the WORKING_SET bucket because the launcher treats them as “favorite” shortcuts.

3. Disable Battery Optimizations for Critical Apps

Navigate to Settings → Battery → Battery optimization, tap the three‑dot menu, select All apps, find the app, and choose Don’t optimize. This exemption tells Android that the app should retain more background privileges, often moving it to a higher bucket.

4. Use Foreground Services When Appropriate

Developers can start a foreground service (e.g., a persistent notification) to keep the app in the ACTIVE bucket. As a user, you can trigger this by starting a music player, navigation, or a fitness tracker that runs in the background.

5. Restrict Apps You Don’t Need

Conversely, if an app is consuming resources unnecessarily, you can force it into a lower bucket by enabling battery optimization or using Force stop from the app info screen.

Step‑by‑Step: Optimizing a Messaging App

Messaging apps are a common case where delayed notifications are frustrating. Follow these steps to ensure your favorite messenger stays in a higher bucket.

1. Check the current bucket using Developer Options or ADB.
2. If the app is in RARELY_USED or RESTRICTED, open the app, send a test message, and keep it in the foreground for at least 30 seconds.
3. Navigate to Settings → Battery → Battery optimization, select All apps, find the messenger, and choose Don’t optimize.
4. Pin the app’s shortcut to your home screen for quick access.
5. Optionally, enable “High‑priority notifications” in the app’s own settings; this signals Android that the app’s notifications are important.
6. After a few hours, re‑check the bucket. It should have moved to WORKING_SET or ACTIVE.

Risks and Compatibility Considerations

While influencing buckets can improve responsiveness, there are trade‑offs:

• Battery impact: Exempting many apps from battery optimization can negate the power‑saving benefits of Android’s Doze mode.
• System stability: Forcing an app to stay in the foreground (e.g., via a persistent notification) may cause the system to kill other background processes if memory is low.
• Manufacturer customizations: Some OEM skins (e.g., Samsung One UI, Xiaomi MIUI) add their own battery‑saving layers that may override or ignore bucket settings. In those cases, you might need to adjust the manufacturer‑specific “App power management” menus.
• Future Android versions: Google may adjust the bucket algorithm or add new categories. The steps described here are valid for Android 9 through Android 13, which cover the majority of devices in use today.

When to Reset All Buckets

If you notice widespread performance issues after installing several apps, a full reset can give the system a clean slate. Here’s how:

1. Open Settings → System → Reset options → Reset app preferences. This does not delete app data but clears all custom defaults, disabled apps, and background restrictions.
2. Reboot the device.
3. After reboot, Android will recompute buckets based on fresh usage data.

Remember that resetting preferences may also re‑enable battery optimizations you previously disabled, so you may need to re‑apply exemptions for critical apps.

Summary

App Standby Buckets are a behind‑the‑scenes mechanism that helps Android balance performance and battery life. By checking which bucket an app occupies and using a combination of frequent interaction, home‑screen shortcuts, and battery‑optimization exemptions, you can guide Android to treat important apps more favorably. Keep an eye on OEM‑specific power‑saving settings, and avoid over‑exempting apps to preserve overall battery health.

With the steps outlined in this guide, you now have a practical toolbox for monitoring and influencing Android’s app‑standby behavior—ensuring that the apps you rely on stay responsive when you need them most.