| /frameworks/base/docs/html/guide/topics/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
688 href="{@docRoot}guide/topics/nfc/advanced-nfc.html#foreground-dispatch">foreground dispatch
689 system</a>, which allows a foreground activity to have priority when an NFC tag is discovered.
690 With this method, the activity must be in the foreground to
724 application that wants to beam data to another device must be in the foreground and the device
753 <li>The activity that is beaming the data must be in the foreground. Both devices must have
768 in the foreground, the standard intent dispatch system is disabled. However, if your activity also
769 enables <a href="{@docRoot}guide/topics/nfc/advanced-nfc.html#foreground-dispatch">foreground
770 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 | 453 final Drawable foreground = mForeground; in draw() local
470 Gravity.apply(mForegroundGravity, foreground.getIntrinsicWidth(), in draw()
471 foreground.getIntrinsicHeight(), selfBounds, overlayBounds, in draw()
473 foreground.setBounds(overlayBounds); in draw()
476 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/topics/fundamentals/ |
| 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 | 89 launcher (or a shortcut on the Home screen), that application's task comes to the foreground. If no
117 to be resumed, while Task B receives user interaction in the foreground.</p>
127 another task takes place, as shown in figure 2. A task can then return to the "foreground" so users
135 foreground—all three activities in its stack are intact and the activity at the top of the
167 to the foreground and resumes the activity at the top of the stack.</li>
381 starting, that task is brought to the foreground with its last state restored and the activity
465 for, when that task comes to the foreground.</p>
470 task as your activity. However, when the travel application's task comes to the foreground, the
|
| D | services.jd | 185 href="#Foreground">run in the foreground</a> (discussed later), then it will almost never be killed.
674 <p>A foreground service is a service that's considered to be something the
676 foreground service must provide a notification for the status bar, which is placed under the
678 either stopped or removed from the foreground.</p>
681 foreground, because the user is explicitly aware
685 <p>To request that your service run in the foreground, call {@link
701 <p>To remove the service from the foreground, call {@link
704 service. However, if you stop the service while it's still running in the foreground, then the
710 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>
|
| D | fragments.jd | 674 <dd>Another activity is in the foreground and has focus, but the activity in which this
675 fragment lives is still visible (the foreground activity is partially transparent or doesn't
|
| /frameworks/base/docs/html/resources/articles/ |
| D | service-api-changes-starting-with.jd | 34 …on the system: it asks that the service's process be treated as in the foreground, essentially mak…
35 …foreground, the user should be "aware" that the service is running in some way and know how to sto…
40 …rantee that there is always a notification while the service is in the foreground, and that the no…
115 // foreground state, since we could be killed at that point.
121 … that, even ignoring the services that inappropriately make themselves foreground, we had a growin…
173 …able processes (that is, processes that are currently considered to be foreground and must be kept…
|
| D | multitasking-android-way.jd | 45 … example downloading web pages) if needed, and come immediately to the foreground if the user retu…
63 <p>Services can further negotiate this behavior by requesting they be considered "foreground." Thi…
|
| /frameworks/base/docs/html/guide/topics/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/base/opengl/tests/hwc/ |
| D | hwcCommit.cpp | 1297 Rectangle foreground(foregroundFormat, startDim, startDim); in numOverlapping() local
1298 foreground.displayFrame.left += 5; in numOverlapping()
1299 foreground.displayFrame.top += 5; in numOverlapping()
1300 foreground.displayFrame.right += 5; in numOverlapping()
1301 foreground.displayFrame.bottom += 5; in numOverlapping()
1303 rectList.push_back(foreground); in numOverlapping()
|
| /frameworks/base/core/java/android/app/ |
| D | ActivityManager.java | 716 public boolean foreground; field in ActivityManager.RunningServiceInfo
808 dest.writeInt(foreground ? 1 : 0); in writeToParcel()
825 foreground = source.readInt() != 0; in readFromParcel()
|
| /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/docs/html/guide/practices/ui_guidelines/ |
| D | activity_task_design.jd | 359 foreground where it has user focus. As shown in the following figure,
404 List Messages activity to the foreground (changing it from stopped to
415 to the foreground. This is true for Contacts and Gallery. If the user
563 with Home in the foreground. The user then launches the Calendar
564 activity, which launches into the foreground, taking user focus,
1152 the foreground in its initial state</b> - For example, in
1154 to the foreground, it always presents the list of conversations.
1158 Gmail from coming to the foreground in whatever state the user last
1167 activity to the foreground, set to display specific data, such as
|
| D | icon_design_status_bar.jd | 123 distractions, allowing users to focus on the foreground activity.</p>
208 <p>The system may dim and shrink status bar icons to allow users to focus on the foreground
|
| /frameworks/base/docs/html/sdk/ |
| D | android-2.3.3.jd | 150 foreground application to take control of a tag event before it is passed to any
202 …sing foreground dispatch</a>, and <a href="{@docRoot}resources/samples/ApiDemos/src/com/example/an…
|
| D | android-2.0.jd | 314 …nd(), that helps (and requires) associating an ongoing notification with the foreground state.</li>
|
| D | android-4.0.jd | 591 the foreground. You must then pass the {@link android.nfc.NdefMessage} to the system in one of two
600 foreground, the system sends the {@link android.nfc.NdefMessage} to the other device.</p></li>
610 foreground, the system calls {@link
651 default behavior: When your application is in the foreground on one device and Android Beam is
|
| /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/design/ |
| D | seamlessness.jd | 122 in the foreground: in that case, the user expects to see your next Activity in
|
| /frameworks/base/docs/html/guide/topics/ui/notifiers/ |
| D | notifications.jd | 68 running in the foreground and its window has focus, you will usually create status bar notifications
|