Cross Reference: /frameworks/base/docs/html/training/sync-adapters/creating-sync-adapter.jd

Lines Matching full:service
66         Bound {@link android.app.Service}.
83         XML that declares the bound service and points to sync adapter-specific metadata.
297     {@link android.app.Service} that passes a special Android binder object from the sync adapter
304     {@link android.app.Service#onCreate onCreate()} method of the service. By instantiating
305     the component in {@link android.app.Service#onCreate onCreate()}, you defer
306     creating it until the service starts, which happens when the framework first tries to run your
313     bound {@link android.app.Service}, instantiates your sync adapter component, and gets the
319  * Define a Service that returns an {@link android.os.IBinder} for the
323 public class SyncService extends Service {
362     <strong>Note:</strong> To see a more detailed example of a bound service for a sync adapter,
543     related to using the component, and you have to declare the bound {@link android.app.Service}
612     Finally, to declare the bound {@link android.app.Service} that the framework uses to
618         &lt;service
627         &lt;/service&gt;
634     is triggered, the system starts the bound service you've created, which in this example is
636 <code><a href="{@docRoot}guide/topics/manifest/service-element.html#exported">android:exported="true"</a></code>
638     {@link android.app.Service}. The attribute
639 <code><a href="{@docRoot}guide/topics/manifest/service-element.html#proc">android:process=":sync"</a></code>
640     tells the system to run the {@link android.app.Service} in a global shared process named
OpenGrok
