android_common_components_dev_doc

Common intents

An intent lets you start an activity in another app by describing an action you'd like to perform, such as "view a map" or "take a picture," in an Intent object. This type of intent is called an implicit intent because it doesn't specify the app component to start, but instead specifies an action and provides some data with which to perform the action.

When you call startActivity() or startActivityForResult() and pass it an implicit intent, the system resolves the intent to an app that can handle the intent and starts its corresponding Activity. If there's more than one app that can handle the intent, the system presents the user with a dialog to pick which app to use.

This page describes several implicit intents that you can use to perform common actions, organized by the type of app that handles the intent. Each section also shows how you can create an intent filter to advertise your app's ability to perform the action.

Caution: If there are no apps on the device that can receive an implicit intent, an app crashes when it calls startActivity(). To first verify that an app exists to receive the intent, call resolveActivity() on your Intent object. If the result is non-null, there is at least one app that can handle the intent, and it's safe to call startActivity(). If the result is null, don't use the intent and, if possible, disable the feature that invokes the intent.

If you're not familiar with how to create intents or intent filters, first read Intents and Intent Filters.

To learn how to fire the intents listed on this page from your development host, see the Verify intents with the Android Debug Bridge section.
Google Voice Actions

Google Voice Actions fires some of the intents listed on this page in response to voice commands. For more information, see Get Started with System Voice Actions.
Alarm clock

The following are common actions for alarm clock apps, including the information you need to create an intent filter to advertise your app's ability to perform each action.
Create an alarm

To create a new alarm, use the ACTION_SET_ALARM action and specify alarm details such as the time and message using the following extras.

Note: Only the hour, minutes, and message extras are available in Android 2.3 (API level 9) and lower. The other extras are available in higher versions of the platform.

Action
    ACTION_SET_ALARM
Data URI
    None
MIME Type
    None 
Extras

    EXTRA_HOUR
        The hour for the alarm.
    EXTRA_MINUTES
        The minutes for the alarm.
    EXTRA_MESSAGE
        A custom message to identify the alarm.
    EXTRA_DAYS
        An ArrayList including each week day on which this alarm repeats. Each day must be declared with an integer from the Calendar class, such as MONDAY.

        For a one-time alarm, don't specify this extra.
    EXTRA_RINGTONE
        A content: URI specifying a ringtone to use with the alarm, or VALUE_RINGTONE_SILENT for no ringtone.

        To use the default ringtone, don't specify this extra.
    EXTRA_VIBRATE
        A boolean specifying whether to vibrate for this alarm.
    EXTRA_SKIP_UI
        A boolean specifying whether the responding app must skip its UI when setting the alarm. If true, the app must bypass any confirmation UI and set the specified alarm.

Example intent:
Kotlin
Java

fun createAlarm(message: String, hour: Int, minutes: Int) {
    val intent = Intent(AlarmClock.ACTION_SET_ALARM).apply {
        putExtra(AlarmClock.EXTRA_MESSAGE, message)
        putExtra(AlarmClock.EXTRA_HOUR, hour)
        putExtra(AlarmClock.EXTRA_MINUTES, minutes)
    }
    if (intent.resolveActivity(packageManager) != null) {
        startActivity(intent)
    }
}

Note:

To invoke the ACTION_SET_ALARM intent, your app must have the SET_ALARM permission:

<uses-permission android:name="com.android.alarm.permission.SET_ALARM" />

Example intent filter:

<activity ...>
    <intent-filter>
        <action android:name="android.intent.action.SET_ALARM" />
        <category android:name="android.intent.category.DEFAULT" />
    </intent-filter>
</activity>

Create a timer

Google Voice Actions

    "set timer for 5 minutes"

To create a countdown timer, use the ACTION_SET_TIMER action and specify timer details such as the duration using the following extras.

Note: This intent is available in Android 4.4 (API level 19) and higher.

Action
    ACTION_SET_TIMER
Data URI
    None
MIME Type
    None 
Extras

    EXTRA_LENGTH
        The length of the timer in seconds.
    EXTRA_MESSAGE
        A custom message to identify the timer.
    EXTRA_SKIP_UI
        A boolean specifying whether the responding app must skip its UI when setting the timer. If true, the app must bypass any confirmation UI and start the specified timer.

Example intent:
Kotlin
Java

fun startTimer(message: String, seconds: Int) {
    val intent = Intent(AlarmClock.ACTION_SET_TIMER).apply {
        putExtra(AlarmClock.EXTRA_MESSAGE, message)
        putExtra(AlarmClock.EXTRA_LENGTH, seconds)
        putExtra(AlarmClock.EXTRA_SKIP_UI, true)
    }
    if (intent.resolveActivity(packageManager) != null) {
        startActivity(intent)
    }
}

Note:

To invoke the ACTION_SET_TIMER intent, your app must have the SET_ALARM permission:

<uses-permission android:name="com.android.alarm.permission.SET_ALARM" />

Example intent filter:

<activity ...>
    <intent-filter>
        <action android:name="android.intent.action.SET_TIMER" />
        <category android:name="android.intent.category.DEFAULT" />
    </intent-filter>
</activity>

Show all alarms

To show the list of alarms, use the ACTION_SHOW_ALARMS action.

Although not many apps invoke this intent, as it's primarily used by system apps, any app that behaves as an alarm clock can implement this intent filter and respond by showing the list of current alarms.

Note: This intent is available in Android 4.4 (API level 19) and higher.

Action
    ACTION_SHOW_ALARMS
Data URI
    None
MIME Type
    None 

Example intent filter:

<activity ...>
    <intent-filter>
        <action android:name="android.intent.action.SHOW_ALARMS" />
        <category android:name="android.intent.category.DEFAULT" />
    </intent-filter>
</activity>

Calendar

Adding an event is a common action for calendar apps. Create an intent filter to advertise your app's ability to perform this action using the information in the following section.
Add a calendar event

To add a new event to the user's calendar, use the ACTION_INSERT action and specify the data URI using Events.CONTENT_URI. You can then specify various event details using the following extras.

Action
    ACTION_INSERT
Data URI
    Events.CONTENT_URI
MIME Type
    "vnd.android.cursor.dir/event" 
