From 5695dc7a3b2ed063c6edb0985fed831b63806120 Mon Sep 17 00:00:00 2001 From: Kweku Adams Date: Mon, 22 Mar 2021 10:59:32 -0700 Subject: [PATCH] Fix EJ documentation. 1. Clarify network access behavior 2. Reword upper limit language Bug: 171305774 Test: N/A Change-Id: Ib33ac75eed0a5c734a7f789fdef6f8c3e521897f --- apex/jobscheduler/framework/java/android/app/job/JobInfo.java | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/apex/jobscheduler/framework/java/android/app/job/JobInfo.java b/apex/jobscheduler/framework/java/android/app/job/JobInfo.java index 4c8ab9385903f..90f2f5e0b1c3f 100644 --- a/apex/jobscheduler/framework/java/android/app/job/JobInfo.java +++ b/apex/jobscheduler/framework/java/android/app/job/JobInfo.java @@ -1462,7 +1462,7 @@ public class JobInfo implements Parcelable { *
    *
  1. Run as soon as possible
  2. *
  3. Be less restricted during Doze and battery saver
  4. - *
  5. Have the same network access as foreground services
  6. + *
  7. Bypass Doze, app standby, and battery saver network restrictions
  8. *
  9. Be less likely to be killed than regular jobs
  10. *
  11. Be subject to background location throttling
  12. *
@@ -1483,7 +1483,7 @@ public class JobInfo implements Parcelable { * *

* Assuming all constraints remain satisfied (including ideal system load conditions), - * expedited jobs are guaranteed to have a minimum allowed runtime of 1 minute. If your + * expedited jobs will have a maximum execution time of at least 1 minute. If your * app has remaining expedited job quota, then the expedited job may potentially run * longer until remaining quota is used up. Just like with regular jobs, quota is not * consumed while the app is on top and visible to the user.