Is notification mandatory while app is running(visible) for the foreground service in API>25

Question

From the stackoverflow and many blogs, i surely understand that foreground service never run without notification in API>25. But still i confuse that Is notification mandory while app is running on screen or visible. For eg. no need of notification when user stand within app. So is this possible to remove notification while app running ? In service class

@Override
public int onStartCommand(Intent intent, int flags, int startId) {
    ......
    if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {

        Notification.Builder builder = new Notification.Builder(this, ANDROID_CHANNEL_ID)
                .setContentTitle(getString(R.string.app_name))
                .setContentText(text)
                .setAutoCancel(true);

        Notification notification = builder.build();
        startForeground(1, notification);

    } 
return START_NOT_STICKY;
}

In activity

Intent myService = new Intent(this, MyService.class);

    if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {
        startForegroundService(myService);
    } else {
        startService(myService);
    }

greeble31 · Accepted Answer · 2019-11-19T13:39:49.303

It's not possible to remove the notification while the foreground service is running, but it is possible to change your foreground service back into a "regular" service. This removes the need for a notification. In fact, the function to use,

stopForeground(boolean removeNotification)

...includes a removeNotification parameter just for that purpose. You service can switch from being "foreground" to "regular" on demand, by alternating calls to startForeground() and stopForeground().

In case it's not clear, you'd probably want to call stopForeground() whenever you have at least one Activity in a "started" state. This is something you'd have to track manually. Then, when the number of "started" activities reaches 0, you'd call startForeground().

EDIT

One approach is to use a bound service. Then, it's easy to call stopForeground() on it when you want.

Assume you have a single Activity. You can bind it to the service (see this doc or use one of these examples). Then your onServiceConnected() function could look like this (adapted from the Google example):

//MyActivity.java:

@Override
public void onServiceConnected(ComponentName className, IBinder service) {
    LocalBinder binder = (LocalBinder) service;
    mService = binder.getService();
    mService.stopForeground(true);      //This makes the notification go away
    bound = true;
}

...

@Override
protected void onStart() {
    super.onStart();
    // Bind to the service
    bindService(new Intent(this, MyService.class), this, Context.BIND_AUTO_CREATE);
}

@Override
protected void onStop() {
    super.onStop();
    // Unbind from the service
    if (bound) {
        Notification.Builder builder = new Notification.Builder(this, ANDROID_CHANNEL_ID)
            .setContentTitle(getString(R.string.app_name))
            .setContentText(text)
            .setAutoCancel(true);

        Notification notification = builder.build();
        mService.startForeground(1, notification);    //This brings the notification back! Service is already running, and continues to run.        

        unbindService(this);
        bound = false;
    }
}

After a long journey got some interesting answer...please suggest some example — Vora Ravi, Nov 19 '19 at 13:20
Sorry, I don't know of any examples offhand. I haven't heard of what you're trying to do too often. My suggestion is to Google it and follow the docs. — greeble31, Nov 19 '19 at 13:23
foreground service back into a "regular" service.?? How to do this....after startForgroundservice() from main activity — Vora Ravi, Nov 19 '19 at 13:25

score 0 · Answer 2 · answered Nov 19 '19 at 08:21

0

No, it is mandatory even your app is running in foreground your foreground service need a notification.

You won't able to hide it.

Why : You can use any other background task handler like intent service, job sclr but things is designed defferent for foreground service your user understand that event i will close this one of it's progress is going to keep running but things is defferent with background service your know it will do something in background but when system decide it's best time to do it not when your app want (as like in foreground service).

One more case ex : Suppose your app in foreground battery level is lower than expected by user or system your foreground service will execute instantly no matter what so it's important for your user to know this it's running and take my resources (battery, data, etc)

Hopefully you got my mean

answered Nov 19 '19 at 08:21

Pratyush

401
3
11

before API 26 my whole app is updated by background service in running mode , but now in after 25 how do i update my app in every second(w/o foreground service,because of irritate notification), please suggest – Vora Ravi Nov 19 '19 at 08:49
job scheduler, intent service or more depending on your adject need – Pratyush Nov 19 '19 at 09:09
job scheduler, intent service are updated every time or certain period ? – Vora Ravi Nov 19 '19 at 09:21
Try to run CountDownTimer with update period you want under any foreground or background thread. – Pratyush Nov 19 '19 at 09:29

Is notification mandatory while app is running(visible) for the foreground service in API>25

2 Answers2

Linked

Related