Extras

    EXTRA_EVENT_ALL_DAY
        A boolean specifying whether this is an all-day event.
    EXTRA_EVENT_BEGIN_TIME
        The start time of the event (milliseconds since epoch).
    EXTRA_EVENT_END_TIME
        The end time of the event (milliseconds since epoch).
    TITLE
        The event title.
    DESCRIPTION
        The event description.
    EVENT_LOCATION
        The event location.
    EXTRA_EMAIL
        A comma-separated list of email addresses that specify the invitees.

    Many more event details can be specified using the constants defined in the CalendarContract.EventsColumns class.

Example intent:
Kotlin
Java

fun addEvent(title: String, location: String, begin: Long, end: Long) {
    val intent = Intent(Intent.ACTION_INSERT).apply {
        data = Events.CONTENT_URI
        putExtra(Events.TITLE, title)
        putExtra(Events.EVENT_LOCATION, location)
        putExtra(CalendarContract.EXTRA_EVENT_BEGIN_TIME, begin)
        putExtra(CalendarContract.EXTRA_EVENT_END_TIME, end)
    }
    if (intent.resolveActivity(packageManager) != null) {
        startActivity(intent)
    }
}

Example intent filter:

<activity ...>
    <intent-filter>
        <action android:name="android.intent.action.INSERT" />
        <data android:mimeType="vnd.android.cursor.dir/event" />
        <category android:name="android.intent.category.DEFAULT" />
    </intent-filter>
</activity>

Camera

The following are common actions for camera apps, including the information you need to create an intent filter to advertise your app's ability to perform each action.
Capture a picture or video and return it

To open a camera app and receive the resulting photo or video, use the ACTION_IMAGE_CAPTURE or ACTION_VIDEO_CAPTURE action. Also specify the URI location where you'd like the camera to save the photo or video, in the EXTRA_OUTPUT extra.

Action
    ACTION_IMAGE_CAPTURE or
    ACTION_VIDEO_CAPTURE
Data URI Scheme
    None
MIME Type
    None
Extras

    EXTRA_OUTPUT
        The URI location where the camera app saves the photo or video file (as a Uri object).

When the camera app successfully returns focus to your activity—in other words, your app receives the onActivityResult() callback—you can access the photo or video at the URI you specified with the EXTRA_OUTPUT value.

Note: When you use ACTION_IMAGE_CAPTURE to capture a photo, the camera might also return a downscaled copy, or thumbnail, of the photo in the result Intent, saved as a Bitmap in an extra field named "data".

Example intent:
Kotlin
Java

const val REQUEST_IMAGE_CAPTURE = 1
val locationForPhotos: Uri = ...

fun capturePhoto(targetFilename: String) {
    val intent = Intent(MediaStore.ACTION_IMAGE_CAPTURE).apply {
        putExtra(MediaStore.EXTRA_OUTPUT, Uri.withAppendedPath(locationForPhotos, targetFilename))
    }
    if (intent.resolveActivity(packageManager) != null) {
        startActivityForResult(intent, REQUEST_IMAGE_CAPTURE)
    }
}

override fun onActivityResult(requestCode: Int, resultCode: Int, data: Intent) {
    if (requestCode == REQUEST_IMAGE_CAPTURE && resultCode == Activity.RESULT_OK) {
        val thumbnail: Bitmap = data.getParcelableExtra("data")
        // Do other work with full size photo saved in locationForPhotos.
        ...
    }
}

To do this when working on Android 12 (API level 31) or higher, refer to the following intent example.

Example intent:
Kotlin
Java

val REQUEST_IMAGE_CAPTURE = 1

private fun dispatchTakePictureIntent() {
    val takePictureIntent = Intent(MediaStore.ACTION_IMAGE_CAPTURE)
    try {
        startActivityForResult(takePictureIntent, REQUEST_IMAGE_CAPTURE)
    } catch (e: ActivityNotFoundException) {
        // Display error state to the user.
    }
}

For more information about how to use this intent to capture a photo, including how to create an appropriate Uri for the output location, read Take photos or Take videos.

Example intent filter:

<activity ...>
    <intent-filter>
        <action android:name="android.media.action.IMAGE_CAPTURE" />
        <category android:name="android.intent.category.DEFAULT" />
    </intent-filter>
</activity>

When handling this intent, have your activity check for the EXTRA_OUTPUT extra in the incoming Intent, then save the captured image or video at the location specified by that extra and call setResult() with an Intent that includes a compressed thumbnail in an extra named "data".
Start a camera app in still image mode

Google Voice Actions

    "take a picture"

To open a camera app in still image mode, use the INTENT_ACTION_STILL_IMAGE_CAMERA action.

Action
    INTENT_ACTION_STILL_IMAGE_CAMERA
Data URI Scheme
    None
MIME Type
    None
Extras
    None

Example intent:
Kotlin
Java

private fun dispatchTakePictureIntent() {
    val takePictureIntent = Intent(MediaStore.ACTION_IMAGE_CAPTURE)
    try {
        startActivityForResult(takePictureIntent, REQUEST_IMAGE_CAPTURE)
    } catch (e: ActivityNotFoundException) {
        // Display error state to the user.
    }
}

Example intent filter:

<activity ...>
    <intent-filter>
        <action android:name="android.media.action.STILL_IMAGE_CAMERA" />
        <category android:name="android.intent.category.DEFAULT" />
    </intent-filter>
</activity>

Start a camera app in video mode

Google Voice Actions

    "record a video"

To open a camera app in video mode, use the INTENT_ACTION_VIDEO_CAMERA action.

Action
    INTENT_ACTION_VIDEO_CAMERA
Data URI Scheme
    None
MIME Type
    None
Extras
    None

Example intent:
Kotlin
Java

fun capturePhoto() {
    val intent = Intent(MediaStore.INTENT_ACTION_VIDEO_CAMERA)
    if (intent.resolveActivity(packageManager) != null) {
        startActivityForResult(intent, REQUEST_IMAGE_CAPTURE)
    }
}

Example intent filter:

<activity ...>
    <intent-filter>
        <action android:name="android.media.action.VIDEO_CAMERA" />
        <category android:name="android.intent.category.DEFAULT" />
    </intent-filter>
</activity>

Contacts/people app

The following are common actions for contacts management apps, including the information you need to create an intent filter to advertise your app's ability to perform each action.
Select a contact

To have the user select a contact and provide your app access to all the contact information, use the ACTION_PICK action and specify the MIME type to Contacts.CONTENT_TYPE.

The result Intent delivered to your onActivityResult() callback contains the content: URI pointing to the selected contact. The response grants your app temporary permissions to read that contact using the Contacts Provider API, even if your app doesn't include the READ_CONTACTS permission.

