ContentResolver

This is the Android platform's base MIME type for a content: URI containing a Cursor of zero or more items. Applications should use this as the base type along with their own sub-type of their content: URIs that represent a directory of items. For example, hypothetical IMAP email client may have a URI content://com.company.provider.imap/inbox for all of the messages in its inbox, whose MIME type would be reported as CURSOR_DIR_BASE_TYPE + "/vnd.company.imap-msg"

Note how the base MIME type varies between this and CURSOR_ITEM_BASE_TYPE depending on whether there is one single item or multiple items in the data set, while the sub-type remains the same because in either case the data structure contained in the cursor is the same.

This is the Android platform's base MIME type for a content: URI containing a Cursor of a single item. Applications should use this as the base type along with their own sub-type of their content: URIs that represent a particular item. For example, hypothetical IMAP email client may have a URI content://com.company.provider.imap/inbox/1 for a particular message in the inbox, whose MIME type would be reported as CURSOR_ITEM_BASE_TYPE + "/vnd.company.imap-msg"

Compare with CURSOR_DIR_BASE_TYPE.

If this extra is set to true then the request will not be retried if it fails.

If this extra is set to true then any backoffs for the initial attempt (e.g. due to retries) are ignored by the sync scheduler. If this request fails and gets rescheduled then the retries will still honor the backoff.

If this extra is set to true then the sync settings (like getSyncAutomatically()) are ignored by the sync scheduler.

Set by the SyncManager to request that the SyncAdapter initialize itself for the given account/authority pair. One required initialization step is to ensure that setIsSyncable(android.accounts.Account, String, int) has been called with a >= 0 value. When this flag is set the SyncAdapter does not need to do a full sync, though it is allowed to do so.

Setting this extra is the equivalent of setting both SYNC_EXTRAS_IGNORE_SETTINGS and SYNC_EXTRAS_IGNORE_BACKOFF

Returns a ContentProviderClient that is associated with the ContentProvider that services the content at uri, starting the provider if necessary. Returns null if there is no provider associated wih the uri. The caller must indicate that they are done with the provider by calling release() which will allow the system to release the provider it it determines that there is no other reason for keeping it active.

Returns a ContentProviderClient that is associated with the ContentProvider with the authority of name, starting the provider if necessary. Returns null if there is no provider associated wih the uri. The caller must indicate that they are done with the provider by calling release() which will allow the system to release the provider it it determines that there is no other reason for keeping it active.

Like acquireContentProviderClient(Uri), but for use when you do not trust the stability of the target content provider. This turns off the mechanism in the platform clean up processes that are dependent on a content provider if that content provider's process goes away. Normally you can safely assume that once you have acquired a provider, you can freely use it as needed and it won't disappear, even if your process is in the background. If using this method, you need to take care to deal with any failures when communicating with the provider, and be sure to close it so that it can be re-opened later. In particular, catching a DeadObjectException from the calls there will let you know that the content provider has gone away; at that point the current ContentProviderClient object is invalid, and you should release it. You can acquire a new one if you would like to try to restart the provider and perform new operations on it.

Like acquireContentProviderClient(String), but for use when you do not trust the stability of the target content provider. This turns off the mechanism in the platform clean up processes that are dependent on a content provider if that content provider's process goes away. Normally you can safely assume that once you have acquired a provider, you can freely use it as needed and it won't disappear, even if your process is in the background. If using this method, you need to take care to deal with any failures when communicating with the provider, and be sure to close it so that it can be re-opened later. In particular, catching a DeadObjectException from the calls there will let you know that the content provider has gone away; at that point the current ContentProviderClient object is invalid, and you should release it. You can acquire a new one if you would like to try to restart the provider and perform new operations on it.

Specifies that a sync should be requested with the specified the account, authority, and extras at the given frequency. If there is already another periodic sync scheduled with the account, authority and extras then a new periodic sync won't be added, instead the frequency of the previous one will be updated.

These periodic syncs honor the "syncAutomatically" and "masterSyncAutomatically" settings. Although these sync are scheduled at the specified frequency, it may take longer for it to actually be started if other syncs are ahead of it in the sync operation queue. This means that the actual start time may drift.

