Lines Matching refs:contact

43     This lesson shows you how to use an {@link android.content.Intent} to insert a new contact or
44     modify a contact's data. Instead of accessing the Contacts Provider directly, an
51     Using an {@link android.content.Intent} to insert or update a single contact is the preferred
68     You often want to allow the user to insert a new contact when your app receives new data. For
69     example, a restaurant review app can allow users to add the restaurant as a contact as they're
74     Inserting a contact using the contacts app inserts a new <em>raw</em> contact into the Contacts
77     contact. The contacts app also notifies users if the raw contact already exists. Users then have
78     option of canceling the insertion, in which case no contact is created. To learn
93 // Creates a new Intent to insert a contact
99     If you already have details for the contact, such as a phone number or email address, you can
142     This call opens a screen in the contacts app that allows users to enter a new contact. The
143     account type and account name for the contact is listed at the top of the screen. Once users
144     enter the data and click <i>Done</i>, the contacts app's contact list appears. Users return to
149     Editing an existing contact using an {@link android.content.Intent} is useful if the user
150     has already chosen a contact of interest. For example, an app that finds contacts that have
152     then adding it to the contact.
155     To edit an existing contact using an intent, use a procedure similar to
156     inserting a contact. Create an intent as described in the section
157     <a href="#InsertContact">Insert a New Contact Using an Intent</a>, but add the contact's
161     Contacts.CONTENT_ITEM_TYPE} to the intent. If you want to edit the contact with details you
169     finishes editing and saves the edits, the contacts app displays a contact list. When the user
176         A contact's {@link android.provider.ContactsContract.ContactsColumns#LOOKUP_KEY} value is
177         the identifier that you should use to retrieve a contact. It remains constant,
178         even if the provider changes the contact's row ID to handle internal operations.
184     To edit a contact, call {@link android.content.Intent#Intent Intent(action)} to
187     intent to the contact's {@link android.provider.ContactsContract.Contacts#CONTENT_LOOKUP_URI
195     To get a contact's {@link android.provider.ContactsContract.Contacts#CONTENT_LOOKUP_URI
198     Contacts.getLookupUri(id, lookupkey)} with the contact's
211     // The index of the contact's _ID value
217     // A content URI pointing to the contact
221      * Once the user has selected a contact to edit,
222      * this gets the contact's lookup key and _ID values from the
235     // Creates a new Intent to edit a contact
238      * Sets the contact URI to edit, and the data type that the
247     contact, when they click <i>Back</i> they see the contacts list screen. To navigate back to
264     You can add extended data for common contact fields by using the key values specified in
281     You can allow users to choose whether to insert a contact or edit an existing one by sending
284     allow users to add an incoming email address to a new contact, or add it as an additional
285     address for an existing contact. Set the MIME type for this intent to
291     Users can either insert a new contact or pick an existing contact and edit it.
297     // Creates a new Intent to insert or edit a contact