Overview

• The NoType:android/provider/CalendarContract$Calendars;Href=../../../reference/android/provider/CalendarContract.Calendars.html table holds the calendar specific information. Each row in this table contains the details for a single calendar, such as the name, color, sync info, etc.
• The NoType:android/provider/CalendarContract$Events;Href=../../../reference/android/provider/CalendarContract.Events.html table holds the event specific information. Each row in this table has the info for a single event. It contains information such as event title, location, start time, end time, etc. The event can occur one-time or can recur multiple times. Attendees, reminders, and extended properties are stored on separate tables and reference the BaseColumns.Id to link them with the event.
• The NoType:android/provider/CalendarContract$Instances;Href=../../../reference/android/provider/CalendarContract.Instances.html table holds the start and end time for occurrences of an event. Each row in this table represents a single occurrence. For one-time events there will be a 1:1 mapping of instances to events. For recurring events, multiple rows will automatically be generated which correspond to multiple occurrences of that event.
• The NoType:android/provider/CalendarContract$Attendees;Href=../../../reference/android/provider/CalendarContract.Attendees.html table holds the event attendee or guest information. Each row represents a single guest of an event. It specifies the type of guest they are and their attendance response for the event.
• The NoType:android/provider/CalendarContract$Reminders;Href=../../../reference/android/provider/CalendarContract.Reminders.html table holds the alert/notification data. Each row represents a single alert for an event. An event can have multiple reminders. The number of reminders per event is specified in NoType:android/provider/CalendarContract$CalendarColumns;Href=../../../reference/android/provider/CalendarContract.CalendarColumns.html#MAX_REMINDERS which is set by the Sync Adapter that owns the given calendar. Reminders are specified in minutes before the event and have a type.
• The NoType:android/provider/CalendarContract$ExtendedProperties;Href=../../../reference/android/provider/CalendarContract.ExtendedProperties.html table holds opaque data fields used by the sync adapter. The provider takes no action with items in this table except to delete them when their related events are deleted.

• NoType:android/provider/CalendarContract$SyncState;Href=../../../reference/android/provider/CalendarContract.SyncState.html , which contains free-form data maintained by the sync adapters

Overview

