Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit e6ba9000 authored by Dianne Hackborn's avatar Dianne Hackborn Committed by Steve Kondik
Browse files

Fix bug where onStartCommand() was never called with a null intent.

Also clean up some of the service java docs.

Change-Id: I40e7d713e2393f7ee1db9822da8f07fb6304a9e4
parent 2cea2956
Loading
Loading
Loading
Loading
+3 −3
Original line number Diff line number Diff line
@@ -158,9 +158,9 @@ import java.io.PrintWriter;
 * happens, the system will later try to restart the service.  An important
 * consequence of this is that if you implement {@link #onStartCommand onStartCommand()}
 * to schedule work to be done asynchronously or in another thread, then you
 * may want to use {@link #START_FLAG_REDELIVERY} to have the system
 * re-deliver an Intent for you so that it does not get lost if your service
 * is killed while processing it.
 * may want to write information about that work into persistent storage
 * during the onStartCommand() call so that it does not get lost if the service later
 * gets killed.
 * 
 * <p>Other application components running in the same process as the service
 * (such as an {@link android.app.Activity}) can, of course, increase the