| /frameworks/base/tests/FrameworkPerf/src/com/android/frameworkperf/ |
| D | TestService.java | 390 private void threadFinished(boolean foreground) { in threadFinished() argument
392 if (foreground) { in threadFinished()
445 void onInit(Context context, boolean foreground) { in onInit() argument
576 void onInit(Context context, boolean foreground) { in onInit() argument
601 void onInit(Context context, boolean foreground) { in onInit() argument
621 void onInit(Context context, boolean foreground) { in onInit() argument
666 void onInit(Context context, boolean foreground) { in onInit() argument
684 void onInit(Context context, boolean foreground) { in onInit() argument
702 void onInit(Context context, boolean foreground) { in onInit() argument
724 void onInit(Context context, boolean foreground) { in onInit() argument
[all …]
|
| /frameworks/support/v7/palette/src/android/support/v7/graphics/ |
| D | ColorUtils.java | 66 private static double calculateContrast(int foreground, int background) {
70 if (Color.alpha(foreground) < 255) {
72 foreground = compositeColors(foreground, background);
75 final double luminance1 = calculateLuminance(foreground) + 0.05;
88 private static int findMinimumAlpha(int foreground, int background, double minContrastRatio) {
94 int testForeground = modifyAlpha(foreground, 255);
110 testForeground = modifyAlpha(foreground, testAlpha);
|
| /frameworks/base/docs/html/guide/topics/connectivity/nfc/ |
| D | advanced-nfc.jd | 14 <li><a href="#foreground-dispatch">Using the Foreground Dispatch System</a></li>
20 writing to NFC tags, and foreground dispatching, which allows an application in the foreground to
220 <h2 id="foreground-dispatch">Using the Foreground Dispatch System</h2>
222 <p>The foreground dispatch system allows an activity to intercept an intent and claim
225 intents to your application. To enable the foreground dispatch system:</p>
239 <li>Declare intent filters to handle the intents that you want to intercept. The foreground
242 not match, the foreground dispatch system falls back to the intent dispatch system.
271 foreground dispatch when the activity loses ({@link android.app.Activity#onPause onPause()})
274 the main thread and only when the activity is in the foreground (calling in {@link
|
| D | nfc.jd | 313 includes comprehensive reader/writer support as well as foreground NDEF pushing, and API level
727 <ahref="{@docRoot}guide/topics/connectivity/nfc/advanced-nfc.html#foreground-dispatch">foreground
728 dispatch system</a>, which allows a foreground activity to have priority when an NFC tag is
729 discovered. With this method, the activity must be in the foreground to override AARs and the
763 application that wants to beam data to another device must be in the foreground and the device
792 <li>The activity that is beaming the data must be in the foreground. Both devices must have
807 in the foreground, the standard intent dispatch system is disabled. However, if your activity also
808 enables <a href="{@docRoot}guide/topics/connectivity/nfc/advanced-nfc.html#foreground-dispatch">
809 foreground dispatching</a>, then it can still scan tags that match the intent filters set in the
810 foreground dispatching.</p>
|
| /frameworks/base/docs/html/guide/topics/processes/ |
| D | process-lifecycle.jd | 41 <li>A <strong>foreground process</strong> is one that is required for
43 cause its containing process to be considered foreground in different
44 ways. A process is considered to be in the foreground if any of the
67 that is visible to the user on-screen but not in the foreground (its
69 occur, for example, if the foreground Activity is displayed as a dialog
72 required to keep all foreground processes running.
81 running unless there is not enough memory to retain all foreground and visible process.
|
| /frameworks/base/libs/androidfw/tests/data/system/ |
| D | R.h | 26 foreground = 0x01010001, // default enumerator
|
| /frameworks/base/core/java/android/widget/ |
| D | FrameLayout.java | 601 final Drawable foreground = mForeground; in draw() local
618 Gravity.apply(mForegroundGravity, foreground.getIntrinsicWidth(), in draw()
619 foreground.getIntrinsicHeight(), selfBounds, overlayBounds, in draw()
621 foreground.setBounds(overlayBounds); in draw()
624 foreground.draw(canvas); in draw()
|
| /frameworks/base/services/core/java/com/android/server/am/ |
| D | EventLogTags.logtags | 26 # An activity has been resumed into the foreground but was not already running:
28 # An activity has been resumed and is now in the foreground:
52 # An activity has been relaunched, resumed, and is now in the foreground:
|
| /frameworks/base/docs/html/guide/components/ |
| D | processes-and-threads.jd | 91 process is considered to be in the foreground if any of the following conditions are true:</p>
101 <li>It hosts a {@link android.app.Service} that's running "in the foreground"—the
112 <p>Generally, only a few foreground processes exist at any given time. They are killed only as
114 point, the device has reached a memory paging state, so killing some foreground processes is
118 <p>A process that doesn't have any foreground components, but still can
123 <li>It hosts an {@link android.app.Activity} that is not in the foreground, but is still
125 This might occur, for example, if the foreground activity started a dialog, which allows the
128 <li>It hosts a {@link android.app.Service} that's bound to a visible (or foreground)
133 is required to keep all foreground processes running. </p>
142 to retain them along with all foreground and visible processes. </p>
[all …]
|
| D | tasks-and-back-stack.jd | 84 launcher (or a shortcut on the Home screen), that application's task comes to the foreground. If no
116 in the foreground, while Task A is in the background, waiting to be resumed.</p>
127 another task takes place, as shown in figure 2. A task can then return to the "foreground" so users
136 foreground—all three activities in its stack are intact and the activity at the top of the
171 to the foreground and resumes the activity at the top of the stack.</li>
364 that activity exists in a background task, that whole task is brought to the foreground. At this
396 starting, that task is brought to the foreground with its last state restored and the activity
485 for, when that task comes to the foreground.</p>
490 task as your activity. However, when the travel application's task comes to the foreground, the
|
| D | services.jd | 170 href="#Foreground">run in the foreground</a> (discussed later), then it will almost never be killed.
640 <p>A foreground service is a service that's considered to be something the
642 foreground service must provide a notification for the status bar, which is placed under the
644 either stopped or removed from the foreground.</p>
647 foreground, because the user is explicitly aware
651 <p>To request that your service run in the foreground, call {@link
670 <p>To remove the service from the foreground, call {@link
673 service. However, if you stop the service while it's still running in the foreground, then the
|
| D | activities.jd | 355 <dd>The activity is in the foreground of the screen and has user focus. (This state is
359 <dd>Another activity is in the foreground and has focus, but this one is still visible. That is,
452 <li><p>The <b>foreground lifetime</b> of an activity happens between the call to {@link
455 user input focus. An activity can frequently transition in and out of the foreground—for
515 to the foreground, or {@code onStop()} if it becomes hidden.</p></td>
611 foreground (when it "resumes"), those changes are still there.</p>
|
| /frameworks/base/core/java/android/content/res/ |
| D | StringBlock.java | 322 private static CharacterStyle getColor(String color, boolean foreground) { in getColor() argument
332 if (foreground) { in getColor()
343 if (foreground) { in getColor()
|
| /frameworks/base/docs/html/tools/testing/ |
| D | what_to_test.jd | 27 re-start the foreground Activity. You should consider testing the following:
48 the foreground Activity. Besides testing that the application maintains the UI and its
|
| /frameworks/base/docs/html/training/wearables/data-layer/ |
| D | index.jd | 53 <dt><b>DataListener</b> (for foreground activities)</dt>
57 is in the foreground. Using this instead of the
|
| /frameworks/native/opengl/tests/hwc/ |
| D | hwcCommit.cpp | 1295 Rectangle foreground(foregroundFormat, startDim, startDim); in numOverlapping() local
1296 foreground.displayFrame.left += 5; in numOverlapping()
1297 foreground.displayFrame.top += 5; in numOverlapping()
1298 foreground.displayFrame.right += 5; in numOverlapping()
1299 foreground.displayFrame.bottom += 5; in numOverlapping()
1301 rectList.push_back(foreground); in numOverlapping()
|
| /frameworks/base/docs/html/training/run-background-service/ |
| D | index.jd | 37 Unless you specify otherwise, most of the operations you do in an app run in the foreground on
|
| /frameworks/base/docs/html/guide/topics/media/ |
| D | mediaplayer.jd | 24 <li><a href="#foregroundserv">Running as a foreground service</a></li>
399 <h3 id="foregroundserv">Running as a foreground service</h3>
409 In this case, the service should run as a "foreground service." A
410 foreground service holds a higher level of importance within the system—the system will
412 in the foreground, the service also must provide a status bar notification to ensure that users are
416 <p>In order to turn your service into a foreground service, you must create a
435 <p>While your service is running in the foreground, the notification you
445 <p class="img-caption"><strong>Figure 1.</strong> Screenshots of a foreground service's
449 <p>You should only hold on to the "foreground service" status while your
|
| /frameworks/base/docs/html/training/basics/activity-lifecycle/ |
| D | pausing.jd | 35 <p>During normal app use, the foreground activity is sometimes obstructed by other
120 <p>Be aware that the system calls this method every time your activity comes into the foreground,
|
| D | index.jd | 42 activity starts for the first time, it comes to the foreground of the system and receives user
|
| D | recreating.jd | 34 currently stopped and hasn't been used in a long time or the foreground activity requires more
49 the foreground activity because the screen configuration has changed and your activity might need to
|
| D | starting.jd | 54 point at which the activity is running in the foreground and the user can interact with it.</p>
119 <dd>In this state, the activity is in the foreground and the user can interact with it.
123 other activity that's in the foreground is semi-transparent or doesn't cover the entire screen. The
|
| D | stopping.jd | 41 activity in your app that's currently in the foreground is stopped. If the user returns to your
130 <p>When your activity comes back to the foreground from the stopped state, it receives a call to
|
| /frameworks/base/docs/html/google/play-services/ |
| D | location.jd | 53 … <em>Versatility</em>: Meets a wide range of needs, from foreground uses that need highly accurate
|
| /frameworks/base/core/java/android/app/ |
| D | ActivityManager.java | 1423 public boolean foreground; field in ActivityManager.RunningServiceInfo
1515 dest.writeInt(foreground ? 1 : 0); in writeToParcel()
1532 foreground = source.readInt() != 0; in readFromParcel()
|