Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 280de4ea authored by Kweku Adams's avatar Kweku Adams
Browse files

Update documentation.

Remove obsolete comments. We no longer require apps to specify at least
one constraint.
Fix typo.

Bug: 118636037
Bug: 141645789
Test: N/A
Change-Id: I1abf14c10f7330bccb51600eb82a398208a4f542
parent 76182efa
Loading
Loading
Loading
Loading
+2 −3
Original line number Diff line number Diff line
@@ -53,9 +53,8 @@ import java.util.Objects;
 * Container of data passed to the {@link android.app.job.JobScheduler} fully encapsulating the
 * parameters required to schedule work against the calling application. These are constructed
 * using the {@link JobInfo.Builder}.
 * You must specify at least one sort of constraint on the JobInfo object that you are creating.
 * The goal here is to provide the scheduler with high-level semantics about the work you want to
 * accomplish. Doing otherwise with throw an exception in your app.
 * accomplish.
 */
public class JobInfo implements Parcelable {
    private static String TAG = "JobInfo";
@@ -147,7 +146,7 @@ public class JobInfo implements Parcelable {

    /**
     * Query the minimum interval allowed for periodic scheduled jobs.  Attempting
     * to declare a smaller period that this when scheduling a job will result in a
     * to declare a smaller period than this when scheduling a job will result in a
     * job that is still periodic, but will run with this effective period.
     *
     * @return The minimum available interval for scheduling periodic jobs, in milliseconds.