One of the biggest challenges for any mobile operating system is managing battery life. A device that is constantly active in the background will drain its battery in a matter of hours, even if the user isn’t actively using it. To combat this, Google introduced a powerful and intelligent set of power-saving features starting in Android 6.0 Marshmallow, with the most prominent being Doze mode. Doze is a system state that dramatically reduces battery consumption by deferring background CPU and network activity for apps when the device is unused for long periods.
The Problem: Unchecked Background Activity and Wakelocks
In early versions of Android, applications had significant freedom to run in the background. An app could use a `Service` to perform long-running tasks or acquire a `PowerManager.WakeLock` to keep the CPU awake, even when the screen was off. While necessary for some applications (like music players), this system was frequently abused by poorly coded or aggressive apps. A single app holding a wakelock could prevent the device’s CPU from entering a low-power sleep state, leading to catastrophic battery drain—a phenomenon known as a “wakelock drain.”
Users had little control over this behavior, and it was often difficult to identify which app was responsible for the battery drain. Android needed a smarter, system-wide approach to managing background activity, taking control away from individual apps and giving it to the OS.
Introducing Doze Mode: Enforced Idleness
Doze mode is an intelligent system that detects when a device is idle and puts it into a state of deep sleep. Instead of allowing apps to access the network and CPU whenever they please, Doze restricts them and forces them to batch their work into specific, periodic “maintenance windows.” This allows the device’s main processor to remain in a low-power sleep state for the vast majority of the time the device is idle, leading to a massive improvement in standby battery life.
Doze is not a single on/off switch but a series of progressively deeper states of sleep that the device enters as it remains idle for longer periods.
How Doze Mode Works Internally: States and Triggers
The system uses a combination of sensors, primarily the significant motion detector, to determine if the device is idle.
The Triggers for Doze:
- The device must be running on battery power (not charging).
- The screen must be off.
- The device must be stationary for a certain period of time.
The Progression into Deep Idle (Full Doze):
When all the triggers are met, the device begins its journey into Doze mode.
- Initial Idle Period: After the device has been stationary with the screen off for a period of time (e.g., 30 minutes), the system enters the first level of Doze.
- Maintenance Windows: The system will periodically exit Doze for a brief “maintenance window.” During this window, apps are allowed to perform their deferred background work (run syncs, access the network, etc.).
- Increasingly Long Sleep Cycles: As the device remains idle for longer, the time between these maintenance windows increases exponentially. It might start at one hour, then two, then four, and so on, up to a maximum of several hours. This ensures that the longer the device is untouched, the less frequently it wakes up.
This state, where the device is completely stationary, is often referred to as deep idle or full Doze.
You can inspect the state of Doze mode on your device using an ADB command:
$ adb shell dumpsys deviceidle ... mState=IDLE mLightState=IDLE ... Restrictions Imposed by Doze Mode:
When the system is in Doze, a strict set of restrictions are applied to applications:
- Network access is suspended.
- System ignores `WakeLock`s.
- Standard `AlarmManager` alarms are deferred to the next maintenance window.
- The system does not perform Wi-Fi scans.
- Syncs and jobs from `SyncAdapter` and `JobScheduler` are not run.
Doze-on-the-Go (Light Doze)
Starting in Android 7.0 Nougat, Google introduced a lighter, more mobile-friendly version of Doze. This state, often called “Doze-on-the-go,” can activate even when the device is moving (e.g., in your pocket). It applies a subset of the full Doze restrictions, primarily suspending network access and deferring jobs, but it exits for maintenance windows more frequently. This provides a good balance between power saving and keeping apps reasonably fresh while you are on the move.
| Feature | Doze-on-the-Go (Light Idle) | Doze (Deep Idle) |
|---|---|---|
| Trigger | Screen off, on battery (device can be moving). | Screen off, on battery, and stationary for a period of time. |
| Restrictions | Network access disabled, jobs/syncs deferred. | All light idle restrictions, PLUS `WakeLock`s ignored, alarms deferred, no GPS/Wi-Fi scans. |
| Maintenance Windows | Occur relatively frequently (minutes). | Become progressively less frequent (hours). |
Doze vs. App Standby
Doze is often confused with another power-saving feature called App Standby, which was introduced in the same Android version. They work together but target different scenarios.
- Doze is time-based and system-wide. It applies to *all* apps when the device itself is idle.
- App Standby is app-specific and usage-based. The system determines that a user has not actively used a particular app for a few days (e.g., not opened it, no notifications clicked). It then puts that specific app into a “standby” state, deferring its network access and background syncs until the device is charging or the user launches the app again.
Essentially, Doze saves battery when your phone is on the table, while App Standby saves battery by restricting apps you rarely use. These features are key parts of the Android OS, which interacts with other core components like Google Play Services to manage things like high-priority notifications.
For more technical details, the Android Developer Documentation on power-saving modes is the best resource.
Frequently Asked Questions
Why are my notifications sometimes delayed?
This is a direct and intended consequence of Doze mode. If a notification is not classified as “high-priority,” the app will not be allowed to wake the device to deliver it immediately. Instead, the notification will be deferred until the next maintenance window. App developers can use Firebase Cloud Messaging (FCM) to send high-priority notifications (like an incoming call or a critical message alert) that are allowed to wake the device from Doze. If you are experiencing delays for an app where you need instant notifications, the developer may not have implemented their notification system correctly.
Can I disable Doze mode or whitelist an app?
You cannot disable Doze mode entirely, as it is a core system feature. However, you can exempt specific applications from being affected by Doze. You can do this by going to Settings > Apps > [Select your app] > Battery > Unrestricted (or a similar “Battery optimization” setting). This will allow the app to run background tasks and access the network freely, but be aware that whitelisting apps, especially poorly coded ones, can lead to significant battery drain and defeats the purpose of the feature.
Does Doze mode affect my alarms?
It affects standard `AlarmManager` alarms, which are used by apps to schedule tasks. These will be deferred. However, it does *not* affect alarms set in the main Clock app. The Clock app uses a special type of alarm (`AlarmManager.setAlarmClock()`) that is specifically whitelisted by the system to always go off at the designated time, ensuring you don’t miss your morning alarm.