How to Create a Persistent Notification with a Force Close button?
I have a Xamarin Forms app that runs fine, but I need to implement a new feature similar to this link.
I need to create a notification for the app that persists as long as the app is running. There should be a "force kill" button in the notification. Similar to how Google Maps allows the user to 'end navigation' or some music player apps allow the user to control the music from a notification bar.
Can anyone tell me where to begin, or what resources I can check?
Here is a little background of the problem we're facing. We have an app that can create a WebRTC stream. The user can mirror cast their Android device to a screen. Now if they decide to "Swipe Recent" to close the app, the WebRTC service does not get destroyed. The user should use "Force Close" from App Info to truly end their stream. If they don't, they might assume that their Swipe Recent action had closed the app, along with the mirror cast stream, while in fact it is still streaming their screen. This happens on select few Android 8 devices.
We're thinking that perhaps a Notification bar similar to the screenshot will persist even after the app had been swiped from the Recents list, until the user decides to truly terminate the app and its WebRTC service from the notification area.
Thank you.
android service xamarin.forms notifications kill-process asked Nov 13 at 18:33
MrProgrammer
639
add a comment |
I have a Xamarin Forms app that runs fine, but I need to implement a new feature similar to this link.
I need to create a notification for the app that persists as long as the app is running. There should be a "force kill" button in the notification. Similar to how Google Maps allows the user to 'end navigation' or some music player apps allow the user to control the music from a notification bar.
Can anyone tell me where to begin, or what resources I can check?
Here is a little background of the problem we're facing. We have an app that can create a WebRTC stream. The user can mirror cast their Android device to a screen. Now if they decide to "Swipe Recent" to close the app, the WebRTC service does not get destroyed. The user should use "Force Close" from App Info to truly end their stream. If they don't, they might assume that their Swipe Recent action had closed the app, along with the mirror cast stream, while in fact it is still streaming their screen. This happens on select few Android 8 devices.
We're thinking that perhaps a Notification bar similar to the screenshot will persist even after the app had been swiped from the Recents list, until the user decides to truly terminate the app and its WebRTC service from the notification area.
Thank you.
android service xamarin.forms notifications kill-process asked Nov 13 at 18:33
MrProgrammer
639
It seems like your problem should be fixing the fact that a swipe away form the recents doesn't close everything, not hacking in a button to do so in the notification. That's the bad user experience.
– Gabe Sechan
Nov 13 at 18:35
So you only want the stream to work while the Activity is running? Why not just stop the Service in theonDestroy()method of your Activity?
– TheWanderer
Nov 13 at 18:42
Thanks for the suggestion. I've tried that, but OnDestroy() doesn't get called when the app is closed. Neither do Finish(), FinishAndRemoveTask(), Dispose(), or the finalizer... The only one that gets called is OnStop(), but that gets called when the app is minimized. I should only terminate the app when the app is swiped from recents, not when the user goes to the desktop.
– MrProgrammer
Nov 13 at 18:58
add a comment |
I have a Xamarin Forms app that runs fine, but I need to implement a new feature similar to this link.
I need to create a notification for the app that persists as long as the app is running. There should be a "force kill" button in the notification. Similar to how Google Maps allows the user to 'end navigation' or some music player apps allow the user to control the music from a notification bar.
Can anyone tell me where to begin, or what resources I can check?
Here is a little background of the problem we're facing. We have an app that can create a WebRTC stream. The user can mirror cast their Android device to a screen. Now if they decide to "Swipe Recent" to close the app, the WebRTC service does not get destroyed. The user should use "Force Close" from App Info to truly end their stream. If they don't, they might assume that their Swipe Recent action had closed the app, along with the mirror cast stream, while in fact it is still streaming their screen. This happens on select few Android 8 devices.
We're thinking that perhaps a Notification bar similar to the screenshot will persist even after the app had been swiped from the Recents list, until the user decides to truly terminate the app and its WebRTC service from the notification area.
Thank you.
android service xamarin.forms notifications kill-process asked Nov 13 at 18:33
MrProgrammer
639
I have a Xamarin Forms app that runs fine, but I need to implement a new feature similar to this link.
I need to create a notification for the app that persists as long as the app is running. There should be a "force kill" button in the notification. Similar to how Google Maps allows the user to 'end navigation' or some music player apps allow the user to control the music from a notification bar.
Can anyone tell me where to begin, or what resources I can check?
Here is a little background of the problem we're facing. We have an app that can create a WebRTC stream. The user can mirror cast their Android device to a screen. Now if they decide to "Swipe Recent" to close the app, the WebRTC service does not get destroyed. The user should use "Force Close" from App Info to truly end their stream. If they don't, they might assume that their Swipe Recent action had closed the app, along with the mirror cast stream, while in fact it is still streaming their screen. This happens on select few Android 8 devices.
We're thinking that perhaps a Notification bar similar to the screenshot will persist even after the app had been swiped from the Recents list, until the user decides to truly terminate the app and its WebRTC service from the notification area.
Thank you.
android service xamarin.forms notifications kill-process android service xamarin.forms notifications kill-process asked Nov 13 at 18:33
MrProgrammer
639
asked Nov 13 at 18:33
MrProgrammer
639
asked Nov 13 at 18:33
MrProgrammer
639
asked Nov 13 at 18:33
MrProgrammer
639
asked Nov 13 at 18:33
MrProgrammer
639
639
It seems like your problem should be fixing the fact that a swipe away form the recents doesn't close everything, not hacking in a button to do so in the notification. That's the bad user experience.
– Gabe Sechan
Nov 13 at 18:35
So you only want the stream to work while the Activity is running? Why not just stop the Service in theonDestroy()method of your Activity?
– TheWanderer
Nov 13 at 18:42
Thanks for the suggestion. I've tried that, but OnDestroy() doesn't get called when the app is closed. Neither do Finish(), FinishAndRemoveTask(), Dispose(), or the finalizer... The only one that gets called is OnStop(), but that gets called when the app is minimized. I should only terminate the app when the app is swiped from recents, not when the user goes to the desktop.
– MrProgrammer
Nov 13 at 18:58
add a comment |
It seems like your problem should be fixing the fact that a swipe away form the recents doesn't close everything, not hacking in a button to do so in the notification. That's the bad user experience.
– Gabe Sechan
Nov 13 at 18:35
So you only want the stream to work while the Activity is running? Why not just stop the Service in theonDestroy()method of your Activity?
– TheWanderer
Nov 13 at 18:42
Thanks for the suggestion. I've tried that, but OnDestroy() doesn't get called when the app is closed. Neither do Finish(), FinishAndRemoveTask(), Dispose(), or the finalizer... The only one that gets called is OnStop(), but that gets called when the app is minimized. I should only terminate the app when the app is swiped from recents, not when the user goes to the desktop.
– MrProgrammer
Nov 13 at 18:58
It seems like your problem should be fixing the fact that a swipe away form the recents doesn't close everything, not hacking in a button to do so in the notification. That's the bad user experience.
– Gabe Sechan
Nov 13 at 18:35
It seems like your problem should be fixing the fact that a swipe away form the recents doesn't close everything, not hacking in a button to do so in the notification. That's the bad user experience.
– Gabe Sechan
Nov 13 at 18:35
So you only want the stream to work while the Activity is running? Why not just stop the Service in the
onDestroy() method of your Activity?– TheWanderer
Nov 13 at 18:42
So you only want the stream to work while the Activity is running? Why not just stop the Service in the
onDestroy() method of your Activity?– TheWanderer
Nov 13 at 18:42
Thanks for the suggestion. I've tried that, but OnDestroy() doesn't get called when the app is closed. Neither do Finish(), FinishAndRemoveTask(), Dispose(), or the finalizer... The only one that gets called is OnStop(), but that gets called when the app is minimized. I should only terminate the app when the app is swiped from recents, not when the user goes to the desktop.
– MrProgrammer
Nov 13 at 18:58
Thanks for the suggestion. I've tried that, but OnDestroy() doesn't get called when the app is closed. Neither do Finish(), FinishAndRemoveTask(), Dispose(), or the finalizer... The only one that gets called is OnStop(), but that gets called when the app is minimized. I should only terminate the app when the app is swiped from recents, not when the user goes to the desktop.
– MrProgrammer
Nov 13 at 18:58
add a comment |
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%2f53287437%2fhow-to-create-a-persistent-notification-with-a-force-close-button%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f53287437%2fhow-to-create-a-persistent-notification-with-a-force-close-button%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
It seems like your problem should be fixing the fact that a swipe away form the recents doesn't close everything, not hacking in a button to do so in the notification. That's the bad user experience.
– Gabe Sechan
Nov 13 at 18:35
So you only want the stream to work while the Activity is running? Why not just stop the Service in the
onDestroy()method of your Activity?– TheWanderer
Nov 13 at 18:42
Thanks for the suggestion. I've tried that, but OnDestroy() doesn't get called when the app is closed. Neither do Finish(), FinishAndRemoveTask(), Dispose(), or the finalizer... The only one that gets called is OnStop(), but that gets called when the app is minimized. I should only terminate the app when the app is swiped from recents, not when the user goes to the desktop.
– MrProgrammer
Nov 13 at 18:58