Native Android Action

• Action_all_apps: Open an activity that lists all installed applications. Typically, this operation is also handled by the initiator.
• Action_answer: Open an activity that handles incoming calls, which is usually handled by the local phone dialer.
• Action_bug_report: Displays an activity that can report a bug, usually handled by the local bug reporting mechanism.
• Action_call: Open a phone dialer and immediately dial a call using the number provided by the intent data URI. This action should only be used in place of activity in lieu of local dialer. In most cases, using action_dial is a better way.
• Action_call_button: Triggered when the user presses the "Dial button" of the hardware, the dial activity is typically invoked.
• Action_delete: Initiates an activity that allows the deletion of data specified in the intent data URL.
• Action_dial: A dialer is opened and the number to be dialed is provided in advance by the intent data URI. By default, this is handled by the local Android Phone Dialer. The dialer can normalize most of the number styles, for example, tel:555-1234 and Tel: (212) 555 1212 are valid numbers.
• Action_edit: Request an activity that requires the activity to edit the data in the pre-supplied data URI of the intent.
• Action_insert: Opens an activity that can insert a new item at the cursor specified by the intent data URI. When called as a child activity, when it is called as a child activity, it should return a URI that points to the newly inserted item.
• Action_pick: Initiates a child activity that allows you to select an item from the content provider specified by the intent data URI. When it is closed, it should return the selected item URI. The activity started is related to the selected data, for example, passing Content://contacts/people will invoke the local contact list.
• Action_search: Typically used to start a specific search activity. If it is not triggered on a specific activity, the user is prompted to make a selection from all the search-enabled applications. You can use the Searchmanager.query key to provide the search term as a string in a intent extra.
• Action_search_long_press: Allows you to intercept a long-press operation on a hardware search key. Usually handled by the system, a shortcut to voice search has been provided.
• Action_sendto: Initiates an activity to send a message to the contact specified by the intent data URI.
• Action_send: Initiates an activity that sends the data specified in the intent. The recipient needs to be selected by the parsed activity. Use Settype to set the MIME type of the data to be transferred. The data itself should be stored as extra according to its type, using Extra_text or Extra_stream. For email, the local Android application program can also use the Extra_mail, EXTRA_CC, EXTRA_BCC, and Extra_subject keys to receive EXTRA. You should only use the Action_send action to send data to a remote recipient (not another application on the device).
• Action_view: This is the most common generic action that the view requires to view the data provided in the intent data URI in the most reasonable way. Different applications will handle view requests based on the data URI pattern provided. In general, the http: address will open the browser, Tel: The address will open the dialer to dial the number, GEO: Address will be displayed in the Google Maps app, and the contact information will be displayed in the Contact Manager processing.
• Action_web_search: Opens a browser that performs a WEB search based on the query provided by the Searchmanager.query key.

Native Android Action