Intentpublic class Intent extends Object implements android.os.ParcelableAn intent is an abstract description of an operation to be performed. It
can be used with {@link Context#startActivity(Intent) startActivity} to
launch an {@link android.app.Activity},
{@link android.content.Context#sendBroadcast(Intent) broadcastIntent} to
send it to any interested {@link BroadcastReceiver BroadcastReceiver} components,
and {@link android.content.Context#startService} or
{@link android.content.Context#bindService} to communicate with a
background {@link android.app.Service}.
An Intent provides a facility for performing late runtime binding between
the code in different applications. Its most significant use is in the
launching of activities, where it can be thought of as the glue between
activities. It is
basically a passive data structure holding an abstract description of an
action to be performed. The primary pieces of information in an intent
are:
-
action -- The general action to be performed, such as
{@link #ACTION_VIEW}, {@link #ACTION_EDIT}, {@link #ACTION_MAIN},
etc.
-
data -- The data to operate on, such as a person record
in the contacts database, expressed as a {@link android.net.Uri}.
Some examples of action/data pairs are:
-
{@link #ACTION_VIEW} content://contacts/1 -- Display
information about the person whose identifier is "1".
-
{@link #ACTION_DIAL} content://contacts/1 -- Display
the phone dialer with the person filled in.
-
{@link #ACTION_VIEW} tel:123 -- Display
the phone dialer with the given number filled in. Note how the
VIEW action does what what is considered the most reasonable thing for
a particular URI.
-
{@link #ACTION_DIAL} tel:123 -- Display
the phone dialer with the given number filled in.
-
{@link #ACTION_EDIT} content://contacts/1 -- Edit
information about the person whose identifier is "1".
-
{@link #ACTION_VIEW} content://contacts/ -- Display
a list of people, which the user can browse through. This example is a
typical top-level entry into the Contacts application, showing you the
list of people. Selecting a particular person to view would result in a
new intent { {@link #ACTION_VIEW} content://contacts/N }
being used to start an activity to display that person.
In addition to these primary attributes, there are a number of secondary
attributes that you can also include with an intent:
-
category -- Gives additional information about the action
to execute. For example, {@link #CATEGORY_LAUNCHER} means it should
appear in the Launcher as a top-level application, while
{@link #CATEGORY_ALTERNATIVE} means it should be included in a list
of alternative actions the user can perform on a piece of data.
-
type -- Specifies an explicit type (a MIME type) of the
intent data. Normally the type is inferred from the data itself.
By setting this attribute, you disable that evaluation and force
an explicit type.
-
component -- Specifies an explicit name of a component
class to use for the intent. Normally this is determined by looking
at the other information in the intent (the action, data/type, and
categories) and matching that with a component that can handle it.
If this attribute is set then none of the evaluation is performed,
and this component is used exactly as is. By specifying this attribute,
all of the other Intent attributes become optional.
-
extras -- This is a {@link Bundle} of any additional information.
This can be used to provide extended information to the component.
For example, if we have a action to send an e-mail message, we could
also include extra pieces of data here to supply a subject, body,
etc.
Here are some examples of other operations you can specify as intents
using these additional parameters:
-
{@link #ACTION_MAIN} with category {@link #CATEGORY_HOME} --
Launch the home screen.
-
{@link #ACTION_GET_CONTENT} with MIME type
{@link android.provider.Contacts.Phones#CONTENT_URI
vnd.android.cursor.item/phone}
-- Display the list of people's phone numbers, allowing the user to
browse through them and pick one and return it to the parent activity.
-
{@link #ACTION_GET_CONTENT} with MIME type
*{@literal /}* and category {@link #CATEGORY_OPENABLE}
-- Display all pickers for data that can be opened with
{@link ContentResolver#openInputStream(Uri) ContentResolver.openInputStream()},
allowing the user to pick one of them and then some data inside of it
and returning the resulting URI to the caller. This can be used,
for example, in an e-mail application to allow the user to pick some
data to include as an attachment.
There are a variety of standard Intent action and category constants
defined in the Intent class, but applications can also define their own.
These strings use java style scoping, to ensure they are unique -- for
example, the standard {@link #ACTION_VIEW} is called
"android.app.action.VIEW".
Put together, the set of actions, data types, categories, and extra data
defines a language for the system allowing for the expression of phrases
such as "call john smith's cell". As applications are added to the system,
they can extend this language by adding new actions, types, and categories, or
they can modify the behavior of existing phrases by supplying their own
activities that handle them.
Intent Resolution
There are two primary forms of intents you will use.
-
Explicit Intents have specified a component (via
{@link #setComponent} or {@link #setClass}), which provides the exact
class to be run. Often these will not include any other information,
simply being a way for an application to launch various internal
activities it has as the user interacts with the application.
-
Implicit Intents have not specified a component;
instead, they must include enough information for the system to
determine which of the available components is best to run for that
intent.
When using implicit intents, given such an arbitrary intent we need to
know what to do with it. This is handled by the process of Intent
resolution, which maps an Intent to an {@link android.app.Activity},
{@link BroadcastReceiver}, or {@link android.app.Service} (or sometimes two or
more activities/receivers) that can handle it.
The intent resolution mechanism basically revolves around matching an
Intent against all of the <intent-filter> descriptions in the
installed application packages. (Plus, in the case of broadcasts, any {@link BroadcastReceiver}
objects explicitly registered with {@link Context#registerReceiver}.) More
details on this can be found in the documentation on the {@link
IntentFilter} class.
There are three pieces of information in the Intent that are used for
resolution: the action, type, and category. Using this information, a query
is done on the {@link PackageManager} for a component that can handle the
intent. The appropriate component is determined based on the intent
information supplied in the AndroidManifest.xml file as
follows:
-
The action, if given, must be listed by the component as
one it handles.
-
The type is retrieved from the Intent's data, if not
already supplied in the Intent. Like the action, if a type is
included in the intent (either explicitly or implicitly in its
data), then this must be listed by the component as one it handles.
- For data that is not a
content: URI and where no explicit
type is included in the Intent, instead the scheme of the
intent data (such as http: or mailto: ) is
considered. Again like the action, if we are matching a scheme it
must be listed by the component as one it can handle.
-
The categories, if supplied, must all be listed
by the activity as categories it handles. That is, if you include
the categories {@link #CATEGORY_LAUNCHER} and
{@link #CATEGORY_ALTERNATIVE}, then you will only resolve to components
with an intent that lists both of those categories.
Activities will very often need to support the
{@link #CATEGORY_DEFAULT} so that they can be found by
{@link Context#startActivity Context.startActivity()}.
For example, consider the Note Pad sample application that
allows user to browse through a list of notes data and view details about
individual items. Text in italics indicate places were you would replace a
name with one specific to your own package.
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.android.notepad">
<application android:icon="@drawable/app_notes"
android:label="@string/app_name">
<provider class=".NotePadProvider"
android:authorities="com.google.provider.NotePad" />
<activity class=".NotesList" android:label="@string/title_notes_list">
<intent-filter>
<action android:value="android.intent.action.MAIN" />
<category android:value="android.intent.category.LAUNCHER" />
</intent-filter>
<intent-filter>
<action android:value="android.intent.action.VIEW" />
<action android:value="android.intent.action.EDIT" />
<action android:value="android.intent.action.PICK" />
<category android:value="android.intent.category.DEFAULT" />
<type android:value="vnd.android.cursor.dir/vnd.google.note" />
</intent-filter>
<intent-filter>
<action android:value="android.intent.action.GET_CONTENT" />
<category android:value="android.intent.category.DEFAULT" />
<type android:value="vnd.android.cursor.item/vnd.google.note" />
</intent-filter>
</activity>
<activity class=".NoteEditor" android:label="@string/title_note">
<intent-filter android:label="@string/resolve_edit">
<action android:value="android.intent.action.VIEW" />
<action android:value="android.intent.action.EDIT" />
<category android:value="android.intent.category.DEFAULT" />
<type android:value="vnd.android.cursor.item/vnd.google.note" />
</intent-filter>
<intent-filter>
<action android:value="android.intent.action.INSERT" />
<category android:value="android.intent.category.DEFAULT" />
<type android:value="vnd.android.cursor.dir/vnd.google.note" />
</intent-filter>
</activity>
<activity class=".TitleEditor" android:label="@string/title_edit_title"
android:theme="@android:style/Theme.Dialog">
<intent-filter android:label="@string/resolve_title">
<action android:value="com.android.notepad.action.EDIT_TITLE" />
<category android:value="android.intent.category.DEFAULT" />
<category android:value="android.intent.category.ALTERNATIVE" />
<category android:value="android.intent.category.SELECTED_ALTERNATIVE" />
<type android:value="vnd.android.cursor.item/vnd.google.note" />
</intent-filter>
</activity>
</application>
</manifest>
The first activity,
com.android.notepad.NotesList , serves as our main
entry into the app. It can do three things as described by its three intent
templates:
<intent-filter>
<action android:value="{@link #ACTION_MAIN android.intent.action.MAIN}" />
<category android:value="{@link #CATEGORY_LAUNCHER android.intent.category.LAUNCHER}" />
</intent-filter>
This provides a top-level entry into the NotePad application: the standard
MAIN action is a main entry point (not requiring any other information in
the Intent), and the LAUNCHER category says that this entry point should be
listed in the application launcher.
<intent-filter>
<action android:value="{@link #ACTION_VIEW android.intent.action.VIEW}" />
<action android:value="{@link #ACTION_EDIT android.intent.action.EDIT}" />
<action android:value="{@link #ACTION_PICK android.intent.action.PICK}" />
<category android:value="{@link #CATEGORY_DEFAULT android.intent.category.DEFAULT}" />
<type android:value="vnd.android.cursor.dir/vnd.google.note" />
</intent-filter>
This declares the things that the activity can do on a directory of
notes. The type being supported is given with the <type> tag, where
vnd.android.cursor.dir/vnd.google.note is a URI from which
a Cursor of zero or more items (vnd.android.cursor.dir ) can
be retrieved which holds our note pad data (vnd.google.note ).
The activity allows the user to view or edit the directory of data (via
the VIEW and EDIT actions), or to pick a particular note and return it
to the caller (via the PICK action). Note also the DEFAULT category
supplied here: this is required for the
{@link Context#startActivity Context.startActivity} method to resolve your
activity when its component name is not explicitly specified.
<intent-filter>
<action android:value="{@link #ACTION_GET_CONTENT android.intent.action.GET_CONTENT}" />
<category android:value="{@link #CATEGORY_DEFAULT android.intent.category.DEFAULT}" />
<type android:value="vnd.android.cursor.item/vnd.google.note" />
</intent-filter>
This filter describes the ability return to the caller a note selected by
the user without needing to know where it came from. The data type
vnd.android.cursor.item/vnd.google.note is a URI from which
a Cursor of exactly one (vnd.android.cursor.item ) item can
be retrieved which contains our note pad data (vnd.google.note ).
The GET_CONTENT action is similar to the PICK action, where the activity
will return to its caller a piece of data selected by the user. Here,
however, the caller specifies the type of data they desire instead of
the type of data the user will be picking from.
Given these capabilities, the following intents will resolve to the
NotesList activity:
-
{ action=android.app.action.MAIN } matches all of the
activities that can be used as top-level entry points into an
application.
-
{ action=android.app.action.MAIN,
category=android.app.category.LAUNCHER } is the actual intent
used by the Launcher to populate its top-level list.
-
{ action=android.app.action.VIEW
data=content://com.google.provider.NotePad/notes }
displays a list of all the notes under
"content://com.google.provider.NotePad/notes", which
the user can browse through and see the details on.
-
{ action=android.app.action.PICK
data=content://com.google.provider.NotePad/notes }
provides a list of the notes under
"content://com.google.provider.NotePad/notes", from which
the user can pick a note whose data URL is returned back to the caller.
-
{ action=android.app.action.GET_CONTENT
type=vnd.android.cursor.item/vnd.google.note }
is similar to the pick action, but allows the caller to specify the
kind of data they want back so that the system can find the appropriate
activity to pick something of that data type.
The second activity,
com.android.notepad.NoteEditor , shows the user a single
note entry and allows them to edit it. It can do two things as described
by its two intent templates:
<intent-filter android:label="@string/resolve_edit">
<action android:value="{@link #ACTION_VIEW android.intent.action.VIEW}" />
<action android:value="{@link #ACTION_EDIT android.intent.action.EDIT}" />
<category android:value="{@link #CATEGORY_DEFAULT android.intent.category.DEFAULT}" />
<type android:value="vnd.android.cursor.item/vnd.google.note" />
</intent-filter>
The first, primary, purpose of this activity is to let the user interact
with a single note, as decribed by the MIME type
vnd.android.cursor.item/vnd.google.note . The activity can
either VIEW a note or allow the user to EDIT it. Again we support the
DEFAULT category to allow the activity to be launched without explicitly
specifying its component.
<intent-filter>
<action android:value="{@link #ACTION_INSERT android.intent.action.INSERT}" />
<category android:value="{@link #CATEGORY_DEFAULT android.intent.category.DEFAULT}" />
<type android:value="vnd.android.cursor.dir/vnd.google.note" />
</intent-filter>
The secondary use of this activity is to insert a new note entry into
an existing directory of notes. This is used when the user creates a new
note: the INSERT action is executed on the directory of notes, causing
this activity to run and have the user create the new note data which
it then adds to the content provider.
Given these capabilities, the following intents will resolve to the
NoteEditor activity:
-
{ action=android.app.action.VIEW
data=content://com.google.provider.NotePad/notes/{ID} }
shows the user the content of note {ID}.
-
{ action=android.app.action.EDIT
data=content://com.google.provider.NotePad/notes/{ID} }
allows the user to edit the content of note {ID}.
-
{ action=android.app.action.INSERT
data=content://com.google.provider.NotePad/notes }
creates a new, empty note in the notes list at
"content://com.google.provider.NotePad/notes"
and allows the user to edit it. If they keep their changes, the URI
of the newly created note is returned to the caller.
The last activity,
com.android.notepad.TitleEditor , allows the user to
edit the title of a note. This could be implemented as a class that the
application directly invokes (by explicitly setting its component in
the Intent), but here we show a way you can publish alternative
operations on existing data:
<intent-filter android:label="@string/resolve_title">
<action android:value="com.android.notepad.action.EDIT_TITLE" />
<category android:value="{@link #CATEGORY_DEFAULT android.intent.category.DEFAULT}" />
<category android:value="{@link #CATEGORY_ALTERNATIVE android.intent.category.ALTERNATIVE}" />
<category android:value="{@link #CATEGORY_SELECTED_ALTERNATIVE android.intent.category.SELECTED_ALTERNATIVE}" />
<type android:value="vnd.android.cursor.item/vnd.google.note" />
</intent-filter>
In the single intent template here, we
have created our own private action called
com.android.notepad.action.EDIT_TITLE which means to
edit the title of a note. It must be invoked on a specific note
(data type vnd.android.cursor.item/vnd.google.note ) like the previous
view and edit actions, but here displays and edits the title contained
in the note data.
In addition to supporting the default category as usual, our title editor
also supports two other standard categories: ALTERNATIVE and
SELECTED_ALTERNATIVE. Implementing
these categories allows others to find the special action it provides
without directly knowing about it, through the
{@link android.content.pm.PackageManager#queryIntentActivityOptions} method, or
more often to build dynamic menu items with
{@link android.view.Menu#addIntentOptions}. Note that in the intent
template here was also supply an explicit name for the template
(via android:label="@string/resolve_title" ) to better control
what the user sees when presented with this activity as an alternative
action to the data they are viewing.
Given these capabilities, the following intent will resolve to the
TitleEditor activity:
Standard Activity Actions
These are the current standard actions that Intent defines for launching
activities (usually through {@link Context#startActivity}. The most
important, and by far most frequently used, are {@link #ACTION_MAIN} and
{@link #ACTION_EDIT}.
- {@link #ACTION_MAIN}
- {@link #ACTION_VIEW}
- {@link #ACTION_ATTACH_DATA}
- {@link #ACTION_EDIT}
- {@link #ACTION_PICK}
- {@link #ACTION_CHOOSER}
- {@link #ACTION_GET_CONTENT}
- {@link #ACTION_DIAL}
- {@link #ACTION_CALL}
- {@link #ACTION_SEND}
- {@link #ACTION_SENDTO}
- {@link #ACTION_ANSWER}
- {@link #ACTION_INSERT}
- {@link #ACTION_DELETE}
- {@link #ACTION_RUN}
- {@link #ACTION_SYNC}
- {@link #ACTION_PICK_ACTIVITY}
- {@link #ACTION_SEARCH}
- {@link #ACTION_WEB_SEARCH}
- {@link #ACTION_FACTORY_TEST}
Standard Broadcast Actions
These are the current standard actions that Intent defines for receiving
broadcasts (usually through {@link Context#registerReceiver} or a
<receiver> tag in a manifest).
- {@link #ACTION_TIME_TICK}
- {@link #ACTION_TIME_CHANGED}
- {@link #ACTION_TIMEZONE_CHANGED}
- {@link #ACTION_BOOT_COMPLETED}
- {@link #ACTION_PACKAGE_ADDED}
- {@link #ACTION_PACKAGE_CHANGED}
- {@link #ACTION_PACKAGE_REMOVED}
- {@link #ACTION_PACKAGE_RESTARTED}
- {@link #ACTION_PACKAGE_DATA_CLEARED}
- {@link #ACTION_UID_REMOVED}
- {@link #ACTION_BATTERY_CHANGED}
Standard Categories
These are the current standard categories that can be used to further
clarify an Intent via {@link #addCategory}.
- {@link #CATEGORY_DEFAULT}
- {@link #CATEGORY_BROWSABLE}
- {@link #CATEGORY_TAB}
- {@link #CATEGORY_ALTERNATIVE}
- {@link #CATEGORY_SELECTED_ALTERNATIVE}
- {@link #CATEGORY_LAUNCHER}
- {@link #CATEGORY_INFO}
- {@link #CATEGORY_HOME}
- {@link #CATEGORY_PREFERENCE}
- {@link #CATEGORY_TEST}
Standard Extra Data
These are the current standard fields that can be used as extra data via
{@link #putExtra}.
- {@link #EXTRA_TEMPLATE}
- {@link #EXTRA_INTENT}
- {@link #EXTRA_STREAM}
- {@link #EXTRA_TEXT}
Flags
These are the possible flags that can be used in the Intent via
{@link #setFlags} and {@link #addFlags}. See {@link #setFlags} for a list
of all possible flags. |
Fields Summary |
---|
public static final String | ACTION_MAINActivity Action: Start as a main entry point, does not expect to
receive data.
Input: nothing
Output: nothing | public static final String | ACTION_VIEWActivity Action: Display the data to the user. This is the most common
action performed on data -- it is the generic action you can use on
a piece of data to get the most reasonable thing to occur. For example,
when used on a contacts entry it will view the entry; when used on a
mailto: URI it will bring up a compose window filled with the information
supplied by the URI; when used with a tel: URI it will invoke the
dialer.
Input: {@link #getData} is URI from which to retrieve data.
Output: nothing. | public static final String | ACTION_DEFAULTA synonym for {@link #ACTION_VIEW}, the "standard" action that is
performed on a piece of data. | public static final String | ACTION_ATTACH_DATAUsed to indicate that some piece of data should be attached to some other
place. For example, image data could be attached to a contact. It is up
to the recipient to decide where the data should be attached; the intent
does not specify the ultimate destination.
Input: {@link #getData} is URI of data to be attached.
Output: nothing. | public static final String | ACTION_EDITActivity Action: Provide explicit editable access to the given data.
Input: {@link #getData} is URI of data to be edited.
Output: nothing. | public static final String | ACTION_INSERT_OR_EDITActivity Action: Pick an existing item, or insert a new item, and then edit it.
Input: {@link #getType} is the desired MIME type of the item to create or edit.
The extras can contain type specific data to pass through to the editing/creating
activity.
Output: The URI of the item that was picked. This must be a content:
URI so that any receiver can access it. | public static final String | ACTION_PICKActivity Action: Pick an item from the data, returning what was selected.
Input: {@link #getData} is URI containing a directory of data
(vnd.android.cursor.dir/*) from which to pick an item.
Output: The URI of the item that was picked. | public static final String | ACTION_CREATE_SHORTCUTActivity Action: Creates a shortcut.
Input: Nothing.
Output: An Intent representing the shortcut. The intent must contain three
extras: SHORTCUT_INTENT (value: Intent), SHORTCUT_NAME (value: String),
and SHORTCUT_ICON (value: Bitmap) or SHORTCUT_ICON_RESOURCE
(value: ShortcutIconResource). | public static final String | EXTRA_SHORTCUT_INTENTThe name of the extra used to define the Intent of a shortcut. | public static final String | EXTRA_SHORTCUT_NAMEThe name of the extra used to define the name of a shortcut. | public static final String | EXTRA_SHORTCUT_ICONThe name of the extra used to define the icon, as a Bitmap, of a shortcut. | public static final String | EXTRA_SHORTCUT_ICON_RESOURCEThe name of the extra used to define the icon, as a ShortcutIconResource, of a shortcut. | public static final String | ACTION_CHOOSERActivity Action: Display an activity chooser, allowing the user to pick
what they want to before proceeding. This can be used as an alternative
to the standard activity picker that is displayed by the system when
you try to start an activity with multiple possible matches, with these
differences in behavior:
- You can specify the title that will appear in the activity chooser.
- The user does not have the option to make one of the matching
activities a preferred activity, and all possible activities will
always be shown even if one of them is currently marked as the
preferred activity.
This action should be used when the user will naturally expect to
select an activity in order to proceed. An example if when not to use
it is when the user clicks on a "mailto:" link. They would naturally
expect to go directly to their mail app, so startActivity() should be
called directly: it will
either launch the current preferred app, or put up a dialog allowing the
user to pick an app to use and optionally marking that as preferred.
In contrast, if the user is selecting a menu item to send a picture
they are viewing to someone else, there are many different things they
may want to do at this point: send it through e-mail, upload it to a
web service, etc. In this case the CHOOSER action should be used, to
always present to the user a list of the things they can do, with a
nice title given by the caller such as "Send this photo with:".
As a convenience, an Intent of this form can be created with the
{@link #createChooser} function.
Input: No data should be specified. get*Extra must have
a {@link #EXTRA_INTENT} field containing the Intent being executed,
and can optionally have a {@link #EXTRA_TITLE} field containing the
title text to display in the chooser.
Output: Depends on the protocol of {@link #EXTRA_INTENT}. | public static final String | ACTION_GET_CONTENTActivity Action: Allow the user to select a particular kind of data and
return it. This is different than {@link #ACTION_PICK} in that here we
just say what kind of data is desired, not a URI of existing data from
which the user can pick. A ACTION_GET_CONTENT could allow the user to
create the data as it runs (for example taking a picture or recording a
sound), let them browser over the web and download the desired data,
etc.
There are two main ways to use this action: if you want an specific kind
of data, such as a person contact, you set the MIME type to the kind of
data you want and launch it with {@link Context#startActivity(Intent)}.
The system will then launch the best application to select that kind
of data for you.
You may also be interested in any of a set of types of content the user
can pick. For example, an e-mail application that wants to allow the
user to add an attachment to an e-mail message can use this action to
bring up a list of all of the types of content the user can attach.
In this case, you should wrap the GET_CONTENT intent with a chooser
(through {@link #createChooser}), which will give the proper interface
for the user to pick how to send your data and allow you to specify
a prompt indicating what they are doing. You will usually specify a
broad MIME type (such as image/* or {@literal *}/*), resulting in a
broad range of content types the user can select from.
When using such a broad GET_CONTENT action, it is often desireable to
only pick from data that can be represented as a stream. This is
accomplished by requiring the {@link #CATEGORY_OPENABLE} in the Intent.
Input: {@link #getType} is the desired MIME type to retrieve. Note
that no URI is supplied in the intent, as there are no constraints on
where the returned data originally comes from. You may also include the
{@link #CATEGORY_OPENABLE} if you can only accept data that can be
opened as a stream.
Output: The URI of the item that was picked. This must be a content:
URI so that any receiver can access it. | public static final String | ACTION_DIALActivity Action: Dial a number as specified by the data. This shows a
UI with the number being dialed, allowing the user to explicitly
initiate the call.
Input: If nothing, an empty dialer is started; else {@link #getData}
is URI of a phone number to be dialed or a tel: URI of an explicit phone
number.
Output: nothing. | public static final String | ACTION_CALLActivity Action: Perform a call to someone specified by the data.
Input: If nothing, an empty dialer is started; else {@link #getData}
is URI of a phone number to be dialed or a tel: URI of an explicit phone
number.
Output: nothing.
Note: there will be restrictions on which applications can initiate a
call; most applications should use the {@link #ACTION_DIAL}.
Note: this Intent cannot be used to call emergency
numbers. Applications can dial emergency numbers using
{@link #ACTION_DIAL}, however. | public static final String | ACTION_CALL_EMERGENCYActivity Action: Perform a call to an emergency number specified by the
data.
Input: {@link #getData} is URI of a phone number to be dialed or a
tel: URI of an explicit phone number.
Output: nothing. | public static final String | ACTION_CALL_PRIVILEGEDActivity action: Perform a call to any number (emergency or not)
specified by the data.
Input: {@link #getData} is URI of a phone number to be dialed or a
tel: URI of an explicit phone number.
Output: nothing. | public static final String | ACTION_SENDTOActivity Action: Send a message to someone specified by the data.
Input: {@link #getData} is URI describing the target.
Output: nothing. | public static final String | ACTION_SENDActivity Action: Deliver some data to someone else. Who the data is
being delivered to is not specified; it is up to the receiver of this
action to ask the user where the data should be sent.
When launching a SEND intent, you should usually wrap it in a chooser
(through {@link #createChooser}), which will give the proper interface
for the user to pick how to send your data and allow you to specify
a prompt indicating what they are doing.
Input: {@link #getType} is the MIME type of the data being sent.
get*Extra can have either a {@link #EXTRA_TEXT}
or {@link #EXTRA_STREAM} field, containing the data to be sent. If
using EXTRA_TEXT, the MIME type should be "text/plain"; otherwise it
should be the MIME type of the data in EXTRA_STREAM. Use {@literal *}/*
if the MIME type is unknown (this will only allow senders that can
handle generic data streams).
Optional standard extras, which may be interpreted by some recipients as
appropriate, are: {@link #EXTRA_EMAIL}, {@link #EXTRA_CC},
{@link #EXTRA_BCC}, {@link #EXTRA_SUBJECT}.
Output: nothing. | public static final String | ACTION_ANSWERActivity Action: Handle an incoming phone call.
Input: nothing.
Output: nothing. | public static final String | ACTION_INSERTActivity Action: Insert an empty item into the given container.
Input: {@link #getData} is URI of the directory (vnd.android.cursor.dir/*)
in which to place the data.
Output: URI of the new data that was created. | public static final String | ACTION_DELETEActivity Action: Delete the given data from its container.
Input: {@link #getData} is URI of data to be deleted.
Output: nothing. | public static final String | ACTION_RUNActivity Action: Run the data, whatever that means.
Input: ? (Note: this is currently specific to the test harness.)
Output: nothing. | public static final String | ACTION_SYNCActivity Action: Perform a data synchronization.
Input: ?
Output: ? | public static final String | ACTION_PICK_ACTIVITYActivity Action: Pick an activity given an intent, returning the class
selected.
Input: get*Extra field {@link #EXTRA_INTENT} is an Intent
used with {@link PackageManager#queryIntentActivities} to determine the
set of activities from which to pick.
Output: Class name of the activity that was selected. | public static final String | ACTION_SEARCHActivity Action: Perform a search.
Input: {@link android.app.SearchManager#QUERY getStringExtra(SearchManager.QUERY)}
is the text to search for. If empty, simply
enter your search results Activity with the search UI activated.
Output: nothing. | public static final String | ACTION_SYSTEM_TUTORIALActivity Action: Start the platform-defined tutorial
Input: {@link android.app.SearchManager#QUERY getStringExtra(SearchManager.QUERY)}
is the text to search for. If empty, simply
enter your search results Activity with the search UI activated.
Output: nothing. | public static final String | ACTION_WEB_SEARCHActivity Action: Perform a web search.
Input: {@link android.app.SearchManager#QUERY
getStringExtra(SearchManager.QUERY)} is the text to search for. If it is
a url starts with http or https, the site will be opened. If it is plain
text, Google search will be applied.
Output: nothing. | public static final String | ACTION_ALL_APPSActivity Action: List all available applications
Input: Nothing.
Output: nothing. | public static final String | ACTION_SET_WALLPAPERActivity Action: Show settings for choosing wallpaper
Input: Nothing.
Output: Nothing. | public static final String | ACTION_BUG_REPORTActivity Action: Show activity for reporting a bug.
Input: Nothing.
Output: Nothing. | public static final String | ACTION_FACTORY_TESTActivity Action: Main entry point for factory tests. Only used when
the device is booting in factory test node. The implementing package
must be installed in the system image.
Input: nothing
Output: nothing | public static final String | ACTION_CALL_BUTTONActivity Action: The user pressed the "call" button to go to the dialer
or other appropriate UI for placing a call.
Input: Nothing.
Output: Nothing. | public static final String | ACTION_VOICE_COMMANDActivity Action: Start Voice Command.
Input: Nothing.
Output: Nothing. | public static final String | ACTION_SEARCH_LONG_PRESSActivity Action: Start action associated with long pressing on the
search key.
Input: Nothing.
Output: Nothing. | public static final String | ACTION_SCREEN_OFFBroadcast Action: Sent after the screen turns off. | public static final String | ACTION_SCREEN_ONBroadcast Action: Sent after the screen turns on. | public static final String | ACTION_USER_PRESENTBroadcast Action: Sent when the user is present after device wakes up (e.g when the
keyguard is gone). | public static final String | ACTION_TIME_TICKBroadcast Action: The current time has changed. Sent every
minute. You can not receive this through components declared
in manifests, only by exlicitly registering for it with
{@link Context#registerReceiver(BroadcastReceiver, IntentFilter)
Context.registerReceiver()}. | public static final String | ACTION_TIME_CHANGEDBroadcast Action: The time was set. | public static final String | ACTION_DATE_CHANGEDBroadcast Action: The date has changed. | public static final String | ACTION_TIMEZONE_CHANGEDBroadcast Action: The timezone has changed. The intent will have the following extra values:
- time-zone - The java.util.TimeZone.getID() value identifying the new time zone.
| public static final String | ACTION_ALARM_CHANGEDAlarm Changed Action: This is broadcast when the AlarmClock
application's alarm is set or unset. It is used by the
AlarmClock application and the StatusBar service. | public static final String | ACTION_SYNC_STATE_CHANGEDSync State Changed Action: This is broadcast when the sync starts or stops or when one has
been failing for a long time. It is used by the SyncManager and the StatusBar service. | public static final String | ACTION_BOOT_COMPLETEDBroadcast Action: This is broadcast once, after the system has finished
booting. It can be used to perform application-specific initialization,
such as installing alarms. You must hold the
{@link android.Manifest.permission#RECEIVE_BOOT_COMPLETED} permission
in order to receive this broadcast. | public static final String | ACTION_CLOSE_SYSTEM_DIALOGSBroadcast Action: This is broadcast when a user action should request a
temporary system dialog to dismiss. Some examples of temporary system
dialogs are the notification window-shade and the recent tasks dialog. | public static final String | ACTION_PACKAGE_INSTALLBroadcast Action: Trigger the download and eventual installation
of a package.
Input: {@link #getData} is the URI of the package file to download. | public static final String | ACTION_PACKAGE_ADDEDBroadcast Action: A new application package has been installed on the
device. The data contains the name of the package. Note that the
newly installed package does not receive this broadcast.
My include the following extras:
- {@link #EXTRA_UID} containing the integer uid assigned to the new package.
- {@link #EXTRA_REPLACING} is set to true if this is following
an {@link #ACTION_PACKAGE_REMOVED} broadcast for the same package.
| public static final String | ACTION_PACKAGE_REPLACEDBroadcast Action: A new version of an application package has been
installed, replacing an existing version that was previously installed.
The data contains the name of the package.
My include the following extras:
- {@link #EXTRA_UID} containing the integer uid assigned to the new package.
| public static final String | ACTION_PACKAGE_REMOVEDBroadcast Action: An existing application package has been removed from
the device. The data contains the name of the package. The package
that is being installed does not receive this Intent.
- {@link #EXTRA_UID} containing the integer uid previously assigned
to the package.
- {@link #EXTRA_DATA_REMOVED} is set to true if the entire
application -- data and code -- is being removed.
- {@link #EXTRA_REPLACING} is set to true if this will be followed
by an {@link #ACTION_PACKAGE_ADDED} broadcast for the same package.
| public static final String | ACTION_PACKAGE_CHANGEDBroadcast Action: An existing application package has been changed (e.g. a component has been
enabled or disabled. The data contains the name of the package.
- {@link #EXTRA_UID} containing the integer uid assigned to the package.
| public static final String | ACTION_PACKAGE_RESTARTEDBroadcast Action: The user has restarted a package, and all of its
processes have been killed. All runtime state
associated with it (processes, alarms, notifications, etc) should
be removed. Note that the restarted package does not
receive this broadcast.
The data contains the name of the package.
- {@link #EXTRA_UID} containing the integer uid assigned to the package.
| public static final String | ACTION_PACKAGE_DATA_CLEAREDBroadcast Action: The user has cleared the data of a package. This should
be preceded by {@link #ACTION_PACKAGE_RESTARTED}, after which all of
its persistent data is erased and this broadcast sent.
Note that the cleared package does not
receive this broadcast. The data contains the name of the package.
- {@link #EXTRA_UID} containing the integer uid assigned to the package.
| public static final String | ACTION_UID_REMOVEDBroadcast Action: A user ID has been removed from the system. The user
ID number is stored in the extra data under {@link #EXTRA_UID}. | public static final String | ACTION_WALLPAPER_CHANGEDBroadcast Action: The current system wallpaper has changed. See
{@link Context#getWallpaper} for retrieving the new wallpaper. | public static final String | ACTION_CONFIGURATION_CHANGEDBroadcast Action: The current device {@link android.content.res.Configuration}
(orientation, locale, etc) has changed. When such a change happens, the
UIs (view hierarchy) will need to be rebuilt based on this new
information; for the most part, applications don't need to worry about
this, because the system will take care of stopping and restarting the
application to make sure it sees the new changes. Some system code that
can not be restarted will need to watch for this action and handle it
appropriately. | public static final String | ACTION_BATTERY_CHANGEDBroadcast Action: The charging state, or charge level of the battery has
changed.
You can not receive this through components declared
in manifests, only by exlicitly registering for it with
{@link Context#registerReceiver(BroadcastReceiver, IntentFilter)
Context.registerReceiver()}. | public static final String | ACTION_BATTERY_LOWBroadcast Action: Indicates low battery condition on the device.
This broadcast corresponds to the "Low battery warning" system dialog. | public static final String | ACTION_DEVICE_STORAGE_LOWBroadcast Action: Indicates low memory condition on the device | public static final String | ACTION_DEVICE_STORAGE_OKBroadcast Action: Indicates low memory condition on the device no longer exists | public static final String | ACTION_MANAGE_PACKAGE_STORAGEBroadcast Action: Indicates low memory condition notification acknowledged by user
and package management should be started.
This is triggered by the user from the ACTION_DEVICE_STORAGE_LOW
notification. | public static final String | ACTION_UMS_CONNECTEDBroadcast Action: The device has entered USB Mass Storage mode.
This is used mainly for the USB Settings panel.
Apps should listen for ACTION_MEDIA_MOUNTED and ACTION_MEDIA_UNMOUNTED broadcasts to be notified
when the SD card file system is mounted or unmounted | public static final String | ACTION_UMS_DISCONNECTEDBroadcast Action: The device has exited USB Mass Storage mode.
This is used mainly for the USB Settings panel.
Apps should listen for ACTION_MEDIA_MOUNTED and ACTION_MEDIA_UNMOUNTED broadcasts to be notified
when the SD card file system is mounted or unmounted | public static final String | ACTION_MEDIA_REMOVEDBroadcast Action: External media has been removed.
The path to the mount point for the removed media is contained in the Intent.mData field. | public static final String | ACTION_MEDIA_UNMOUNTEDBroadcast Action: External media is present, but not mounted at its mount point.
The path to the mount point for the removed media is contained in the Intent.mData field. | public static final String | ACTION_MEDIA_CHECKINGBroadcast Action: External media is present, and being disk-checked
The path to the mount point for the checking media is contained in the Intent.mData field. | public static final String | ACTION_MEDIA_NOFSBroadcast Action: External media is present, but is using an incompatible fs (or is blank)
The path to the mount point for the checking media is contained in the Intent.mData field. | public static final String | ACTION_MEDIA_MOUNTEDBroadcast Action: External media is present and mounted at its mount point.
The path to the mount point for the removed media is contained in the Intent.mData field.
The Intent contains an extra with name "read-only" and Boolean value to indicate if the
media was mounted read only. | public static final String | ACTION_MEDIA_SHAREDBroadcast Action: External media is unmounted because it is being shared via USB mass storage.
The path to the mount point for the removed media is contained in the Intent.mData field. | public static final String | ACTION_MEDIA_BAD_REMOVALBroadcast Action: External media was removed from SD card slot, but mount point was not unmounted.
The path to the mount point for the removed media is contained in the Intent.mData field. | public static final String | ACTION_MEDIA_UNMOUNTABLEBroadcast Action: External media is present but cannot be mounted.
The path to the mount point for the removed media is contained in the Intent.mData field. | public static final String | ACTION_MEDIA_EJECTBroadcast Action: User has expressed the desire to remove the external storage media.
Applications should close all files they have open within the mount point when they receive this intent.
The path to the mount point for the media to be ejected is contained in the Intent.mData field. | public static final String | ACTION_MEDIA_SCANNER_STARTEDBroadcast Action: The media scanner has started scanning a directory.
The path to the directory being scanned is contained in the Intent.mData field. | public static final String | ACTION_MEDIA_SCANNER_FINISHEDBroadcast Action: The media scanner has finished scanning a directory.
The path to the scanned directory is contained in the Intent.mData field. | public static final String | ACTION_MEDIA_SCANNER_SCAN_FILEBroadcast Action: Request the media scanner to scan a file and add it to the media database.
The path to the file is contained in the Intent.mData field. | public static final String | ACTION_MEDIA_BUTTONBroadcast Action: The "Media Button" was pressed. Includes a single
extra field, {@link #EXTRA_KEY_EVENT}, containing the key event that
caused the broadcast. | public static final String | ACTION_CAMERA_BUTTONBroadcast Action: The "Camera Button" was pressed. Includes a single
extra field, {@link #EXTRA_KEY_EVENT}, containing the key event that
caused the broadcast. | public static final String | ACTION_GTALK_SERVICE_CONNECTEDBroadcast Action: An GTalk connection has been established. | public static final String | ACTION_GTALK_SERVICE_DISCONNECTEDBroadcast Action: An GTalk connection has been disconnected. | public static final String | ACTION_INPUT_METHOD_CHANGEDBroadcast Action: An input method has been changed. | public static final String | ACTION_AIRPLANE_MODE_CHANGED Broadcast Action: The user has switched the phone into or out of Airplane Mode. One or
more radios have been turned off or on. The intent will have the following extra value:
- state - A boolean value indicating whether Airplane Mode is on. If true,
then cell radio and possibly other radios such as bluetooth or WiFi may have also been
turned off
| public static final String | ACTION_PROVIDER_CHANGEDBroadcast Action: Some content providers have parts of their namespace
where they publish new events or items that the user may be especially
interested in. For these things, they may broadcast this action when the
set of interesting items change.
For example, GmailProvider sends this notification when the set of unread
mail in the inbox changes.
The data of the intent identifies which part of which provider
changed. When queried through the content resolver, the data URI will
return the data set in question.
The intent will have the following extra values:
- count - The number of items in the data set. This is the
same as the number of items in the cursor returned by querying the
data URI.
This intent will be sent at boot (if the count is non-zero) and when the
data set changes. It is possible for the data set to change without the
count changing (for example, if a new unread message arrives in the same
sync operation in which a message is archived). The phone should still
ring/vibrate/etc as normal in this case. | public static final String | ACTION_HEADSET_PLUGBroadcast Action: Wired Headset plugged in or unplugged.
The intent will have the following extra values:
- state - 0 for unplugged, 1 for plugged.
- name - Headset type, human readable string
| public static final String | ACTION_NEW_OUTGOING_CALLBroadcast Action: An outgoing call is about to be placed.
The Intent will have the following extra value:
- {@link android.content.Intent#EXTRA_PHONE_NUMBER} -
the phone number originally intended to be dialed.
Once the broadcast is finished, the resultData is used as the actual
number to call. If null , no call will be placed.
It is perfectly acceptable for multiple receivers to process the
outgoing call in turn: for example, a parental control application
might verify that the user is authorized to place the call at that
time, then a number-rewriting application might add an area code if
one was not specified.
For consistency, any receiver whose purpose is to prohibit phone
calls should have a priority of 0, to ensure it will see the final
phone number to be dialed.
Any receiver whose purpose is to rewrite phone numbers to be called
should have a positive priority.
Negative priorities are reserved for the system for this broadcast;
using them may cause problems.
Any BroadcastReceiver receiving this Intent must not
abort the broadcast.
Emergency calls cannot be intercepted using this mechanism, and
other calls cannot be modified to call emergency numbers using this
mechanism.
You must hold the
{@link android.Manifest.permission#PROCESS_OUTGOING_CALLS}
permission to receive this Intent. | public static final String | ACTION_REBOOTBroadcast Action: Have the device reboot. This is only for use by
system code. | public static final String | CATEGORY_DEFAULTSet if the activity should be an option for the default action
(center press) to perform on a piece of data. Setting this will
hide from the user any activities without it set when performing an
action on some data. Note that this is normal -not- set in the
Intent when initiating an action -- it is for use in intent filters
specified in packages. | public static final String | CATEGORY_BROWSABLEActivities that can be safely invoked from a browser must support this
category. For example, if the user is viewing a web page or an e-mail
and clicks on a link in the text, the Intent generated execute that
link will require the BROWSABLE category, so that only activities
supporting this category will be considered as possible actions. By
supporting this category, you are promising that there is nothing
damaging (without user intervention) that can happen by invoking any
matching Intent. | public static final String | CATEGORY_ALTERNATIVESet if the activity should be considered as an alternative action to
the data the user is currently viewing. See also
{@link #CATEGORY_SELECTED_ALTERNATIVE} for an alternative action that
applies to the selection in a list of items.
Supporting this category means that you would like your activity to be
displayed in the set of alternative things the user can do, usually as
part of the current activity's options menu. You will usually want to
include a specific label in the <intent-filter> of this action
describing to the user what it does.
The action of IntentFilter with this category is important in that it
describes the specific action the target will perform. This generally
should not be a generic action (such as {@link #ACTION_VIEW}, but rather
a specific name such as "com.android.camera.action.CROP. Only one
alternative of any particular action will be shown to the user, so using
a specific action like this makes sure that your alternative will be
displayed while also allowing other applications to provide their own
overrides of that particular action. | public static final String | CATEGORY_SELECTED_ALTERNATIVESet if the activity should be considered as an alternative selection
action to the data the user has currently selected. This is like
{@link #CATEGORY_ALTERNATIVE}, but is used in activities showing a list
of items from which the user can select, giving them alternatives to the
default action that will be performed on it. | public static final String | CATEGORY_TABIntended to be used as a tab inside of an containing TabActivity. | public static final String | CATEGORY_LAUNCHERShould be displayed in the top-level launcher. | public static final String | CATEGORY_INFOProvides information about the package it is in; typically used if
a package does not contain a {@link #CATEGORY_LAUNCHER} to provide
a front-door to the user without having to be shown in the all apps list. | public static final String | CATEGORY_HOMEThis is the home activity, that is the first activity that is displayed
when the device boots. | public static final String | CATEGORY_PREFERENCEThis activity is a preference panel. | public static final String | CATEGORY_DEVELOPMENT_PREFERENCEThis activity is a development preference panel. | public static final String | CATEGORY_EMBEDCapable of running inside a parent activity container. | public static final String | CATEGORY_MONKEYThis activity may be exercised by the monkey or other automated test tools. | public static final String | CATEGORY_TESTTo be used as a test (not part of the normal user experience). | public static final String | CATEGORY_UNIT_TESTTo be used as a unit test (run through the Test Harness). | public static final String | CATEGORY_SAMPLE_CODETo be used as an sample code example (not part of the normal user
experience). | public static final String | CATEGORY_OPENABLEUsed to indicate that a GET_CONTENT intent only wants URIs that can be opened with
ContentResolver.openInputStream. Openable URIs must support the columns in OpenableColumns
when queried, though it is allowable for those columns to be blank. | public static final String | CATEGORY_FRAMEWORK_INSTRUMENTATION_TESTTo be used as code under test for framework instrumentation tests. | public static final String | EXTRA_TEMPLATEThe initial data to place in a newly created record. Use with
{@link #ACTION_INSERT}. The data here is a Map containing the same
fields as would be given to the underlying ContentProvider.insert()
call. | public static final String | EXTRA_TEXTA constant CharSequence that is associated with the Intent, used with
{@link #ACTION_SEND} to supply the literal data to be sent. Note that
this may be a styled CharSequence, so you must use
{@link Bundle#getCharSequence(String) Bundle.getCharSequence()} to
retrieve it. | public static final String | EXTRA_STREAMA content: URI holding a stream of data associated with the Intent,
used with {@link #ACTION_SEND} to supply the data being sent. | public static final String | EXTRA_EMAILA String[] holding e-mail addresses that should be delivered to. | public static final String | EXTRA_CCA String[] holding e-mail addresses that should be carbon copied. | public static final String | EXTRA_BCCA String[] holding e-mail addresses that should be blind carbon copied. | public static final String | EXTRA_SUBJECTA constant string holding the desired subject line of a message. | public static final String | EXTRA_INTENTAn Intent describing the choices you would like shown with
{@link #ACTION_PICK_ACTIVITY}. | public static final String | EXTRA_TITLEA CharSequence dialog title to provide to the user when used with a
{@link #ACTION_CHOOSER}. | public static final String | EXTRA_KEY_EVENTA {@link android.view.KeyEvent} object containing the event that
triggered the creation of the Intent it is in. | public static final String | EXTRA_DONT_KILL_APPUsed as an boolean extra field in {@link android.content.Intent#ACTION_PACKAGE_REMOVED} or
{@link android.content.Intent#ACTION_PACKAGE_CHANGED} intents to override the default action
of restarting the application. | public static final String | EXTRA_PHONE_NUMBERA String holding the phone number originally entered in
{@link android.content.Intent#ACTION_NEW_OUTGOING_CALL}, or the actual
number to call in a {@link android.content.Intent#ACTION_CALL}. | public static final String | EXTRA_UIDUsed as an int extra field in {@link android.content.Intent#ACTION_UID_REMOVED}
intents to supply the uid the package had been assigned. Also an optional
extra in {@link android.content.Intent#ACTION_PACKAGE_REMOVED} or
{@link android.content.Intent#ACTION_PACKAGE_CHANGED} for the same
purpose. | public static final String | EXTRA_DATA_REMOVEDUsed as a boolean extra field in {@link android.content.Intent#ACTION_PACKAGE_REMOVED}
intents to indicate whether this represents a full uninstall (removing
both the code and its data) or a partial uninstall (leaving its data,
implying that this is an update). | public static final String | EXTRA_REPLACINGUsed as a boolean extra field in {@link android.content.Intent#ACTION_PACKAGE_REMOVED}
intents to indicate that this is a replacement of the package, so this
broadcast will immediately be followed by an add broadcast for a
different version of the same package. | public static final String | EXTRA_ALARM_COUNTUsed as an int extra field in {@link android.app.AlarmManager} intents
to tell the application being invoked how many pending alarms are being
delievered with the intent. For one-shot alarms this will always be 1.
For recurring alarms, this might be greater than 1 if the device was
asleep or powered off at the time an earlier alarm would have been
delivered. | public static final int | FLAG_GRANT_READ_URI_PERMISSIONIf set, the recipient of this Intent will be granted permission to
perform read operations on the Uri in the Intent's data. | public static final int | FLAG_GRANT_WRITE_URI_PERMISSIONIf set, the recipient of this Intent will be granted permission to
perform write operations on the Uri in the Intent's data. | public static final int | FLAG_FROM_BACKGROUNDCan be set by the caller to indicate that this Intent is coming from
a background operation, not from direct user interaction. | public static final int | FLAG_DEBUG_LOG_RESOLUTIONA flag you can enable for debugging: when set, log messages will be
printed during the resolution of this intent to show you what has
been found to create the final resolved list. | public static final int | FLAG_ACTIVITY_NO_HISTORYIf set, the new activity is not kept in the history stack. As soon as
the user navigates away from it, the activity is finished. This may also
be set with the {@link android.R.styleable#AndroidManifestActivity_noHistory
noHistory} attribute. | public static final int | FLAG_ACTIVITY_SINGLE_TOPIf set, the activity will not be launched if it is already running
at the top of the history stack. | public static final int | FLAG_ACTIVITY_NEW_TASKIf set, this activity will become the start of a new task on this
history stack. A task (from the activity that started it to the
next task activity) defines an atomic group of activities that the
user can move to. Tasks can be moved to the foreground and background;
all of the activities inside of a particular task always remain in
the same order. See
Application Fundamentals:
Activities and Tasks for more details on tasks.
This flag is generally used by activities that want
to present a "launcher" style behavior: they give the user a list of
separate things that can be done, which otherwise run completely
independently of the activity launching them.
When using this flag, if a task is already running for the activity
you are now starting, then a new activity will not be started; instead,
the current task will simply be brought to the front of the screen with
the state it was last in. See {@link #FLAG_ACTIVITY_MULTIPLE_TASK} for a flag
to disable this behavior.
This flag can not be used when the caller is requesting a result from
the activity being launched. | public static final int | FLAG_ACTIVITY_MULTIPLE_TASKDo not use this flag unless you are implementing your own
top-level application launcher. Used in conjunction with
{@link #FLAG_ACTIVITY_NEW_TASK} to disable the
behavior of bringing an existing task to the foreground. When set,
a new task is always started to host the Activity for the
Intent, regardless of whether there is already an existing task running
the same thing.
Because the default system does not include graphical task management,
you should not use this flag unless you provide some way for a user to
return back to the tasks you have launched.
This flag is ignored if
{@link #FLAG_ACTIVITY_NEW_TASK} is not set.
See Application Fundamentals:
Activities and Tasks for more details on tasks. | public static final int | FLAG_ACTIVITY_CLEAR_TOPIf set, and the activity being launched is already running in the
current task, then instead of launching a new instance of that activity,
all of the other activities on top of it will be closed and this Intent
will be delivered to the (now on top) old activity as a new Intent.
For example, consider a task consisting of the activities: A, B, C, D.
If D calls startActivity() with an Intent that resolves to the component
of activity B, then C and D will be finished and B receive the given
Intent, resulting in the stack now being: A, B.
The currently running instance of task B in the above example will
either receive the new intent you are starting here in its
onNewIntent() method, or be itself finished and restarted with the
new intent. If it has declared its launch mode to be "multiple" (the
default) it will be finished and re-created; for all other launch modes
it will receive the Intent in the current instance.
This launch mode can also be used to good effect in conjunction with
{@link #FLAG_ACTIVITY_NEW_TASK}: if used to start the root activity
of a task, it will bring any currently running instance of that task
to the foreground, and then clear it to its root state. This is
especially useful, for example, when launching an activity from the
notification manager.
See Application Fundamentals:
Activities and Tasks for more details on tasks. | public static final int | FLAG_ACTIVITY_FORWARD_RESULTIf set and this intent is being used to launch a new activity from an
existing one, then the reply target of the existing activity will be
transfered to the new activity. This way the new activity can call
{@link android.app.Activity#setResult} and have that result sent back to
the reply target of the original activity. | public static final int | FLAG_ACTIVITY_PREVIOUS_IS_TOPIf set and this intent is being used to launch a new activity from an
existing one, the current activity will not be counted as the top
activity for deciding whether the new intent should be delivered to
the top instead of starting a new one. The previous activity will
be used as the top, with the assumption being that the current activity
will finish itself immediately. | public static final int | FLAG_ACTIVITY_EXCLUDE_FROM_RECENTSIf set, the new activity is not kept in the list of recently launched
activities. | public static final int | FLAG_ACTIVITY_BROUGHT_TO_FRONTThis flag is not normally set by application code, but set for you by
the system as described in the
{@link android.R.styleable#AndroidManifestActivity_launchMode
launchMode} documentation for the singleTask mode. | public static final int | FLAG_ACTIVITY_RESET_TASK_IF_NEEDEDIf set, and this activity is either being started in a new task or
bringing to the top an existing task, then it will be launched as
the front door of the task. This will result in the application of
any affinities needed to have that task in the proper state (either
moving activities to or from it), or simply resetting that task to
its initial state if needed. | public static final int | FLAG_ACTIVITY_LAUNCHED_FROM_HISTORYThis flag is not normally set by application code, but set for you by
the system if this activity is being launched from history
(longpress home key). | public static final int | FLAG_ACTIVITY_CLEAR_WHEN_TASK_RESETIf set, this marks a point in the task's activity stack that should
be cleared when the task is reset. That is, the next time the task
is broad to the foreground with
{@link #FLAG_ACTIVITY_RESET_TASK_IF_NEEDED} (typically as a result of
the user re-launching it from home), this activity and all on top of
it will be finished so that the user does not return to them, but
instead returns to whatever activity preceeded it.
This is useful for cases where you have a logical break in your
application. For example, an e-mail application may have a command
to view an attachment, which launches an image view activity to
display it. This activity should be part of the e-mail application's
task, since it is a part of the task the user is involved in. However,
if the user leaves that task, and later selects the e-mail app from
home, we may like them to return to the conversation they were
viewing, not the picture attachment, since that is confusing. By
setting this flag when launching the image viewer, that viewer and
any activities it starts will be removed the next time the user returns
to mail. | public static final int | FLAG_ACTIVITY_NO_USER_ACTIONIf set, this flag will prevent the normal {@link android.app.Activity#onUserLeaveHint}
callback from occurring on the current frontmost activity before it is
paused as the newly-started activity is brought to the front.
Typically, an activity can rely on that callback to indicate that an
explicit user action has caused their activity to be moved out of the
foreground. The callback marks an appropriate point in the activity's
lifecycle for it to dismiss any notifications that it intends to display
"until the user has seen them," such as a blinking LED.
If an activity is ever started via any non-user-driven events such as
phone-call receipt or an alarm handler, this flag should be passed to {@link
Context#startActivity Context.startActivity}, ensuring that the pausing
activity does not think the user has acknowledged its notification. | public static final int | FLAG_ACTIVITY_REORDER_TO_FRONTIf set in an Intent passed to {@link Context#startActivity Context.startActivity()},
this flag will cause the launched activity to be brought to the front of its
task's history stack if it is already running.
For example, consider a task consisting of four activities: A, B, C, D.
If D calls startActivity() with an Intent that resolves to the component
of activity B, then B will be brought to the front of the history stack,
with this resulting order: A, C, D, B.
This flag will be ignored if {@link #FLAG_ACTIVITY_CLEAR_TOP} is also
specified. | public static final int | FLAG_RECEIVER_REGISTERED_ONLYIf set, when sending a broadcast only registered receivers will be
called -- no BroadcastReceiver components will be launched. | public static final int | FLAG_RECEIVER_REGISTERED_ONLY_BEFORE_BOOTIf set, when sending a broadcast before boot has completed only
registered receivers will be called -- no BroadcastReceiver components
will be launched. Sticky intent state will be recorded properly even
if no receivers wind up being called. If {@link #FLAG_RECEIVER_REGISTERED_ONLY}
is specified in the broadcast intent, this flag is unnecessary.
This flag is only for use by system sevices as a convenience to
avoid having to implement a more complex mechanism around detection
of boot completion. | private String | mAction | private android.net.Uri | mData | private String | mType | private ComponentName | mComponent | private int | mFlags | private HashSet | mCategories | private android.os.Bundle | mExtras | public static final int | FILL_IN_ACTIONUse with {@link #fillIn} to allow the current action value to be
overwritten, even if it is already set. | public static final int | FILL_IN_DATAUse with {@link #fillIn} to allow the current data or type value
overwritten, even if it is already set. | public static final int | FILL_IN_CATEGORIESUse with {@link #fillIn} to allow the current categories to be
overwritten, even if they are already set. | public static final int | FILL_IN_COMPONENTUse with {@link #fillIn} to allow the current component value to be
overwritten, even if it is already set. | public static final Parcelable.Creator | CREATOR |
Constructors Summary |
---|
public Intent(String action, android.net.Uri uri, Context packageContext, Class cls)Create an intent for a specific component with a specified action and data.
This is equivalent using {@link #Intent(String, android.net.Uri)} to
construct the Intent and then calling {@link #setClass} to set its
class.
Note: scheme and host name matching in the Android framework is
case-sensitive, unlike the formal RFC. As a result,
you should always ensure that you write your Uri with these elements
using lower case letters, and normalize any Uris you receive from
outside of Android to ensure the scheme and host is lower case.
mAction = action;
mData = uri;
mComponent = new ComponentName(packageContext, cls);
| private Intent(android.os.Parcel in)
readFromParcel(in);
| public Intent()Create an empty intent.
// ---------------------------------------------------------------------
| public Intent(Intent o)Copy constructor.
this.mAction = o.mAction;
this.mData = o.mData;
this.mType = o.mType;
this.mComponent = o.mComponent;
this.mFlags = o.mFlags;
if (o.mCategories != null) {
this.mCategories = new HashSet<String>(o.mCategories);
}
if (o.mExtras != null) {
this.mExtras = new Bundle(o.mExtras);
}
| private Intent(Intent o, boolean all)
this.mAction = o.mAction;
this.mData = o.mData;
this.mType = o.mType;
this.mComponent = o.mComponent;
if (o.mCategories != null) {
this.mCategories = new HashSet<String>(o.mCategories);
}
| public Intent(String action)Create an intent with a given action. All other fields (data, type,
class) are null. Note that the action must be in a
namespace because Intents are used globally in the system -- for
example the system VIEW action is android.intent.action.VIEW; an
application's custom action would be something like
com.google.app.myapp.CUSTOM_ACTION.
mAction = action;
| public Intent(String action, android.net.Uri uri)Create an intent with a given action and for a given data url. Note
that the action must be in a namespace because Intents are
used globally in the system -- for example the system VIEW action is
android.intent.action.VIEW; an application's custom action would be
something like com.google.app.myapp.CUSTOM_ACTION.
Note: scheme and host name matching in the Android framework is
case-sensitive, unlike the formal RFC. As a result,
you should always ensure that you write your Uri with these elements
using lower case letters, and normalize any Uris you receive from
outside of Android to ensure the scheme and host is lower case.
mAction = action;
mData = uri;
| public Intent(Context packageContext, Class cls)Create an intent for a specific component. All other fields (action, data,
type, class) are null, though they can be modified later with explicit
calls. This provides a convenient way to create an intent that is
intended to execute a hard-coded class name, rather than relying on the
system to find an appropriate class for you; see {@link #setComponent}
for more information on the repercussions of this.
mComponent = new ComponentName(packageContext, cls);
|
Methods Summary |
---|
public android.content.Intent | addCategory(java.lang.String category)Add a new category to the intent. Categories provide additional detail
about the action the intent is perform. When resolving an intent, only
activities that provide all of the requested categories will be
used.
if (mCategories == null) {
mCategories = new HashSet<String>();
}
mCategories.add(category);
return this;
| public android.content.Intent | addFlags(int flags)Add additional flags to the intent (or with existing flags
value).
mFlags |= flags;
return this;
| public java.lang.Object | clone()
return new Intent(this);
| public android.content.Intent | cloneFilter()Make a clone of only the parts of the Intent that are relevant for
filter matching: the action, data, type, component, and categories.
return new Intent(this, false);
| public static android.content.Intent | createChooser(android.content.Intent target, java.lang.CharSequence title)Convenience function for creating a {@link #ACTION_CHOOSER} Intent.
Intent intent = new Intent(ACTION_CHOOSER);
intent.putExtra(EXTRA_INTENT, target);
if (title != null) {
intent.putExtra(EXTRA_TITLE, title);
}
return intent;
| public int | describeContents()
return (mExtras != null) ? mExtras.describeContents() : 0;
| public int | fillIn(android.content.Intent other, int flags)Copy the contents of other in to this object, but only
where fields are not defined by this object. For purposes of a field
being defined, the following pieces of data in the Intent are
considered to be separate fields:
- action, as set by {@link #setAction}.
- data URI and MIME type, as set by {@link #setData(Uri)},
{@link #setType(String)}, or {@link #setDataAndType(Uri, String)}.
- categories, as set by {@link #addCategory}.
- component, as set by {@link #setComponent(ComponentName)} or
related methods.
- each top-level name in the associated extras.
In addition, you can use the {@link #FILL_IN_ACTION},
{@link #FILL_IN_DATA}, {@link #FILL_IN_CATEGORIES}, and
{@link #FILL_IN_COMPONENT} to override the restriction where the
corresponding field will not be replaced if it is already set.
For example, consider Intent A with {data="foo", categories="bar"}
and Intent B with {action="gotit", data-type="some/thing",
categories="one","two"}.
Calling A.fillIn(B, Intent.FILL_IN_DATA) will result in A now
containing: {action="gotit", data-type="some/thing",
categories="bar"}.
int changes = 0;
if ((mAction == null && other.mAction == null)
|| (flags&FILL_IN_ACTION) != 0) {
mAction = other.mAction;
changes |= FILL_IN_ACTION;
}
if ((mData == null && mType == null &&
(other.mData != null || other.mType != null))
|| (flags&FILL_IN_DATA) != 0) {
mData = other.mData;
mType = other.mType;
changes |= FILL_IN_DATA;
}
if ((mCategories == null && other.mCategories == null)
|| (flags&FILL_IN_CATEGORIES) != 0) {
if (other.mCategories != null) {
mCategories = new HashSet<String>(other.mCategories);
}
changes |= FILL_IN_CATEGORIES;
}
if ((mComponent == null && other.mComponent == null)
|| (flags&FILL_IN_COMPONENT) != 0) {
mComponent = other.mComponent;
changes |= FILL_IN_COMPONENT;
}
mFlags |= other.mFlags;
if (mExtras == null) {
if (other.mExtras != null) {
mExtras = new Bundle(other.mExtras);
}
} else if (other.mExtras != null) {
try {
Bundle newb = new Bundle(other.mExtras);
newb.putAll(mExtras);
mExtras = newb;
} catch (RuntimeException e) {
// Modifying the extras can cause us to unparcel the contents
// of the bundle, and if we do this in the system process that
// may fail. We really should handle this (i.e., the Bundle
// impl shouldn't be on top of a plain map), but for now just
// ignore it and keep the original contents. :(
Log.w("Intent", "Failure filling in extras", e);
}
}
return changes;
| public boolean | filterEquals(android.content.Intent other)Determine if two intents are the same for the purposes of intent
resolution (filtering). That is, if their action, data, type,
class, and categories are the same. This does not compare
any extra data included in the intents.
if (other == null) {
return false;
}
if (mAction != other.mAction) {
if (mAction != null) {
if (!mAction.equals(other.mAction)) {
return false;
}
} else {
if (!other.mAction.equals(mAction)) {
return false;
}
}
}
if (mData != other.mData) {
if (mData != null) {
if (!mData.equals(other.mData)) {
return false;
}
} else {
if (!other.mData.equals(mData)) {
return false;
}
}
}
if (mType != other.mType) {
if (mType != null) {
if (!mType.equals(other.mType)) {
return false;
}
} else {
if (!other.mType.equals(mType)) {
return false;
}
}
}
if (mComponent != other.mComponent) {
if (mComponent != null) {
if (!mComponent.equals(other.mComponent)) {
return false;
}
} else {
if (!other.mComponent.equals(mComponent)) {
return false;
}
}
}
if (mCategories != other.mCategories) {
if (mCategories != null) {
if (!mCategories.equals(other.mCategories)) {
return false;
}
} else {
if (!other.mCategories.equals(mCategories)) {
return false;
}
}
}
return true;
| public int | filterHashCode()Generate hash code that matches semantics of filterEquals().
int code = 0;
if (mAction != null) {
code += mAction.hashCode();
}
if (mData != null) {
code += mData.hashCode();
}
if (mType != null) {
code += mType.hashCode();
}
if (mComponent != null) {
code += mComponent.hashCode();
}
if (mCategories != null) {
code += mCategories.hashCode();
}
return code;
| public java.lang.String | getAction()Retrieve the general action to be performed, such as
{@link #ACTION_VIEW}. The action describes the general way the rest of
the information in the intent should be interpreted -- most importantly,
what to do with the data returned by {@link #getData}.
return mAction;
| public boolean[] | getBooleanArrayExtra(java.lang.String name)Retrieve extended data from the intent.
return mExtras == null ? null : mExtras.getBooleanArray(name);
| public boolean | getBooleanExtra(java.lang.String name, boolean defaultValue)Retrieve extended data from the intent.
return mExtras == null ? defaultValue :
mExtras.getBoolean(name, defaultValue);
| public android.os.Bundle | getBundleExtra(java.lang.String name)Retrieve extended data from the intent.
return mExtras == null ? null : mExtras.getBundle(name);
| public byte[] | getByteArrayExtra(java.lang.String name)Retrieve extended data from the intent.
return mExtras == null ? null : mExtras.getByteArray(name);
| public byte | getByteExtra(java.lang.String name, byte defaultValue)Retrieve extended data from the intent.
return mExtras == null ? defaultValue :
mExtras.getByte(name, defaultValue);
| public java.util.Set | getCategories()Return the set of all categories in the intent. If there are no categories,
returns NULL.
return mCategories;
| public char[] | getCharArrayExtra(java.lang.String name)Retrieve extended data from the intent.
return mExtras == null ? null : mExtras.getCharArray(name);
| public char | getCharExtra(java.lang.String name, char defaultValue)Retrieve extended data from the intent.
return mExtras == null ? defaultValue :
mExtras.getChar(name, defaultValue);
| public java.lang.CharSequence | getCharSequenceExtra(java.lang.String name)Retrieve extended data from the intent.
return mExtras == null ? null : mExtras.getCharSequence(name);
| public ComponentName | getComponent()Retrieve the concrete component associated with the intent. When receiving
an intent, this is the component that was found to best handle it (that is,
yourself) and will always be non-null; in all other cases it will be
null unless explicitly set.
return mComponent;
| public android.net.Uri | getData()Retrieve data this intent is operating on. This URI specifies the name
of the data; often it uses the content: scheme, specifying data in a
content provider. Other schemes may be handled by specific activities,
such as http: by the web browser.
return mData;
| public java.lang.String | getDataString()The same as {@link #getData()}, but returns the URI as an encoded
String.
return mData != null ? mData.toString() : null;
| public double[] | getDoubleArrayExtra(java.lang.String name)Retrieve extended data from the intent.
return mExtras == null ? null : mExtras.getDoubleArray(name);
| public double | getDoubleExtra(java.lang.String name, double defaultValue)Retrieve extended data from the intent.
return mExtras == null ? defaultValue :
mExtras.getDouble(name, defaultValue);
| public java.lang.Object | getExtra(java.lang.String name)Retrieve extended data from the intent.
return getExtra(name, null);
| public java.lang.Object | getExtra(java.lang.String name, java.lang.Object defaultValue)Retrieve extended data from the intent.
Object result = defaultValue;
if (mExtras != null) {
Object result2 = mExtras.get(name);
if (result2 != null) {
result = result2;
}
}
return result;
| public android.os.Bundle | getExtras()Retrieves a map of extended data from the intent.
return (mExtras != null)
? new Bundle(mExtras)
: null;
| public int | getFlags()Retrieve any special flags associated with this intent. You will
normally just set them with {@link #setFlags} and let the system
take the appropriate action with them.
return mFlags;
| public float[] | getFloatArrayExtra(java.lang.String name)Retrieve extended data from the intent.
return mExtras == null ? null : mExtras.getFloatArray(name);
| public float | getFloatExtra(java.lang.String name, float defaultValue)Retrieve extended data from the intent.
return mExtras == null ? defaultValue :
mExtras.getFloat(name, defaultValue);
| public android.os.IBinder | getIBinderExtra(java.lang.String name)Retrieve extended data from the intent.
return mExtras == null ? null : mExtras.getIBinder(name);
| public int[] | getIntArrayExtra(java.lang.String name)Retrieve extended data from the intent.
return mExtras == null ? null : mExtras.getIntArray(name);
| public int | getIntExtra(java.lang.String name, int defaultValue)Retrieve extended data from the intent.
return mExtras == null ? defaultValue :
mExtras.getInt(name, defaultValue);
| public java.util.ArrayList | getIntegerArrayListExtra(java.lang.String name)Retrieve extended data from the intent.
return mExtras == null ? null : mExtras.getIntegerArrayList(name);
| public static android.content.Intent | getIntent(java.lang.String uri)Create an intent from a URI. This URI may encode the action,
category, and other intent fields, if it was returned by toURI(). If
the Intent was not generate by toURI(), its data will be the entire URI
and its action will be ACTION_VIEW.
The URI given here must not be relative -- that is, it must include
the scheme and full path.
int i = 0;
try {
// simple case
i = uri.lastIndexOf("#");
if (i == -1) return new Intent(ACTION_VIEW, Uri.parse(uri));
// old format Intent URI
if (!uri.startsWith("#Intent;", i)) return getIntentOld(uri);
// new format
Intent intent = new Intent(ACTION_VIEW);
// fetch data part, if present
if (i > 0) {
intent.mData = Uri.parse(uri.substring(0, i));
}
i += "#Intent;".length();
// loop over contents of Intent, all name=value;
while (!uri.startsWith("end", i)) {
int eq = uri.indexOf('=", i);
int semi = uri.indexOf(';", eq);
String value = uri.substring(eq + 1, semi);
// action
if (uri.startsWith("action=", i)) {
intent.mAction = value;
}
// categories
else if (uri.startsWith("category=", i)) {
intent.addCategory(value);
}
// type
else if (uri.startsWith("type=", i)) {
intent.mType = value;
}
// launch flags
else if (uri.startsWith("launchFlags=", i)) {
intent.mFlags = Integer.decode(value).intValue();
}
// component
else if (uri.startsWith("component=", i)) {
intent.mComponent = ComponentName.unflattenFromString(value);
}
// extra
else {
String key = Uri.decode(uri.substring(i + 2, eq));
value = Uri.decode(value);
// create Bundle if it doesn't already exist
if (intent.mExtras == null) intent.mExtras = new Bundle();
Bundle b = intent.mExtras;
// add EXTRA
if (uri.startsWith("S.", i)) b.putString(key, value);
else if (uri.startsWith("B.", i)) b.putBoolean(key, Boolean.parseBoolean(value));
else if (uri.startsWith("b.", i)) b.putByte(key, Byte.parseByte(value));
else if (uri.startsWith("c.", i)) b.putChar(key, value.charAt(0));
else if (uri.startsWith("d.", i)) b.putDouble(key, Double.parseDouble(value));
else if (uri.startsWith("f.", i)) b.putFloat(key, Float.parseFloat(value));
else if (uri.startsWith("i.", i)) b.putInt(key, Integer.parseInt(value));
else if (uri.startsWith("l.", i)) b.putLong(key, Long.parseLong(value));
else if (uri.startsWith("s.", i)) b.putShort(key, Short.parseShort(value));
else throw new URISyntaxException(uri, "unknown EXTRA type", i);
}
// move to the next item
i = semi + 1;
}
return intent;
} catch (IndexOutOfBoundsException e) {
throw new URISyntaxException(uri, "illegal Intent URI format", i);
}
| public static android.content.Intent | getIntentOld(java.lang.String uri)
Intent intent;
int i = uri.lastIndexOf('#");
if (i >= 0) {
Uri data = null;
String action = null;
if (i > 0) {
data = Uri.parse(uri.substring(0, i));
}
i++;
if (uri.regionMatches(i, "action(", 0, 7)) {
i += 7;
int j = uri.indexOf(')", i);
action = uri.substring(i, j);
i = j + 1;
}
intent = new Intent(action, data);
if (uri.regionMatches(i, "categories(", 0, 11)) {
i += 11;
int j = uri.indexOf(')", i);
while (i < j) {
int sep = uri.indexOf('!", i);
if (sep < 0) sep = j;
if (i < sep) {
intent.addCategory(uri.substring(i, sep));
}
i = sep + 1;
}
i = j + 1;
}
if (uri.regionMatches(i, "type(", 0, 5)) {
i += 5;
int j = uri.indexOf(')", i);
intent.mType = uri.substring(i, j);
i = j + 1;
}
if (uri.regionMatches(i, "launchFlags(", 0, 12)) {
i += 12;
int j = uri.indexOf(')", i);
intent.mFlags = Integer.decode(uri.substring(i, j)).intValue();
i = j + 1;
}
if (uri.regionMatches(i, "component(", 0, 10)) {
i += 10;
int j = uri.indexOf(')", i);
int sep = uri.indexOf('!", i);
if (sep >= 0 && sep < j) {
String pkg = uri.substring(i, sep);
String cls = uri.substring(sep + 1, j);
intent.mComponent = new ComponentName(pkg, cls);
}
i = j + 1;
}
if (uri.regionMatches(i, "extras(", 0, 7)) {
i += 7;
final int closeParen = uri.indexOf(')", i);
if (closeParen == -1) throw new URISyntaxException(uri,
"EXTRA missing trailing ')'", i);
while (i < closeParen) {
// fetch the key value
int j = uri.indexOf('=", i);
if (j <= i + 1 || i >= closeParen) {
throw new URISyntaxException(uri, "EXTRA missing '='", i);
}
char type = uri.charAt(i);
i++;
String key = uri.substring(i, j);
i = j + 1;
// get type-value
j = uri.indexOf('!", i);
if (j == -1 || j >= closeParen) j = closeParen;
if (i >= j) throw new URISyntaxException(uri, "EXTRA missing '!'", i);
String value = uri.substring(i, j);
i = j;
// create Bundle if it doesn't already exist
if (intent.mExtras == null) intent.mExtras = new Bundle();
// add item to bundle
try {
switch (type) {
case 'S":
intent.mExtras.putString(key, Uri.decode(value));
break;
case 'B":
intent.mExtras.putBoolean(key, Boolean.parseBoolean(value));
break;
case 'b":
intent.mExtras.putByte(key, Byte.parseByte(value));
break;
case 'c":
intent.mExtras.putChar(key, Uri.decode(value).charAt(0));
break;
case 'd":
intent.mExtras.putDouble(key, Double.parseDouble(value));
break;
case 'f":
intent.mExtras.putFloat(key, Float.parseFloat(value));
break;
case 'i":
intent.mExtras.putInt(key, Integer.parseInt(value));
break;
case 'l":
intent.mExtras.putLong(key, Long.parseLong(value));
break;
case 's":
intent.mExtras.putShort(key, Short.parseShort(value));
break;
default:
throw new URISyntaxException(uri, "EXTRA has unknown type", i);
}
} catch (NumberFormatException e) {
throw new URISyntaxException(uri, "EXTRA value can't be parsed", i);
}
char ch = uri.charAt(i);
if (ch == ')") break;
if (ch != '!") throw new URISyntaxException(uri, "EXTRA missing '!'", i);
i++;
}
}
if (intent.mAction == null) {
// By default, if no action is specified, then use VIEW.
intent.mAction = ACTION_VIEW;
}
} else {
intent = new Intent(ACTION_VIEW, Uri.parse(uri));
}
return intent;
| public long[] | getLongArrayExtra(java.lang.String name)Retrieve extended data from the intent.
return mExtras == null ? null : mExtras.getLongArray(name);
| public long | getLongExtra(java.lang.String name, long defaultValue)Retrieve extended data from the intent.
return mExtras == null ? defaultValue :
mExtras.getLong(name, defaultValue);
| public android.os.Parcelable[] | getParcelableArrayExtra(java.lang.String name)Retrieve extended data from the intent.
return mExtras == null ? null : mExtras.getParcelableArray(name);
| public java.util.ArrayList | getParcelableArrayListExtra(java.lang.String name)Retrieve extended data from the intent.
return mExtras == null ? null : mExtras.<T>getParcelableArrayList(name);
| public T | getParcelableExtra(java.lang.String name)Retrieve extended data from the intent.
return mExtras == null ? null : mExtras.<T>getParcelable(name);
| public java.lang.String | getScheme()Return the scheme portion of the intent's data. If the data is null or
does not include a scheme, null is returned. Otherwise, the scheme
prefix without the final ':' is returned, i.e. "http".
This is the same as calling getData().getScheme() (and checking for
null data).
return mData != null ? mData.getScheme() : null;
| public java.io.Serializable | getSerializableExtra(java.lang.String name)Retrieve extended data from the intent.
return mExtras == null ? null : mExtras.getSerializable(name);
| public short[] | getShortArrayExtra(java.lang.String name)Retrieve extended data from the intent.
return mExtras == null ? null : mExtras.getShortArray(name);
| public short | getShortExtra(java.lang.String name, short defaultValue)Retrieve extended data from the intent.
return mExtras == null ? defaultValue :
mExtras.getShort(name, defaultValue);
| public java.lang.String[] | getStringArrayExtra(java.lang.String name)Retrieve extended data from the intent.
return mExtras == null ? null : mExtras.getStringArray(name);
| public java.util.ArrayList | getStringArrayListExtra(java.lang.String name)Retrieve extended data from the intent.
return mExtras == null ? null : mExtras.getStringArrayList(name);
| public java.lang.String | getStringExtra(java.lang.String name)Retrieve extended data from the intent.
return mExtras == null ? null : mExtras.getString(name);
| public java.lang.String | getType()Retrieve any explicit MIME type included in the intent. This is usually
null, as the type is determined by the intent data.
return mType;
| public boolean | hasCategory(java.lang.String category)Check if an category exists in the intent.
return mCategories != null && mCategories.contains(category);
| public boolean | hasExtra(java.lang.String name)Returns true if an extra value is associated with the given name.
return mExtras != null && mExtras.containsKey(name);
| public boolean | hasFileDescriptors()Returns true if the Intent's extras contain a parcelled file descriptor.
return mExtras != null && mExtras.hasFileDescriptors();
| public static android.content.Intent | parseIntent(android.content.res.Resources resources, org.xmlpull.v1.XmlPullParser parser, android.util.AttributeSet attrs)Parses the "intent" element (and its children) from XML and instantiates
an Intent object. The given XML parser should be located at the tag
where parsing should start (often named "intent"), from which the
basic action, data, type, and package and class name will be
retrieved. The function will then parse in to any child elements,
looking for tags to add categories and
to attach extra data
to the intent.
Intent intent = new Intent();
TypedArray sa = resources.obtainAttributes(attrs,
com.android.internal.R.styleable.Intent);
intent.setAction(sa.getString(com.android.internal.R.styleable.Intent_action));
String data = sa.getString(com.android.internal.R.styleable.Intent_data);
String mimeType = sa.getString(com.android.internal.R.styleable.Intent_mimeType);
intent.setDataAndType(data != null ? Uri.parse(data) : null, mimeType);
String packageName = sa.getString(com.android.internal.R.styleable.Intent_targetPackage);
String className = sa.getString(com.android.internal.R.styleable.Intent_targetClass);
if (packageName != null && className != null) {
intent.setComponent(new ComponentName(packageName, className));
}
sa.recycle();
int outerDepth = parser.getDepth();
int type;
while ((type=parser.next()) != XmlPullParser.END_DOCUMENT
&& (type != XmlPullParser.END_TAG || parser.getDepth() > outerDepth)) {
if (type == XmlPullParser.END_TAG || type == XmlPullParser.TEXT) {
continue;
}
String nodeName = parser.getName();
if (nodeName.equals("category")) {
sa = resources.obtainAttributes(attrs,
com.android.internal.R.styleable.IntentCategory);
String cat = sa.getString(com.android.internal.R.styleable.IntentCategory_name);
sa.recycle();
if (cat != null) {
intent.addCategory(cat);
}
XmlUtils.skipCurrentTag(parser);
} else if (nodeName.equals("extra")) {
if (intent.mExtras == null) {
intent.mExtras = new Bundle();
}
resources.parseBundleExtra("extra", attrs, intent.mExtras);
XmlUtils.skipCurrentTag(parser);
} else {
XmlUtils.skipCurrentTag(parser);
}
}
return intent;
| public android.content.Intent | putExtra(java.lang.String name, boolean value)Add extended data to the intent. The name must include a package
prefix, for example the app com.android.contacts would use names
like "com.android.contacts.ShowAll".
if (mExtras == null) {
mExtras = new Bundle();
}
mExtras.putBoolean(name, value);
return this;
| public android.content.Intent | putExtra(java.lang.String name, byte value)Add extended data to the intent. The name must include a package
prefix, for example the app com.android.contacts would use names
like "com.android.contacts.ShowAll".
if (mExtras == null) {
mExtras = new Bundle();
}
mExtras.putByte(name, value);
return this;
| public android.content.Intent | putExtra(java.lang.String name, char value)Add extended data to the intent. The name must include a package
prefix, for example the app com.android.contacts would use names
like "com.android.contacts.ShowAll".
if (mExtras == null) {
mExtras = new Bundle();
}
mExtras.putChar(name, value);
return this;
| public android.content.Intent | putExtra(java.lang.String name, short value)Add extended data to the intent. The name must include a package
prefix, for example the app com.android.contacts would use names
like "com.android.contacts.ShowAll".
if (mExtras == null) {
mExtras = new Bundle();
}
mExtras.putShort(name, value);
return this;
| public android.content.Intent | putExtra(java.lang.String name, int value)Add extended data to the intent. The name must include a package
prefix, for example the app com.android.contacts would use names
like "com.android.contacts.ShowAll".
if (mExtras == null) {
mExtras = new Bundle();
}
mExtras.putInt(name, value);
return this;
| public android.content.Intent | putExtra(java.lang.String name, long value)Add extended data to the intent. The name must include a package
prefix, for example the app com.android.contacts would use names
like "com.android.contacts.ShowAll".
if (mExtras == null) {
mExtras = new Bundle();
}
mExtras.putLong(name, value);
return this;
| public android.content.Intent | putExtra(java.lang.String name, float value)Add extended data to the intent. The name must include a package
prefix, for example the app com.android.contacts would use names
like "com.android.contacts.ShowAll".
if (mExtras == null) {
mExtras = new Bundle();
}
mExtras.putFloat(name, value);
return this;
| public android.content.Intent | putExtra(java.lang.String name, double value)Add extended data to the intent. The name must include a package
prefix, for example the app com.android.contacts would use names
like "com.android.contacts.ShowAll".
if (mExtras == null) {
mExtras = new Bundle();
}
mExtras.putDouble(name, value);
return this;
| public android.content.Intent | putExtra(java.lang.String name, java.lang.String value)Add extended data to the intent. The name must include a package
prefix, for example the app com.android.contacts would use names
like "com.android.contacts.ShowAll".
if (mExtras == null) {
mExtras = new Bundle();
}
mExtras.putString(name, value);
return this;
| public android.content.Intent | putExtra(java.lang.String name, java.lang.CharSequence value)Add extended data to the intent. The name must include a package
prefix, for example the app com.android.contacts would use names
like "com.android.contacts.ShowAll".
if (mExtras == null) {
mExtras = new Bundle();
}
mExtras.putCharSequence(name, value);
return this;
| public android.content.Intent | putExtra(java.lang.String name, android.os.Parcelable value)Add extended data to the intent. The name must include a package
prefix, for example the app com.android.contacts would use names
like "com.android.contacts.ShowAll".
if (mExtras == null) {
mExtras = new Bundle();
}
mExtras.putParcelable(name, value);
return this;
| public android.content.Intent | putExtra(java.lang.String name, android.os.Parcelable[] value)Add extended data to the intent. The name must include a package
prefix, for example the app com.android.contacts would use names
like "com.android.contacts.ShowAll".
if (mExtras == null) {
mExtras = new Bundle();
}
mExtras.putParcelableArray(name, value);
return this;
| public android.content.Intent | putExtra(java.lang.String name, java.io.Serializable value)Add extended data to the intent. The name must include a package
prefix, for example the app com.android.contacts would use names
like "com.android.contacts.ShowAll".
if (mExtras == null) {
mExtras = new Bundle();
}
mExtras.putSerializable(name, value);
return this;
| public android.content.Intent | putExtra(java.lang.String name, boolean[] value)Add extended data to the intent. The name must include a package
prefix, for example the app com.android.contacts would use names
like "com.android.contacts.ShowAll".
if (mExtras == null) {
mExtras = new Bundle();
}
mExtras.putBooleanArray(name, value);
return this;
| public android.content.Intent | putExtra(java.lang.String name, byte[] value)Add extended data to the intent. The name must include a package
prefix, for example the app com.android.contacts would use names
like "com.android.contacts.ShowAll".
if (mExtras == null) {
mExtras = new Bundle();
}
mExtras.putByteArray(name, value);
return this;
| public android.content.Intent | putExtra(java.lang.String name, short[] value)Add extended data to the intent. The name must include a package
prefix, for example the app com.android.contacts would use names
like "com.android.contacts.ShowAll".
if (mExtras == null) {
mExtras = new Bundle();
}
mExtras.putShortArray(name, value);
return this;
| public android.content.Intent | putExtra(java.lang.String name, char[] value)Add extended data to the intent. The name must include a package
prefix, for example the app com.android.contacts would use names
like "com.android.contacts.ShowAll".
if (mExtras == null) {
mExtras = new Bundle();
}
mExtras.putCharArray(name, value);
return this;
| public android.content.Intent | putExtra(java.lang.String name, int[] value)Add extended data to the intent. The name must include a package
prefix, for example the app com.android.contacts would use names
like "com.android.contacts.ShowAll".
if (mExtras == null) {
mExtras = new Bundle();
}
mExtras.putIntArray(name, value);
return this;
| public android.content.Intent | putExtra(java.lang.String name, long[] value)Add extended data to the intent. The name must include a package
prefix, for example the app com.android.contacts would use names
like "com.android.contacts.ShowAll".
if (mExtras == null) {
mExtras = new Bundle();
}
mExtras.putLongArray(name, value);
return this;
| public android.content.Intent | putExtra(java.lang.String name, float[] value)Add extended data to the intent. The name must include a package
prefix, for example the app com.android.contacts would use names
like "com.android.contacts.ShowAll".
if (mExtras == null) {
mExtras = new Bundle();
}
mExtras.putFloatArray(name, value);
return this;
| public android.content.Intent | putExtra(java.lang.String name, double[] value)Add extended data to the intent. The name must include a package
prefix, for example the app com.android.contacts would use names
like "com.android.contacts.ShowAll".
if (mExtras == null) {
mExtras = new Bundle();
}
mExtras.putDoubleArray(name, value);
return this;
| public android.content.Intent | putExtra(java.lang.String name, java.lang.String[] value)Add extended data to the intent. The name must include a package
prefix, for example the app com.android.contacts would use names
like "com.android.contacts.ShowAll".
if (mExtras == null) {
mExtras = new Bundle();
}
mExtras.putStringArray(name, value);
return this;
| public android.content.Intent | putExtra(java.lang.String name, android.os.Bundle value)Add extended data to the intent. The name must include a package
prefix, for example the app com.android.contacts would use names
like "com.android.contacts.ShowAll".
if (mExtras == null) {
mExtras = new Bundle();
}
mExtras.putBundle(name, value);
return this;
| public android.content.Intent | putExtra(java.lang.String name, android.os.IBinder value)Add extended data to the intent. The name must include a package
prefix, for example the app com.android.contacts would use names
like "com.android.contacts.ShowAll".
if (mExtras == null) {
mExtras = new Bundle();
}
mExtras.putIBinder(name, value);
return this;
| public android.content.Intent | putExtras(android.content.Intent src)Copy all extras in 'src' in to this intent.
if (src.mExtras != null) {
if (mExtras == null) {
mExtras = new Bundle(src.mExtras);
} else {
mExtras.putAll(src.mExtras);
}
}
return this;
| public android.content.Intent | putExtras(android.os.Bundle extras)Add a set of extended data to the intent. The keys must include a package
prefix, for example the app com.android.contacts would use names
like "com.android.contacts.ShowAll".
if (mExtras == null) {
mExtras = new Bundle();
}
mExtras.putAll(extras);
return this;
| public android.content.Intent | putIntegerArrayListExtra(java.lang.String name, java.util.ArrayList value)Add extended data to the intent. The name must include a package
prefix, for example the app com.android.contacts would use names
like "com.android.contacts.ShowAll".
if (mExtras == null) {
mExtras = new Bundle();
}
mExtras.putIntegerArrayList(name, value);
return this;
| public android.content.Intent | putParcelableArrayListExtra(java.lang.String name, java.util.ArrayList value)Add extended data to the intent. The name must include a package
prefix, for example the app com.android.contacts would use names
like "com.android.contacts.ShowAll".
if (mExtras == null) {
mExtras = new Bundle();
}
mExtras.putParcelableArrayList(name, value);
return this;
| public android.content.Intent | putStringArrayListExtra(java.lang.String name, java.util.ArrayList value)Add extended data to the intent. The name must include a package
prefix, for example the app com.android.contacts would use names
like "com.android.contacts.ShowAll".
if (mExtras == null) {
mExtras = new Bundle();
}
mExtras.putStringArrayList(name, value);
return this;
| public void | readFromParcel(android.os.Parcel in)
mAction = in.readString();
mData = Uri.CREATOR.createFromParcel(in);
mType = in.readString();
mFlags = in.readInt();
mComponent = ComponentName.readFromParcel(in);
int N = in.readInt();
if (N > 0) {
mCategories = new HashSet<String>();
int i;
for (i=0; i<N; i++) {
mCategories.add(in.readString());
}
} else {
mCategories = null;
}
mExtras = in.readBundle();
| public void | removeCategory(java.lang.String category)Remove an category from an intent.
if (mCategories != null) {
mCategories.remove(category);
if (mCategories.size() == 0) {
mCategories = null;
}
}
| public void | removeExtra(java.lang.String name)Remove extended data from the intent.
if (mExtras != null) {
mExtras.remove(name);
if (mExtras.size() == 0) {
mExtras = null;
}
}
| public android.content.Intent | replaceExtras(android.content.Intent src)Completely replace the extras in the Intent with the extras in the
given Intent.
mExtras = src.mExtras != null ? new Bundle(src.mExtras) : null;
return this;
| public android.content.Intent | replaceExtras(android.os.Bundle extras)Completely replace the extras in the Intent with the given Bundle of
extras.
mExtras = extras != null ? new Bundle(extras) : null;
return this;
| public ComponentName | resolveActivity(android.content.pm.PackageManager pm)Return the Activity component that should be used to handle this intent.
The appropriate component is determined based on the information in the
intent, evaluated as follows:
If {@link #getComponent} returns an explicit class, that is returned
without any further consideration.
The activity must handle the {@link Intent#CATEGORY_DEFAULT} Intent
category to be considered.
If {@link #getAction} is non-NULL, the activity must handle this
action.
If {@link #resolveType} returns non-NULL, the activity must handle
this type.
If {@link #addCategory} has added any categories, the activity must
handle ALL of the categories specified.
If there are no activities that satisfy all of these conditions, a
null string is returned.
If multiple activities are found to satisfy the intent, the one with
the highest priority will be used. If there are multiple activities
with the same priority, the system will either pick the best activity
based on user preference, or resolve to a system class that will allow
the user to pick an activity and forward from there.
This method is implemented simply by calling
{@link PackageManager#resolveActivity} with the "defaultOnly" parameter
true.
This API is called for you as part of starting an activity from an
intent. You do not normally need to call it yourself.
if (mComponent != null) {
return mComponent;
}
ResolveInfo info = pm.resolveActivity(
this, PackageManager.MATCH_DEFAULT_ONLY);
if (info != null) {
return new ComponentName(
info.activityInfo.applicationInfo.packageName,
info.activityInfo.name);
}
return null;
| public android.content.pm.ActivityInfo | resolveActivityInfo(android.content.pm.PackageManager pm, int flags)Resolve the Intent into an {@link ActivityInfo}
describing the activity that should execute the intent. Resolution
follows the same rules as described for {@link #resolveActivity}, but
you get back the completely information about the resolved activity
instead of just its class name.
ActivityInfo ai = null;
if (mComponent != null) {
try {
ai = pm.getActivityInfo(mComponent, flags);
} catch (PackageManager.NameNotFoundException e) {
// ignore
}
} else {
ResolveInfo info = pm.resolveActivity(
this, PackageManager.MATCH_DEFAULT_ONLY);
if (info != null) {
ai = info.activityInfo;
}
}
return ai;
| public java.lang.String | resolveType(Context context)Return the MIME data type of this intent. If the type field is
explicitly set, that is simply returned. Otherwise, if the data is set,
the type of that data is returned. If neither fields are set, a null is
returned.
return resolveType(context.getContentResolver());
| public java.lang.String | resolveType(ContentResolver resolver)Return the MIME data type of this intent. If the type field is
explicitly set, that is simply returned. Otherwise, if the data is set,
the type of that data is returned. If neither fields are set, a null is
returned.
if (mType != null) {
return mType;
}
if (mData != null) {
if ("content".equals(mData.getScheme())) {
return resolver.getType(mData);
}
}
return null;
| public java.lang.String | resolveTypeIfNeeded(ContentResolver resolver)Return the MIME data type of this intent, only if it will be needed for
intent resolution. This is not generally useful for application code;
it is used by the frameworks for communicating with back-end system
services.
if (mComponent != null) {
return mType;
}
return resolveType(resolver);
| public android.content.Intent | setAction(java.lang.String action)Set the general action to be performed.
mAction = action;
return this;
| public android.content.Intent | setClass(Context packageContext, java.lang.Class cls)Convenience for calling {@link #setComponent(ComponentName)} with the
name returned by a {@link Class} object.
mComponent = new ComponentName(packageContext, cls);
return this;
| public android.content.Intent | setClassName(Context packageContext, java.lang.String className)Convenience for calling {@link #setComponent} with an
explicit class name.
mComponent = new ComponentName(packageContext, className);
return this;
| public android.content.Intent | setClassName(java.lang.String packageName, java.lang.String className)Convenience for calling {@link #setComponent} with an
explicit application package name and class name.
mComponent = new ComponentName(packageName, className);
return this;
| public android.content.Intent | setComponent(ComponentName component)(Usually optional) Explicitly set the component to handle the intent.
If left with the default value of null, the system will determine the
appropriate class to use based on the other fields (action, data,
type, categories) in the Intent. If this class is defined, the
specified class will always be used regardless of the other fields. You
should only set this value when you know you absolutely want a specific
class to be used; otherwise it is better to let the system find the
appropriate class so that you will respect the installed applications
and user preferences.
mComponent = component;
return this;
| public android.content.Intent | setData(android.net.Uri data)Set the data this intent is operating on. This method automatically
clears any type that was previously set by {@link #setType}.
Note: scheme and host name matching in the Android framework is
case-sensitive, unlike the formal RFC. As a result,
you should always ensure that you write your Uri with these elements
using lower case letters, and normalize any Uris you receive from
outside of Android to ensure the scheme and host is lower case.
mData = data;
mType = null;
return this;
| public android.content.Intent | setDataAndType(android.net.Uri data, java.lang.String type)(Usually optional) Set the data for the intent along with an explicit
MIME data type. This method should very rarely be used -- it allows you
to override the MIME type that would ordinarily be inferred from the
data with your own type given here.
Note: MIME type, Uri scheme, and host name matching in the
Android framework is case-sensitive, unlike the formal RFC definitions.
As a result, you should always write these elements with lower case letters,
and normalize any MIME types or Uris you receive from
outside of Android to ensure these elements are lower case before
supplying them here.
mData = data;
mType = type;
return this;
| public void | setExtrasClassLoader(java.lang.ClassLoader loader)Sets the ClassLoader that will be used when unmarshalling
any Parcelable values from the extras of this Intent.
if (mExtras != null) {
mExtras.setClassLoader(loader);
}
| public android.content.Intent | setFlags(int flags)Set special flags controlling how this intent is handled. Most values
here depend on the type of component being executed by the Intent,
specifically the FLAG_ACTIVITY_* flags are all for use with
{@link Context#startActivity Context.startActivity()} and the
FLAG_RECEIVER_* flags are all for use with
{@link Context#sendBroadcast(Intent) Context.sendBroadcast()}.
See the Application Fundamentals:
Activities and Tasks documentation for important information on how some of these options impact
the behavior of your application.
mFlags = flags;
return this;
| public android.content.Intent | setType(java.lang.String type)Set an explicit MIME data type. This is used to create intents that
only specify a type and not data, for example to indicate the type of
data to return. This method automatically clears any data that was
previously set by {@link #setData}.
Note: MIME type matching in the Android framework is
case-sensitive, unlike formal RFC MIME types. As a result,
you should always write your MIME types with lower case letters,
and any MIME types you receive from outside of Android should be
converted to lower case before supplying them here.
mData = null;
mType = type;
return this;
| public java.lang.String | toString()
StringBuilder b = new StringBuilder();
b.append("Intent {");
if (mAction != null) b.append(" action=").append(mAction);
if (mCategories != null) {
b.append(" categories={");
Iterator<String> i = mCategories.iterator();
boolean didone = false;
while (i.hasNext()) {
if (didone) b.append(",");
didone = true;
b.append(i.next());
}
b.append("}");
}
if (mData != null) b.append(" data=").append(mData);
if (mType != null) b.append(" type=").append(mType);
if (mFlags != 0) b.append(" flags=0x").append(Integer.toHexString(mFlags));
if (mComponent != null) b.append(" comp=").append(mComponent.toShortString());
if (mExtras != null) b.append(" (has extras)");
b.append(" }");
return b.toString();
| public java.lang.String | toURI()
StringBuilder uri = new StringBuilder(mData != null ? mData.toString() : "");
uri.append("#Intent;");
if (mAction != null) {
uri.append("action=").append(mAction).append(';");
}
if (mCategories != null) {
for (String category : mCategories) {
uri.append("category=").append(category).append(';");
}
}
if (mType != null) {
uri.append("type=").append(mType).append(';");
}
if (mFlags != 0) {
uri.append("launchFlags=0x").append(Integer.toHexString(mFlags)).append(';");
}
if (mComponent != null) {
uri.append("component=").append(mComponent.flattenToShortString()).append(';");
}
if (mExtras != null) {
for (String key : mExtras.keySet()) {
final Object value = mExtras.get(key);
char entryType =
value instanceof String ? 'S" :
value instanceof Boolean ? 'B" :
value instanceof Byte ? 'b" :
value instanceof Character ? 'c" :
value instanceof Double ? 'd" :
value instanceof Float ? 'f" :
value instanceof Integer ? 'i" :
value instanceof Long ? 'l" :
value instanceof Short ? 's" :
'\0";
if (entryType != '\0") {
uri.append(entryType);
uri.append('.");
uri.append(Uri.encode(key));
uri.append('=");
uri.append(Uri.encode(value.toString()));
uri.append(';");
}
}
}
uri.append("end");
return uri.toString();
| public void | writeToParcel(android.os.Parcel out, int flags)
out.writeString(mAction);
Uri.writeToParcel(out, mData);
out.writeString(mType);
out.writeInt(mFlags);
ComponentName.writeToParcel(mComponent, out);
if (mCategories != null) {
out.writeInt(mCategories.size());
for (String category : mCategories) {
out.writeString(category);
}
} else {
out.writeInt(0);
}
out.writeBundle(mExtras);
|
|