Android local applications also use intent to start activity and Child Activity.
The following list lists the local actions saved in the intent class with static string constants. You can use this action when creating an implicit intent in your own application to start the activity and subactivity.
In the next section, you will learn about intent filter and how to register your own activity to handle these actions.
Export action_answer
Open an activity to process incoming calls. Currently, it is processed by a local dialing tool.
❑ Action_call
Start the dialing tool and immediately initialize a call with the number in the Data Uri. Generally, if possible, it is considered to be a better method than dial_action.
❑ Action_delete
Start an activity to delete the data entry stored in the URI.
❑ Action_dial
Start a dialing program and use the number preset in the Data URI to dial. By default, it is handled by the local dialing tool of Android. This dial-up tool regulates most numbers. For example, tel: 555-1234 and Tel: (212) 555 1212 are valid numbers.
Export action_edit
Request an activity to edit the data at the URI.
❑ Action_insert
Open an activity that can insert a new project to a specific cursor in the data field. When called as a child activity, it must return the URI of the newly inserted project.
❑ Action_pick
Start a sub-activity to let you select a project from the URI data. When disabled, it must return the URI pointing to the selected project. The activity to be started depends on the data to be selected. For example, passing in content: // contacts/people will cause a local contact list.
❑ Action_search
Start a UI to perform the search. Use the searchmanager. query key value in the intent data packet to provide the search content string.
Export action_sendto
Start an activity to send a message to the specified contact in the URI.
Export action_send
Start an activity to send specific data (the recipient chooses to parse the activity ). Use settype to set the intent type to the MIME type of the transmitted data.
The data itself depends on the type to use extra_text or extra_stream for storage. In the case of e-mail, Android local applications can also accept extra_email, extra_cc, extra_bcc, and extra_subject key values.
Export action_view
The most common action. The view action requires that the data in the intent URI be displayed in the most reasonable way. Different applications process view requests, depending on the data in the URI. Generally, http: Address is opened in the browser, tel: Address is opened and called in the dialing tool, and GEO: Address is displayed in the Google map application, the contact content is displayed in the contact Manager.
Export action_web_search
Open an activity and perform a webpage search based on the text in the Data Uri.
Like these activity actions, Android also includes a large number of broadcast actions to create intent to notify the application of system messages. These broadcast actions will be described later in this chapter.