CODEWITHSUNDEEP
android
Cheok Yan Cheng
Cheok Yan Cheng

Reputation: 42690

IntentService will be killed after I stop my application

I am referring to android design considerations: AsyncTask vs Service (IntentService?)

According to the discussion, AsyncTask does not suit, because it is tightly "bound" to your Activity

So, I launch a Thread (I assume AsyncTask and Thread belong to same category), have an infinity running loop in it and did the following testing.

So, I expect after I change from Thread to Service, my Service will keep alive even after I quit or kill my app. 

Intent intent = new Intent(this, SyncWithCloudService.class);
startService(intent);

public class SyncWithCloudService extends IntentService {
    public SyncWithCloudService() {
        super("SyncWithCloudService");
    }

    @Override
    protected void onHandleIntent(Intent intent) {
        int i = 0;
        while (true) {
            Log.i("CHEOK", "Service i is " + (i++));
            try {
                Thread.sleep(1000);
            } catch (InterruptedException ex) {
                Log.i("CHEOK", "", ex);
            }
        }
    }
}

    // Doesn't matter whether I use "android:process" or not.
    <service 
        android:name="com.xxx.xml.SyncWithCloudService" 
        android:process=".my_process" >
    </service>

However, my finding is that,

It seems that the behaviour of Service and Thread are the same. So, why I should use Service instead of Thread? Is there anything I had missed out? I thought my Service suppose to keep running, even after I kill my app?

Upvotes: 16

Views: 15822

Answers (5)

ElOjcar
ElOjcar

Reputation: 301

You can invoke setIntentRedelivery(true) in the constructor of the IntentService

Upvotes: 1

Ismael
Ismael

Reputation: 357

In your IntentService you can override onStartCommand() returning START_REDELIVER_INTENT

Then if killed, your service will be restarted automatically by the system after some time with the same Intent.

Be sure to call the super implementation on onStartCommand() like this:

@Override
public int onStartCommand(Intent intent, int flags, int startId) {
    super.onStartCommand(intent,flags,startId);
    return START_REDELIVER_INTENT;
}

Upvotes: 1

Viswanath Lekshmanan
Viswanath Lekshmanan

Reputation: 10083

Actually there are different kinds of services you can implement. Use a Service instead of IntentService. There you need to look at START_STICKY , START_NOT_STICKY and START_REDELIVER_INTENT you can keep your service running in background even if your activity dies. Android services

Upvotes: 4

David Wasser
David Wasser

Reputation: 95578

Nope. Service will stop running when you kill your application. When you kill your application all components of it are killed (activities, services, etc.).

In general the behaviour of Thread and Service are similar. However, If you start a Thread from an Activity and then shutdown the activity (ie: quit your application), eventually Android will notice that your process has no active components in it (since Android doesn't recognize your Thread as an active component) and it will just kill your process, thereby killing the thread.

However, if you have a Service running, then Android will notice that you have a service running and not kill it so readily. However, it is still possible that Android will kill your service process if it isn't "in use".

Upvotes: 12

tolgap
tolgap

Reputation: 9778

You are using startService(). The Service will run until it's code is done, or until Android decides it should be killed. Look up on bound services. On your Activity.onDestroy() you should call unbindService().

Upvotes: 1

Related Questions