Android Question Sticky Service not working on Android 8.0

Sticky services should no longer be used. They will not work properly and will be killed quickly.

You should use a foreground service if you want to keep the process running in the background.

Inman said:

Also is it possible to turn off via code, the persistent notification that is usually up when a service is running?

Click to expand...

Not without exiting foreground mode.

What change should I make to the present code to make the service self-restart? By present code I mean the service has just the following attributes:

• #StartAtBoot: True
• #StartCommandReturnValue: android.app.Service.START_STICKY

You should remove the second line and make your service a foreground service.

You can do it by adding this line to Service_Create:

Search for Service.StartForeground for other options.

Ok great. Thank you for clarifying.

Another doubt. In your other thread, you mentioned this:

You need to do one thing which is to stop the automatic foreground mode when the service completed its task.
This can be done in two ways:

1. Call Service.StopAutomaticForeground. This will stop the automatic foreground mode if the service was in that mode. Otherwise it will not do anything.
It is safe to call it multiple times. The service will not be immediately destroyed.

2. Call StopService(Me).

If you don't stop the automatic foreground mode then a notification icon will be left after the task completed.

Click to expand...

This could work in the case of the push notifications example you mention where the service can stop itself as soon as it receives the push notification and can wake up when the next push arrives.

But in my case the service needs to be alive all the time as FileObserver won't work otherwise. Does that mean the service will always be a foreground service and that it will always have the persistent notification?

Also how does foreground service impact battery life when compared to sticky services in Android 8.0? Does it hold a wakelock thereby not allowing the device to go to sleep? I am asking this because whenever there is a persistent notification, users get alarmed and some even leave negative reviews on Play Store saying the app is draining battery even though the reality might be different.

Inman said:

Does that mean the service will always be a foreground service and that it will always have the persistent notification?

Click to expand...

Yes.

Inman said:

Does it hold a wakelock thereby not allowing the device to go to sleep?

Click to expand...

No. However the process will keep running so it will have some impact.

You can instead use StartServiceAt to start your app every hour do whatever it needs to do and stop.