Killing android application from task manager kills services started by app

Question

My application has one activity which starts two services but does not bind them. If I select return button to exit application (I cannot see it in task manager), both of th

Answer 1

As it was already mentioned, it's expected behavior. Killing an app, which started the Service should kill running Service as well. If you want to keep your Service running when app is killed, you should start the Service in a separate process, what can be achieved by the following declaration in the Manifest:

<service
    android:name=".ServiceClassName"
    android:process=":yourappname_background" >
    ...

Reference: https://stackoverflow.com/a/15474347/1150795

Please note that usually app is not killed until a user explicitly kills it from the task/app manager or system kills it due to limited resources, low battery or similar reason. I'm not sure if it's typical use case to handle such things and if you really need to care about that.

Answer 2

I am not sure! But you should give a try to this

Answer 3

That is the intended behavior of Task Managers (and force stop in ManageApplication). What good would stopping an application do if it left running the background work that the application was doing?

There is no way for you to prevent the user from killing your service on a stock version of Android OS

Answer 4

This is the behaviour expected. Services do not run in their own process. When you application is killed, your entire process dies with it.

In the documentation I attached, there is an orange block a page down (unfortunately, I don't think I can link to it :-( ) That will tell you pretty much what a service is in a nutshell.