Lines Matching full:strong
92 <p class="caution"><strong>Caution:</strong> A service runs in the
93 main thread of its hosting process—the service does <strong>not</strong> create its own thread
94 and does <strong>not</strong> run in a separate process (unless you specify otherwise). This means
222 <p>To ensure your app is secure, <strong>always use an explicit intent when starting or binding
223 your {@link android.app.Service}</strong> and do not declare intent filters for the service. If
264 <p class="caution"><strong>Caution:</strong> A services runs in the same process as the application
566 <p class="caution"><strong>Caution:</strong> It's important that your application stops its services
666 <p class="caution"><strong>Caution:</strong> The integer ID you give to {@link
763 <p class="note"><strong>Note:</strong> Unlike the activity lifecycle callback methods, you are
767 <p class="img-caption"><strong>Figure 2.</strong> The service lifecycle. The diagram on the left
775 <li>The <strong>entire lifetime</strong> of a service happens between the time {@link
789 <li>The <strong>active lifetime</strong> of a service begins with a call to either {@link
801 <p class="note"><strong>Note:</strong> Although a started service is stopped by a call to