Tip: If you need access to only a specific piece of contact information, such as a phone number or email address, instead see the next section about how to select specific contact data.

Action
    ACTION_PICK
Data URI Scheme
    None
MIME Type
    Contacts.CONTENT_TYPE 

Example intent:
Kotlin
Java

const val REQUEST_SELECT_CONTACT = 1

fun selectContact() {
    val intent = Intent(Intent.ACTION_PICK).apply {
        type = ContactsContract.Contacts.CONTENT_TYPE
    }
    if (intent.resolveActivity(packageManager) != null) {
        startActivityForResult(intent, REQUEST_SELECT_CONTACT)
    }
}

override fun onActivityResult(requestCode: Int, resultCode: Int, data: Intent) {
    if (requestCode == REQUEST_SELECT_CONTACT && resultCode == RESULT_OK) {
        val contactUri: Uri = data.data
        // Do something with the selected contact at contactUri.
        //...
    }
}

For information about how to retrieve contact details once you have the contact URI, read Retrieve details for a contact.

When you retrieve the contact URI using this intent, you generally don't need the READ_CONTACTS permission to read basic details for that contact, such as display name and whether the contact is starred. However, if you're trying to read more specific data about a given contact—such as their phone number or email address—you need the READ_CONTACTS permission.
Select specific contact data

To have the user select a specific piece of information from a contact, such as a phone number, email address, or other data type, use the ACTION_PICK action and specify the MIME type to one of the following content types, such as CommonDataKinds.Phone.CONTENT_TYPE to get the contact's phone number.

Note: In many cases, your app needs to have the READ_CONTACTS permission to view specific information about a particular contact.

If you need to retrieve only one type of data from a contact, this technique with a CONTENT_TYPE from the ContactsContract.CommonDataKinds classes is more efficient than using the Contacts.CONTENT_TYPE, as shown in the preceding section. The result provides you direct access to the desired data without requiring you to perform a more complex query to Contacts Provider.

The result Intent delivered to your onActivityResult() callback contains the content: URI pointing to the selected contact data. The response grants your app temporary permissions to read that contact data even if your app doesn't include the READ_CONTACTS permission.

Action
    ACTION_PICK
Data URI Scheme
    None
MIME Type

    CommonDataKinds.Phone.CONTENT_TYPE
        Pick from contacts with a phone number.
    CommonDataKinds.Email.CONTENT_TYPE
        Pick from contacts with an email address.
    CommonDataKinds.StructuredPostal.CONTENT_TYPE
        Pick from contacts with a postal address.

    Or one of many other CONTENT_TYPE values under ContactsContract.

Example intent:
Kotlin
Java

const val REQUEST_SELECT_PHONE_NUMBER = 1

fun selectContact() {
    // Start an activity for the user to pick a phone number from contacts.
    val intent = Intent(Intent.ACTION_PICK).apply {
        type = CommonDataKinds.Phone.CONTENT_TYPE
    }
    if (intent.resolveActivity(packageManager) != null) {
        startActivityForResult(intent, REQUEST_SELECT_PHONE_NUMBER)
    }
}

override fun onActivityResult(requestCode: Int, resultCode: Int, data: Intent) {
    if (requestCode == REQUEST_SELECT_PHONE_NUMBER && resultCode == Activity.RESULT_OK) {
        // Get the URI and query the content provider for the phone number.
        val contactUri: Uri = data.data
        val projection: Array<String> = arrayOf(CommonDataKinds.Phone.NUMBER)
        contentResolver.query(contactUri, projection, null, null, null).use { cursor ->
            // If the cursor returned is valid, get the phone number.
            if (cursor.moveToFirst()) {
                val numberIndex = cursor.getColumnIndex(CommonDataKinds.Phone.NUMBER)
                val number = cursor.getString(numberIndex)
                // Do something with the phone number.
                ...
            }
        }
    }
}

View a contact

To display the details for a known contact, use the ACTION_VIEW action and specify the contact with a content: URI as the intent data.

There are two primary ways to initially retrieve the contact's URI:

    Use the contact URI returned by the ACTION_PICK action shown in the preceding section. This approach doesn't require any app permissions.
    Access the list of all contacts directly, as described in Retrieve a list of contacts. This approach requires the READ_CONTACTS permission.

Action
    ACTION_VIEW
Data URI Scheme
    content:<URI>
MIME Type
    None. The type is inferred from the contact URI. 

Example intent:
Kotlin
Java

fun viewContact(contactUri: Uri) {
    val intent = Intent(Intent.ACTION_VIEW, contactUri)
    if (intent.resolveActivity(packageManager) != null) {
        startActivity(intent)
    }
}

Edit an existing contact

To edit a known contact, use the ACTION_EDIT action, specify the contact with a content: URI as the intent data, and include any known contact information in extras specified by constants in ContactsContract.Intents.Insert.

There are two primary ways to initially retrieve the contact URI:

    Use the contact URI returned by the ACTION_PICK action shown in the preceding section. This approach doesn't require any app permissions.
    Access the list of all contacts directly, as described in Retrieve a list of contacts. This approach requires the READ_CONTACTS permission.

Action
    ACTION_EDIT
Data URI Scheme
    content:<URI>
MIME Type
    The type is inferred from the contact URI. 
Extras
    One or more of the extras defined in ContactsContract.Intents.Insert so you can populate fields of the contact details. 

Example intent:
Kotlin
Java

fun editContact(contactUri: Uri, email: String) {
    val intent = Intent(Intent.ACTION_EDIT).apply {
        data = contactUri
        putExtra(ContactsContract.Intents.Insert.EMAIL, email)
    }
    if (intent.resolveActivity(packageManager) != null) {
        startActivity(intent)
    }
}

For more information about how to edit a contact, read Modify contacts using intents.
Insert a contact

To insert a new contact, use the ACTION_INSERT action, specify Contacts.CONTENT_TYPE as the MIME type, and include any known contact information in extras specified by constants in ContactsContract.Intents.Insert.

Action
    ACTION_INSERT
Data URI Scheme
    None
MIME Type
    Contacts.CONTENT_TYPE
Extras
    One or more of the extras defined in ContactsContract.Intents.Insert. 

Example intent:
Kotlin
Java

fun insertContact(name: String, email: String) {
    val intent = Intent(Intent.ACTION_INSERT).apply {
        type = ContactsContract.Contacts.CONTENT_TYPE
        putExtra(ContactsContract.Intents.Insert.NAME, name)
        putExtra(ContactsContract.Intents.Insert.EMAIL, email)
    }
    if (intent.resolveActivity(packageManager) != null) {
        startActivity(intent)
    }
}

