| /frameworks/base/packages/SystemUI/src/com/android/systemui/statusbar/ |
| D | ExpandableNotificationRow.java | 218 public void setIconAnimationRunning(boolean running) { in setIconAnimationRunning() argument
219 setIconAnimationRunning(running, mPublicLayout); in setIconAnimationRunning()
220 setIconAnimationRunning(running, mPrivateLayout); in setIconAnimationRunning()
222 setIconAnimationRunningForChild(running, mChildrenContainer.getHeaderView()); in setIconAnimationRunning()
227 child.setIconAnimationRunning(running); in setIconAnimationRunning()
230 mIconAnimationRunning = running; in setIconAnimationRunning()
233 private void setIconAnimationRunning(boolean running, NotificationContentView layout) { in setIconAnimationRunning() argument
238 setIconAnimationRunningForChild(running, contractedChild); in setIconAnimationRunning()
239 setIconAnimationRunningForChild(running, expandedChild); in setIconAnimationRunning()
240 setIconAnimationRunningForChild(running, headsUpChild); in setIconAnimationRunning()
[all …]
|
| /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/tests/LegacyRestoreTest/ |
| D | README | 3 Nexus 4 running Android 4.3 (API 18), and so predates the Android 4.4 changes
8 running Android 4.3, but fails to restore correctly on a device running Android 4.4,
13 archive, using the same key, generated on a Nexus 4 running Android 4.4 with a fix
|
| /frameworks/base/core/java/android/widget/ |
| D | ViewFlipper.java | 172 boolean running = mVisible && mStarted && mUserPresent; in updateRunning()
173 if (running != mRunning) { in updateRunning()
174 if (running) { in updateRunning()
180 mRunning = running; in updateRunning()
|
| D | AdapterViewFlipper.java | 236 boolean running = !mAdvancedByHost && mVisible && mStarted && mUserPresent in updateRunning()
238 if (running != mRunning) { in updateRunning()
239 if (running) { in updateRunning()
245 mRunning = running; in updateRunning()
|
| D | Chronometer.java | 292 boolean running = mVisible && mStarted; in updateRunning()
293 if (running != mRunning) { in updateRunning()
294 if (running) { in updateRunning()
301 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/guide/topics/manifest/ |
| D | uses-permission-sdk-23-element.jd | 22 the app is running on a device with <a
25 is running API level 22 or lower, the app does not have the specified
31 device that is running API level 22 or lower, the system prompts the user
38 you can request the permission <em>only</em> if the app is running on
42 grants permissions to the app while it is running.
|
| /frameworks/base/packages/Keyguard/src/com/android/keyguard/ |
| D | KeyguardUpdateMonitorCallback.java | 231 public void onFaceUnlockStateChanged(boolean running, int userId) { } in onFaceUnlockStateChanged() argument
236 public void onFingerprintRunningStateChanged(boolean running) { } in onFingerprintRunningStateChanged() argument
|
| /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/google/play/billing/ |
| D | billing_promotions.jd | 111 running. Furthermore, if a user makes a purchase while the app is running and
141 in the Play Store app while the app is running. Your app can find out right
169 isn't running, your activity's {@link android.app.Activity#onPause onPause()} method must
179 isn't running. This behavior is not necessary and may be annoying to the
181 To find out about any purchases the user made while the app wasn't running,
236 <h4 id="test-app-not-running">App is installed, but not running</h4>
241 following sequence on a device that has your app installed but not running:
256 <h4 id="test-app-running">App is installed and running
260 If the user redeems a promo code for an app that is currently running on the
|
| /frameworks/base/core/tests/coretests/src/com/android/internal/os/ |
| D | BatteryStatsTimeBaseTest.java | 40 public void populate(long uptime, long realtime, boolean running, long pastUptime, in populate() argument
45 mRunning = running; in populate()
54 public void verify(long uptime, long realtime, boolean running, long pastUptime, in verify() argument
59 Assert.assertEquals(running, mRunning); in verify()
|
| /frameworks/base/docs/html/topic/libraries/support-library/ |
| D | index.jd | 86 it is running on Android 4.4, which does not include native support for
92 Support libraries allow apps running on older versions of the Android
94 platform. For example, an app running on a version of Android lower than 5.0
110 behavior depends on what version of Android the app is running on. If the
112 the framework to perform the task. If the app is running on an earlier
116 need to check what version of Android it's running on; instead, the app
179 platform version your app is running on. If the platform supports the
|
| /frameworks/native/cmds/flatland/ |
| D | README.txt | 13 turned off and background services should be stopped before running the
21 frequency when running flatland. At a minimum this includes the CPU, GPU, and
26 If running the benchmark with the clocks locked causes thermal issues, the -s
73 locked and that no heavy-weight services / daemons are running in the
|
| /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/av/media/libstagefright/webm/ |
| D | WebmFrameThread.h | 36 virtual bool running() { return false; } in running() function
74 bool running() { in running() function
|
| /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.
|
| /frameworks/multidex/library/ |
| D | README.android | 4 with multiple dex of applications running on API 4+.
|
| /frameworks/base/docs/html/training/scheduling/ |
| D | index.jd | 40 to keep running until a critical operation finishes.</p>
63 of the lifetime of the application, even if the application is not running and/or the
|
| /frameworks/base/media/mca/filterfw/java/android/filterfw/core/ |
| D | AsyncRunner.java | 231 synchronized private void setRunning(boolean running) { in setRunning() argument
232 isProcessing = running; in setRunning()
|
| /frameworks/base/docs/html/training/permissions/ |
| D | index.jd | 63 Learn how to request permissions from the user while the app is running.
64 This lesson only applies to apps on devices running Android 6.0 (API level
|
| /frameworks/base/docs/html/training/articles/ |
| D | memory.jd | 172 <p>More information about how processes are cached while not running in the foreground and how
194 to perform work in the background, do not keep it running unless
199 running. This makes the process very expensive because the RAM used by the service can’t be used by
203 currently running.</p>
211 <p>Leaving a service running when it’s not needed is <strong>one of the worst memory-management
213 running. Not only will it increase the risk of your app performing poorly due to RAM constraints,
257 <p>Your app is running and not considered killable, but the device is running low on memory and the
262 <p>Your app is running and not considered killable, but the device is running much lower on
268 <p>Your app is still running, but the system has already killed most of the processes in the
271 the system prefers to keep alive, such as those hosting a running service.</p>
[all …]
|
| /frameworks/base/docs/html/about/versions/ |
| D | android-2.3.4.jd | 56 connected peripherals with applications running on the platform. The capability
63 made available to devices running Android 2.3.4 by means of an optional external
74 running Android 3.1, if those devices support USB accessories. </p>
102 3.1. An Android-powered device running Android 2.3.4 can not function as a USB
114 <li>An actual hardware device running Android 2.3.4 (or Android 3.1) with USB
|
| /frameworks/base/docs/html/training/backup/ |
| D | index.jd | 30 on devices running Android 6.0, and those running Android 5.1 (API level
|
| /frameworks/base/core/tests/systemproperties/ |
| D | run_core_systemproperties_test.sh | 12 echo You must lunch before running this test.
|