Android - Service, IntentService, JobIntentService - they are stoped if app killed

Question

I have read to many same questions here in StackOverflow and in Web but cannot configure something like "never ending service" or running even when app is removed from task (force killed). I am just wondering how services like Viber or WhatsUp working, because when we force killed those application we are still able to receive messages when someone write to us(So service is running still). I know about foreground service , but it is not solution because user don't want to see the notification. So here what i have tried. : This code in running inside services to detect real-time changes, and just wanted for this to stay active in every condition of app : Foreground, Background, Removed etc...

firestoreDb!!.collection("example").document("example").collection("real_time_request")
                    .addSnapshotListener { documentSnapshot: QuerySnapshot?, _: FirebaseFirestoreException? ->

                    }

I am using service like this to get real time data from Firestore Database when something changes in user's collection.

The ways i tries services are :

FirestoreListeners : IntentService("Firestore Listeners")
FirestoreListeners : Service
FirestoreListeners : JobIntentService

Everything above is working fine when app is in foreground or in background, but the services are killed after app is force closed (when removed from task)

I have tried to make this changes in manifest :

android:stopWithTask="false"
android:directBootAware="true"
android:process=":remote"

In application hierarchy :

android:persistent="true"

In IntentService onHandleIntent :

setIntentRedelivery(true)

In service onStartCommand :

return START_STICKY

Tried to to restart service if the system destroy or kill it :

override fun onTaskRemoved(rootIntent: Intent) {
        val restartServiceIntent = Intent(applicationContext, this::class.java)
        restartServiceIntent.setPackage(packageName)
        val restartServicePendingIntent = PendingIntent.getService(applicationContext, 1, restartServiceIntent, PendingIntent.FLAG_ONE_SHOT)
        val alarmService = applicationContext.getSystemService(Context.ALARM_SERVICE) as AlarmManager
        alarmService.set(AlarmManager.ELAPSED_REALTIME, SystemClock.elapsedRealtime() + 1000, restartServicePendingIntent)
        Log.e("Service Firestore ", "Task Removed")
        super.onTaskRemoved(rootIntent)
    }

But nothing works OK. What is the best solution to achieve this ? So the purpose is for something to be running on background and listening for Firestore Changes(or something else) even after app killed or removed from tasks , like Viber etc... Maybe they are using foreground service without notification icon ? But i don't think that Android allow us to make this kind of foreground service (without notification)

I have read some articles about WorkManager and as Google says :

Note: WorkManager is intended for tasks that require a guarantee that the system will run them even if the app exits, like uploading app data to a server. It is not intended for in-process background work that can safely be terminated if the app process goes away; for situations like that, we recommend using ThreadPools.

But can't figure out how it is exactly work or how to use for my purpose

Thanks

Have you tried the codelab from google? https://codelabs.developers.google.com/codelabs/android-workmanager/#0 — Raghav Satyadev, Dec 24 '18 at 14:28
have a look at this solution: https://stackoverflow.com/a/50639788/5479863 — Abdul Aziz, Dec 26 '18 at 12:28

score 3 · Answer 1 · answered Dec 20 '18 at 18:04

3

You could use FCM push notification to woke up the device when your app is in not running/foreground.When app receives push notifications, you could start your service to do required task. Again you might not be able to start service when app is in background, for that you might need to run service as foreground service.

answered Dec 20 '18 at 18:04

Ramesh Yankati

1,197
9
13

Hi, thanks for your idea. Yes you'r right about this workaround but i don't think that viber or others use something like this workaround to woke up device. – EAK TEAM Dec 20 '18 at 18:09
And what about services that don't use FCM ? – EAK TEAM Dec 20 '18 at 18:16
I believe whatsApp/Viber should be using FCM.. Now days most of the calling apps are using FCM – Ramesh Yankati Dec 20 '18 at 18:17
I understand , but what about services who for E.x check for something if online or not, if it is stopped can't use FCM. I think FCM is solution only for like messaging app, what for others ? – EAK TEAM Dec 20 '18 at 18:27
@EAKTEAM I am not familiar with Android programming beyond the rudiments, but did you consider it might very well simply not be possible to do what you want? In fact, I hope it is not, because running a background task that survives force killing and doesn’t show any notifications (I hope I understood correctly that is what you want) seems like a security problem. – 11684 Dec 23 '18 at 20:03
@11684 i understand. But for this reason, Google it self why don't implement a service only foe this purpose like FCM ? HAHA i know you cant answer this but just asking – EAK TEAM Dec 23 '18 at 20:05
@EAKTEAM I’m not entirely sure I understand your comment (but for what reason? For what purpose?), but FCM is not a problem since it does show notifications to the user (so it cannot do anything without the user knowing). – 11684 Dec 23 '18 at 20:12

score 2 · Answer 2 · answered Dec 26 '18 at 19:13

WorkManager is now the best solution for doing some work background. Because now Android OS is more restrictive about what it allows to run in the background for a long period of time. From the official documentation... WorkManager chooses an appropriate way to schedule a background task--depending on the device API level and included dependencies, WorkManager might use JobScheduler, Firebase JobDispatcher, or AlarmManager.

Android developer website is a good place to start learning WorkManager https://developer.android.com/topic/libraries/architecture/workmanager/basics.

For a periodic task that will run continuously with a delay in between, You can create a PeriodicWorkRequest and enqueue it on WorkManager instance. https://developer.android.com/topic/libraries/architecture/workmanager/basics#recurring

Another older way is just using AlarmManager. In this way, you don't have to keep running a service in the background all the time. You can set a repeating alarm and when it fires, you can start a service and do what you need.

score 0 · Answer 3 · answered Dec 28 '18 at 14:20

In Android Doze mode documentation they specify the use of FirebaseJobDispatcher which will work even in Doze mode. but this will work only once in every 15 minutes. You can use WorkManager from Android Architecture components which can appropriately use FirebaseJobDispatcher, AlarmManager and JobScheduler on corresponding supported API levels

score 0 · Answer 4 · answered Dec 29 '18 at 14:45

0

You've mentioned that you are familiar with an app that it does what you need. Check the manifest file of the app using https://play.google.com/store/apps/details?id=sk.styk.martin.apkanalyzer (or similar app) or refactor an app. Regards.

answered Dec 29 '18 at 14:45

displayName

105
2
15

Android - Service, IntentService, JobIntentService - they are stoped if app killed

4 Answers4