For more information about how to insert a contact, read Modify contacts using intents.
Email

Composing an email with optional attachments is a common action for email apps. Create an intent filter to advertise your app's ability to perform this action using the information in the following section.
Compose an email with optional attachments

To compose an email, use one of the following actions based on whether you'll include attachments or not, and include email details such as the recipient and subject using the extra keys listed.

Action
    ACTION_SENDTO (for no attachment) or
    ACTION_SEND (for one attachment) or
    ACTION_SEND_MULTIPLE (for multiple attachments)
Data URI Scheme
    None
MIME Type

    "text/plain"
    "*/*"

Extras

    Intent.EXTRA_EMAIL
        A string array of all "To" recipient email addresses.
    Intent.EXTRA_CC
        A string array of all "CC" recipient email addresses.
    Intent.EXTRA_BCC
        A string array of all "BCC" recipient email addresses.
    Intent.EXTRA_SUBJECT
        A string with the email subject.
    Intent.EXTRA_TEXT
        A string with the body of the email.
    Intent.EXTRA_STREAM
        A Uri pointing to the attachment. If using the ACTION_SEND_MULTIPLE action, this instead is an ArrayList containing multiple Uri objects.

Example intent:
Kotlin
Java

fun composeEmail(addresses: Array<String>, subject: String, attachment: Uri) {
    val intent = Intent(Intent.ACTION_SEND).apply {
        type = "*/*"
        putExtra(Intent.EXTRA_EMAIL, addresses)
        putExtra(Intent.EXTRA_SUBJECT, subject)
        putExtra(Intent.EXTRA_STREAM, attachment)
    }
    if (intent.resolveActivity(packageManager) != null) {
        startActivity(intent)
    }
}

If you want to make sure that your intent is handled only by an email app, and not a text messaging or social app, then use the ACTION_SENDTO action and include the "mailto:" data scheme as shown in the following example:
Kotlin
Java

fun composeEmail(addresses: Array<String>, subject: String) {
    val intent = Intent(Intent.ACTION_SENDTO).apply {
        data = Uri.parse("mailto:") // Only email apps handle this.
        putExtra(Intent.EXTRA_EMAIL, addresses)
        putExtra(Intent.EXTRA_SUBJECT, subject)
    }
    if (intent.resolveActivity(packageManager) != null) {
        startActivity(intent)
    }
}

Example intent filter:

<activity ...>
    <intent-filter>
        <action android:name="android.intent.action.SEND" />
        <data android:type="*/*" />
        <category android:name="android.intent.category.DEFAULT" />
    </intent-filter>
    <intent-filter>
        <action android:name="android.intent.action.SENDTO" />
        <data android:scheme="mailto" />
        <category android:name="android.intent.category.DEFAULT" />
    </intent-filter>
</activity>

File storage

The following are common actions for file storage apps, including the information you need to create an intent filter to advertise your app's ability to perform each action.
Retrieve a specific type of file

To request that the user select a file such as a document or photo and return a reference to your app, use the ACTION_GET_CONTENT action and specify your desired MIME type. The file reference returned to your app is transient to your activity's current lifecycle, so if you want to access it later you must import a copy that you can read later.

This intent also lets the user create a new file in the process. For example, instead of selecting an existing photo, the user can capture a new photo with the camera.

The result intent delivered to your onActivityResult() method includes data with a URI pointing to the file. The URI can be anything, such as an http: URI, file: URI, or content: URI. However, if you'd like to restrict selectable files to only those that are accessible from a content provider (a content: URI) and that are available as a file stream with openFileDescriptor(), add the CATEGORY_OPENABLE category to your intent.

On Android 4.3 (API level 18) and higher, you can also let the user select multiple files by adding EXTRA_ALLOW_MULTIPLE to the intent, set to true. You can then access each of the selected files in a ClipData object returned by getClipData().

Action
    ACTION_GET_CONTENT
Data URI Scheme
    None
MIME Type
    The MIME type corresponding to the file type the user needs to select. 
Extras

    EXTRA_ALLOW_MULTIPLE
        A boolean that declares whether the user can select more than one file at a time. 
    EXTRA_LOCAL_ONLY
        A boolean that declares whether the returned file must be available directly from the device, rather than requiring a download from a remote service. 

Category (optional)

    CATEGORY_OPENABLE
        To return only "openable" files that can be represented as a file stream with openFileDescriptor().

Example intent to get a photo:
Kotlin
Java

const val REQUEST_IMAGE_GET = 1

fun selectImage() {
    val intent = Intent(Intent.ACTION_GET_CONTENT).apply {
        type = "image/*"
    }
    if (intent.resolveActivity(packageManager) != null) {
        startActivityForResult(intent, REQUEST_IMAGE_GET)
    }
}

override fun onActivityResult(requestCode: Int, resultCode: Int, data: Intent) {
    if (requestCode == REQUEST_IMAGE_GET && resultCode == Activity.RESULT_OK) {
        val thumbnail: Bitmap = data.getParcelableExtra("data")
        val fullPhotoUri: Uri = data.data
        // Do work with photo saved at fullPhotoUri.
        ...
    }
}

Example intent filter to return a photo:

<activity ...>
    <intent-filter>
        <action android:name="android.intent.action.GET_CONTENT" />
        <data android:type="image/*" />
        <category android:name="android.intent.category.DEFAULT" />
        <!-- The OPENABLE category declares that the returned file is accessible
             from a content provider that supports OpenableColumns
             and ContentResolver.openFileDescriptor(). -->
        <category android:name="android.intent.category.OPENABLE" />
    </intent-filter>
</activity>

Open a specific type of file

Instead of retrieving a copy of a file that you must import to your app, by using the ACTION_GET_CONTENT action, when running on Android 4.4 or higher you can instead request to open a file that's managed by another app by using the ACTION_OPEN_DOCUMENT action and specifying a MIME type. To also let the user create a new document that your app can write to, use the ACTION_CREATE_DOCUMENT action instead.

For example, instead of selecting from existing PDF documents, the ACTION_CREATE_DOCUMENT intent lets users select where they'd like to create a new document, such as within another app that manages the document's storage. Your app then receives the URI location of where it can write the new document.

