Searched refs:worker (Results 1 – 18 of 18) sorted by relevance
/frameworks/base/docs/html/training/articles/ |
D | perf-anr.jd | 56 worker thread and do most of the work there. This keeps the UI thread (which drives the user 91 resizing bitmaps should be done in a worker thread (or in the case of databases 94 <p>The most effecive way to create a worker thread for longer 131 <p>To execute this worker thread, simply create an instance and 148 be sure that your UI thread does not block while waiting for the worker thread to 150 {@link java.lang.Thread#sleep Thread.sleep()}. Instead of blocking while waiting for a worker 163 tasks via worker threads, your 187 <li>For games specifically, do calculations for moves in a worker
|
/frameworks/base/docs/html/guide/components/ |
D | processes-and-threads.jd | 182 simply create a worker thread—particularly if the operation will likely outlast the activity. 224 your UI from a worker thread—you must do all manipulation to your user interface from the UI 237 "worker" threads).</p> 256 android.widget.ImageView} from the worker thread instead of the UI thread. This can result in 293 difficult to maintain. To handle more complex interactions with a worker thread, you might consider 294 using a {@link android.os.Handler} in your worker thread, to process messages delivered from the UI 296 which simplifies the execution of worker thread tasks that need to interact with the UI.</p> 302 interface. It performs the blocking operations in a worker thread and then publishes the results on 322 /** The system calls this to perform work in a worker thread and 337 part that should be done on a worker thread and the part that should be done on the UI thread.</p> [all …]
|
D | services.jd | 278 <dd>This is a subclass of {@link android.app.Service} that uses a worker thread to handle all 298 <li>Creates a default worker thread that executes all intents delivered to {@link 324 * constructor with a name for the worker thread. 331 * The IntentService calls this method from the default worker thread with 359 that the {@link android.app.IntentService} can properly handle the life of the worker thread.</p> 391 android.app.IntentService}. That is, for each start request, it uses a worker thread to perform the
|
D | fragments.jd | 73 activity layout; you may also use a fragment without its own UI as an invisible worker for the 366 <p>For an example activity that uses a fragment as a background worker, without a UI, see the {@code
|
D | bound-services.jd | 130 <p>This is the preferred technique when your service is merely a background worker for your own
|
/frameworks/av/media/libstagefright/webm/ |
D | WebmFrameThread.cpp | 34 WebmFrameThread *worker = reinterpret_cast<WebmFrameThread*>(arg); in wrap() local 35 worker->run(); in wrap()
|
/frameworks/base/docs/html/training/volley/ |
D | simple.jd | 30 {@code Request} objects. The {@code RequestQueue} manages worker threads for running the 104 parsse the response on the worker thread, writes the response to cache, and posts the parsed 107 <p>Note that expensive operations like blocking I/O and parsing/decoding are done on worker
|
D | request-custom.jd | 87 Volley calls {@code parseNetworkResponse()} from a worker thread. This ensures that
|
D | request.jd | 54 expensive image operations (decoding, resizing) automatically happen on a worker thread.</li>
|
/frameworks/base/services/core/java/com/android/server/notification/ |
D | EventConditionProvider.java | 72 public EventConditionProvider(Looper worker) { in EventConditionProvider() argument 74 mWorker = new Handler(worker); in EventConditionProvider()
|
/frameworks/base/services/core/java/com/android/server/ |
D | AssetAtlasService.java | 373 ComputeWorker worker = new ComputeWorker(start, end, step, in computeBestConfiguration() local 375 new Thread(worker, "Atlas Worker #" + (i + 1)).start(); in computeBestConfiguration()
|
/frameworks/base/docs/html/training/improving-layouts/ |
D | smooth-scrolling.jd | 40 <p>Using a background thread ("worker thread") removes strain from the main thread so it can focus
|
/frameworks/base/docs/html/training/displaying-bitmaps/ |
D | process-bitmap.jd | 125 back to the worker task. In this case, a {@link android.graphics.drawable.BitmapDrawable} is used so
|
/frameworks/base/docs/html/tools/debugging/ |
D | systrace.jd | 234 sprinkling in a few per frame, or per worker thread task can go a long way to adding context to a
|
/frameworks/base/docs/html/training/location/ |
D | display-address.jd | 109 The intent service handles an intent asynchronously on a worker thread, and
|
/frameworks/base/docs/html/distribute/essentials/ |
D | optimizing-your-app.jd | 323 operations off the main thread to worker threads. Android offers built-in
|
/frameworks/base/docs/html/about/versions/ |
D | android-3.0.jd | 64 <p>You can also use a fragment without providing a UI and instead use the fragment as a worker 306 fragments to dynamically load data from worker threads. The {@link
|
/frameworks/base/services/core/java/com/android/server/am/ |
D | ActivityManagerService.java | 12425 Thread worker = new Thread("Error dump: " + dropboxTag) { in addErrorToDropBox() local 12477 worker.run(); in addErrorToDropBox() 12479 worker.start(); in addErrorToDropBox()
|