From 90a5187d3266e0faa75133c2e8ac2763a17450d0 Mon Sep 17 00:00:00 2001 From: Christopher Tate Date: Tue, 28 Apr 2015 15:43:44 -0700 Subject: Give scheduled jobs a more substantial timeslice One minute turns out to be quite limiting in practice, and we still shut them down summarily when their run constraints become unsatisfied, so widen the window to 10 minutes. Bug 20143368 Change-Id: I2aba521f65b94e9fb8d519b0492625d35aaba267 --- services/core/java/com/android/server/job/JobServiceContext.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/services/core/java/com/android/server/job/JobServiceContext.java b/services/core/java/com/android/server/job/JobServiceContext.java index 53ceb2e..b066d6b 100644 --- a/services/core/java/com/android/server/job/JobServiceContext.java +++ b/services/core/java/com/android/server/job/JobServiceContext.java @@ -68,7 +68,7 @@ public class JobServiceContext extends IJobCallback.Stub implements ServiceConne private static final int defaultMaxActiveJobsPerService = ActivityManager.isLowRamDeviceStatic() ? 1 : 3; /** Amount of time a job is allowed to execute for before being considered timed-out. */ - private static final long EXECUTING_TIMESLICE_MILLIS = 60 * 1000; + private static final long EXECUTING_TIMESLICE_MILLIS = 10 * 60 * 1000; /** Amount of time the JobScheduler will wait for a response from an app for a message. */ private static final long OP_TIMEOUT_MILLIS = 8 * 1000; -- cgit v1.1