Whereas the intent delivered to your onActivityResult() method from the ACTION_GET_CONTENT action might return a URI of any type, the result intent from ACTION_OPEN_DOCUMENT and ACTION_CREATE_DOCUMENT always specify the chosen file as a content: URI that's backed by a DocumentsProvider. You can open the file with openFileDescriptor() and query its details using columns from DocumentsContract.Document.

The returned URI grants your app long-term read access to the file, also possibly with write access. The ACTION_OPEN_DOCUMENT action is particularly useful when you want to read an existing file without making a copy into your app or when you want to open and edit a file in place.

You can also let the user select multiple files by adding EXTRA_ALLOW_MULTIPLE to the intent, set to true. If the user selects just one item, then you can retrieve the item from getData(). If the user selects more than one item, then getData() returns null and you must instead retrieve each item from a ClipData object that is returned by getClipData().

Note: Your intent must specify a MIME type and must declare the CATEGORY_OPENABLE category. If appropriate, you can specify more than one MIME type by adding an array of MIME types with the EXTRA_MIME_TYPES extra—if you do so, you must set the primary MIME type in setType() to "*/*".

Action
    ACTION_OPEN_DOCUMENT or
    ACTION_CREATE_DOCUMENT
Data URI Scheme
    None
MIME Type
    The MIME type corresponding to the file type the user needs to select. 
Extras

    EXTRA_MIME_TYPES
        An array of MIME types corresponding to the types of files your app is requesting. When you use this extra, you must set the primary MIME type in setType() to "*/*".
    EXTRA_ALLOW_MULTIPLE
        A boolean that declares whether the user can select more than one file at a time. 
    EXTRA_TITLE
        For use with ACTION_CREATE_DOCUMENT to specify an initial filename. 
    EXTRA_LOCAL_ONLY
        A boolean that declares whether the returned file must be available directly from the device, rather than requiring a download from a remote service. 

Category

    CATEGORY_OPENABLE
        To return only "openable" files that can be represented as a file stream with openFileDescriptor().

Example intent to get a photo:
Kotlin
Java

const val REQUEST_IMAGE_OPEN = 1

fun selectImage2() {
    val intent = Intent(Intent.ACTION_OPEN_DOCUMENT).apply {
        type = "image/*"
        addCategory(Intent.CATEGORY_OPENABLE)
    }
    // Only the system receives the ACTION_OPEN_DOCUMENT, so no need to test.
    startActivityForResult(intent, REQUEST_IMAGE_OPEN)
}

override fun onActivityResult(requestCode: Int, resultCode: Int, data: Intent) {
    if (requestCode == REQUEST_IMAGE_OPEN && resultCode == Activity.RESULT_OK) {
        val fullPhotoUri: Uri = data.data
        // Do work with full size photo saved at fullPhotoUri.
        ...
    }
}

Third-party apps can't respond to an intent with the ACTION_OPEN_DOCUMENT action. Instead, the system receives this intent and displays all the files available from various apps in a unified user interface.

To provide your app's files in this UI and let other apps open them, you must implement a DocumentsProvider and include an intent filter for PROVIDER_INTERFACE ("android.content.action.DOCUMENTS_PROVIDER"), as shown in the following example:

<provider ...
    android:grantUriPermissions="true"
    android:exported="true"
    android:permission="android.permission.MANAGE_DOCUMENTS">
    <intent-filter>
        <action android:name="android.content.action.DOCUMENTS_PROVIDER" />
    </intent-filter>
</provider>

For more information about how to make the files managed by your app openable from other apps, read Open files using storage access framework.
Local actions

Calling a car is a common local action. Create an intent filter to advertise your app's ability to perform this action using the information in the following section.
Call a car

Google Voice Actions

    "get me a taxi"
    "call me a car"

(Wear OS only)

To call a taxi, use the ACTION_RESERVE_TAXI_RESERVATION action.

Note: Apps must ask for confirmation from the user before completing this action.

Action
    ACTION_RESERVE_TAXI_RESERVATION
Data URI
    None
MIME Type
    None
Extras
    None

Example intent:
Kotlin
Java

fun callCar() {
    val intent = Intent(ReserveIntents.ACTION_RESERVE_TAXI_RESERVATION)
    if (intent.resolveActivity(packageManager) != null) {
        startActivity(intent)
    }
}

Example intent filter:

<activity ...>
    <intent-filter>
        <action android:name="com.google.android.gms.actions.RESERVE_TAXI_RESERVATION" />
        <category android:name="android.intent.category.DEFAULT" />
    </intent-filter>
</activity>

Maps

Showing a location on a map is a common action for map apps. Create an intent filter to advertise your app's ability to perform this action using the information in the following section.
Show a location on a map

To open a map, use the ACTION_VIEW action and specify the location information in the intent data with one of the following schemes.

Action
    ACTION_VIEW
Data URI Scheme

    geo:latitude,longitude
        Show the map at the given longitude and latitude.

        Example: "geo:47.6,-122.3" 
    geo:latitude,longitude?z=zoom
        Show the map at the given longitude and latitude at a certain zoom level. A zoom level of 1 shows the whole Earth, centered at the given lat,lng. The highest (closest) zoom level is 23.

        Example: "geo:47.6,-122.3?z=11" 
    geo:0,0?q=lat,lng(label)
        Show the map at the given longitude and latitude with a string label.

        Example: "geo:0,0?q=34.99,-106.61(Treasure)" 
    geo:0,0?q=my+street+address
        Show the location for "my street address", which can be a specific address or location query.

        Example: "geo:0,0?q=1600+Amphitheatre+Parkway%2C+CA"

        Note: All strings passed in the geo URI must be encoded. For example, the string 1st & Pike, Seattle becomes 1st%20%26%20Pike%2C%20Seattle. Spaces in the string are encoded with %20 or replaced with the plus sign (+).

MIME Type
    None

Example intent:
Kotlin
Java

fun showMap(geoLocation: Uri) {
    val intent = Intent(Intent.ACTION_VIEW).apply {
        data = geoLocation
    }
    if (intent.resolveActivity(packageManager) != null) {
        startActivity(intent)
    }
}

Example intent filter:

<activity ...>
    <intent-filter>
        <action android:name="android.intent.action.VIEW" />
        <data android:scheme="geo" />
        <category android:name="android.intent.category.DEFAULT" />
    </intent-filter>
</activity>

Music or video

The following are common actions for music and video apps, including the information you need to create an intent filter to advertise your app's ability to perform each action.
Play a media file

To play a music file, use the ACTION_VIEW action and specify the URI location of the file in the intent data.

