From bf2860a54a4a161fa5c6d48b82c0d398018efa45 Mon Sep 17 00:00:00 2001
From: Adarsh Fernando tagging
Bug:27567618
Change-Id: I855b294b5f79c309c8c52f6c26188646c4adc243
---
docs/html/preview/api-overview.jd | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/docs/html/preview/api-overview.jd b/docs/html/preview/api-overview.jd
index 7eba386a97828..c0aa1be9d4d57 100644
--- a/docs/html/preview/api-overview.jd
+++ b/docs/html/preview/api-overview.jd
@@ -539,7 +539,7 @@ GPS/Wi-Fi scans. The best practices for adapting your app to Doze are the same whether the
device is moving or not, so if you already updated your app to gracefully
handle Doze, you're all set. If not, start adapting
+href="{@docRoot}training/monitoring-device-state/doze-standby.html#assessing_your_app">adapting
your app to Doze now. and Project Svelte: Background optimizations
@@ -558,8 +558,13 @@ for users. Apps can schedule jobs while letting the system optimize based on
memory, power, and connectivity conditions. JobScheduler offers control and
simplicity, and we want all apps to use it.
Another good option is GCMNetworkManager, part of Google Pl
+ Another good option is
+ GCMNetworkManager, part of Google Play Services, which
+ offers similar job scheduling with compatibility across legacy versions of
+ Android.
+
We're continuing to extend JobScheduler and GCMNetworkManager to meet more of
your use cases — for example, in Android N you can now schedule background