Difference between START_STICKY and START_REDELIVE

问题:

I am creating a service for my android app, providing data to the service via Intents. The problem is that when the service is destroyed by the system than the intent data provided to it can't be restored, as a result of which my app crashes.

I have heard START_REDELIVER_INTENT will restart my service as soon as there is sufficient memory available restoring the intent data provided to service whereas the START_STICKY will not restore the intent data.

am i right ? or is there something I don't know ?

Also my service is taking forever to restart after it is destroyed by the system.

回答1:

START_STICKY- It will tell the system to create a newest copy of the service, when available memory is sufficient to do, after it retains state and recovers from the low memory. In this process we will loose the results that might have calculated before.

START_REDELIVER_INTENT- It will tell the system to restart and regain the service after the crash and also redeliver the intents that were present at the time of crash happened.

beside this we can have also a little note about START_NOT_STICKY

START_NOT_STICKY- It will tell the system not to worry and bother about to restart the service, even when it is having sufficient available memory.

please visit for more

http://developer.android.com/reference/android/app/Service.html

回答2:

If you are overriding onstartCommand() method, its your responsibility to stop it when not needed by calling stopSelf() or stopService() command.