Action
    ACTION_VIEW
Data URI Scheme

    file:<URI>
    content:<URI>
    http:<URL>

MIME Type

    "audio/*"
    "application/ogg"
    "application/x-ogg"
    "application/itunes"
    Or any other that your app requires.

Example intent:
Kotlin
Java

fun playMedia(file: Uri) {
    val intent = Intent(Intent.ACTION_VIEW).apply {
        data = file
    }
    if (intent.resolveActivity(packageManager) != null) {
        startActivity(intent)
    }
}

Example intent filter:

<activity ...>
    <intent-filter>
        <action android:name="android.intent.action.VIEW" />
        <data android:type="audio/*" />
        <data android:type="application/ogg" />
        <category android:name="android.intent.category.DEFAULT" />
    </intent-filter>
</activity>

Play music based on a search query

Google Voice Actions

    "play michael jackson billie jean"

To play music based on a search query, use the INTENT_ACTION_MEDIA_PLAY_FROM_SEARCH intent. An app might fire this intent in response to the user's voice command to play music. The receiving app for this intent performs a search within its inventory to match existing content to the given query and starts playing that content.

In this intent, include the EXTRA_MEDIA_FOCUS string extra, which specifies the intended search mode. For example, the search mode can specify whether the search is for an artist name or song name.

Action
    INTENT_ACTION_MEDIA_PLAY_FROM_SEARCH
Data URI Scheme
    None
MIME Type
    None
Extras

    MediaStore.EXTRA_MEDIA_FOCUS (required)

        Indicates the search mode: whether the user is looking for a particular artist, album, song, or playlist. Most search modes take additional extras. For example, if the user is interested in listening to a particular song, the intent might have three additional extras: the song title, the artist, and the album. This intent supports the following search modes for each value of EXTRA_MEDIA_FOCUS:

        Any - "vnd.android.cursor.item/*"

            Play any music. The receiving app plays some music based on a smart choice, such as the last playlist the user listened to.

            Additional extras:

                QUERY (required): an empty string. This extra is always provided for backward compatibility. Existing apps that don't know about search modes can process this intent as an unstructured search.

        Unstructured - "vnd.android.cursor.item/*"

            Play a particular song, album, or genre from an unstructured search query. Apps can generate an intent with this search mode when they can't identify the type of content the user wants to listen to. Use more specific search modes when possible.

            Additional extras:

                QUERY (required): a string that contains any combination of the artist, the album, the song name, or the genre.

        Genre - Audio.Genres.ENTRY_CONTENT_TYPE

            Play music of a particular genre.

            Additional extras:

                "android.intent.extra.genre" (required) - The genre.
                QUERY (required): the genre. This extra is always provided for backward compatibility. Existing apps that don't know about search modes can process this intent as an unstructured search.

        Artist - Audio.Artists.ENTRY_CONTENT_TYPE

            Play music from a particular artist.

            Additional extras:

                EXTRA_MEDIA_ARTIST (required): the artist.
                "android.intent.extra.genre": the genre.
                QUERY (required): a string that contains any combination of the artist or the genre. This extra is always provided for backward compatibility. Existing apps that don't know about search modes can process this intent as an unstructured search.

        Album - Audio.Albums.ENTRY_CONTENT_TYPE

            Play music from a particular album.

            Additional extras:

                EXTRA_MEDIA_ALBUM (required): the album.
                EXTRA_MEDIA_ARTIST: the artist.
                "android.intent.extra.genre": the genre.
                QUERY (required): a string that contains any combination of the album or the artist. This extra is always provided for backward compatibility. Existing apps that don't know about search modes can process this intent as an unstructured search.

        Song - "vnd.android.cursor.item/audio"

            Play a particular song.

            Additional extras:

                EXTRA_MEDIA_ALBUM: the album.
                EXTRA_MEDIA_ARTIST: the artist.
                "android.intent.extra.genre": the genre.
                EXTRA_MEDIA_TITLE (required): the song name.
                QUERY (required): a string that contains any combination of the album, the artist, the genre, or the title. This extra is always provided for backward compatibility. Existing apps that don't know about search modes can process this intent as an unstructured search.

        Playlist - Audio.Playlists.ENTRY_CONTENT_TYPE
            Android playlists are deprecated. The API is no longer maintained, but the current functionality remains for compatibility.

            Play a particular playlist or a playlist that matches some criteria specified by additional extras.

            Additional extras:

                EXTRA_MEDIA_ALBUM: the album.
                EXTRA_MEDIA_ARTIST: the artist.
                "android.intent.extra.genre": the genre.
                "android.intent.extra.playlist": the playlist.
                EXTRA_MEDIA_TITLE: the song name that the playlist is based on.
                QUERY (required): a string that contains any combination of the album, the artist, the genre, the playlist, or the title. This extra is always provided for backward compatibility. Existing apps that don't know about search modes can process this intent as an unstructured search.

Example intent:

If the user wants to listen to music from a particular artist, a search app might generate the following intent:
Kotlin
Java

fun playSearchArtist(artist: String) {
    val intent = Intent(MediaStore.INTENT_ACTION_MEDIA_PLAY_FROM_SEARCH).apply {
        putExtra(MediaStore.EXTRA_MEDIA_FOCUS, MediaStore.Audio.Artists.ENTRY_CONTENT_TYPE)
        putExtra(MediaStore.EXTRA_MEDIA_ARTIST, artist)
        putExtra(SearchManager.QUERY, artist)
    }
    if (intent.resolveActivity(packageManager) != null) {
        startActivity(intent)
    }
}

Example intent filter:

<activity ...>
    <intent-filter>
        <action android:name="android.media.action.MEDIA_PLAY_FROM_SEARCH" />
        <category android:name="android.intent.category.DEFAULT" />
    </intent-filter>
</activity>

When handling this intent in your activity, check the value of the EXTRA_MEDIA_FOCUS extra in the incoming Intent to determine the search mode. Once your activity has identified the search mode, read the values of the additional extras for that particular search mode. With this information, your app can then perform the search within its inventory to play the content that matches the search query. This is shown in the following example.
Kotlin
Java

