title: About START_STICKY in Service
body: <p>About using <a href="http://developer.android.com/reference/android/app/Service.html#START_STICKY" rel="nofollow">START_STICKY</a> in Android Service.</p>
  
  <p>official document says:</p>
  
  <blockquote>
    <p>if this service's process is killed while it is started (after
    returning from onStartCommand(Intent, int, int)), then leave it in the
    started state but don't retain this delivered intent. Later the system
    will try to re-create the service. Because it is in the started state,
    it will guarantee to call onStartCommand(Intent, int, int) after
    creating the new service instance;</p>
  </blockquote>
  
  <p>This is understandable, so when an started service's process is killed due to lack of memory, the OS will automatically try to start the service again later. </p>
  
  <p>My question is, if my code starts the service <code>startService(...)</code>, and later stop it(e.g. I have a "STOP" button on my app's UI, when press it, I call <code>stopService(...)</code>), will system later start the service again? Or will the service instance be cleared from memory completely without later being created by system? (No service binding for this scenario)</p>