Destroy foreground notification when the service get killed

Question

I have a foreground service to download some contents form the web.

Unfortunately, due to bug which reported here my service being killed when a receiver received a broadcast within my service but it's notification won't be killed and I saw the following log in my logcat:

I/ActivityManager(449): Killing 11073:my-package-name/u0a102 (adj 0): remove task

Is there anyway to to destroy foreground notification when it's parent service get killed by OS?

Have you tried to call `stopForground(true)` inside `onTaskRemoved()`? — Nikola Despotoski, Sep 09 '14 at 01:08
@NikolaDespotoski It's not good method for a foregorund service. — Ali, Sep 09 '14 at 11:36

score 1 · Answer 1 · answered Sep 13 '14 at 17:52

1

Service ending remove the foreground notification.

@Override
public void onDestroy() {
    // mycleanup first
    stopForeground(true);
    super.onDestroy();
}

answered Sep 13 '14 at 17:52

danny117

5,581
1
26
35

score 1 · Answer 2 · answered Sep 15 '14 at 14:20

Use stopForeground:

@Override
public void onDestroy() {
 // as the bug seems to exists for android 4.4
 if (android.os.Build.VERSION.SDK_INT == android.os.Build.VERSION_CODES.KITKAT)
 {
    stopForeground(true);
 }
  super.onDestroy();
}

or

public void onTaskRemoved (Intent rootIntent)
{
 // as the bug seems to exists for android 4.4
 if (android.os.Build.VERSION.SDK_INT == android.os.Build.VERSION_CODES.KITKAT)
 {
   stopForeground(true);
 }
}

bgplaya · Answer 3 · 2014-09-15T21:09:54.913

1

Inside the notification check periodically (e.g. Handler) if service is still running using code below:

public static boolean isMyServiceRunning(Context context) {
    ActivityManager manager = (ActivityManager) context.getSystemService(Context.ACTIVITY_SERVICE);
    for (ActivityManager.RunningServiceInfo service : manager.getRunningServices(Integer.MAX_VALUE))                           {
        if (MyService.class.getName().equals(service.service.getClassName())) {
            return true;
        }
    }
    return false;
}

And if not just shut down notification.

private static final int DEALY = 10000;
private Handler handler = new Handler();

...
handler.postDelayed(ensureSericeIsRunning, DELAY);
...

private Runnable ensureSericeIsRunning = new Runnable() {

    @Override
    public void run() {
        if (!isMyServiceRunning(getActivity())){
            //shut down notification
        } else {
            handler.postDelayed(ensureSericeIsRunning, DELAY);
        }
    }
};

edited Sep 15 '14 at 21:09

answered Sep 15 '14 at 21:01

bgplaya

1,105
15
27

Great suggestion but please note that whenever service get killed by OS all other references will be removed too! – Ali Sep 15 '14 at 23:26
What do you mean? Doesn't notification still available to cancel with a Notification Manager? – bgplaya Sep 16 '14 at 05:35
I believe it is what you need: while serivce will be killed next call of isMyServiceRunning will return false and you can just cancel notification. Could you clarify what's wrong? – bgplaya Sep 16 '14 at 05:43

Kosh · Answer 4 · 2014-09-09T01:42:27.927

0

You could remove the notification from onStop or onDestroy inside of your service class. P.S there no guarantee this would work, in api 14 and above the service can still be running even without foreground notification, you could return START_STICKY that will bring back your service even if the system destroyed it, system will restart it.

 @Override
    public int onStartCommand(Intent intent, int flags, int startId) {
    return START_STICKY;
}

edited Sep 09 '14 at 01:42

answered Sep 09 '14 at 00:58

Kosh

6,140
3
36
67

Nope it doesn't work in my case, even `START_STICKY` does not restart the service in KitKat!!! – Ali Sep 09 '14 at 11:38
Can u share which phone u using and are u using stock rom or custom? – Kosh Sep 09 '14 at 23:32
Yes, It's Nexus 5 with AOSP KitKat ROM, please also check this link http://stackoverflow.com/questions/20636330/start-sticky-does-not-work-on-android-kitkat-edit-and-jelly-bean/20681898#20681898 – Ali Sep 10 '14 at 01:13
that bug im not facing using Galaxy s5 rooted stock rom, two days ago i was using CM11, and trust me developing on AOSP isn't a good idea, i had a lots of issues regards my last freelancing app, while running on CM11, try to revert to stock rom, and test it out. you will see loads of differences between running on stock and AOSP. – Kosh Sep 10 '14 at 02:07

score 0 · Answer 5 · answered Sep 09 '14 at 01:39

0

use onDestroy(). Even tho the documentation says it is not guaranteed to be called, I have tested multiple times and the only cases it doesn't get called is when the system kills the process, but to that point your notification will be killed to, so it's ok.

answered Sep 09 '14 at 01:39

Christopher Francisco

15,672
28
94
206

1

No, when service being killed by OS the notification won't be killed! – Ali Sep 09 '14 at 11:57

score 0 · Answer 6 · answered Sep 11 '14 at 15:39

0

use the service onTaskRemoved() method.

answered Sep 11 '14 at 15:39

jinnybrain

30
1
2

Destroy foreground notification when the service get killed

6 Answers6

Linked