Periodic syncs are not allowed to have any of SYNC_EXTRAS_DO_NOT_RETRY, SYNC_EXTRAS_IGNORE_BACKOFF, SYNC_EXTRAS_IGNORE_SETTINGS, SYNC_EXTRAS_INITIALIZE, SYNC_EXTRAS_FORCE, SYNC_EXTRAS_EXPEDITED, SYNC_EXTRAS_MANUAL set to true. If any are supplied then an IllegalArgumentException will be thrown.

This method requires the caller to hold the permission WRITE_SYNC_SETTINGS.

Request notifications when the different aspects of the SyncManager change. The different items that can be requested are:

• SYNC_OBSERVER_TYPE_PENDING
• SYNC_OBSERVER_TYPE_ACTIVE
• SYNC_OBSERVER_TYPE_SETTINGS

Applies each of the ContentProviderOperation objects and returns an array of their results. Passes through OperationApplicationException, which may be thrown by the call to apply(ContentProvider, ContentProviderResult[], int). If all the applications succeed then a ContentProviderResult array with the same number of elements as the operations will be returned. It is implementation-specific how many, if any, operations will have been successfully applied if a call to apply results in a OperationApplicationException.

Inserts multiple rows into a table at the given URL. This function make no guarantees about the atomicity of the insertions.

Call a provider-defined method. This can be used to implement read or write interfaces which are cheaper than using a Cursor and/or do not fit into the traditional table model.

Cancel any active or pending syncs that match account and authority. The account and authority can each independently be set to null, which means that syncs with any account or authority, respectively, will match.

Cancel any active or pending syncs that match the Uri. If the uri is null then all syncs will be canceled.

Deletes row(s) specified by a content URI. If the content provider supports transactions, the deletion will be atomic.

If a sync is active returns the information about it, otherwise returns null.

This method requires the caller to hold the permission READ_SYNC_STATS.

Returns a list with information about all the active syncs. This list will be empty if there are no active syncs.

This method requires the caller to hold the permission READ_SYNC_STATS.

Check if this account/provider is syncable.

This method requires the caller to hold the permission READ_SYNC_SETTINGS.

Gets the master auto-sync setting that applies to all the providers and accounts. If this is false then the per-provider auto-sync setting is ignored.

This method requires the caller to hold the permission READ_SYNC_SETTINGS.

Get the list of information about the periodic syncs for the given account and authority.

This method requires the caller to hold the permission READ_SYNC_SETTINGS.

Query for the possible MIME types for the representations the given content URL can be returned when opened as as stream with openTypedAssetFileDescriptor(Uri, String, Bundle). Note that the types here are not necessarily a superset of the type returned by getType(Uri) -- many content providers can not return a raw stream for the structured data that they contain.

Get information about the SyncAdapters that are known to the system.

Check if the provider should be synced when a network tickle is received

This method requires the caller to hold the permission READ_SYNC_SETTINGS.

Return the MIME type of the given content URL.

Inserts a row into a table at the given URL. If the content provider supports transactions the insertion will be atomic.

Returns true if there is currently a sync operation for the given account or authority in the pending list, or actively being processed.

This method requires the caller to hold the permission READ_SYNC_STATS.

Return true if the pending status is true of any matching authorities.

This method requires the caller to hold the permission READ_SYNC_STATS.

Notify registered observers that a row was updated. To register, call registerContentObserver(). By default, CursorAdapter objects will get this notification. If syncToNetwork is true, this will attempt to schedule a local sync using the sync adapter that's registered for the authority of the provided uri. No account will be passed to the sync adapter, so all matching accounts will be synchronized.

Notify registered observers that a row was updated and attempt to sync changes to the network. To register, call registerContentObserver(). By default, CursorAdapter objects will get this notification.

Open a raw file descriptor to access data under a URI. This interacts with the underlying openAssetFile(Uri, String) method of the provider associated with the given URI, to retrieve any file stored there.

Accepts the following URI schemes:

• content (SCHEME_CONTENT)
• android.resource (SCHEME_ANDROID_RESOURCE)
• file (SCHEME_FILE)

The android.resource (SCHEME_ANDROID_RESOURCE) Scheme

A Uri object can be used to reference a resource in an APK file. The Uri should be one of the following formats:

