Logic Behind OS O Background Service Limitations

Question

New restrictions on the execution of background services are explained here and here .

This new behavior seems to terminate applications that do a lot of things in the background, even if the user does not know what is fair enough.

However, one suggested workaround is to use a scheduled task instead. But can't this also lead to the fact that the application "will do many things in the background without the user even knowing"? The only difference is that Android decides when it will be done, and not in the application.

So what is the essence of the new restrictions? Or maybe I missed something fundamental.

EDIT: this is not a duplicate of this question ... what is it about using startServiceInForeground()as an alternative (or the documentation related to it), while this question is about using the planned work as an alternative (and whether it completely destroys the purpose of the new restrictions ) These are completely different alternatives.

Answer 1

I see your thought.

It seems to me (after reading the documents) that this is the only professional that we get with the new JobScheduler.

However, if you look at Job Scheduler Enhancements in O

Scheduled tasks now support several new restrictions:

JobInfo.isRequireStorageNotLow() , .

JobInfo.isRequireBatteryNotLow() , ; , .

NETWORK_TYPE_METERED , , .

, JobInfo , .

, , , , .

, , , / . , [JobScheduler.enque()] (https://developer.android.com/reference/android/app/job/JobScheduler.html#enqueue(android.app.job.JobInfo, android.app.job.JobWorkItem)), , JobScheduler , , . , JobScheduler / (, ). .

---

:

, , API , , , , , , , . .