| /frameworks/base/docs/html/training/contacts-provider/ |
| D | modify-data.jd | 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
[all …]
|
| D | index.jd | 52 contact, and modifying contacts using intents. The basic techniques described
67 <li>Match by contact name</li>
68 <li>Match any type of contact data</li>
69 <li>Match a specific type of contact data, such as a phone number</li>
76 Learn how to retrieve the details for a single contact. A contact's details are data
84 Learn how to modify a contact by sending an intent to the People app.
88 <a href="display-contact-badge.html">Displaying the Quick Contact Badge</a>
93 clicks the contact badge widget, a dialog opens that displays the contact's details and
94 action buttons for apps that can handle the details. For example, if the contact has an
|
| D | display-contact-badge.jd | 57 contact's photo thumbnail image.
66 The large image associated with the contact, or no image is available, a placeholder
74 example, if the contact's details include one or more email addresses, an email icon
75 appears. When users click the icon, all of the contact's email addresses appear. When users
81 The {@link android.widget.QuickContactBadge} view provides instant access to a contact's
82 details, as well as a fast way of communicating with the contact. Users don't have to look up
83 a contact, find and copy information, and then paste it into the appropriate app. Instead, they
107 To display a contact in the {@link android.widget.QuickContactBadge}, you need a content URI
108 for the contact and a {@link android.graphics.Bitmap} for the small image. You generate
143 To set the content URI for the contact, call
[all …]
|
| D | retrieve-names.jd | 53 <dt>Match contact names</dt>
55 Retrieve a list of contacts by matching the search string to all or part of the contact
96 This technique tries to match a search string to the name of a contact or contacts in the
151 {@link android.support.v4.app.Fragment} to display the details for a contact that the user
175 {@link android.support.v4.app.LoaderManager.LoaderCallbacks}. Also, to help detect which contact
217 // Define variables for the contact the user selects
218 // The contact's _ID value
220 // The contact's LOOKUP_KEY
222 // A content URI for the selected contact
285 <h3 id="SetListener">Set the selected contact listener</h3>
[all …]
|
| D | retrieve-details.jd | 43 This lesson shows how to retrieve detail data for a contact, such as email addresses, phone
44 numbers, and so forth. It's the details that users are looking for when they retrieve a contact.
45 You can give them all the details for a contact, or only display details of a particular type,
50 {@link android.provider.ContactsContract.Contacts} row for a contact the user has picked.
56 To retrieve all the details for a contact, search the
57 {@link android.provider.ContactsContract.Data} table for any rows that contain the contact's
66 <strong>Note:</strong> Retrieving all the details for a contact reduces the performance of a
132 find the contact. For example:
283 Retrieving a specific data type for a contact, such as all the emails, follows the same pattern
346 Define a search text expression that retrieves rows for a specific contact's
|
| /frameworks/base/tests/AccessoryDisplay/sink/src/com/android/accessorydisplay/sink/ |
| D | UsbHid.java | 107 final Contact contact = contacts[i]; in generateReport() local
109 buffer.put((byte)((contact.id << 2) | 0x03)); in generateReport()
111 buffer.put((byte)contact.x).put((byte)(contact.x >> 8)); in generateReport()
113 buffer.put((byte)contact.y).put((byte)(contact.y >> 8)); in generateReport()
|
| /frameworks/base/docs/html/guide/topics/providers/ |
| D | contacts-provider.jd | 141 Rows representing different people, based on aggregations of raw contact rows.
153 Rows containing the details for raw contact, such as email addresses or phone numbers.
163 A raw contact represents a person's data coming from a single account type and account
170 Most of the data for a raw contact isn't stored in the
177 <h3 id="RawContactsColumns">Important raw contact columns</h3>
183 <strong>Table 1.</strong> Important raw contact columns.
196 The account name for the account type that's the source of this raw contact.
212 The account type that's the source of this raw contact. For example, the account
226 The "deleted" flag for a raw contact.
242 A raw contact's name is not stored in its row in
[all …]
|
| /frameworks/base/docs/html/training/basics/intents/ |
| D | result.jd | 34 contact and you'll receive the contact details as a result.</p>
56 <p>For example, here's how to start an activity that allows the user to pick a contact:</p>
85 <p>For example, here's how you can handle the result for the "pick a contact" intent:</p>
94 // The user picked a contact.
95 // The Intent's data Uri identifies which contact was selected.
97 // Do something with the contact here (bigger example below)
105 contact the user selected.</p>
111 versions) always returns a result with the content URI that identifies the selected contact, and the
116 <h4>Bonus: Read the contact data</h4>
122 result data to get the phone number from the selected contact:</p>
[all …]
|
| /frameworks/base/docs/html-intl/intl/zh-cn/training/basics/intents/ |
| D | result.jd | 94 // The user picked a contact.
95 // The Intent's data Uri identifies which contact was selected.
97 // Do something with the contact here (bigger example below)
131 // Get the URI that points to the selected contact
136 // Perform the query on the contact to get the NUMBER column
|
| /frameworks/base/docs/html-intl/intl/ja/training/basics/intents/ |
| D | result.jd | 94 // The user picked a contact.
95 // The Intent's data Uri identifies which contact was selected.
97 // Do something with the contact here (bigger example below)
131 // Get the URI that points to the selected contact
136 // Perform the query on the contact to get the NUMBER column
|
| /frameworks/base/docs/html-intl/intl/zh-tw/training/basics/intents/ |
| D | result.jd | 94 // The user picked a contact.
95 // The Intent's data Uri identifies which contact was selected.
97 // Do something with the contact here (bigger example below)
131 // Get the URI that points to the selected contact
136 // Perform the query on the contact to get the NUMBER column
|
| /frameworks/base/docs/html-intl/intl/ru/training/basics/intents/ |
| D | result.jd | 94 // The user picked a contact.
95 // The Intent's data Uri identifies which contact was selected.
97 // Do something with the contact here (bigger example below)
131 // Get the URI that points to the selected contact
136 // Perform the query on the contact to get the NUMBER column
|
| /frameworks/base/docs/html-intl/intl/ko/training/basics/intents/ |
| D | result.jd | 94 // The user picked a contact.
95 // The Intent's data Uri identifies which contact was selected.
97 // Do something with the contact here (bigger example below)
131 // Get the URI that points to the selected contact
136 // Perform the query on the contact to get the NUMBER column
|
| /frameworks/opt/telephony/src/java/com/android/internal/telephony/ |
| D | IccProvider.java | 511 Object[] contact = new Object[4]; in loadRecord() local
516 contact[0] = alphaTag; in loadRecord()
517 contact[1] = number; in loadRecord()
527 contact[2] = emailString.toString(); in loadRecord()
529 contact[3] = id; in loadRecord()
530 cursor.addRow(contact); in loadRecord()
|
| /frameworks/base/docs/html/guide/practices/ui_guidelines/ |
| D | menu_design.jd | 231 In the above example, if the user performs touch & hold on the contact
234 on this contact.
239 command for that selection — in this case, "View contact".
241 first item in the Context menu. In this example, selecting the contact
242 "Obi Wan Kenobi" runs the same command "View contact" that is listed
249 on this contact. The Context menu displays the commands in a list,
250 while the "View contact" activity splits them into various items in the
344 The Context menu would typically contain commands "View contact", "Call contact",
345 and "Edit contact".
381 be available by the user touching the phone number itself when viewing contact details.
[all …]
|
| D | activity_task_design.jd | 204 basically of four activities: dialer, contacts list, view contact, and
205 new contact, as shown in the following screenshots:
457 chooses Home > Contacts then chooses a contact, they are viewing
458 the details of a contact. If they start again by choosing Home >
460 than the contact they were last viewing. Contacts is designed this way
490 activity has a field for a picture of a contact, but the Gallery is
495 chooses Contacts, selects the contact for viewing, chooses <em>Menu</em> >
496 Edit contact and touches the picture field, which launches the Gallery
499 in the contact.
698 View the list of contacts - resolves to a contact list viewer activity
[all …]
|
| /frameworks/base/docs/html/training/wearables/watch-faces/ |
| D | interacting.jd | 74 <p>Before sending the next command, the system judges whether the contact is a single tap, which is
87 make a new contact with the screen.</p>
125 and responds accordingly. If the event is initial contact by the user's finger,
127 of the finger after contact, it performs the action on which the
128 user tapped. If the event is prolonged contact by the finger, the app
|
| /frameworks/base/docs/html/about/versions/ |
| D | android-2.0-highlights.jd | 87 <li>Multiple accounts can be added to a device for email and contact
93 a contact's information and communication modes. For example, a user can tap a
94 contact photo and select to call, SMS, or email the person. Other applications
96 when you touch a contact photo or status icon.</li>
146 contact names as suggestions.</li>
|
| /frameworks/opt/chips/src/com/android/ex/chips/ |
| D | RecipientEditTextView.java | 672 private Bitmap createChipBitmap(RecipientEntry contact, TextPaint paint) { in createChipBitmap() argument
673 paint.setColor(getDefaultChipTextColor(contact)); in createChipBitmap()
674 ChipBitmapContainer bitmapContainer = createChipBitmap(contact, paint, in createChipBitmap()
675 getChipBackground(contact), getDefaultChipBackgroundColor(contact)); in createChipBitmap()
678 loadAvatarIcon(contact, bitmapContainer); in createChipBitmap()
683 private ChipBitmapContainer createChipBitmap(RecipientEntry contact, TextPaint paint, in createChipBitmap() argument
698 int iconWidth = contact.isValid() ? in createChipBitmap()
702 CharSequence ellipsizedText = ellipsizeText(createChipDisplayText(contact), paint, in createChipBitmap()
708 final int startPadding = contact.isValid() ? mChipTextStartPadding : mChipTextEndPadding; in createChipBitmap()
777 private void loadAvatarIcon(final RecipientEntry contact, in loadAvatarIcon() argument
[all …]
|
| /frameworks/base/docs/html-intl/intl/pt-br/training/basics/intents/ |
| D | result.jd | 94 // The user picked a contact.
95 // The Intent's data Uri identifies which contact was selected.
97 // Do something with the contact here (bigger example below)
131 // Get the URI that points to the selected contact
136 // Perform the query on the contact to get the NUMBER column
|
| /frameworks/base/docs/html/guide/components/ |
| D | intents-common.jd | 35 <li><a href="#PickContact">Select a contact</a></li>
36 <li><a href="#PickContactDat">Select specific contact data</a></li>
37 <li><a href="#ViewContact">View a contact</a></li>
38 <li><a href="#EditContact">Edit an existing contact</a></li>
39 <li><a href="#InsertContact">Insert a contact</a></li>
718 <h3 id="PickContact">Select a contact</h3>
720 <p>To have the user select a contact and provide your app access to all the contact information,
727 <code>content:</code> URI pointing to the selected contact. The response grants
728 your app temporary permissions to read that contact using the <a
732 <p class="note"><strong>Tip:</strong> If you need access to only a specific piece of contact
[all …]
|
| /frameworks/base/docs/html/distribute/tools/promote/ |
| D | brand.jd | 14 href="https://support.google.com/googleplay/contact/brand_developer">Android and Google Play Brand …
127 href="https://support.google.com/googleplay/contact/brand_developer">Android
171 Submit your marketing via the <a href="https://support.google.com/googleplay/contact/brand_develope…
201 href="https://support.google.com/googleplay/contact/brand_developer">Android
|
| /frameworks/base/docs/html/training/implementing-navigation/ |
| D | descendant.jd | 53 …, when viewing the contact details screen for an entry in the phone address book, a child screen d…
|
| /frameworks/base/docs/html/tv/adt-1/ |
| D | regulatory.jd | 55 potential for human contact during normal operation is minimized.</p>
80 doit être utilisé de sorte que la possibilité d'un contact humain pendant le fonctionnement
|
| /frameworks/base/docs/html/training/gestures/ |
| D | movement.jd | 47 android.view.MotionEvent#ACTION_MOVE} event whenever the current touch contact
54 detecting touch events is often based more on movement than on simple contact.
|