Close application by alarm in dozen mode
I'm trying to solve strange problem. This device work only with my Application. Application is always opened. Every night i application should been closed. I added alarm for different SDK-case and it work:
AlarmManager alarmManager = (AlarmManager) context.getSystemService(Context.ALARM_SERVICE);
if (SDK_INT < Build.VERSION_CODES.KITKAT)
alarmManager.set(AlarmManager.RTC, time, pendingIntent);
else if (SDK_INT < Build.VERSION_CODES.M)
alarmManager.setExact(AlarmManager.RTC, time, pendingIntent);
else
alarmManager.setExactAndAllowWhileIdle(AlarmManager.RTC, time, pendingIntent);
On alarm receiver i try to kill application:
android.os.Process.killProcess(android.os.Process.myPid());
System.exit(0);
In finnaly application closed only when tablet doesn't sleep. When tablet in doze mode, application will killed and immediately start an application.class then app will be restarted. SDK of tablet 24. Alarm is work - i check it.
So... Where i wrong? My problem in killProcess
? Why app is killing when tablet is not sleep and it doesn't work when tablet is sleep?
java android
add a comment |
I'm trying to solve strange problem. This device work only with my Application. Application is always opened. Every night i application should been closed. I added alarm for different SDK-case and it work:
AlarmManager alarmManager = (AlarmManager) context.getSystemService(Context.ALARM_SERVICE);
if (SDK_INT < Build.VERSION_CODES.KITKAT)
alarmManager.set(AlarmManager.RTC, time, pendingIntent);
else if (SDK_INT < Build.VERSION_CODES.M)
alarmManager.setExact(AlarmManager.RTC, time, pendingIntent);
else
alarmManager.setExactAndAllowWhileIdle(AlarmManager.RTC, time, pendingIntent);
On alarm receiver i try to kill application:
android.os.Process.killProcess(android.os.Process.myPid());
System.exit(0);
In finnaly application closed only when tablet doesn't sleep. When tablet in doze mode, application will killed and immediately start an application.class then app will be restarted. SDK of tablet 24. Alarm is work - i check it.
So... Where i wrong? My problem in killProcess
? Why app is killing when tablet is not sleep and it doesn't work when tablet is sleep?
java android
add a comment |
I'm trying to solve strange problem. This device work only with my Application. Application is always opened. Every night i application should been closed. I added alarm for different SDK-case and it work:
AlarmManager alarmManager = (AlarmManager) context.getSystemService(Context.ALARM_SERVICE);
if (SDK_INT < Build.VERSION_CODES.KITKAT)
alarmManager.set(AlarmManager.RTC, time, pendingIntent);
else if (SDK_INT < Build.VERSION_CODES.M)
alarmManager.setExact(AlarmManager.RTC, time, pendingIntent);
else
alarmManager.setExactAndAllowWhileIdle(AlarmManager.RTC, time, pendingIntent);
On alarm receiver i try to kill application:
android.os.Process.killProcess(android.os.Process.myPid());
System.exit(0);
In finnaly application closed only when tablet doesn't sleep. When tablet in doze mode, application will killed and immediately start an application.class then app will be restarted. SDK of tablet 24. Alarm is work - i check it.
So... Where i wrong? My problem in killProcess
? Why app is killing when tablet is not sleep and it doesn't work when tablet is sleep?
java android
I'm trying to solve strange problem. This device work only with my Application. Application is always opened. Every night i application should been closed. I added alarm for different SDK-case and it work:
AlarmManager alarmManager = (AlarmManager) context.getSystemService(Context.ALARM_SERVICE);
if (SDK_INT < Build.VERSION_CODES.KITKAT)
alarmManager.set(AlarmManager.RTC, time, pendingIntent);
else if (SDK_INT < Build.VERSION_CODES.M)
alarmManager.setExact(AlarmManager.RTC, time, pendingIntent);
else
alarmManager.setExactAndAllowWhileIdle(AlarmManager.RTC, time, pendingIntent);
On alarm receiver i try to kill application:
android.os.Process.killProcess(android.os.Process.myPid());
System.exit(0);
In finnaly application closed only when tablet doesn't sleep. When tablet in doze mode, application will killed and immediately start an application.class then app will be restarted. SDK of tablet 24. Alarm is work - i check it.
So... Where i wrong? My problem in killProcess
? Why app is killing when tablet is not sleep and it doesn't work when tablet is sleep?
java android
java android
asked Nov 22 '18 at 11:28
Georgiy ChebotarevGeorgiy Chebotarev
124110
124110
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
After several hours, i found finally solution. KillProcess can restart your application in some cases - it is known bug. In my case i happened in sleeping (dozen) mode. So, if you want to kill application, you should use finish()
. I created a special ShutdownActivity with constant method of creation. I can't give you fully code, but something i can.
Start activity with this flags:
intent.addFlags(Intent.FLAG_ACTIVITY_NEW_TASK | Intent.FLAG_ACTIVITY_CLEAR_TASK | Intent.FLAG_ACTIVITY_EXCLUDE_FROM_RECENTS | Intent.FLAG_ACTIVITY_NO_ANIMATION);
in create method of you finish activity interrupt it:
if(android.os.Build.VERSION.SDK_INT >= 21)
finishAndRemoveTask();
else
finish();
android.os.Process.killProcess(Process.myPid()); // it can be system.exit(0) too
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%2f53429964%2fclose-application-by-alarm-in-dozen-mode%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
After several hours, i found finally solution. KillProcess can restart your application in some cases - it is known bug. In my case i happened in sleeping (dozen) mode. So, if you want to kill application, you should use finish()
. I created a special ShutdownActivity with constant method of creation. I can't give you fully code, but something i can.
Start activity with this flags:
intent.addFlags(Intent.FLAG_ACTIVITY_NEW_TASK | Intent.FLAG_ACTIVITY_CLEAR_TASK | Intent.FLAG_ACTIVITY_EXCLUDE_FROM_RECENTS | Intent.FLAG_ACTIVITY_NO_ANIMATION);
in create method of you finish activity interrupt it:
if(android.os.Build.VERSION.SDK_INT >= 21)
finishAndRemoveTask();
else
finish();
android.os.Process.killProcess(Process.myPid()); // it can be system.exit(0) too
add a comment |
After several hours, i found finally solution. KillProcess can restart your application in some cases - it is known bug. In my case i happened in sleeping (dozen) mode. So, if you want to kill application, you should use finish()
. I created a special ShutdownActivity with constant method of creation. I can't give you fully code, but something i can.
Start activity with this flags:
intent.addFlags(Intent.FLAG_ACTIVITY_NEW_TASK | Intent.FLAG_ACTIVITY_CLEAR_TASK | Intent.FLAG_ACTIVITY_EXCLUDE_FROM_RECENTS | Intent.FLAG_ACTIVITY_NO_ANIMATION);
in create method of you finish activity interrupt it:
if(android.os.Build.VERSION.SDK_INT >= 21)
finishAndRemoveTask();
else
finish();
android.os.Process.killProcess(Process.myPid()); // it can be system.exit(0) too
add a comment |
After several hours, i found finally solution. KillProcess can restart your application in some cases - it is known bug. In my case i happened in sleeping (dozen) mode. So, if you want to kill application, you should use finish()
. I created a special ShutdownActivity with constant method of creation. I can't give you fully code, but something i can.
Start activity with this flags:
intent.addFlags(Intent.FLAG_ACTIVITY_NEW_TASK | Intent.FLAG_ACTIVITY_CLEAR_TASK | Intent.FLAG_ACTIVITY_EXCLUDE_FROM_RECENTS | Intent.FLAG_ACTIVITY_NO_ANIMATION);
in create method of you finish activity interrupt it:
if(android.os.Build.VERSION.SDK_INT >= 21)
finishAndRemoveTask();
else
finish();
android.os.Process.killProcess(Process.myPid()); // it can be system.exit(0) too
After several hours, i found finally solution. KillProcess can restart your application in some cases - it is known bug. In my case i happened in sleeping (dozen) mode. So, if you want to kill application, you should use finish()
. I created a special ShutdownActivity with constant method of creation. I can't give you fully code, but something i can.
Start activity with this flags:
intent.addFlags(Intent.FLAG_ACTIVITY_NEW_TASK | Intent.FLAG_ACTIVITY_CLEAR_TASK | Intent.FLAG_ACTIVITY_EXCLUDE_FROM_RECENTS | Intent.FLAG_ACTIVITY_NO_ANIMATION);
in create method of you finish activity interrupt it:
if(android.os.Build.VERSION.SDK_INT >= 21)
finishAndRemoveTask();
else
finish();
android.os.Process.killProcess(Process.myPid()); // it can be system.exit(0) too
answered Nov 22 '18 at 13:43
Georgiy ChebotarevGeorgiy Chebotarev
124110
124110
add a comment |
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%2f53429964%2fclose-application-by-alarm-in-dozen-mode%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