JobIntentService与IntentService的区别

最新推荐文章于 2024-08-27 12:11:22 发布

原创最新推荐文章于 2024-08-27 12:11:22 发布 · 3.6k 阅读

1 ·

CC 4.0 BY-SA版权

文章标签：

#android

Android 专栏收录该内容

46 篇文章

订阅专栏

JobIntentService与IntentService在Android O之前用于后台任务执行，但在Android O及更高版本中，JobIntentService受JobScheduler策略影响，不会在设备休眠（Doze模式）时立即执行，可能导致延迟，不适合处理即时任务。IntentService则相对不受此限制。

JobIntentService与IntentService都是可以用来执行后台任务，在Android O之前，使用起来效果没多大差别，但是Android O以后JobIntentService不会立即执行，等手机进入一定状态后才会执行任务，所以不能用来执行及时的后台任务。

When running as a pre-O service, the act of enqueueing work will generally start the service immediately, regardless of whether the device is dozing or in other conditions. When running as a Job, it will be subject to standard JobScheduler policies for a Job with a setOverrideDeadline(long) of 0: the job will not run while the device is dozing, it may get delayed more than a service if the device is under strong memory pressure with lots of demand to run jobs.

the job will not run while the device is dozing 重点是这里的说明。
关于Doze模式的介绍，请参考：
Android中的Doze模式

参考JobIntentService的部分代码：

    @RequiresApi(26)
    static final class JobWorkEnqueuer extends JobIntentService.WorkEnqueuer {
        private final JobInfo mJobInfo;
        private final JobScheduler mJobScheduler;

        JobWorkEnqueuer(Context context, ComponentName cn, int jobId) {
            super(cn);
            ensureJobId(jobId);
            JobInfo.Builder b = new JobInfo.Builder(jobId, mComponentName);
            mJobInfo = b.setOverrideDeadline(0).build();
            mJobScheduler = (JobScheduler) context.getApplicationContext().getSystemService(
                    Context.JOB_SCHEDULER_SERVICE);
        }

        @Override
        void enqueueWork(Intent work) {
            if (DEBUG) Log.d(TAG, "Enqueueing work: " + work);
            mJobScheduler.enqueue(mJobInfo, new JobWorkItem(work));
        }
    }