Testing doze and standby mode

Question

I switched off the screen display of my Nexus 5 device running Android M and then issued the following commands.

im17-x0:~ r.j$ adb shell dumpsys battery unplug
im17-x0:~ r.j$ adb shell dumpsys deviceidle step
Stepped to: IDLE_PENDING
im17-x0:~ r.a$ adb shell dumpsys deviceidle step
Stepped to: SENSING
im17-x0:~ r.a$ adb shell dumpsys deviceidle step
Stepped to: IDLE

Now ideally my device should go to idle mode. But i started a CountDownTimer before putting it in idle mode and its still running. Also the network access is still there in my phone ( checked using this function)

Why is the device not going in doze mode? Following the options from here for standby mode also has the same effect. Why?

Also in that timer,if i check for isDeviceIdleMode(), it returns true.

Answer 1

I've got a few tips for you here:

Network Access

I'd suggest testing network access by actually attempting a network call and logging it out. There's a documented bug with checking network access programmatically while in idle mode:
https://code.google.com/p/android-developer-preview/issues/detail?id=3164

Checking Idle/Doze Mode

There isn't much documentation out there, but there are some methods which aren't muted by Doze mode. Using CountDownTimer might be one of those. I'd try setting an alarm using setExact(), which has been documented not to work when the app is in idle mode. If you can log something out when that alarm fires, you're definitely not in idle mode.

Let me know how that works for you!

Answer 2

As of now, the behavior looks like this

1. isDeviceIdleMode() will return true.
2. Network availability check in the app always returns true.( Checked using this function)
3. There is no change in the network (no network broadcast fired ) when a device enters and comes out of doze mode. However, there is a broadcast fired(doze broadcast) when the device goes into and comes out of doze mode.
4. However we can’t make a network call in doze mode.( Tried using HttpUrlConnection)

For getNetworkInfo() returning true in doze mode, there is a bug reported in Android (Link)

Answer 3

Here is some useful information on Idle Mode:

deviceidle - Is a new android service, that will always run and listen for the several system events, which can trigger it in/out of the idle mode (also known as a Doze mode):

1.Screen on/off
2.Charging status
3.Significant motion detect

DeviceIdleController - When the device is awake and in-use, the controller is in the ACTIVE state. External events like inactivity time-out, user powering off the screen, motion detection ... will drive the state machine into INACTIVE. This state machine contains seven states:

1.ACTIVE - Device is in use, or connected to a charge source.
2.INACTIVE - Device has recently come out of the active state, meaning that user turned off the display or unplugged it.
3.IDLE_PENDING - Hold on, we are about to enter idle mode.
4.SENSING
5.LOCATING
6.IDLE - Device is idle.
7.IDLE_MAINTENANCE - Window is open for applications to do processing. Then will back to IDLE.

Idle State - In order to put the device into an Idle state you can use the following adb commands:

>adb shell dumpsys battery unplug
>adb shell dumpsys deviceidle force-idle

Active State - In order to put the device back into the Active state you may simulate the following key event:

> adb shell input keyevent KEYCODE_WAKEUP

I also needed a quick option to toggle between Active and Idle states so I wrote a batch script adbIdleModeSwitch.bat for these purposes, you may download and use it: https://drive.google.com/file/d/0B81qFnPX_eUUYTMxOTd1UG94NVk/view