| /packages/apps/VideoEditor/src/com/android/videoeditor/service/ |
| IntentPool.java | 29 * A pool of Intents
|
| /packages/inputmethods/LatinIME/java/src/com/android/inputmethod/dictionarypack/ |
| DictionaryPackConstants.java | 55 // In the above intents, the name of the string extra that contains the name of the client
|
| /packages/providers/ApplicationsProvider/src/com/android/providers/applications/ |
| ApplicationLauncher.java | 33 * This class is purely here to get launch intents.
|
| /packages/providers/DrmProvider/src/com/android/providers/drm/ |
| DrmPushReceiver.java | 37 if (intent.getAction().equals(Telephony.Sms.Intents.WAP_PUSH_RECEIVED_ACTION)) {
|
| /packages/providers/MediaProvider/src/com/android/providers/media/ |
| MediaScannerReceiver.java | 42 // handle intents related to external storage
|
| /frameworks/base/docs/html/google/play/billing/v2/ |
| billing_integrate.jd | 43 intents from Google Play.</li>
57 <li>Handling broadcast intents (asynchronous responses) from Google Play.</li>
97 (broadcast intents) from Google Play. Forwards all messages to the
330 (broadcast intents) from Google Play, and you need to declare the {@link android.app.Service}
335 intents that are sent from the Google Play application.</p>
340 android.content.BroadcastReceiver} that handles broadcast intents from the Google Play
535 (broadcast intents).</p>
556 <li>Handle the broadcast intents that are sent by the Google Play application.</li>
642 <h5>Handling broadcast intents</h5>
645 intents). First, the Google Play application sends a <code>RESPONSE_CODE</code> broadcast intent
[all...] |
| /frameworks/base/docs/html/sdk/api_diff/5/changes/ |
| pkg_android.provider.html | 301 <A NAME="ContactsContract.Intents"></A>
302 <nobr><A HREF="../../../../reference/android/provider/ContactsContract.Intents.html" target="_top"><code>ContactsContract.Intents</code></A></nobr>
308 <A NAME="ContactsContract.Intents.Insert"></A>
309 <nobr><A HREF="../../../../reference/android/provider/ContactsContract.Intents.Insert.html" target="_top"><code>ContactsContract.Intents.<br>Insert</code></A></nobr>
526 <A NAME="Contacts.Intents"></A>
527 <nobr><A HREF="android.provider.Contacts.Intents.html">Contacts.Intents</A></nobr>
533 <A NAME="Contacts.Intents.Insert"></A
[all...] |
| alldiffs_index_all.html | 150 <nobr><A HREF="android.provider.Contacts.Intents.Insert.html#android.provider.Contacts.Intents.Insert.ACTION" class="hiddenlink" target="rightframe">ACTION</A>
322 <nobr><A HREF="android.provider.Contacts.Intents.html#android.provider.Contacts.Intents.ATTACH_IMAGE" class="hiddenlink" target="rightframe">ATTACH_IMAGE</A>
[all...] |
| /frameworks/base/docs/html/guide/topics/connectivity/nfc/ |
| nfc.jd | 16 <li><a href="#filtering-intents">Filtering for Intents</a>
21 <li><a href="#obtain-info">Obtaining information from intents</a></li>
57 scanned NFC tag can <a href="#filtering-intents">declare an intent filter</a> and
246 is presented so the user can select the Activity. The tag dispatch system defines three intents,
270 intents.</li>
283 intent or until the tag dispatch system tries all possible intents.</li>
284 <li>If no applications filter for any of the intents, do nothing.</li>
295 other two intents, giving the user a better experience.</p>
299 <p>Before you can access a device's NFC hardware and properly handle NFC intents, declare thes
[all...] |
| /frameworks/base/core/java/android/app/ |
| IntentService.java | 37 * will receive the Intents, launch a worker thread, and stop the service as
88 * and the intent redelivered. If multiple Intents have been sent, only
|
| /frameworks/base/core/java/android/bluetooth/ |
| BluetoothProfile.java | 32 * Extra for the connection state intents of the individual profiles.
40 * Extra for the connection state intents of the individual profiles.
|
| /frameworks/base/docs/html/guide/appendix/ |
| app-intents.jd | 1 page.title=Reference of Available Intents
7 <h3>Intents handled by Google Android applications<a name="googleintents" id="googleintents"></a></h3>
|
| /frameworks/base/docs/html/training/camera/ |
| videobasics.jd | 27 <li><a href="{@docRoot}guide/components/intents-filters.html">Intents and Intent
|
| /frameworks/base/docs/html/training/monitoring-device-state/ |
| connectivity-monitoring.jd | 27 <li><a href="{@docRoot}guide/components/intents-filters.html">Intents and Intent Filters</a>
|
| docking-monitoring.jd | 26 <li><a href="{@docRoot}guide/components/intents-filters.html">Intents and Intent Filters</a>
|
| /frameworks/base/docs/html/training/notify-user/ |
| build-notification.jd | 31 <a href="{@docRoot}guide/components/intents-filters.html">
32 Intents and Intent Filters
|
| managing.jd | 29 <a href="{@docRoot}guide/components/intents-filters.html">
30 Intents and Intent Filters
|
| /frameworks/base/docs/html/training/run-background-service/ |
| create-service.jd | 21 <a href="{@docRoot}guide/components/intents-filters.html">Intents and Intent Filters</a>
|
| /frameworks/opt/photoviewer/src/com/android/ex/photo/ |
| Intents.java | 28 * Build intents to start app activities
30 public class Intents {
|
| /packages/apps/Phone/src/com/android/phone/ |
| EmergencyCallbackModeService.java | 83 // Register receiver for intents
111 * Listens for Emergency Callback Mode intents
|
| /packages/apps/QuickSearchBox/res/values/ |
| config.xml | 47 <!-- The component name of the activity that search intents in the Apps corpus are sent to.
48 If not set, Apps search intents are sent to the Apps suggestion source. -->
|
| /frameworks/base/docs/html/design/patterns/ |
| navigation.jd | 164 <h4>Activities, tasks, and intents</h4>
175 app's assistance in performing an action. An app's activities can indicate which intents
176 they can respond to. For common intents such as "Share", the user may have many apps installed
181 <p>To understand how activities, tasks, and intents work together, consider how one app allows users
210 <p>When your app registers to handle intents with an activity deep within the app's hierarchy,
|
| /frameworks/base/core/java/android/content/ |
| BroadcastReceiver.java | 30 * Base class for code that will receive intents sent by sendBroadcast().
50 * (You won't receive intents when paused,
82 * from Intents that are used to start Activities with
85 * to see or capture Intents used with startActivity(); likewise, when
106 * <p>For information about how to use this class to receive and resolve intents, read the
107 * <a href="{@docRoot}guide/topics/intents/intents-filters.html">Intents and Intent Filters</a>
138 * {@link android.support.v4.content.LocalBroadcastManager}, since intents
483 * Intents that they may receive
[all...] |
| /frameworks/base/docs/html/guide/components/ |
| fundamentals.jd | 218 Intents bind individual components to each other at runtime (you can think of them
239 <p>The other component type, content provider, is not activated by intents. Rather, it is
264 <p>For more information about using intents, see the <a
265 href="{@docRoot}guide/components/intents-filters.html">Intents and
359 the real power of intents lies in the concept of intent actions. With intent actions, you simply
370 intent filters that declare the capabilities of the component so it can respond to intents
376 intent filter in its manifest entry to respond to "send" intents (in order to send email). An
383 href="{@docRoot}guide/components/intents-filters.html">Intents and Intent Filters</a> document
[all...] |
| /frameworks/base/docs/html/guide/topics/providers/ |
| calendar-provider.jd | 38 <li><a href="#intents">Calendar Intents</a>
42 <li><a href="#intent-view">Using intents to view calendar data</a></li>
74 Provider offers a set of intents, as described in <a href="#intents">Calendar
75 Intents</a>. These intents take users to the Calendar application to insert, view,
172 <li><strong>Inserting, updating, and viewing calendar events.</strong> To directly insert, modify, and read events from the Calendar Provider, you need the appropriate <a href="#manifest">permissions</a>. However, if you're not building a full-fledged calendar application or sync adapter, requesting these permissions isn't necessary. You can instead use intents supported by Android's Calendar application to hand off read and write operations to that application. When you use the intents, your application sends users to the Calendar application to perform the desired operation
176 recommended approach. For more information, see <a href="#intents">Calenda
[all...] |
