Each new version of Android includes new “tricks” that aim to improve performance of Google's operating system when it comes to reducing the battery consumption of the phone or tablet in question. The new Marshmallow version is no exception, and the name of the new feature is Pickups.
This comes to replace and improve the disaster that was Project Volta en Android Lollipop, which hasn't exactly been the version of the Mountain View company's development that performed best in terms of autonomy. Therefore, Doze is important since it has to correct what was happening and, at the same time, provide new options that are effective.
How Doze works
The truth is that Google's idea with Doze is really curious and efficientThis new option “attacks” consumption when the phone is in repose, something that happens quite frequently and takes up most of our time in everyday life - as has been shown in several studies. That is to say, its operation comes into play when, for example, we carry our phone unused and remains still with the screen off (If there is continued movement, the sensors may postpone the deeper mode).
This does not cause the loss of connectivity, either Internet or access to the networks necessary to receive calls, but this is one of the few things that remain active if Doze is working (some processes more occasionally they are executed, but they are not relevant or very numerous). In addition, Google has taken care to offer maximum configuration and control by users, since it is possible set priority apps, which is always positive. Of course, the more you add, the less the battery lasts, as is logical to think.
The fact is that depending on the use given to the phone or tablet, the increase in autonomy that is achieved with Doze in Android Marshmallow can reach up to 35% more time of use. It's not bad at all, really, and on this occasion, as I have been able to check what is indicated is fulfilled -although with slight variations in time, but which are not very important-.
Using Doze
By default in Android 6.0 The functionality is enabled, so nothing needs to be done for it to start working. reduce the consumption of the terminal in question. However, below we indicate what has to be done to manage what we have commented before regarding the applications that you do not want Doze to close when the device goes to sleep. Is the next:
- Access the System Settings and look for the option called Battery which is in the Device section
- Use the icon in the upper right, just the one with three vertical dots. Now select Battery optimization
- In the menu at the top, which has a triangle pointing down on the right, the available options are displayed when you press them, the ones you are interested in appear when you choose All applications
- Click on each one you want to configure and in the pop-up window choose Do not optimize in case you don't want Doze to put it to sleep when the device goes to sleep
Other tutorials for new version of Google's operating system you can meet them in this section of Android Help, which will allow you to configure your device in the best possible way.
What you should know about Doze and App Standby
Doze minimizes the background activity when the screen is off and the device is not charging. It goes into cycles of inactivity and maintenance: For brief periods of time, the system allows syncs, jobs, and snoozed alarms, then returns the system to sleep to save battery life.
Over time, Android added two levels: Light Doze (more permissive, just have the screen off and no charge) and Deep Doze (more restrictive after a stationary period). In both cases, the network and background CPU are severely limited, but the Receiving Calls and critical system functions.
In parallel there is Standby App, which decides whether an app is inactive due to lack of use and postpones its network activity. Android classifies apps into buckets (Active, Working Set, Frequent, Infrequent, Never Run) and adjust how many jobs, alarms, and network accesses each one can do.
Exceptions, notifications and best practices
Apps can ask to be excluded from optimizations from Settings > Battery > Optimization, or through the system intent when its primary function requires it. However, Google Play limits requests exclusion if they are not justified by the central function.
For reliable notifications without draining battery, it is recommended to use Firebase Cloud Messaging (FCM): the messages of high priority can wake up the app briefly even in Doze, and normal priority ones are delivered in the next maintenance window. Avoid keeping persistent connections own if you can rely on FCM.
If you need alarms in Doze, use setAndAllowWhileIdle() o setExactAndAllowWhileIdle() de alarmmanager to ensure its execution within reasonable limits. To check if your app is exempt, use isIgnoringBatteryOptimizations() and adjust your logic to respect the cycles of maintenance.
App Standby Buckets: How It Affects You
Android can move your app between buckets based on usage. In Active there are no restrictions; in Working set light limits apply; in Frequent y Infrequent jobs, alarms and urgent messages are limited; in Never executed The restrictions are maximum. You can view or modify the bucket with development tools and UsageStatsManager to understand the impact.
Advanced Settings (Root): Naptime and Doze Settings Editor
If you are an advanced user, you can set the timers and Doze thresholds with apps like nap time o Doze Settings Editor. They allow you to change downtimes, maintenance windows and sensor sensitivity, and even save profiles with different aggressiveness.
A very aggressive profile can force the immediate entry in Light and Deep Doze by turning off the screen, reducing maintenance windows to zero, blocking alarms and mute the networkThis achieves almost zero nighttime consumption, but it implies not receive notifications push or alarms until the device is unlocked, in addition to freezing synchronizations.
Important: Apps that promise to “upgrade Doze” to older versions they do not reply the system's behavior and often resort to tricks like VPN; they are not recommended by low profit and possible side effects.
How to test and diagnose your setup
To validate your app or understand the impact of Doze, you can force states with ADB. Enter and exit idle with adb shell dumpsys deviceidle force-idle y adb shell dumpsys deviceidle unforce, simulates disconnection with adb shell dumpsys battery unplug and resets with adb shell dumpsys battery reset. This is how you will check critical behaviors of notifications, jobs and alarms.
Analyze consumption with Batterystats and view it in Battery Historian to identify wakelocks, jobs, syncs, and power-draining processes. Use it in both general tests as in specific scenarios (uploads, downloads, localization) and under forced Doze or App Standby states.
Usage tips, battery saving, and recent changes
Mode Battery saving The system hardens limits on all apps and can disable background location; enable it manually or schedule it by percentage or routine. Note that the system resets battery stats after full charges to provide more reliable data.
In recent versions, Android can hibernate unused apps revoking permissions, clearing temporary files, and hiding their notifications. Additionally, some apps must request permission from exact alarms If you need complete accuracy, use inaccurate alarms to consume less.
If you need to skirt optimizations, consider controlled options like wakelocks punctual or keep the screen on in playback or guided navigation scenarios, always with caution and measuring your energy impact.
Doze provides real savings by limiting unnecessary things when you're not touching your phone, and with a well-thought-out configuration—fair exceptions, use of FCM, testing with ADB, and, if necessary, advanced settings—it's possible to combine solid autonomy and reliability in notifications and critical tasks without sacrificing the daily experience.