Lines Matching full:service
55 <activity>}</a>, <a href="{@docRoot}guide/topics/manifest/service-element.html">{@code
56 <service>}</a>, <a href="{@docRoot}guide/topics/manifest/receiver-element.html">{@code
105 <li>It hosts a {@link android.app.Service} that's bound to the activity that the user is
108 <li>It hosts a {@link android.app.Service} that's running "in the foreground"—the
109 service has called {@link android.app.Service#startForeground startForeground()}.
111 <li>It hosts a {@link android.app.Service} that's executing one of its lifecycle
112 callbacks ({@link android.app.Service#onCreate onCreate()}, {@link android.app.Service#onStart
113 onStart()}, or {@link android.app.Service#onDestroy onDestroy()}).</li>
135 <li>It hosts a {@link android.app.Service} that's bound to a visible (or foreground)
143 <li><b>Service process</b>
144 <p>A process that is running a service that has been started with the {@link
146 higher categories. Although service processes are not directly tied to anything the user sees, they
157 visible, or service process. Usually there are many background processes running, so they are kept
177 components currently active in the process. For example, if a process hosts a service and a visible
178 activity, the process is ranked as a visible process, not a service process.</p>
183 service in process A is bound to a component in process B, process A is always considered at least
186 <p>Because a process running a service is ranked higher than a process with background activities,
188 href="{@docRoot}guide/components/services.html">service</a> for that operation, rather than
190 For example, an activity that's uploading a picture to a web site should start a service to perform
192 Using a service guarantees that the operation will have at least "service process" priority,
379 href="{@docRoot}guide/components/bound-services.html">bound service</a>. When a call on a
384 IBinder} (it's not executed in the UI thread of the process). For example, whereas a service's
385 {@link android.app.Service#onBind onBind()} method would be called from the UI thread of the
386 service's process, methods implemented in the object that {@link android.app.Service#onBind
388 in the pool. Because a service can have more than one client, more than one pool thread can engage
415 <p>To perform IPC, your application must bind to a service, using {@link