override fun onCreate(savedInstanceState: Bundle?) {
    ...
    if (intent.action.compareTo(MediaStore.INTENT_ACTION_MEDIA_PLAY_FROM_SEARCH) == 0) {

        val mediaFocus: String? = intent.getStringExtra(MediaStore.EXTRA_MEDIA_FOCUS)
        val query: String? = intent.getStringExtra(SearchManager.QUERY)

        // Some of these extras might not be available depending on the search mode.
        val album: String? = intent.getStringExtra(MediaStore.EXTRA_MEDIA_ALBUM)
        val artist: String? = intent.getStringExtra(MediaStore.EXTRA_MEDIA_ARTIST)
        val genre: String? = intent.getStringExtra("android.intent.extra.genre")
        val playlist: String? = intent.getStringExtra("android.intent.extra.playlist")
        val title: String? = intent.getStringExtra(MediaStore.EXTRA_MEDIA_TITLE)

        // Determine the search mode and use the corresponding extras.
        when {
            mediaFocus == null -> {
                // 'Unstructured' search mode (backward compatible)
                playUnstructuredSearch(query)
            }
            mediaFocus.compareTo("vnd.android.cursor.item/*") == 0 -> {
                if (query?.isNotEmpty() == true) {
                    // 'Unstructured' search mode.
                    playUnstructuredSearch(query)
                } else {
                    // 'Any' search mode.
                    playResumeLastPlaylist()
                }
            }
            mediaFocus.compareTo(MediaStore.Audio.Genres.ENTRY_CONTENT_TYPE) == 0 -> {
                // 'Genre' search mode.
                playGenre(genre)
            }
            mediaFocus.compareTo(MediaStore.Audio.Artists.ENTRY_CONTENT_TYPE) == 0 -> {
                // 'Artist' search mode.
                playArtist(artist, genre)
            }
            mediaFocus.compareTo(MediaStore.Audio.Albums.ENTRY_CONTENT_TYPE) == 0 -> {
                // 'Album' search mode.
                playAlbum(album, artist)
            }
            mediaFocus.compareTo("vnd.android.cursor.item/audio") == 0 -> {
                // 'Song' search mode.
                playSong(album, artist, genre, title)
            }
            mediaFocus.compareTo(MediaStore.Audio.Playlists.ENTRY_CONTENT_TYPE) == 0 -> {
                // 'Playlist' search mode.
                playPlaylist(album, artist, genre, playlist, title)
            }
        }
    }
}

New note

Creating a note is a common action for note-taking apps. Create an intent filter to advertise your app's ability to perform this action using the information in the following section.
Create a note

To create a new note, use the ACTION_CREATE_NOTE action and specify note details such as the subject and text using following extras.

Note: Apps must ask for confirmation from the user before completing this action.

Action
    ACTION_CREATE_NOTE 
Data URI Scheme
    None
MIME Type
    PLAIN_TEXT_TYPE
    "*/*"
Extras

    EXTRA_NAME
        A string indicating the title or subject of the note.
    EXTRA_TEXT
        A string indicating the text of the note.

Example intent:
Kotlin
Java

fun createNote(subject: String, text: String) {
    val intent = Intent(NoteIntents.ACTION_CREATE_NOTE).apply {
        putExtra(NoteIntents.EXTRA_NAME, subject)
        putExtra(NoteIntents.EXTRA_TEXT, text)
    }
    if (intent.resolveActivity(packageManager) != null) {
        startActivity(intent)
    }
}

Example intent filter:

<activity ...>
    <intent-filter>
        <action android:name="com.google.android.gms.actions.CREATE_NOTE" />
        <category android:name="android.intent.category.DEFAULT" />
        <data android:mimeType="*/*" />
    </intent-filter>
</activity>

Phone

Initiating a call is a common action for phone apps. Create an intent filter to advertise your app's ability to perform this action using the information in the following section.
Initiate a phone call

To open the phone app and dial a phone number, use the ACTION_DIAL action and specify a phone number using the following URI scheme. When the phone app opens, it displays the phone number, and the user must tap the Call button to begin the phone call.

Google Voice Actions

    "call 555-5555"
    "call bob"
    "call voicemail"

To place a phone call directly, use the ACTION_CALL action and specify a phone number using the following URI scheme. When the phone app opens, it begins the phone call. The user doesn't need to tap the Call button.

The ACTION_CALL action requires that you add the CALL_PHONE permission to your manifest file:

<uses-permission android:name="android.permission.CALL_PHONE" />

Action

        ACTION_DIAL - Opens the dialer or phone app.
        ACTION_CALL - Places a phone call (requires the CALL_PHONE permission)

Data URI Scheme

        tel:<phone-number>
        voicemail:<phone-number>

MIME Type
    None

Valid telephone numbers are those defined in the IETF RFC 3966. Valid examples include the following:

    tel:2125551212
    tel:(212) 555 1212

The Phone app's dialer is good at normalizing schemes, such as telephone numbers. So the scheme described isn't strictly required in the Uri.parse() method. However, if you haven't tried a scheme or are unsure whether it can be handled, use the Uri.fromParts() method instead.

Example intent:
Kotlin
Java

fun dialPhoneNumber(phoneNumber: String) {
    val intent = Intent(Intent.ACTION_DIAL).apply {
        data = Uri.parse("tel:$phoneNumber")
    }
    if (intent.resolveActivity(packageManager) != null) {
        startActivity(intent)
    }
}

Search

The following are common actions for search apps, including the information you need to create an intent filter to advertise your app's ability to perform each action.
Search using a specific app

Google Voice Actions

    "search for cat videos on myvideoapp"

To support search within the context of your app, declare an intent filter in your app with the SEARCH_ACTION action, as shown in the following intent filter example.

Note: We don't recommend using SEARCH_ACTION for app search. Instead, implement the GET_THING action to leverage Google Assistant's built-in support for in-app search. For more information, see the Google Assistant App Actions documentation.

Action

    "com.google.android.gms.actions.SEARCH_ACTION"
        Support search queries from Google Voice Actions.

Extras

    QUERY
        A string that contains the search query.

Example intent filter:

<activity android:name=".SearchActivity">
    <intent-filter>
        <action android:name="com.google.android.gms.actions.SEARCH_ACTION"/>
        <category android:name="android.intent.category.DEFAULT"/>
    </intent-filter>
</activity>

Perform a web search

To initiate a web search, use the ACTION_WEB_SEARCH action and specify the search string in the SearchManager.QUERY extra.

Action
    ACTION_WEB_SEARCH
Data URI Scheme
    None
MIME Type
    None
Extras

    SearchManager.QUERY
        The search string.

Example intent:
Kotlin
Java

