Android app standby buckets, explained

Last reviewed: September 23, 2026 · Markdown version

Android sorts your apps into five priority buckets — active, working set, frequent, rare and restricted — based on how recently and how frequently you use each one. The bucket decides how freely that app may ask for resources: an app you open daily gets to work often, and one you never open barely at all.

The five buckets

Android's developer documentation says the buckets "help the system prioritize apps' requests for resources based on how recently and how frequently the apps are used", and that "Based on app usage patterns, each app is placed in one of five priority buckets" (App Standby Buckets, read 23 September 2026).

Active — "app is being used or was used very recently."
Working set — "app is in regular use."
Frequent — "app is often used but not daily."
Rare — "app isn't frequently used."
Restricted — "app consumes a lot of system resources or might exhibit undesirable behavior."

What the lower buckets cost an app

The same page is specific about the bottom two. For rare: "If an app is in the rare bucket, the system imposes strict restrictions on its ability to run jobs and trigger alarms. The system also limits the app's ability to connect to the internet." For restricted, the ceiling is a number — "You can run jobs once per day in a 10-minute batched session."

It also says how an app ends up restricted. On Android 13 and higher, unless the app qualifies for an exemption, one trigger is that "The user doesn't interact with your app for a specific number of days" — 45 on Android 12 and 12L, and "Android 13 reduces the number of days to 8." So an app that is meant to work in the background on its own does better if you open it now and then — not because opening it triggers the work, but because interaction is part of what Android grades it on.

Why this is not a bug in the app

Bucketing sits alongside two older power-saving features. In Android's words, "Doze reduces battery consumption by deferring background CPU and network activity for apps when the device is unused for long periods of time", and "App Standby defers background network activity for apps with no recent user activity" (Optimize for Doze and App Standby, read 23 September 2026). Even the scheduler apps use does not promise a time: WorkManager's guide says the repeat interval is "the minimum time between repetitions", and that "The exact time that the worker is going to be executed depends on the constraints that you are using in your WorkRequest object and on the optimizations performed by the system" (Define work requests, read 23 September 2026). That holds for every app on the phone, not just the one you are annoyed with. The deferral mechanisms in full.

Where Adinand Auto File Sorter fits

This is exactly the ground its Pro background sorting stands on, so the app is built to admit it. It schedules with Android's WorkManager and takes no wake lock and no battery-optimisation exemption. You pick an interval — every 15 minutes, every hour, every 6 hours or once a day — and 15 minutes is there because it is the shortest interval WorkManager accepts ("The minimum repeat interval that can be defined is 15 minutes", per the same guide), not because a run is promised at that moment. A health indicator reports when the system has not let the job run, so a quiet phone is visible rather than mysterious, and every background run is listed in Sort History and can be undone.

What the app does comes from its own code audit.