diff --git a/docs/html/training/monitoring-device-state/doze-standby.jd b/docs/html/training/monitoring-device-state/doze-standby.jd index 4eb681fb30ca3..249539ac707e9 100644 --- a/docs/html/training/monitoring-device-state/doze-standby.jd +++ b/docs/html/training/monitoring-device-state/doze-standby.jd @@ -217,7 +217,7 @@ minutes per app.

The Doze restriction on network access is also likely to affect your app, especially if the app relies on real-time messages such as tickles or notifications. If your app requires a persistent connection to the network to - receive messages, you should use Google Cloud Messaging(GCM) + receive messages, you should use Google Cloud Messaging (GCM) if possible.

@@ -283,7 +283,7 @@ minutes per app.

High-priority GCM messages do not otherwise affect Doze mode, and they don’t - affect the state of any other app, This means that your app can use them to communicate + affect the state of any other app. This means that your app can use them to communicate efficiently while minimizing battery impacts across the system and device.

@@ -377,13 +377,18 @@ matches the acceptable use cases for whitelist
  • Run your app and leave it active.
    • -
  • Force the system to cycle through Doze modes by running the following - commands: +
  • Shut off the device screen. (The app remains active.)
    • - 
    $ adb shell dumpsys battery unplug
-$ adb shell dumpsys deviceidle step
-$ adb shell dumpsys deviceidle -h
    +
  • Force the system to cycle through Doze modes by running the following + commands: + + 
    +$ adb shell dumpsys battery unplug
+$ adb shell dumpsys deviceidle step
    + +

    You may need to run the second command more than once. Repeat it until + the device state changes to idle.

  • Observe the behavior of your app after you reactivate the device. Make