fun searchWeb(query: String) {
    val intent = Intent(Intent.ACTION_WEB_SEARCH).apply {
        putExtra(SearchManager.QUERY, query)
    }
    if (intent.resolveActivity(packageManager) != null) {
        startActivity(intent)
    }
}

Settings

To open a screen in the system Settings app when your app requires the user to change something, use one of the following intent actions:

Action
    ACTION_SETTINGS
    ACTION_WIRELESS_SETTINGS
    ACTION_AIRPLANE_MODE_SETTINGS
    ACTION_WIFI_SETTINGS
    ACTION_APN_SETTINGS
    ACTION_BLUETOOTH_SETTINGS
    ACTION_DATE_SETTINGS
    ACTION_LOCALE_SETTINGS
    ACTION_INPUT_METHOD_SETTINGS
    ACTION_DISPLAY_SETTINGS
    ACTION_SECURITY_SETTINGS
    ACTION_LOCATION_SOURCE_SETTINGS
    ACTION_INTERNAL_STORAGE_SETTINGS
    ACTION_MEMORY_CARD_SETTINGS

    For additional settings screens that are available, see the Settings documentation .
Data URI Scheme
    None
MIME Type
    None

Example intent:
Kotlin
Java

fun openWifiSettings() {
    val intent = Intent(Settings.ACTION_WIFI_SETTINGS)
    if (intent.resolveActivity(packageManager) != null) {
        startActivity(intent)
    }
}

Text messaging

Composing an SMS/MMS message with an attachment is a common action for text messaging apps. Create an intent filter to advertise your app's ability to perform this action using the information in the following section.
Compose an SMS/MMS message with attachment

To initiate an SMS or MMS text message, use one of the following intent actions and specify message details such as the phone number, subject, and message body using the following extra keys.

Action
    ACTION_SENDTO or
    ACTION_SEND or
    ACTION_SEND_MULTIPLE
Data URI Scheme

    sms:<phone_number>
    smsto:<phone_number>
    mms:<phone_number>
    mmsto:<phone_number>

    These schemes are all handled the same way. 
MIME Type

    "text/plain"
    "image/*"
    "video/*"

Extras

    "subject"
        A string for the message subject (usually for MMS only).
    "sms_body"
        A string for the text message.
    EXTRA_STREAM
        A Uri pointing to the image or video to attach. If using the ACTION_SEND_MULTIPLE action, this extra is an ArrayList of Uri objects pointing to the images or videos to attach.

Example intent:
Kotlin
Java

fun composeMmsMessage(message: String, attachment: Uri) {
    val intent = Intent(Intent.ACTION_SENDTO).apply {
        type = HTTP.PLAIN_TEXT_TYPE
        putExtra("sms_body", message)
        putExtra(Intent.EXTRA_STREAM, attachment)
    }
    if (intent.resolveActivity(packageManager) != null) {
        startActivity(intent)
    }
}

If you want to make sure that your intent is handled only by a text messaging app, and not other email or social apps, then use the ACTION_SENDTO action and include the "smsto:" data scheme as shown in the following example:
Kotlin
Java

fun composeMmsMessage(message: String, attachment: Uri) {
    val intent = Intent(Intent.ACTION_SEND).apply {
        data = Uri.parse("smsto:")  // Only SMS apps respond to this.
        putExtra("sms_body", message)
        putExtra(Intent.EXTRA_STREAM, attachment)
    }
    if (intent.resolveActivity(packageManager) != null) {
        startActivity(intent)
    }
}

Example intent filter:

<activity ...>
    <intent-filter>
        <action android:name="android.intent.action.SEND" />
        <data android:type="text/plain" />
        <data android:type="image/*" />
        <category android:name="android.intent.category.DEFAULT" />
    </intent-filter>
</activity>

Note: If you're developing an SMS/MMS messaging app, you must implement intent filters for several additional actions in order to be available as the default SMS app on Android 4.4 and higher. For more information, see the documentation at Telephony.
Web browser

Loading a web URL is a common action for web browser apps. Create an intent filter to advertise your app's ability to perform this action using the information in the following section.
Load a web URL

Google Voice Actions

    "open example.com"

To open a web page, use the ACTION_VIEW action and specify the web URL in the intent data.

Action
    ACTION_VIEW
Data URI Scheme
    http:<URL>
    https:<URL>
MIME Type

    "text/plain"
    "text/html"
    "application/xhtml+xml"
    "application/vnd.wap.xhtml+xml"

Example intent:
Kotlin
Java

fun openWebPage(url: String) {
    val webpage: Uri = Uri.parse(url)
    val intent = Intent(Intent.ACTION_VIEW, webpage)
    if (intent.resolveActivity(packageManager) != null) {
        startActivity(intent)
    }
}

Example intent filter:

<activity ...>
    <intent-filter>
        <action android:name="android.intent.action.VIEW" />
        <!-- Include the host attribute if you want your app to respond
             only to URLs with your app's domain. -->
        <data android:scheme="http" android:host="www.example.com" />
        <category android:name="android.intent.category.DEFAULT" />
        <!-- The BROWSABLE category is required to get links from web pages. -->
        <category android:name="android.intent.category.BROWSABLE" />
    </intent-filter>
</activity>

Tip: If your Android app provides functionality similar to your web site, include an intent filter for URLs that point to your web site. Then, if users have your app installed, links from emails or other web pages pointing to your web site open your Android app instead of your web page. Learn more in Handling Android App Links.

Starting in Android 12 (API level 31), a generic web intent resolves to an activity in your app only if your app is approved for the specific domain contained in that web intent. If your app isn't approved for the domain, the web intent resolves to the user's default browser app instead.
Verify intents with the Android Debug Bridge

To verify that your app responds to the intents that you want to support, you can use the adb tool to fire specific intents by doing the following:

    Set up an Android device for development or use a virtual device.
    Install a version of your app that handles the intents you want to support.
    Fire an intent using adb:

adb shell am start -a <ACTION> -t <MIME_TYPE> -d <DATA> \
  -e <EXTRA_NAME> <EXTRA_VALUE> -n <ACTIVITY>

For example:

    adb shell am start -a android.intent.action.DIAL \
      -d tel:555-5555 -n org.example.MyApp/.MyActivity

    If you define the required intent filters, handle the intent.

For more information, see Issue shell commands.

Was this helpful?

Content and code samples on this page are subject to the licenses described in the Content License. Java and OpenJDK are trademarks or registered trademarks of Oracle and/or its affiliates.

Last updated 2024-03-29 UTC.