Lines Matching refs:started
72 <dd>A service is "started" when an application component (such as an activity) starts it by
73 calling {@link android.content.Context#startService startService()}. Once started, a service
74 can run in the background indefinitely, even if the component that started it is destroyed. Usually,
75 a started service performs a single operation and does not return a result to the caller.
88 service can work both ways—it can be started (to run indefinitely) and also allow binding.
93 <p>Regardless of whether your application is started, bound, or both, any application component
140 requests that the service be started, by calling {@link android.content.Context#startService
141 startService()}. Once this method executes, the service is started and can run in the
179 Otherwise, if the service was started and is long-running, then the system will lower its position
181 killing—if your service is started, then you must design it to gracefully handle restarts
255 <p>A started service is one that another component starts by calling {@link
259 <p>When a service is started, it has a lifecycle that's independent of the
260 component that started it and the service can run in the background indefinitely, even if
261 the component that started it is destroyed. As such, the service should stop itself when its job
284 <p>Traditionally, there are two classes you can extend to create a started service:</p>
305 <p>Because most started services don't need to handle multiple requests simultaneously
346 * the intent that started the service. When this method returns, IntentService
399 implementation of a started service very simple. If, however, you require your service to
559 <p>A started service must manage its own lifecycle. That is, the system does not stop or
609 (you do <em>not</em> need to stop a bound service in the way you must when the service is started
624 complicated than a started service, so the bound service discussion appears in a separate
706 <li>A started service
724 started with {@link android.content.Context#startService startService()}. For example, a background
725 music service could be started by calling {@link android.content.Context#startService
808 <p>If the service is started, the active lifetime ends the same time that the entire lifetime
815 <p class="note"><strong>Note:</strong> Although a started service is stopped by a call to
825 in mind that any service, no matter how it's started, can potentially allow clients to bind to it.
826 So, a service that was initially started with {@link android.app.Service#onStartCommand