App won't die when swipe killed, notification showing up
I am working on an app that makes calls over VOIP.
There is a service that runs in the background to receive incoming VOIP calls. Hence it tends to run in the background for a while. When the app is swipe killed on Android 9 phones, a white dot associated with the notification for that service appears. I try to kill the service like this:
stopForeground(true);
boolean result = stopSelfResult(-1);
It stops but it seems to reappear. The app itself doesn't get completely killed, only put in the background. When I bring it back up and then swipe kill it a second time or press force stop in app info screen, only then does it die. When I try killing the app, I notice this output in the logs which may be helpful:
12-31 17:13:30.254 W/System (21332): A resource failed to call close.
12-31 17:13:30.254 W/System (21332): A resource failed to call close.
12-31 17:13:31.421 I/Choreographer(21332): Skipped 667 frames! The application may be doing too much work on its main thread.
12-31 17:13:50.729 I/BatteryChangeReceiver(21332): App is in background
I am not sure what's keeping the dang app alive as the service itself seems to shut down just fine. It may be some other resource but I have no idea where to begin investigating this. Any ideas?
android asked Dec 31 '18 at 22:56
Manav DuttaManav Dutta
1
add a comment |
I am working on an app that makes calls over VOIP.
There is a service that runs in the background to receive incoming VOIP calls. Hence it tends to run in the background for a while. When the app is swipe killed on Android 9 phones, a white dot associated with the notification for that service appears. I try to kill the service like this:
stopForeground(true);
boolean result = stopSelfResult(-1);
It stops but it seems to reappear. The app itself doesn't get completely killed, only put in the background. When I bring it back up and then swipe kill it a second time or press force stop in app info screen, only then does it die. When I try killing the app, I notice this output in the logs which may be helpful:
12-31 17:13:30.254 W/System (21332): A resource failed to call close.
12-31 17:13:30.254 W/System (21332): A resource failed to call close.
12-31 17:13:31.421 I/Choreographer(21332): Skipped 667 frames! The application may be doing too much work on its main thread.
12-31 17:13:50.729 I/BatteryChangeReceiver(21332): App is in background
I am not sure what's keeping the dang app alive as the service itself seems to shut down just fine. It may be some other resource but I have no idea where to begin investigating this. Any ideas?
android asked Dec 31 '18 at 22:56
Manav DuttaManav Dutta
1
You might try to run it on the UI thread. There are a bunch of examples, but this one was the first one that came up for me: stackoverflow.com/a/31217966/897007
– Dale
Dec 31 '18 at 23:25
add a comment |
I am working on an app that makes calls over VOIP.
There is a service that runs in the background to receive incoming VOIP calls. Hence it tends to run in the background for a while. When the app is swipe killed on Android 9 phones, a white dot associated with the notification for that service appears. I try to kill the service like this:
stopForeground(true);
boolean result = stopSelfResult(-1);
It stops but it seems to reappear. The app itself doesn't get completely killed, only put in the background. When I bring it back up and then swipe kill it a second time or press force stop in app info screen, only then does it die. When I try killing the app, I notice this output in the logs which may be helpful:
12-31 17:13:30.254 W/System (21332): A resource failed to call close.
12-31 17:13:30.254 W/System (21332): A resource failed to call close.
12-31 17:13:31.421 I/Choreographer(21332): Skipped 667 frames! The application may be doing too much work on its main thread.
12-31 17:13:50.729 I/BatteryChangeReceiver(21332): App is in background
I am not sure what's keeping the dang app alive as the service itself seems to shut down just fine. It may be some other resource but I have no idea where to begin investigating this. Any ideas?
android asked Dec 31 '18 at 22:56
Manav DuttaManav Dutta
1
I am working on an app that makes calls over VOIP.
There is a service that runs in the background to receive incoming VOIP calls. Hence it tends to run in the background for a while. When the app is swipe killed on Android 9 phones, a white dot associated with the notification for that service appears. I try to kill the service like this:
stopForeground(true);
boolean result = stopSelfResult(-1);
It stops but it seems to reappear. The app itself doesn't get completely killed, only put in the background. When I bring it back up and then swipe kill it a second time or press force stop in app info screen, only then does it die. When I try killing the app, I notice this output in the logs which may be helpful:
12-31 17:13:30.254 W/System (21332): A resource failed to call close.
12-31 17:13:30.254 W/System (21332): A resource failed to call close.
12-31 17:13:31.421 I/Choreographer(21332): Skipped 667 frames! The application may be doing too much work on its main thread.
12-31 17:13:50.729 I/BatteryChangeReceiver(21332): App is in background
I am not sure what's keeping the dang app alive as the service itself seems to shut down just fine. It may be some other resource but I have no idea where to begin investigating this. Any ideas?
android android asked Dec 31 '18 at 22:56
Manav DuttaManav Dutta
1
asked Dec 31 '18 at 22:56
Manav DuttaManav Dutta
1
asked Dec 31 '18 at 22:56
Manav DuttaManav Dutta
1
asked Dec 31 '18 at 22:56
Manav DuttaManav Dutta
1
asked Dec 31 '18 at 22:56
Manav DuttaManav Dutta
1
1
You might try to run it on the UI thread. There are a bunch of examples, but this one was the first one that came up for me: stackoverflow.com/a/31217966/897007
– Dale
Dec 31 '18 at 23:25
add a comment |
You might try to run it on the UI thread. There are a bunch of examples, but this one was the first one that came up for me: stackoverflow.com/a/31217966/897007
– Dale
Dec 31 '18 at 23:25
You might try to run it on the UI thread. There are a bunch of examples, but this one was the first one that came up for me: stackoverflow.com/a/31217966/897007
– Dale
Dec 31 '18 at 23:25
You might try to run it on the UI thread. There are a bunch of examples, but this one was the first one that came up for me: stackoverflow.com/a/31217966/897007
– Dale
Dec 31 '18 at 23:25
add a comment |
0
active
oldest
votes
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%2f53991997%2fapp-wont-die-when-swipe-killed-notification-showing-up%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f53991997%2fapp-wont-die-when-swipe-killed-notification-showing-up%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
You might try to run it on the UI thread. There are a bunch of examples, but this one was the first one that came up for me: stackoverflow.com/a/31217966/897007
– Dale
Dec 31 '18 at 23:25