Doze is among the more interesting options that come with Android M, as well as potentially huge for that platform. Google has stated over and over the latest version of Android would improve battery existence, however they may have really tried it this time around. Doze puts apps into deep sleep once the device is not being used in order to save power, and Google’s developer docs explain just how this works.

Doze is placed to activate whenever a system is unplugged, stationary, and also the screen is off. During Doze, the telephone or tablet will periodically awaken to sync data, but otherwise the majority of things remain asleep. This is what happens in the system level with Doze.

Network access is disabled, unless of course your application gets to be a high priority Google Cloud Messaging tickle.

Wake tresses are overlooked.

Alarms scheduled using the AlarmManager class are disabled, aside from alarms that you have set with thesetAlarmClock() method and AlarmManager.setAndAllowWhileIdle().

Wireless scans aren’t performed.

Syncs and jobs for the sync adapters and JobScheduler aren’t allowed to operate.

Developers can designate some push messages as high-priority, which enables the unit to awaken for any brief time. Which should eliminate many of the wakelocks brought on by rogue apps without anyone’s knowledge. Apps also should not have the ability to trigger device wake-ups (alarms) without getting a very good reason.

Low-priority jobs might be queued when ever the unit wakes support, but developers are cautioned to check their apps and make certain they are able to recover gracefully from finding yourself in hibernation. We are still in the past, so there can be some unforeseen effects of Doze. We’ll need to observe how developers cope.