| /frameworks/base/tests/SslLoad/src/com/android/sslload/ |
| D | SslLoad.java | 49 private boolean running = false; field in SslLoad
71 running = false; in onStop()
77 running = !running; in onClick()
78 button.setText(running ? "STOP" : "GO"); in onClick()
79 if (running) { in onClick()
89 while (!running) { in run()
|
| /frameworks/base/services/java/com/android/server/am/ |
| D | DeviceMonitor.java | 45 private boolean running = false; field in DeviceMonitor
202 running = false; in stop()
209 while (!running) { in waitForStart()
220 if (!running) { in startMonitoring()
221 running = true; in startMonitoring()
|
| /frameworks/base/tests/CoreTests/android/core/ |
| D | TestWebServer.java | 222 boolean running = false; field in TestWebServer.AcceptThread
253 running = true; in run()
255 while (running) { in run()
260 running = false; in run()
279 running = false; in run()
283 running = false; in run()
291 running = false; in close()
349 boolean running = false; field in TestWebServer.Worker
375 running = false; in close()
385 running = true; in run()
[all …]
|
| /frameworks/base/core/java/android/widget/ |
| D | ViewFlipper.java | 173 boolean running = mVisible && mStarted && mUserPresent; in updateRunning()
174 if (running != mRunning) { in updateRunning()
175 if (running) { in updateRunning()
182 mRunning = running; in updateRunning()
|
| D | AdapterViewFlipper.java | 222 boolean running = !mAdvancedByHost && mVisible && mStarted && mUserPresent in updateRunning()
224 if (running != mRunning) { in updateRunning()
225 if (running) { in updateRunning()
232 mRunning = running; in updateRunning()
|
| D | Chronometer.java | 254 boolean running = mVisible && mStarted; in updateRunning()
255 if (running != mRunning) { in updateRunning()
256 if (running) { in updateRunning()
263 mRunning = running; in updateRunning()
|
| /frameworks/base/docs/html/guide/topics/processes/ |
| D | process-lifecycle.jd | 6 be run, and will remain running until it is no longer needed <em>and</em>
12 that the system knows are running, how important these things are to the user,
31 it terminates the spawned thread running in the process. The solution to this problem
36 places each process into an "importance hierarchy" based on the components running in
47 <li> It is running an {@link android.app.Activity}
50 <li> It has a {@link android.content.BroadcastReceiver} that is currently running
72 required to keep all foreground processes running.
81 running unless there is not enough memory to retain all foreground and visible process.
91 previous processes types. Usually there are many of these processes running,
93 by the user is the last to be killed when running low on memory.
|
| /frameworks/base/docs/html/tools/help/uiautomator/ |
| D | IAutomationSupport.jd | 10 <p>Provides auxiliary support for running test cases
84 <div class="jd-descrdiv">Allows the running test cases to send out interim status</div>
162 …<div class="jd-tagdata jd-tagdescr"><p>Allows the running test cases to send out interim status</p…
|
| /frameworks/base/docs/html/tools/help/ |
| D | gltracer.jd | 8 <li><a href="#running">Running Tracer</a></li>
23 <p class="note"><strong>Note:</strong> The Tracer tool requires a device running Android 4.1 (API
27 <h2 id="running">Running Tracer</h2>
54 OpenGL ES code. The Tracer tool operates by connecting to a device running Android 4.1 (API Level
55 16) or higher that is running the application you want to analyze. The Tracer tool captures trace
56 information while the application is running and saves it to a {@code .gltrace} file for
|
| /frameworks/base/docs/html/training/multiple-threads/ |
| D | communicate-ui.jd | 33 from the task to objects running on the user interface (UI) thread. This feature allows your
38 objects; this thread is called the UI thread. Only objects running on the UI thread have access
40 <em>aren't</em> running on your UI thread, they don't have access to UI objects. To move data
42 running on the UI thread.
94 To move data from a task object running on a background thread to an object on the UI thread,
98 the {@link android.os.Handler}. Because {@link android.os.Handler} is running on the UI thread,
103 For example, here's a {@link java.lang.Runnable}, running on a background thread, that decodes a
144 because you're not currently running on the UI thread.
224 running on the UI thread, it can safely move the {@link android.graphics.Bitmap} to the
|
| /frameworks/base/docs/html/tools/debugging/ |
| D | systrace.jd | 16 <li><a href="#running">Running a trace</a></li>
21 <li><a href="#long-processes">Long running processes</a></li>
55 running Android 4.1 and higher, such as the report in figure 1.</p>
60 for a running application and related Android system processes.
67 must have a device running Android 4.1 or higher. Setup the device for
130 <h3 id="running">Running a trace</h3>
164 <h3 id="long-processes">Long running processes</h3>
173 <strong>Figure 2.</strong> Excerpt from a trace of a smoothly running application with a regular
185 <p>Long running processes show up as thicker than usual execution bars in a trace. These thicker
190 also look at other processes running at the same time, looking for a thread in one process that is
[all …]
|
| D | debugging-projects-cmdline.jd | 40 environment yourself by running a few tools that are provided in the Android SDK. To begin
50 application running under the device that you installed it to.</li>
63 <p>Your IDE should attach to your application running on the emulator, showing you its threads
69 system to kill the selected application if it is currently running. You can use this to kill your
|
| /frameworks/base/docs/html/training/backward-compatible-ui/ |
| D | using-component.jd | 133 <p>When running the application, this code inflates the correct activity layout and instantiates ei…
135 <p>Below are two screenshots of this implementation running on an Android 2.3 and Android 4.0 devic…
138 …alt="Example screenshot of tabs running on an Android 2.3 device (using TabHelperEclair)." width="…
141 …alt="Example screenshots of tabs running on an Android 4.0 device (using TabHelperHoneycomb)." wid…
143 …trong>Figure 1.</strong> Example screenshots of backward-compatible tabs running on an Android 2.3…
|
| /frameworks/base/docs/html/google/gcm/ |
| D | demo.jd | 33 …k in your Android application. This tutorial walks you through setting up and running the demo.</p>
51 …<li>A running web server compatible with Servlets API version 2.5, such as <a href="http://tomcat.…
60 <li>Emulator (or device) running Android 2.2 with Google APIs.</li>
78 …aging for Android Library</strong> in the SDK Manager, make sure you are running version 20 or hig…
83 <li>Generate the server's WAR file by running <code>ant war</code>:</li>
103 …<li>Deploy the <code>dist/gcm-demo.war</code> to your running server. For instance, if you're usin…
108 <p class="note"><strong>Note:</strong> You can get the IP by running <code>ifconfig</code> on Linux…
151 [java] INFO: The server is running at http://192.168.1.10:8080/
153 [java] INFO: The admin console is running at http://192.168.1.10:8080/_ah/admin
158 …<p class="note"><strong>Note:</strong> You can get the IP by running <code>ifconfig</code> on Linu…
[all …]
|
| /frameworks/base/tests/FrameworkPerf/src/com/android/frameworkperf/ |
| D | TestService.java | 292 boolean running; in run()
295 running = mBackgroundOp.onRun(); in run()
297 } while (evalRepeat(running, true) && running); in run()
305 boolean running; in run()
308 running = mForegroundOp.onRun(); in run()
310 } while (evalRepeat(true, running) && running); in run()
|
| /frameworks/base/docs/html/guide/faq/ |
| D | framework.jd | 14 running before starting it?</a></li>
47 long-running code, to avoid blocking the main UI thread.</p>
100 <p>Even while an application appears to continue running, the system
127 <h2>How can I check if an Activity is already running before starting
130 <p>The general mechanism to start a new activity if its not running—
131 or to bring the activity stack to the front if is already running in the
|
| /frameworks/testing/androidtestlib/ |
| D | README | 1 an currently experimental static library for running JUnit4 tests on Android.
|
| /frameworks/base/docs/html/training/run-background-service/ |
| D | create-service.jd | 34 The {@link android.app.IntentService} class provides a straightforward structure for running
35 an operation on a single background thread. This allows it to handle long-running operations
49 Work requests run sequentially. If an operation is running in an
54 An operation running on an {@link android.app.IntentService} can't be interrupted.
|
| D | index.jd | 34 a special thread called the UI thread. This can cause problems, because long-running operations
37 help you off-load operations onto a separate thread running in the background. The most useful
|
| /frameworks/base/docs/html/about/ |
| D | flexible.jd | 20 <p>Android apps are flexible and easily adapt to the device on which they are running. Although the
23 appropriate resources when running your app, based on the current device’s configuration.</p>
|
| /frameworks/base/docs/html/tools/devices/ |
| D | emulator.jd | 90 many Android platforms and hardware permutations. Once your application is running on
194 dialog, in the Target tab. When the emulator is running, you can issue
215 When the emulator is running, you can also connect to the emulator instance's
283 <li>If you are running the emulator from the command line, just include the {@code -gpu on}
290 <li>If you are running the emulator from Eclipse, run your Android application using an AVD with
313 <p>Many modern CPUs provide extensions for running virtual machines (VMs) more efficiently. Taking
333 within these additional requirements of running an emulator inside an accelerated virtual
343 <li><strong>Other VM Drivers</strong> - If you are running another virtualization technology on
345 hosting software before running an accelerated emulator.</li>
359 <p>If your development environment meets all of the requirements for running a VM-accelerated
[all …]
|
| /frameworks/base/docs/html/about/versions/ |
| D | android-2.3.4.jd | 55 connected peripherals with applications running on the platform. The capability
62 made available to devices running Android 2.3.4 by means of an optional external
73 running Android 3.1, if those devices support USB accessories. </p>
101 3.1. An Android-powered device running Android 2.3.4 can not function as a USB
113 <li>An actual hardware device running Android 2.3.4 (or Android 3.1) with USB
|
| /frameworks/base/media/mca/filterfw/java/android/filterfw/core/ |
| D | AsyncRunner.java | 239 synchronized private void setRunning(boolean running) { in setRunning() argument
240 isProcessing = running; in setRunning()
|
| /frameworks/base/core/tests/systemproperties/ |
| D | run_core_systemproperties_test.sh | 12 echo You must lunch before running this test.
|
| /frameworks/base/docs/html/training/articles/ |
| D | perf-anr.jd | 55 interface event loop) running and prevents the system from concluding that your code
87 Potentially long running operations such as network
104 // Do the long-running work in here
159 called in the UI thread, applications should avoid potentially long-running
163 potentially long running action needs to be taken in response to an intent
168 long running operations such as network or database operations that
|