Lines Matching full:service
285 mechanism where authentication is possible such as with a {@link android.app.Service}. (Even
297 <p>The <acronym title="Short Message Service">SMS</acronym> protocol was primarily designed for
382 know why a component or service requires a personal information, don?t
459 supplied by the user, and then use a short-lived, service-specific
464 {@link android.accounts.AccountManager} class to invoke a cloud-based service and do not store
521 android.app.Service}, and {@link android.content.BroadcastReceiver}.
530 href="{@docRoot}guide/topics/manifest/service-element.html#exported">{@code <service>}</a>
572 confirm that it is properly formatted for the invoked receiver, service, or
580 <p>A {@link android.app.Service} is often used to supply functionality for other applications to
581 use. Each service class must have a corresponding <a
582 href="{@docRoot}guide/topics/manifest/service-element.html">{@code <service>}</a> declaration in its
586 application. However, if you add any intent filters to the service declaration, then it is exported
588 href="{@docRoot}guide/topics/manifest/service-element.html#exported">{@code
591 href="{@docRoot}guide/topics/manifest/service-element.html#prmsn">{@code android:permission}</a>
596 able to start, stop, or bind to the service.</p>
598 <p>A service can protect individual IPC calls into it with permissions, by
618 application manifest for the {@link android.app.Service} or {@link
629 before accessing a service on behalf of the caller, as the identify of your
631 by a {@link android.app.Service}, the {@link
633 invocation may fail if you do not have permission to access the given service.
638 <p>For more information about performing IPC with a service, see