• A row in the NoType:android/provider/ContactsContract$Data;Href=../../../reference/android/provider/ContactsContract.Data.html table can store any kind of personal data, such as a phone number or email addresses. The set of data kinds that can be stored in this table is open-ended. There is a predefined set of common kinds, but any application can add its own data kinds.
• A row in the NoType:android/provider/ContactsContract$RawContacts;Href=../../../reference/android/provider/ContactsContract.RawContacts.html table represents a set of data describing a person and associated with a single account (for example, one of the user's Gmail accounts).
• A row in the NoType:android/provider/ContactsContract$Contacts;Href=../../../reference/android/provider/ContactsContract.Contacts.html table represents an aggregate of one or more RawContacts presumably describing the same person. When data in or associated with the RawContacts table is changed, the affected aggregate contacts are updated as necessary.

• NoType:android/provider/ContactsContract$Groups;Href=../../../reference/android/provider/ContactsContract.Groups.html , which contains information about raw contact groups such as Gmail contact groups. The current API does not support the notion of groups spanning multiple accounts.
• NoType:android/provider/ContactsContract$StatusUpdates;Href=../../../reference/android/provider/ContactsContract.StatusUpdates.html , which contains social status updates including IM availability.
• NoType:android/provider/ContactsContract$AggregationExceptions;Href=../../../reference/android/provider/ContactsContract.AggregationExceptions.html , which is used for manual aggregation and disaggregation of raw contacts
• NoType:android/provider/ContactsContract$Settings;Href=../../../reference/android/provider/ContactsContract.Settings.html , which contains visibility and sync settings for accounts and groups.
• NoType:android/provider/ContactsContract$SyncState;Href=../../../reference/android/provider/ContactsContract.SyncState.html , which contains free-form data maintained on behalf of sync adapters
• NoType:android/provider/ContactsContract$PhoneLookup;Href=../../../reference/android/provider/ContactsContract.PhoneLookup.html , which is used for quick caller-ID lookup

Columns

Column aliases

Column aliases

Column aliases

Column aliases

Column aliases

Column aliases

Column aliases

Column aliases

Column aliases

Column aliases

Column aliases

Column aliases

Column aliases

Operations

Insert

The user's profile entry cannot be created explicitly (attempting to do so will throw an exception). When a raw contact is inserted into the profile, the provider will check for the existence of a profile on the device. If one is found, the raw contact's RawContactsColumns.ContactId column gets the _ID of the profile Contact. If no match is found, the profile Contact is created and its _ID is put into the RawContactsColumns.ContactId column of the newly inserted raw contact.

Update

The profile Contact has the same update restrictions as Contacts in general, but requires the android.permission.WRITE_PROFILE permission.

Delete

The profile Contact cannot be explicitly deleted. It will be removed automatically if all of its constituent raw contact entries are deleted.

Query

• The Profile.ContentUri for profiles behaves in much the same way as retrieving a contact by ID, except that it will only ever return the user's profile contact.
• The profile contact supports all of the same sub-paths as an individual contact does - the content of the profile contact can be retrieved as entities or data rows. Similarly, specific raw contact entries can be retrieved by appending the desired raw contact ID within the profile.

Columns

Columns

Account check

Operations

Insert

Update

Delete

Deletes can be made against either a specific photo item in a stream item, or against all or a selected subset of photo items under a stream item. For example:

Deleting a single photo via the StreamItemPhotos.ContentDirectory sub-path of a stream item:

Deleting all photos under a stream item

Query

Querying for a specific photo in a stream item

java Example

 Cursor c = getContentResolver().query(
     ContentUris.withAppendedId(
         Uri.withAppendedPath(
             ContentUris.withAppendedId(StreamItems.CONTENT_URI, streamItemId)
             StreamItems.StreamItemPhotos#CONTENT_DIRECTORY),
         streamItemPhotoId), null, null, null, null);

Querying for all photos in a stream item

java Example

 Cursor c = getContentResolver().query(
     Uri.withAppendedPath(
         ContentUris.withAppendedId(StreamItems.CONTENT_URI, streamItemId)
         StreamItems.StreamItemPhotos#CONTENT_DIRECTORY),
     null, null, null, StreamItemPhotos.SORT_INDEX);

The record will contain both a StreamItemPhotosColumns.PhotoFileId and a StreamItemPhotosColumns.PhotoUri. The StreamItemPhotosColumns.PhotoFileId can be used in conjunction with the DisplayPhoto API to retrieve photo content, or you can open the StreamItemPhotosColumns.PhotoUri as an asset file, as follows:

java Example

 public InputStream openDisplayPhoto(String photoUri) {
     try {
         AssetFileDescriptor fd = getContentResolver().openAssetFileDescriptor(photoUri, "r");
         return fd.createInputStream();
     } catch (IOException e) {
         return null;
     }
 }

• An activity that can respond to the intent action LiveFolders.ActionCreateLiveFolder. The activity is responsible for creating the live folder.
• A ContentProvider to provide the live folder items.

Lifecycle

Setting up the live folder activity

 public static class MyLiveFolder extends Activity {
     public static final Uri CONTENT_URI = Uri.parse("content://my.app/live");

     protected void onCreate(Bundle savedInstanceState) {
         super.onCreate(savedInstanceState);

         final Intent intent = getIntent();
         final String action = intent.getAction();

         if (LiveFolders.ACTION_CREATE_LIVE_FOLDER.equals(action)) {
             setResult(RESULT_OK, createLiveFolder(this, CONTENT_URI, "My LiveFolder",
                     R.drawable.ic_launcher_contacts_phones));
         } else {
             setResult(RESULT_CANCELED);
         }

         finish();
     }

     private static Intent createLiveFolder(Context context, Uri uri, String name,
             int icon) {

         final Intent intent = new Intent();

         intent.setData(uri);
         intent.putExtra(LiveFolders.EXTRA_LIVE_FOLDER_NAME, name);
         intent.putExtra(LiveFolders.EXTRA_LIVE_FOLDER_ICON,
                 Intent.ShortcutIconResource.fromContext(context, icon));
         intent.putExtra(LiveFolders.EXTRA_LIVE_FOLDER_DISPLAY_MODE, LiveFolders.DISPLAY_MODE_LIST);

         return intent;
     }
 }

Setting up the content provider