Android: Sleep stages/levels on an Android device?

Is there a notion of sleep stages/levels on Android?

From browsing the mailing lists, I'm aware that there exist a stage called "Deep Sleep". Do execution for all apps halt when devic开发者_开发知识库e reaches this state? If so, besides user hitting the power button, what else could wake the device back up?

From browsing the mailing lists, I'm aware that there exist a stage called "Deep Sleep".

There is not really a separate stage called "deep sleep". There is only "awake", "asleep", and "off".

Do execution for all apps halt when device reaches this state?

Execution of all processes ceases when the device goes to sleep or is powered off.

If so, besides user hitting the power button, what else could wake the device back up?

• An alarm from AlarmManager
• An incoming phone call
• An incoming text message
• If you have a socket open on wireless data (not WiFi), an incoming packet on that socket

Those are the big ones. There might be others.

I've noticed the following behaviour:

1. You have your activity open and stop interacting with it

2. After a few seconds (it depends on how the device is configured) the screen will go off.

   When the screen goes off, onSaveInstance and onPause are called.

3. A few seconds later (usually ~15s) the device enters into sleep mode (is this the correct name?)

   When this happens, the following methods are invoked: onStop (calling isFinishing returns false), onRetainNonConfigurationInstance and onDestroy.

   So far so good. Now, the strange behaviour begins: just after the last onDestroy finishes, another activity is created: onCreate, onStart, onRestoreInstanceState, onResume and finally onPause are invoked.

   I find no reason for this strange behaviour. Why would another activity be created just to go straight to pause mode? This happens immediatly after onDestroy of the original activity!

This was tested on Galaxy S. I didn't test what happens after a few hours with no activity. I'm not sure if anything else will happen.

I hope this will help you.

A short addition to the commonsware's list. After looking for a way to run methods periodically while phone is asleep, I've found out that TimerTask functions during sleep mode.

TimerTask is, in my experience, easier to work with if all you want is to run methods from a service and not to start an activity.

In Android API 23 the way 'sleep' works was been changed. They have added Doze and App Standby. You can read about both of them here.

Doze: This would be 'sleep'. A few minutes after the screen shuts off the phone will enter this mode shutting down all network connections. Then at certain intervals (maybe a linear back-off policy for example) the apps will be 'allowed' to access the network for ~10 seconds. There is no real way around this if you want to publish your app to Google Play outside of using Google FCM. It might also be worth noting that uptimeMillis is not guaranteed to be updated during Doze because the CPU can enter deep sleep mode (elapsedRealtime will still be accurate).

App Standby: This will essentially stop your app if the device determines that the app is 'idle'. An idle app is a state that is determined by these factors

• Has the app been launched by the user?
• Has the app run a foreground service?
• Has the app generated a notification?
• Is the app an active device admin app?

If the answer to all of these is no, the app will be set to 'idle' and have greatly restricted network access (allowed once a day and/or while charging only). I am not sure how long an app must meet these criteria. However, it seems to be at least a few days before the App Standby state will be entered.

Bonus: Device States (managed by DeviceIdleController)

• ACTIVE - In use, or connected to a power source.
• INACTIVE - Device has come out of the active state (user turned off the screen or unplugged it)
• IDLE_PENDING - About to enter idle mode.
• IDLE - Device is idle (Different than an app being flagged as idle from App Standby. This is the entire device.).
• IDLE_MAINTENANCE - Open for applications to do processing (10 second window).

If you want a background service or worker to check if the app is in the IDLE state then you can use the function isDeviceIdleMode (only works when entering Deep Doze, see below).

Example

(getSystemService(Context.POWER_SERVICE) as PowerManager).isDeviceIdleMode

Some more complications

1. API 24 added more complexities to the Doze mode (Light Doze and Deep Doze). This essentially puts nested states inside the device states.
2. API 28 added "Adaptive Battery" prediction, which makes use of Doze to hibernate user apps the OS determines the user will not use.
3. API 28 also added "App Standby Buckets" to add more states to App Standby than just idle and active.

Besides the "awake", "asleep", and "off" states that @CommonsWare mentioned, there is the distinction between whether the CPU is asleep, or just the screen is. For example, the official docs here describe it this way:

To avoid draining the battery, an Android device that is left idle quickly falls asleep. However, there are times when an application needs to wake up the screen or the CPU and keep it awake to complete some work. [emphasis added]

In the three-stage framework that CommonsWare described, a device whose screen is dark is probably not categorized as "asleep" unless the CPU is also stopped. But as the above paragraph implies, the screen-dark state can legitimately be referred to as "asleep." No doubt this is why people refer to "deep sleep" to clarify that they're talking about the CPU being asleep.

This doc page also mentions

When an Android device is left idle, it will first dim, then turn off the screen, and ultimately turn off the CPU. This prevents the device's battery from quickly getting drained.

So if you want to be comprehensive, you could add "dim" to the list of "sleep stages/levels":

1. awake
2. dim
3. screen off
4. CPU off (true "sleep" or "deep sleep")
5. power off

Apparently the transition from 2 to 3 to 4 is pretty fast when the idle timeout occurs. But there are other times when the screen can be off without a transition to deep sleep; e.g. when playing audio (at least in certain apps).

I wish I could tell you how to predict when the device will transition from screen off to CPU off -- e.g. how long the timeout is -- but I haven't found that information. What I have found is FLAG_KEEP_SCREEN_ON and WAKE_LOCK to prevent one or the other from happening.

P.S. If you want to be exhaustive, you could count daydream in your list of "sleep stages":

Daydream is a new [as of Android 4.2] interactive screensaver mode for Android devices. It activates automatically when the device is inserted into a dock or when the device is left idle while plugged in to a charger (instead of turning the screen off).

From the point of view of the previously-running app, it sounds like daydream behaves like switching to a different app. So it's not really a matter of the device sleeping, though your activity does get stopped, I would assume.