Android Oreo killing background services and clears pending alarms, scheduled jobs after entering doze mode

Question

My app has a background service running that gets users current location and update it to a server every five minutes. To run this location update process continuously, I use alarm manager to set its next execution time from the service itself. However, when I install the app in my Nokia 6 running Android 8.1 it works for some time and if I keep the phone idle for some time, my service will get killed with the next alarms by the application also being cleared from system alarm manager. My guess was that the idle time makes the phone enter doze mode. However, I don't understand why the alarm managers got cleared. To my understanding, the doze mode should open up maintenance windows periodically to execute any pending tasks.

To mitigate this issue, I tried to apply a Job Scheduler service on top of Alarm Manager, which runs every 15 minutes. Purpose of this job scheduler was to re-start the service which has the alarm manager in it, so even if it gets killed and the alarm is cleared, job scheduler would re-up the service.

After I tested this patch and keeping it for some time to go into idle mode, it resulted in getting both Job Scheduler Service and Service which has the alarm in it killed with the scheduled jobs and alarms getting cleared from the system.

It is said in the Android documentation that we can use JobScheduler to mitigate its background execution limitations. And to test this out I forced killed the two services when I tested the app, but the already scheduled job did not get cleared, and it made the service with the alarm run again successfully. I don't understand the reason for this behavior, although the Evernote guys give an explanation that could match this scenario in here Android Job by Evernote

Any ideas for this abnormal behavior?

Test Environment Details

• Device : Nokia 6 (TA-1021)
• OS : Android 8.1.0

Answer 1

I assumed currently DOZE mode not allowed to background service so you need to find a way that DOZE mode will not affect on your app.To solve your issue you should use foreground service. or make some battery setting. Any way my better option is you should go with Firebase Cloud Messaging

Answer 2

You would not be able to run background services long running in Oreo as there are behaviour changes, now Oreo to optimise system memory, battery etc, it kills background service, to solve your issue you should use foreground service.

Have a look at Background execution limits https://developer.android.com/about/versions/oreo/android-8.0-changes

A suggestion from me, if you can use FCM then go for it, becasue apps like WeChat, Facebook uses it, to deliver notifications and they don't face any problem...

Hope this helps in understanding the issue....

Answer 3

I'm currently facing the same issue and doing the same workaraound like you do. That is, setting the Jobscheduler to a periodic job to launch my Foreground Service every 15 min in case it is getting killed for whatever reasons like a killed task. This works like a charm on pre Oreo Versions.

For Oreo the only solution I am awared of at the moment is, to allow the app to autostart in the settings. Under installed apps that is. Then it should work like pre Oreo again. What Ive heard but not tested yet, is to set the setPersisted(true) option in the Job Scheduler. Let me know if that helps

Answer 4

In Doze more, the alarms do not get reset, but get deferred to a later time. You have two mainstream options here:

1. Use either setAndAllowWhileIdle() or setExactAndAllowWhileIdle(). However, these too can fire at the maximum frequency of 1 time per 9 minutes. So you'll have to decrease the frequency at which you get location in your app.

2. Use a foreground service by way of showing a foreground notification. Everyone does that (apps like Uber, Google Maps etc). That way, your service won't get killed, and be treated as though you have an app open.