As described in Power management, the system can impose power restrictions on apps for a number of reasons. The following table outlines the current restrictions. These restrictions do not apply while the device is charging.
In each case, the most restrictive applicable setting is the one that takes effect. For example, if Battery Saver is active and an app is in the Rare bucket, the more stringent App Standby Buckets restrictions on FCM are applied.
Note: The values in this table are subject to change. These values are given as examples, and improvements to the balance between battery life and timeliness of content updates may cause them to change.
|Setting||Jobs *||Alarms †||Network ‡||Firebase Cloud Messaging §|
|User Restricts Background Activity|
|Restrictions enabled:||Never||Never||Never||No restriction|
|Doze active:||Deferred to window||Regular alarms: Deferred to window
While-idle alarms: Deferred up to 9 minutes
|Deferred to window||High priority: No restriction
Normal priority: Deferred to window
|App Standby Buckets
|Active:||No restriction||No restriction||No restriction||No restriction|
|Working set:||Deferred up to 2 hours||Deferred up to 6 minutes||No restriction||No restriction|
|Frequent:||Deferred up to 8 hours||Deferred up to 30 minutes||No restriction||High priority: 10/day|
|Rare:||Deferred up to 24 hours||Deferred up to 2 hours||Deferred up to 24 hours||High priority: 5/day|
* If jobs restrictions are in force, the app is granted a window of ten minutes at the specified interval. At the end of the ten minutes, all jobs are postponed until the next window.
† If alarm restrictions are in force, all alarms will fire at the scheduled window, and run for a maximum of 10 seconds.
‡ If network access is restricted, the app is granted a window of 10 minutes to use the network at the specified interval.
§ If high-priority FCM messages are capped, any messages after the cap is reached are treated as normal-priority messages.