• android.resource://package_name/id_number
package_name is your package name as listed in your AndroidManifest.xml. For example com.example.myapp
id_number is the int form of the ID.
  The easiest way to construct this form is

  Uri uri = Uri.parse("android.resource://com.example.myapp/" + R.raw.my_resource");

• android.resource://package_name/type/name
package_name is your package name as listed in your AndroidManifest.xml. For example com.example.myapp
type is the string form of the resource type. For example, raw or drawable. name is the string form of the resource name. That is, whatever the file name was in your res directory, without the type extension. The easiest way to construct this form is

  Uri uri = Uri.parse("android.resource://com.example.myapp/raw/my_resource");

Note that if this function is called for read-only input (mode is "r") on a content: URI, it will instead call openTypedAssetFileDescriptor(Uri, String, Bundle) for you with a MIME type of "*\/*". This allows such callers to benefit from any built-in data conversion that a provider implements.

Open a raw file descriptor to access data under a URI. This is like openAssetFileDescriptor(Uri, String), but uses the underlying openFile(Uri, String) ContentProvider.openFile()} method, so will not work with providers that return sub-sections of files. If at all possible, you should use openAssetFileDescriptor(Uri, String). You will receive a FileNotFoundException exception if the provider returns a sub-section of a file.

Accepts the following URI schemes:

• content (SCHEME_CONTENT)
• file (SCHEME_FILE)

See openAssetFileDescriptor(Uri, String) for more information on these schemes.

Open a stream on to the content associated with a content URI. If there is no data associated with the URI, FileNotFoundException is thrown.

Accepts the following URI schemes:

• content (SCHEME_CONTENT)
• android.resource (SCHEME_ANDROID_RESOURCE)
• file (SCHEME_FILE)

See openAssetFileDescriptor(Uri, String) for more information on these schemes.

Synonym for openOutputStream(uri, "w").

Open a stream on to the content associated with a content URI. If there is no data associated with the URI, FileNotFoundException is thrown.

Accepts the following URI schemes:

• content (SCHEME_CONTENT)
• file (SCHEME_FILE)

See openAssetFileDescriptor(Uri, String) for more information on these schemes.

Open a raw file descriptor to access (potentially type transformed) data from a "content:" URI. This interacts with the underlying openTypedAssetFile(Uri, String, Bundle) method of the provider associated with the given URI, to retrieve retrieve any appropriate data stream for the data stored there.

Unlike openAssetFileDescriptor(Uri, String), this function only works with "content:" URIs, because content providers are the only facility with an associated MIME type to ensure that the returned data stream is of the desired type.

All text/* streams are encoded in UTF-8.

Query the given URI, returning a Cursor over the result set.

For best performance, the caller should follow these guidelines:

• Provide an explicit projection, to prevent reading data from storage that aren't going to be used.
• Use question mark parameter markers such as 'phone=?' instead of explicit values in the selection parameter, so that queries that differ only by those values will be recognized as the same for caching purposes.

Query the given URI, returning a Cursor over the result set.

For best performance, the caller should follow these guidelines:

• Provide an explicit projection, to prevent reading data from storage that aren't going to be used.
• Use question mark parameter markers such as 'phone=?' instead of explicit values in the selection parameter, so that queries that differ only by those values will be recognized as the same for caching purposes.

Register an observer class that gets callbacks when data identified by a given content URI changes.

Remove a periodic sync. Has no affect if account, authority and extras don't match an existing periodic sync.

This method requires the caller to hold the permission WRITE_SYNC_SETTINGS.

Remove a previously registered status change listener.

Start an asynchronous sync operation. If you want to monitor the progress of the sync you may register a SyncObserver. Only values of the following types may be used in the extras bundle:

• Integer
• Long
• Boolean
• Float
• Double
• String

Set whether this account/provider is syncable.

This method requires the caller to hold the permission WRITE_SYNC_SETTINGS.

Sets the master auto-sync setting that applies to all the providers and accounts. If this is false then the per-provider auto-sync setting is ignored.

This method requires the caller to hold the permission WRITE_SYNC_SETTINGS.

Set whether or not the provider is synced when it receives a network tickle.

This method requires the caller to hold the permission WRITE_SYNC_SETTINGS.

Start an asynchronous sync operation. If you want to monitor the progress of the sync you may register a SyncObserver. Only values of the following types may be used in the extras bundle:

• Integer
• Long
• Boolean
• Float
• Double
• String

Unregisters a change observer.

Update row(s) in a content URI. If the content provider supports transactions the update will be atomic.

Check that only values of the following types are in the Bundle:

• Integer
• Long
• Boolean
• Float
• Double
• String
• Account
• null