IntentService + startForeground vs JobIntentService
Since Android Oreo background execution limits, the docs recommend to refactor IntentService
s to JobIntentService
.
https://developer.android.com/about/versions/oreo/background
JobIntentService
runs immediately as an IntentService
below Oreo, but schedules a Job on Oreo+
https://developer.android.com/reference/android/support/v4/app/JobIntentService
In what cases would it make sense to run a normal IntentService
as a foreground Service
with a persistent notification, and when is a JobIntentService
better?
One downside I can see in JobIntentService
is that it doesn't start immediately.
android android-service intentservice android-intentservice android-jobscheduler
add a comment |
Since Android Oreo background execution limits, the docs recommend to refactor IntentService
s to JobIntentService
.
https://developer.android.com/about/versions/oreo/background
JobIntentService
runs immediately as an IntentService
below Oreo, but schedules a Job on Oreo+
https://developer.android.com/reference/android/support/v4/app/JobIntentService
In what cases would it make sense to run a normal IntentService
as a foreground Service
with a persistent notification, and when is a JobIntentService
better?
One downside I can see in JobIntentService
is that it doesn't start immediately.
android android-service intentservice android-intentservice android-jobscheduler
add a comment |
Since Android Oreo background execution limits, the docs recommend to refactor IntentService
s to JobIntentService
.
https://developer.android.com/about/versions/oreo/background
JobIntentService
runs immediately as an IntentService
below Oreo, but schedules a Job on Oreo+
https://developer.android.com/reference/android/support/v4/app/JobIntentService
In what cases would it make sense to run a normal IntentService
as a foreground Service
with a persistent notification, and when is a JobIntentService
better?
One downside I can see in JobIntentService
is that it doesn't start immediately.
android android-service intentservice android-intentservice android-jobscheduler
Since Android Oreo background execution limits, the docs recommend to refactor IntentService
s to JobIntentService
.
https://developer.android.com/about/versions/oreo/background
JobIntentService
runs immediately as an IntentService
below Oreo, but schedules a Job on Oreo+
https://developer.android.com/reference/android/support/v4/app/JobIntentService
In what cases would it make sense to run a normal IntentService
as a foreground Service
with a persistent notification, and when is a JobIntentService
better?
One downside I can see in JobIntentService
is that it doesn't start immediately.
android android-service intentservice android-intentservice android-jobscheduler
android android-service intentservice android-intentservice android-jobscheduler
asked Nov 11 '18 at 12:02
Florian WaltherFlorian Walther
9811524
9811524
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Foreground service is not affected by Doze, but you still have to use wake locks, if you need your task to be continued when the screen is off.
The JobIntentService (which uses the JobScheduler) manages wake locks for you, but you have less control when the job will be started.
I would use the foreground IntentService (or Service) for high priority tasks (e.g. downloading a database) that should run immediatelly and that should not be paused / killed by system.
I would use the JobIntentService in conjunction with AlarmManager to schedule low priority tasks like refreshing the widget's data periodically.
Thank you. I am just trying to figure out under which circumstances the job would get deferred. The docs say that the job doesn't get executed if the device is in doze, but how would I even callenqueue
while the device is in doze?
– Florian Walther
Nov 13 '18 at 9:07
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53248528%2fintentservice-startforeground-vs-jobintentservice%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Foreground service is not affected by Doze, but you still have to use wake locks, if you need your task to be continued when the screen is off.
The JobIntentService (which uses the JobScheduler) manages wake locks for you, but you have less control when the job will be started.
I would use the foreground IntentService (or Service) for high priority tasks (e.g. downloading a database) that should run immediatelly and that should not be paused / killed by system.
I would use the JobIntentService in conjunction with AlarmManager to schedule low priority tasks like refreshing the widget's data periodically.
Thank you. I am just trying to figure out under which circumstances the job would get deferred. The docs say that the job doesn't get executed if the device is in doze, but how would I even callenqueue
while the device is in doze?
– Florian Walther
Nov 13 '18 at 9:07
add a comment |
Foreground service is not affected by Doze, but you still have to use wake locks, if you need your task to be continued when the screen is off.
The JobIntentService (which uses the JobScheduler) manages wake locks for you, but you have less control when the job will be started.
I would use the foreground IntentService (or Service) for high priority tasks (e.g. downloading a database) that should run immediatelly and that should not be paused / killed by system.
I would use the JobIntentService in conjunction with AlarmManager to schedule low priority tasks like refreshing the widget's data periodically.
Thank you. I am just trying to figure out under which circumstances the job would get deferred. The docs say that the job doesn't get executed if the device is in doze, but how would I even callenqueue
while the device is in doze?
– Florian Walther
Nov 13 '18 at 9:07
add a comment |
Foreground service is not affected by Doze, but you still have to use wake locks, if you need your task to be continued when the screen is off.
The JobIntentService (which uses the JobScheduler) manages wake locks for you, but you have less control when the job will be started.
I would use the foreground IntentService (or Service) for high priority tasks (e.g. downloading a database) that should run immediatelly and that should not be paused / killed by system.
I would use the JobIntentService in conjunction with AlarmManager to schedule low priority tasks like refreshing the widget's data periodically.
Foreground service is not affected by Doze, but you still have to use wake locks, if you need your task to be continued when the screen is off.
The JobIntentService (which uses the JobScheduler) manages wake locks for you, but you have less control when the job will be started.
I would use the foreground IntentService (or Service) for high priority tasks (e.g. downloading a database) that should run immediatelly and that should not be paused / killed by system.
I would use the JobIntentService in conjunction with AlarmManager to schedule low priority tasks like refreshing the widget's data periodically.
answered Nov 11 '18 at 13:06
Derek KDerek K
338213
338213
Thank you. I am just trying to figure out under which circumstances the job would get deferred. The docs say that the job doesn't get executed if the device is in doze, but how would I even callenqueue
while the device is in doze?
– Florian Walther
Nov 13 '18 at 9:07
add a comment |
Thank you. I am just trying to figure out under which circumstances the job would get deferred. The docs say that the job doesn't get executed if the device is in doze, but how would I even callenqueue
while the device is in doze?
– Florian Walther
Nov 13 '18 at 9:07
Thank you. I am just trying to figure out under which circumstances the job would get deferred. The docs say that the job doesn't get executed if the device is in doze, but how would I even call
enqueue
while the device is in doze?– Florian Walther
Nov 13 '18 at 9:07
Thank you. I am just trying to figure out under which circumstances the job would get deferred. The docs say that the job doesn't get executed if the device is in doze, but how would I even call
enqueue
while the device is in doze?– Florian Walther
Nov 13 '18 at 9:07
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53248528%2fintentservice-startforeground-vs-jobintentservice%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown