Android app standby buckets, explained
Last reviewed: September 19, 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 documentation describes the mechanism as prioritising "apps' requests for resources based on how recently and how frequently the apps are used", and says that "based on app usage patterns, each app is placed in one of five priority buckets".
- 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 documentation 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 stated as a number — "You can run jobs once per day in a 10-minute batched session."
Read that the other way round and it is a useful piece of practical advice: an app that is supposed to do something regularly in the background will do it more reliably if you open it now and then. Not because opening it triggers the work, but because usage is the signal Android grades it on.
Why this is not a bug in the app
Bucketing sits alongside Doze and App Standby, which defer background CPU and network activity when a device is unused or an app has not been touched. Between them they make "it will run every fifteen minutes" a request rather than a promise — 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 simply the shortest interval WorkManager accepts, not a claim about when a run happens. A health indicator on the home screen 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.
Sources: App Standby Buckets and Optimize for Doze and App Standby, both read on 16 September 2026. What the app does comes from its own code audit.