They are related to services. We all know that services continue to run in the background, and they also consume some memory to execute.
So, since more applications are running on the Android device, the device’s memory continues to decline, and when the time comes when the device’s memory becomes critically low, the android system begins to terminate the processes to free up the occupied memory by the processes.
But you can perform some important tasks with services, which can also be terminated as the service stops. therefore, these concepts should tell the Android system what action you want to perform when the device’s memory is stabilized and when it is ready to restart services.
The simplest explanation for this might be
START_STICKY- informs the system about creating a new copy of the service when a sufficient amount of memory is available, after it is restored from low memory. Here you will lose results that could be calculated earlier.
START_NOT_STICKY- tells the system not to bother restarting the service, even if it has enough memory.
START_REDELIVER_INTENT- tells the system to restart the service after the failure, and also to renew the intentions that were present during the failure.
Sahil Mahajan Mj Dec 27 '12 at 12:35 2012-12-27 12:35
source share