From caa32fa05eddb1ed6e57ca396715b81ee8968e91 Mon Sep 17 00:00:00 2001 From: Dirk Dougherty Date: Fri, 16 Oct 2015 10:08:55 -0700 Subject: [PATCH] Doc change: updates to Doze/Standby cases. Change-Id: I30c9e0440e0a4bf3fc6bb1fa78b2a85baad3b357 --- docs/html/training/monitoring-device-state/doze-standby.jd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/html/training/monitoring-device-state/doze-standby.jd b/docs/html/training/monitoring-device-state/doze-standby.jd index 4eb681fb30ca3..e167254ef3363 100644 --- a/docs/html/training/monitoring-device-state/doze-standby.jd +++ b/docs/html/training/monitoring-device-state/doze-standby.jd @@ -421,7 +421,7 @@ $ adb shell am get-inactive <packageName>

The table below highlights the acceptable use cases for requesting or being on the Battery Optimizations exceptions whitelist. In general, your app should not be on the - whitelist unless Doze and App Standby break the core function of the app, and there is a + whitelist unless Doze or App Standby break the core function of the app or there is a technical reason why your app cannot use GCM high-priority messages.

For more information, see Support for Other Use Cases @@ -453,7 +453,7 @@ $ adb shell am get-inactive <packageName> Instant messaging, chat, or calling app; enterprise VOIP apps No, can not use GCM because of technical dependency on another messaging - service + service or Doze and App Standby break the core function of the app. Acceptable