| /frameworks/base/tests/FrameworkPerf/src/com/android/frameworkperf/ |
| D | TestService.java | 374 private void threadFinished(boolean foreground) { in threadFinished() argument
376 if (foreground) { in threadFinished()
429 void onInit(Context context, boolean foreground) { in onInit() argument
560 void onInit(Context context, boolean foreground) { in onInit() argument
585 void onInit(Context context, boolean foreground) { in onInit() argument
605 void onInit(Context context, boolean foreground) { in onInit() argument
650 void onInit(Context context, boolean foreground) { in onInit() argument
668 void onInit(Context context, boolean foreground) { in onInit() argument
686 void onInit(Context context, boolean foreground) { in onInit() argument
708 void onInit(Context context, boolean foreground) { in onInit() argument
[all …]
|
| /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
721 href="{@docRoot}guide/topics/connectivity/nfc/advanced-nfc.html#foreground-dispatch">foreground dis…
722 system</a>, which allows a foreground activity to have priority when an NFC tag is discovered.
723 With this method, the activity must be in the foreground to
757 application that wants to beam data to another device must be in the foreground and the device
786 <li>The activity that is beaming the data must be in the foreground. Both devices must have
801 in the foreground, the standard intent dispatch system is disabled. However, if your activity also
802 … <a href="{@docRoot}guide/topics/connectivity/nfc/advanced-nfc.html#foreground-dispatch">foreground
803 dispatching</a>, then it can still scan tags that match the intent filters set in the foreground
|
| /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/core/java/android/widget/ |
| D | FrameLayout.java | 470 final Drawable foreground = mForeground; in draw() local
487 Gravity.apply(mForegroundGravity, foreground.getIntrinsicWidth(), in draw()
488 foreground.getIntrinsicHeight(), selfBounds, overlayBounds, in draw()
490 foreground.setBounds(overlayBounds); in draw()
493 foreground.draw(canvas); in draw()
|
| /frameworks/base/services/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 | 96 process is considered to be in the foreground if any of the following conditions are true:</p>
106 <li>It hosts a {@link android.app.Service} that's running "in the foreground"—the
117 <p>Generally, only a few foreground processes exist at any given time. They are killed only as
119 point, the device has reached a memory paging state, so killing some foreground processes is
123 <p>A process that doesn't have any foreground components, but still can
128 <li>It hosts an {@link android.app.Activity} that is not in the foreground, but is still
130 This might occur, for example, if the foreground activity started a dialog, which allows the
133 <li>It hosts a {@link android.app.Service} that's bound to a visible (or foreground)
138 is required to keep all foreground processes running. </p>
147 to retain them along with all foreground and visible processes. </p>
[all …]
|
| D | tasks-and-back-stack.jd | 90 launcher (or a shortcut on the Home screen), that application's task comes to the foreground. If no
122 in the foreground, while Task A is in the background, waiting to be resumed.</p>
133 another task takes place, as shown in figure 2. A task can then return to the "foreground" so users
142 foreground—all three activities in its stack are intact and the activity at the top of the
177 to the foreground and resumes the activity at the top of the stack.</li>
368 that activity exists in a background task, that whole task is brought to the foreground. At this
400 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 | 178 href="#Foreground">run in the foreground</a> (discussed later), then it will almost never be killed.
667 <p>A foreground service is a service that's considered to be something the
669 foreground service must provide a notification for the status bar, which is placed under the
671 either stopped or removed from the foreground.</p>
674 foreground, because the user is explicitly aware
678 <p>To request that your service run in the foreground, call {@link
694 <p>To remove the service from the foreground, call {@link
697 service. However, if you stop the service while it's still running in the foreground, then the
703 5). In order to run your service in the foreground on older versions of the platform, you must
|
| D | activities.jd | 360 <dd>The activity is in the foreground of the screen and has user focus. (This state is
364 <dd>Another activity is in the foreground and has focus, but this one is still visible. That is,
457 <li><p>The <b>foreground lifetime</b> of an activity happens between the call to {@link
460 user input focus. An activity can frequently transition in and out of the foreground—for
520 to the foreground, or {@code onStop()} if it becomes hidden.</p></td>
616 foreground (when it "resumes"), those changes are still there.</p>
|
| /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/guide/basics/ |
| D | appmodel.jd | 24 item that can be brought to the foreground in front of other
62 to the foreground instead of starting a new task.</p>
95 application this way, its current task state will be brought to the foreground,
139 a new task (or its existing task to be brought to the foreground). Using
156 is to bring to the foreground the current task matching the new activity's
163 if your task is already running, then it will be brought to the foreground,
|
| /frameworks/native/opengl/tests/hwc/ |
| D | hwcCommit.cpp | 1296 Rectangle foreground(foregroundFormat, startDim, startDim); in numOverlapping() local
1297 foreground.displayFrame.left += 5; in numOverlapping()
1298 foreground.displayFrame.top += 5; in numOverlapping()
1299 foreground.displayFrame.right += 5; in numOverlapping()
1300 foreground.displayFrame.bottom += 5; in numOverlapping()
1302 rectList.push_back(foreground); in numOverlapping()
|
| /frameworks/base/docs/html/training/run-background-service/ |
| D | index.jd | 33 Unless you specify otherwise, most of the operations you do in an app run in the foreground on
|
| D | report-status.jd | 190 when your app is in the background, but doesn't force your app to the foreground. If you
|
| /frameworks/base/docs/html/guide/topics/media/ |
| D | mediaplayer.jd | 25 <li><a href="#foregroundserv">Running as a foreground service</a></li>
400 <h3 id="foregroundserv">Running as a foreground service</h3>
410 In this case, the service should run as a "foreground service." A
411 foreground service holds a higher level of importance within the system—the system will
413 in the foreground, the service also must provide a status bar notification to ensure that users are
417 <p>In order to turn your service into a foreground service, you must create a
436 <p>While your service is running in the foreground, the notification you
446 <p class="img-caption"><strong>Figure 1.</strong> Screenshots of a foreground service's
450 <p>You should only hold on to the "foreground service" status while your
|
| /frameworks/base/core/java/android/app/ |
| D | ActivityManager.java | 955 public boolean foreground; field in ActivityManager.RunningServiceInfo
1047 dest.writeInt(foreground ? 1 : 0); in writeToParcel()
1064 foreground = source.readInt() != 0; in readFromParcel()
|
| /frameworks/base/docs/html/training/basics/activity-lifecycle/ |
| D | pausing.jd | 39 <p>During normal app use, the foreground activity is sometimes obstructed by other
124 <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 | 36 currently stopped and hasn't been used in a long time or the foreground activity requires more
51 the foreground activity because the screen configuration has changed and your activity might need to
|
| D | starting.jd | 56 point at which the activity is running in the foreground and the user can interact with it.</p>
121 <dd>In this state, the activity is in the foreground and the user can interact with it.
125 other activity that's in the foreground is semi-transparent or doesn't cover the entire screen. The
|
| D | stopping.jd | 45 activity in your app that's currently in the foreground is stopped. If the user returns to your
134 <p>When your activity comes back to the foreground from the stopped state, it receives a call to
|
| /frameworks/base/docs/html/training/basics/location/ |
| D | locationmanager.jd | 59 …ethod. If your application intends to receive location updates in the foreground (within an {@lin…
|
| /frameworks/base/docs/html/guide/topics/resources/ |
| D | color-list-resource.jd | 118 application is in the foreground), "false" if this item should be used when the application
|
| /frameworks/base/docs/html/guide/practices/ui_guidelines/ |
| D | activity_task_design.jd | 398 foreground where it has user focus. As shown in the following figure,
444 List Messages activity to the foreground (changing it from stopped to
455 to the foreground. This is true for Contacts and Gallery. If the user
603 with Home in the foreground. The user then launches the Calendar
604 activity, which launches into the foreground, taking user focus,
|