| afccaa84c8d1b9aa45040ddeb0edd42ba80e80d6 |
|
04-Oct-2012 |
Christopher Tate <ctate@google.com> |
Use myUserId() only in registerContentObserver()
The reason for this is a bit subtle: we want to guarantee that
when a content observer is registered using the public API, it
is *always* bound to the host user's view of the data behind the
observed Uri, never the calling user's. Now, the reason it was
the calling user in the first place is that the Settings provider
(and potentially any singleton provider) needs the observers
underlying Cursors returned from query() to be tied to the caller's
user, not the provider's host user.
In order to accomplish that now that the public-facing behavior is
always tied to the host user, the concrete class that implements
the Cursor type handled by the Settings provider has been extended
with a new hidden API for setting a notification observer tied to
an arbitrary user; and then the provider explicitly downcasts the
query result's Cursor to that class in order to register the
notification observer. We can do this safely because this is platform
code; if we change the way that these underlying cursors are constructed,
we can just fix this point of call to follow along. If they get out
of sync in the future, the Settings provider will scream bloody
murder in the log and throw a crashing exception.
Bug 7231549
Change-Id: I0aaceebb8b4108c56f8b9964ca7f9e698ddd91c8
/frameworks/base/core/java/android/content/ContentResolver.java
|
| b7564454297ba1706670ccab0562cac6676d0a77 |
|
20-Sep-2012 |
Christopher Tate <ctate@google.com> |
Multiuser awareness in content observer infrastructure
Content observers are registered under the calling user's identity,
not under the provider host's identity (unless the caller is using
the new permissioned entry points that allow observers to be
registered for a different user's view of the data). The most important
implication of this is that when the settings provider is directly
queried, the Cursor returned to the app is wired for change notifications
based on that calling app's user.
Note that it is not possible to use query() / insert() to read/write
data for different users. All such manipulations should use the
standard get* / put* methods in Settings.*.
Bug 7122169
Change-Id: If5d9ec44927e5e56e4e7635438f4ef48a5430986
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 16aa9736175f5bbe924a6e5587a2ca47c2dd702b |
|
18-Sep-2012 |
Christopher Tate <ctate@google.com> |
Per-user content observer APIs
Callers with INTERACT_ACROSS_USERS_FULL permission can now observe content
for a given user's view (and can notify content uri changes targeted to a
specific user). An observer watching for UserHandle.USER_ALL will see all
notifications for the given uri across all users; similarly, a notifier
who specifies USER_ALL will broadcast the change to all observers across
all users.
The API handles both USER_ALL or USER_CURRENT, and explicitly forbids
any other "pseudouser" designations.
This CL also revs the Settings provider to notify with USER_ALL for
changes to global settings, and with only the affected user's handle
for all other changes.
Bug 7122169
Change-Id: I94248b11aa91d1beb0a36432e82fe5725bb1264f
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 5e03e2ca7d25b899b129baad2dd5eca6bf99d88a |
|
06-Sep-2012 |
Dianne Hackborn <hackbod@google.com> |
More multi-user stuff:
- New (hidden) isUserRunning() API.
- Maintain LRU list of visited users.
- New FLAG_IS_DATA_ONLY for ApplicationInfo.
- Clean up pending intent records when force-stopping a user (or package).
(Also fixes bug #6880627: PendingIntent.getService() returns stale
intent of force stopped app)
- Fix force-stopping when installing an app to do the force-stop across
all users for that app.
- When selecting which processes to kill during a force stop, do this
based on the actual packages loaded in the process, not just process
name matching.
- You can now use --user option in am when starting activities, services,
and instrumentation.
- The am --user option accepts "current" and "all" as arguments.
- The pm uninstall command now uninstalls for all users, so it matches
the semantics of the install command.
- PhoneWindowManager now explicitly says to start home in the current
user.
- Activity manager call to retrieve the MIME type from a content provider
now takes a user argument, so it will direct this to the proper user.
- The package manager uninstall paths are now implemented around
PackageSetting, not PackageParser.Package. This allows them to work
even if the application's apk has been removed (in which case it only
exists as a PackageSetting, not the PackageParser.Package parsed from
the apk).
Change-Id: I3522f6fcf32603090bd6e01cc90ce70b6c5aae40
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 9530e3a22d5ffa2019d1a5177b6a441d4d6d048b |
|
19-Jun-2012 |
Nicolas Falliere <nicof@google.com> |
Added or fixed doctrings for required permissions.
Bug: 6591338
Change-Id: Ia2092f9994854701b5fa1425c371817367ae07ec
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 6ae8d1821822296df0606c9cd1c46708cc21cb58 |
|
23-May-2012 |
Dianne Hackborn <hackbod@google.com> |
Fix (mostly) issue #5109947: Race condition between retrieving a...
...content provider and updating its oom adj
This introduces the concept of an "unstable" reference on a content
provider. When holding such a reference (and no normal stable ref),
the content provider dying will not cause the client process to be
killed.
This is used in ContentResolver.query(), .openAssetFileDescriptor(),
and .openTypedAssetFileDescriptor() to first access the provider
with an unstable reference, and if at the point of calling into the
provider we find it is dead then acquiring a new stable reference
and doing the operation again. Thus if the provider process dies
at any point until we get the result back, our own process will not
be killed and we can safely retry the operation.
Arguably there is still the potential for a race -- if somehow the
provider is killed way late by the OOM killer after the query or
open has returned -- but this should now be *extremely* unlikely.
We also continue to have the issue with the other calls, but these
are much less critical, and the same model can't be used there (we
wouldn't want to execute two insert operations for example).
The implementation of this required some significant changes to the
underlying plumbing of content providers, now keeping track of the
two different reference counts, and managing them appropriately. To
facilitate this, the activity manager now has a formal connection
object for a client reference on a content provider, which hands to
the application when opening the provider.
These changes have allowed a lot of the code to be cleaned up and
subtle issues closed. For example, when a process is crashing, we
now have a much better idea of the state of content provider clients
(olding a stable ref, unstable ref, or waiting for it to launch), so
that we can correctly handle each of these.
The client side code is also a fair amount cleaner, though in the
future there is more than should be done. In particular, the two
ProviderClientRecord and ProviderRefCount classes should be combined
into one, part of which is exposed to the ContentResolver internal
API as a reference on a content provider with methods for updating
reference counts and such. Some day we'll do that.
Change-Id: I87b10d1b67573ab899e09ca428f1b556fd669c8c
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 652b6d1e591f6684cda4b93d4712920f287991b4 |
|
10-May-2012 |
Dianne Hackborn <hackbod@google.com> |
Add infrastructure for accessing "unstable" content providers.
We have an API and some stuff that purports to this, but no real
implementation yet.
Change-Id: I93555440014a50fdf79fa3f65318d90fb82265b4
/frameworks/base/core/java/android/content/ContentResolver.java
|
| a7771df3696954f0e279407e8894a916a7cb26cc |
|
08-May-2012 |
Jeff Brown <jeffbrown@google.com> |
Move CancellationSignal to android.os package.
Bug: 6427830
Change-Id: I39451bb1e1d4a8d976ed1c671234f0c8c61658dd
/frameworks/base/core/java/android/content/ContentResolver.java
|
| acb69bb909d098cea284df47d794c17171d84c91 |
|
14-Apr-2012 |
Dianne Hackborn <hackbod@google.com> |
Add direct support for HTML formatted text in ClipData etc.
When using the clipboard, ACTION_SEND, etc., you can now supply
HTML formatted text as one of the representations. This is exposed
as a set of methods on ClipData for building items with HTML
formatted text, and retrieving and coercing to HTML (and styled)
text. In addtion, there is a new EXTRA_HTML_TEXT for interoperating
with the old ACTION_SEND protocol.
Change-Id: I8846520a480c8a5f829ec1e693aeebd425ac170d
/frameworks/base/core/java/android/content/ContentResolver.java
|
| f76a50ce8fdc6aea22cabc77b2977a1a15a79630 |
|
09-Mar-2012 |
Ken Wakasa <kwakasa@google.com> |
Fix obvious typos under frameworks/base/core
Change-Id: Ia5fc3db1bb51824e7523885553be926bcc42d736
/frameworks/base/core/java/android/content/ContentResolver.java
|
| ab38500d9c0b8188dcb1045a24ce91cab1ca39ce |
|
02-Mar-2012 |
Jean-Baptiste Queru <jbq@google.com> |
am dbc591e2: am c69d6134: am 6ae4fe94: am 9303919d: Merge "Adds documentation for ContentResolver notifyChange()"
* commit 'dbc591e27686486c732fca2f94fde645e3487b7a':
Adds documentation for ContentResolver notifyChange()
|
| 4c1241df8f8b7fd5ec3dff6c7e0f66271248e76e |
|
03-Feb-2012 |
Jeff Brown <jeffbrown@google.com> |
Rename CancellationSignal using preferred spelling.
Bug: 5943637
Change-Id: I12a339f285f4db58e79acb5fd8ec2fc1acda5265
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 75ea64fc54f328d37b115cfb1ded1e45c30380ed |
|
26-Jan-2012 |
Jeff Brown <jeffbrown@google.com> |
Implement a cancelation mechanism for queries.
Added new API to enable cancelation of SQLite and content provider
queries by means of a CancelationSignal object. The application
creates a CancelationSignal object and passes it as an argument
to the query. The cancelation signal can then be used to cancel
the query while it is executing.
If the cancelation signal is raised before the query is executed,
then it is immediately terminated.
Change-Id: If2c76e9a7e56ea5e98768b6d4f225f0a1ca61c61
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 86de0590b94bcce27e3038c27464bed510bb564a |
|
23-Jan-2012 |
Jeff Brown <jeffbrown@google.com> |
Clean up content observer code.
Improved the documentation a little bit.
Fixed a bug in ContentService wherein if a ContentObserver was
passed as an argument and its deliverSelfNotifications() method
returned true, then notifyChange would tell all observers that
the change was a self-change even though it was only a self-change
from the perspective of the provided observer.
Deprecated ContentObservable.notifyChange since it is never
used and in general it shouldn't be because we want the notification
to be posted to the handler.
Change-Id: Idde49eb40777e011a068f2adae8a32f779dfb923
/frameworks/base/core/java/android/content/ContentResolver.java
|
| d7a1aada2d1245eaeef973bc3e37619ce8e6d593 |
|
18-Jan-2012 |
Steve Pomeroy <steve@staticfree.info> |
Adds documentation for ContentResolver notifyChange()
Adds clarifying documentation to ContentResolver#notifyChange() to
explain interaction with the sync framework.
Change-Id: Ia1a1ed173e230bc11aa778268749323536ca434f
Signed-off-by: Steve Pomeroy <steve@staticfree.info>
/frameworks/base/core/java/android/content/ContentResolver.java
|
| aac01f699f9f6ccf285bdec7e89ff864f180409d |
|
15-Oct-2011 |
Jeff Brown <jeffbrown@google.com> |
Merge "Add a CrossProcessCursorWrapper. Bug: 5220669"
|
| 558459fe85f56f29a6ed6a4d0adb4a0bd6665884 |
|
14-Oct-2011 |
Joe Fernandez <joefernandez@google.com> |
docs: add developer guide cross-references, Project ACRE, Round 2
Change-Id: I39a534ae3a2a34b4dabc333a09961012ef911d3e
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 825c5132bff21e72c1448241f4c6868563c8d624 |
|
13-Oct-2011 |
Jeff Brown <jeffbrown@google.com> |
Add a CrossProcessCursorWrapper.
Bug: 5220669
The CrossProcessCursorWrapper is a useful building block
for wrapping cursors that will be sent to processes remotely.
It can also transform normal Cursors into CrossProcessCursors
transparently.
The new class fixes common performance problems and bugs
that applications have encountered when implementing
ContentProviders.
Change-Id: Icc59fec10add3f7d8cfbd0495447860c1872c752
/frameworks/base/core/java/android/content/ContentResolver.java
|
| baaf8c3f55d9d95b9d2cd9279e2ce1725da0dc52 |
|
09-Oct-2011 |
Jeff Brown <jeffbrown@google.com> |
Implement CloseGuard in ContentResolver.
Also, don't try to close the cursor from the finalizer,
it just won't work because quite probably the Binder underneath
it has already been finalized or is about to be.
Change-Id: I6363cd30f32abe15412948d126e0bcc5f62943c5
/frameworks/base/core/java/android/content/ContentResolver.java
|
| f40216f98aa63df4a4ff1f26692502cd9078a6fa |
|
28-Jul-2011 |
Jean Chalard <jchalard@google.com> |
Fix a bug where a provider could be never released.
Bug: 5034192
Change-Id: I5d4adf27ea933687d4a0bc5ee76d57b74e708eec
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 43a17654cf4bfe7f1ec22bd8b7b32daccdf27c09 |
|
07-Apr-2011 |
Joe Onorato <joeo@google.com> |
Remove the deprecated things from Config.java. These haven't been working since before 1.0.
Change-Id: Ic2e8fa68797ea9d486f4117f3d82c98233cdab1e
/frameworks/base/core/java/android/content/ContentResolver.java
|
| ef5864f1bb1418307c40fc8ed4cae7545d8a44dd |
|
13-Jan-2011 |
Brad Fitzpatrick <bradfitz@android.com> |
am 2e390809: Merge "Unhide Content{Resolver,Provider}.call()" into honeycomb
* commit '2e3908097b1c86004d50c0a070ca6b76a4d0d7c5':
Unhide Content{Resolver,Provider}.call()
|
| 534c84c1ce19ae20ded249315c3c0558577eca6c |
|
12-Jan-2011 |
Brad Fitzpatrick <bradfitz@android.com> |
Unhide Content{Resolver,Provider}.call()
Change-Id: Ic7833b921f5a8e70ef7d565bfdf461e6e135ff1b
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 43194ce05eef26665572fb248a108fd24d247a8f |
|
12-Jan-2011 |
Brad Fitzpatrick <bradfitz@android.com> |
am 52d70722: am cb842753: Merge "Closing cursor in finalizer to avoid GREF and fd leak in acore"
* commit '52d70722654548d156bd7a1cb8c1f05b94b09f06':
Closing cursor in finalizer to avoid GREF and fd leak in acore
|
| 872a52c6b637faf75262b83fe68ff4e0d9fe044c |
|
20-Dec-2010 |
Johannes Carlsson <johannes.carlsson.x@sonyericsson.com> |
Closing cursor in finalizer to avoid GREF and fd leak in acore
The finalize() call did not clean up completely, this eventually
caused the android.process.acore to crash since it ran out of fds
and GREF to increased above 2000 if an application forgot to close
its cursor objects. A warning was also added when this happens so
that application developers can correct their mistake. The
included test case tries to verify that the finalizer works as
expected by creating a bunch of Cursor objects without closing
them (without this fix the acore process crashes after about 400
iterations and the test case ends with "Process crashed").
Change-Id: I11e485cef1ac02e718b2742108aa88793666c31d
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 03ee779b28227e75f16cb6240c5c667d097e59d1 |
|
28-Dec-2010 |
Jean-Baptiste Queru <jbq@google.com> |
am e90a1b16: am 752942ec: Merge "The phone is crashing when unknown mime content is transferred."
* commit 'e90a1b16a3d6c559cb7fc47ad967a1810d88e923':
The phone is crashing when unknown mime content is transferred.
|
| 145e6c4975536d927e506634514a06c43313df17 |
|
20-Dec-2010 |
Ola Olsson <ola1.olsson@sonyericsson.com> |
The phone is crashing when unknown mime content is transferred.
The content resolver does not take care of the IllegalStateException
that is thrown in getType and that needs to be fixed.
Change-Id: I3e66f1aa259ab91fb9233e1ba07faa1ab6c3f2dd
/frameworks/base/core/java/android/content/ContentResolver.java
|
| c6a69559cb62bd20166c0c9684e64c60d779da38 |
|
28-Sep-2010 |
Fred Quintana <fredq@google.com> |
Add getCurrentSyncs() to the SDK, which replaces the deprecated
getCurrentSync().
Change-Id: I1112df41e48ed93ff4c0c5af4825dbdce0c4cccc
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 64bbbb471ed78ae06f411224849a4556a30fd362 |
|
28-Sep-2010 |
Dianne Hackborn <hackbod@google.com> |
resolved conflicts for merge of a8bce7c8 to master
Change-Id: I34526a3aed6591639e1a1bff8f42e0c5d8e328cc
|
| cca1f0e3476edd09cdd81b075a6b7780a2959b46 |
|
27-Sep-2010 |
Dianne Hackborn <hackbod@google.com> |
Allow all apps to call ContentResolver.getType().
I can't find the bug number for this, but it is needed for some things
we are doing where the app building an intent may not have access to the
URI in the data field. This is for HC, but doing in GB to avoid introducing
integration issues.
Change-Id: I0cac971854198b18775d2a73deb80f23431bfbe2
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 8313fc7e94e46e5cc09f457a15a771a325b9f74f |
|
27-Sep-2010 |
Dianne Hackborn <hackbod@google.com> |
Allow all apps to call ContentResolver.getType().
I can't find the bug number for this, but it is needed for some things
we are doing where the app building an intent may not have access to the
URI in the data field. This is for HC, but doing in GB to avoid introducing
integration issues.
Change-Id: I0cac971854198b18775d2a73deb80f23431bfbe2
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 23fdaf6fb62a9b5154b2508916a21c678462c5d0 |
|
06-Aug-2010 |
Dianne Hackborn <hackbod@google.com> |
Add new ContentProvider for doing conversions to data streams.
This introduces basic infrastructure that should allow content
providers holding complex data to perform on-demand conversion
of their data to streams of various types. It is achieved through
two new content provider APIs, one to interrogate the possible
stream MIME types the provider can return, and the other to
request a stream of data in a particular MIME type.
Because implementations of this will often need to do on-demand
data conversion, there is also a utility intoduced in ContentProvider
for subclasses to easily run a function to write data into a
pipe that is read by the client.
This feature is mostly intended for cut and paste and drag and
drop, as the complex data interchange allowing the source and
destination to negotiate data types and copy (possible large)
data between them. However because it is fundamental facility
of ContentProvider, it can be used in other places, such as for
more advanced GET_CONTENT data exchanges.
An example implementation of this would be in ContactsProvider,
which can now provider a data stream when a client opens certain
pieces of it data, to return data as flat text, a vcard, or other
format.
Change-Id: I58627ea4ed359aa7cf2c66274adb18306c209cb2
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 36e5f667bc889a7b1bc17f9a5bd44f33b2d47020 |
|
25-Jun-2010 |
Dianne Hackborn <hackbod@google.com> |
resolved conflicts for merge of 2eb12a47 to master
Change-Id: I79eb9d9f083e51ec1b99145d81632683669e7a99
|
| 01e4cfc47d0a2c7e7ab383d2fb23224ec52c0301 |
|
25-Jun-2010 |
Dianne Hackborn <hackbod@google.com> |
Some ActivityThread/ActivityManager cleanup.
- Move PackageInfo out of ActivityThread, renaming to LoadedApk.
- Rename some of the other PacakgeInfo inner classes to better
represent what they are.
- Rename HistoryRecord to ActivityRecord.
- Introduce AppGlobals, to eventually let ActivityThread become
package scoped.
Change-Id: Ib714c54ceb3cdbb525dce3db9505f31042e88cf0
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 03f0292744094ec107ffce71301c394503a31ded |
|
09-Jun-2010 |
Gilles Debunne <debunne@google.com> |
New XmlDocumentProvider class.
Minor changes in the Adapters.java helper class.
Extracts data out of a XML document using an XPath-like syntax.
Change-Id: I0617b0783f11c86118b42cd8485d54440810c805
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 020e5345795a157d7829ebbe4d7864595dafc576 |
|
28-Apr-2010 |
Vasu Nori <vnori@google.com> |
bug:2622719 move 'forcing of cursor execution' to ContentProvider
revert part of the CL: Ia561135e974a44ad3e3774ecb23c6a3d0fc38176
and add it to ContentProvider.query() to force query execution
in worker thread, instead of having the main thread incur the cost
of query execution and potentially get ANR
Change-Id: I0ea8a170bd954a421f4ad825f8090319a83a5b2b
/frameworks/base/core/java/android/content/ContentResolver.java
|
| a8fbedbf5e274581ba0cbb20da34ade286fc1cfc |
|
08-Apr-2010 |
Brad Fitzpatrick <bradfitz@android.com> |
Missed these ones in the previous rename.
BUG=2581935
Change-Id: I12e7fc924d7164ab4a5ff7bd6ee52a10f7551ad4
/frameworks/base/core/java/android/content/ContentResolver.java
|
| d5e4fdc8a4743abc0d9fe3cb952a78f9ad078c6b |
|
31-Mar-2010 |
Fred Quintana <fredq@google.com> |
some changes due to an API review
- make EntityIterator extend Iterator and thus not throw a
RemoteException, instead converting it into a RuntimeException.
- rename ActiveSyncInfo to SyncInfo
- change getActiveSync to getCurrentSync
- remove the accessors in SyncInfo and instead make the final
fields publicly accessible
- made AbstractThreadedSyncAdapter.cancelSync not take a thread
Change-Id: I99fde5585bc5f1e95f4873ffbba189074a8d6372
http://b/issue?id=2553539
http://b/issue?id=2553541
http://b/issue?id=2553550
/frameworks/base/core/java/android/content/ContentResolver.java
|
| d2a2daaa89865d19e881ab9af133ce0f3902c820 |
|
11-Mar-2010 |
Omari Stephens <xsdg@android.com> |
Fix small typo in javadoc: "deleting" -> "updating"
Change-Id: Ie0464aa92d33eb5b076a8122f5bd6317fd44a7b2
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 1877d0158b529663b8315482e7346a7bcaa96166 |
|
05-Mar-2010 |
Brad Fitzpatrick <bradfitz@android.com> |
Add "call" method on ContentProvider.
This permits implementing interfaces which are faster than using
remote Cursors. It then uses it for Settings & SettingProvider, which
together account for ~50% of total ContentProvider event loop stalls
across Froyo dogfooders.
For fetching Settings this looks like it should reduce average
Settings lookup from 10 ms to 0.4 ms on Sholes, once the
SettingsProvider serves most gets from in-memory cache. Currently it
brings the Sholes average down from 10ms to 2.5 ms while still using
SQLite queries on each get.
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 1b487ec44b6b5594914d52fa427bec4f29a60541 |
|
26-Feb-2010 |
Fred Quintana <fredq@google.com> |
expose some sync control methods
- ActiveSyncInfo
- ContentResolver.addStatusChangeListener
- SYNC_OBSERVER_TYPE_SETTINGS
- SYNC_OBSERVER_TYPE_PENDING
- SYNC_OBSERVER_TYPE_ACTIVE
- make the ContentService resilient to nulls passed in to the
status change listener registration and unregistration calls
bug http://b/issue?id=2337197
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 25880968cbde25c9edb162c0d70d45dc75239456 |
|
23-Feb-2010 |
Brad Fitzpatrick <bradfitz@android.com> |
Reduce SQLiteDatabase and ContentResolver EventLog logging thresholds.
Turns out the database is used a ton, and not particularly quickly, so
these were spamming the logs at their prior 100ms thresholds. Setting
it to 500ms now. (still sub-sampled, so should be ~5x less spammy...)
/frameworks/base/core/java/android/content/ContentResolver.java
|
| d72f718c9cc4bd5e4701f4c5cdab51b4d8cf6435 |
|
12-Feb-2010 |
Brad Fitzpatrick <bradfitz@android.com> |
Measure walltime in ContentResolver and SQLiteDatabase operations logging.
Previously, SQLiteDatabase was using Debug.threadCpuTimeNanos(), which
doesn't include I/O time (user-perceived latency), and ContentResolver
was using System.currentTimeMillis(), which didn't account for deep
sleeps.
Now both are consistently using SystemClock.uptimeMillis().
/frameworks/base/core/java/android/content/ContentResolver.java
|
| a63730d1f103f78589faef461d2af7351fc49f42 |
|
08-Feb-2010 |
Brad Fitzpatrick <bradfitz@android.com> |
Log ContentProvider operations to the EventLog.
Just like with db_operation, operations over 100ms are always logged,
while operations under that are subsampled.
This will help with performance analysis, getting real-world
performance numbers from dogfooders.
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 53bd2522ca7767f46646606123b6e2689b811850 |
|
06-Feb-2010 |
Fred Quintana <fredq@google.com> |
- change the SyncManager to retry MANUAL syncs that encounter a soft error
- make the sync dump handle the case where there are no accounts
- fix a bug that caused the SyncManager to burn up CPU in the system process
The following was implemented:
scheduler offers:
- settings to disable sync
- retries of certain errors
- backoffs
want a way to control these when scheduling a sync
- "ignore_settings"
- "ignore initial backoff"
- "manual" : ignore settings, ignore initial backoff
- "do not retry"
- need to change the default behavior of not retrying manual syncs to retry regardless
/frameworks/base/core/java/android/content/ContentResolver.java
|
| c5d1c6db61f208b206b260f897bb5bbc64be4d97 |
|
27-Jan-2010 |
Fred Quintana <fredq@google.com> |
add sync polling
- added the ability to specify that a sync (of account/authority/extras)
should occur at a given frequency
- the existing daily poll code was replaced with seeding each
account/authority with a 24 hour periodic sync
- enhanced the "adb shell dumpsys content" output to show the
periodic syncs and when they will next run
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 0ba1cb06c6a0332b76c469bd54dcf6f98128ac82 |
|
08-Jan-2010 |
Tom O'Neill <tomo@google.com> |
ContentResolver.query() includes performance considerations
Mention the desirability of using "?"-substitution in the where clause,
and reemphasize the importance of using an explicit projection.
Change-Id: Iaa489d50db409f34e78bcd55253e5a4e53445cf2
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 2ec6c5699181316e5a5c2cd293c006ac4a8bb101 |
|
10-Dec-2009 |
Fred Quintana <fredq@google.com> |
am 328c0e79: - removed the concept of Entity from the ContentProvider APIs - removed the parcelling ability from Entity and EntityIterator and made them public - added an EntityIterator abstract implementation that allow easy wrapping of a Cursor - changed the VCard c
Merge commit '328c0e7986aa6bb7752ec6de3da9c999920bb55f' into eclair-mr2-plus-aosp
* commit '328c0e7986aa6bb7752ec6de3da9c999920bb55f':
- removed the concept of Entity from the ContentProvider APIs
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 5bba632d877c2878384ff21566c8eb6a1a22f37b |
|
05-Oct-2009 |
Fred Quintana <fredq@google.com> |
- hide Entity and all its references
- remove updateEntity and insertEntity, since they are not
used
- add the RawContacts.Entity class, which is used in lieu of the
android.content.Entity
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 3348f14b3d46b172a5b557f81aac526b7e8bf5fb |
|
30-Sep-2009 |
Costin Manolache <costin@google.com> |
Remove GAIA string
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 4c87a3f26a7c0c75fa371024a8726b59a108fd0f |
|
16-Sep-2009 |
Bjorn Bringert <bringert@android.com> |
Use Resources to load search icons with android.resource URIs
Before, all icon URIs were opened with
ContentResolver.openInputStream(Uri), but that does not
include the density information from the source
application.
Now, if the URI uses the android.resource scheme,
we resolve the URI to a Resources and a resource ID,
and load it with Resources.getDrawable(int).
This requires making OpenResourceIdResult and getResourceId()
in ContentResolver public (but hidden).
This change also caches icons that were specified using just a
resource ID.
Since loading a Drawable from a URI is a generally useful operation,
it would be good to make it easy for apps to do it in the proper
density-independent way. We could add a getDrawable(Uri)
method to the framework. The question is where.
It would be easiest to add it to ContentResolver, but that may be a
bit odd since there is no other code for dealing with Drawables in
ContentResolver. Another alternative is in Resources, since
getDrawable(int) is there, but that class deals with the resources
for a single app, whereas getDrawable(Uri) can open a drawable
from any app. Putting it in Context may be the best choice,
since that's in android.content, and can thus access package
private members in ContentResolver, and since it's already
a dumping place for random useful high-level methods.
Opinions?
Fixes http://b/issue?id=2034526
"Icons on search do not scale for wide VGA"
Change-Id: I44de0b74826e5560141a3174bcbba991ba6264ac
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 4a51c20ce607c74914f90fd897f04080121ac13b |
|
22-Aug-2009 |
Dianne Hackborn <hackbod@google.com> |
I am getting tired of the java doc warnings, so fix them.
Change-Id: I2205eebae419eaf4a0992c9f5b7cd807eb843fe1
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 77709755b74bcc852cd511ff833c2827c0f0e1aa |
|
21-Aug-2009 |
Fred Quintana <fredq@google.com> |
- add a reset to EntityIterator to allow it to go back to the beginning
- clean up the debug printing of SyncResult
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 4a6679b97e0285c5b65ec5c0d9080ff90d3e9e81 |
|
17-Aug-2009 |
Fred Quintana <fredq@google.com> |
make syncadapter set whether the account is syncable
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 20ea6ce0e8a758cc5c33eb2577495bf9f4dce16e |
|
18-Aug-2009 |
Jim Miller <jaggies@google.com> |
Change get/set IsSyncable() methods to static. Add isUserFacing flag to SyncAdapterType. Update api file.
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 718671b441c6318276e6d954a41a95db0d7e6c49 |
|
17-Aug-2009 |
Fred Quintana <fredq@google.com> |
fix build breakage
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 5e787c42f2a6b3afc8ec8320a08d51b2d44b8614 |
|
17-Aug-2009 |
Fred Quintana <fredq@google.com> |
- add a "isSyncable" flag to a given account/authority pair that
indicates whether or not syncs should be attempted for it.
- add public methods to get and set this parameter
/frameworks/base/core/java/android/content/ContentResolver.java
|
| ac9385ef3105fb7464e1f46049c62755a8b7f0e9 |
|
23-Jun-2009 |
Fred Quintana <fredq@google.com> |
- clean up the sync settings names to:
(get|set)SyncAutomatically
(get|set)MasterSyncAutomatically
- change SYNC_EXTRAS_FORCE to SYNC_EXTRAS_MANUAL to mace clear that
this overrides the .*SyncAutomatically settings
- make ContentResolver methods that call the sync controls methods
in IContentService so that SDK users can use them
- rename startSync to requestSync to reinforce the fact that a sync
is not immediately or always started when this method is called
- add an Account parameter to all the sync settings and control methods
- change the sync control methods to take a String authority rather than a Uri uri
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 03d9490758c9318cee6d14d3cc5007556dce92d0 |
|
22-May-2009 |
Fred Quintana <fredq@google.com> |
- create a new generic ISyncAdapter implementation, SyncAdapterNew
- change the applyBatch to take an ArrayList rather than an []
- change Entity to be a final flass that contains ContentValues
- remove the ability to update/insert Entities by a ContentProviderOperation
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 8943737692169f564cd34a9c8d471f3a5d438712 |
|
16-May-2009 |
Fred Quintana <fredq@google.com> |
add ipc support to batching
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 6a8d5332f00bdfade6674b312e7166940aa28348 |
|
08-May-2009 |
Fred Quintana <fredq@google.com> |
content provider entities
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 7a1355950172b7a549820e9a2cd4a9b2099ec32f |
|
06-May-2009 |
Dianne Hackborn <hackbod@google.com> |
merged 231cc608d06ffc31c24bf8aa8c8275bdd2636581
|
| 231cc608d06ffc31c24bf8aa8c8275bdd2636581 |
|
28-Apr-2009 |
Dianne Hackborn <hackbod@google.com> |
Rewrite SyncStorageEngine to use flat files and in-memory data structures.
The previous implementation used a database for storing all of its state, which could cause
a significant amount of IO activity as its tables were updated through the stages of a sync.
This new implementation replaces that in-memory data structures, with hand-written code
for writing them to persistent storage.
There are now 4 files associated with this class, holding various pieces of its state that
should be consistent. These are everything from a main XML file of account information that
must always be retained, to a binary file of per-day statistics that can be thrown away at
any time. Writes of these files as scheduled at various times based on their importance of
the frequency at which they change.
Because the database no longer exists, there needs to be a new explicit interface for
interacting with the sync manager database. This is provided by new APIs on IContentService,
with a hidden method on ContentResolver to retrieve the IContentService so that various
system entities can use it. Other changes in other projects are required to update to the
new API.
The goal here is to have as little an impact on the code and functionality outside of
SyncStorageEngine, though due to the necessary change in API it is still somewhat extensive.
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 718d8a2d7ff3e864a73879eb646f46c14ab74d07 |
|
30-Apr-2009 |
Fred Quintana <fredq@google.com> |
decouple SyncAdapter from ContentProvider
/frameworks/base/core/java/android/content/ContentResolver.java
|
| d9d2f1140b52fd0c014e9deac59f6000564b7e84 |
|
23-Apr-2009 |
Fred Quintana <fredq@google.com> |
change the sync framework and users to understand Account
/frameworks/base/core/java/android/content/ContentResolver.java
|
| b0c6dbd53b26b172fe8eb7d117550e4edf7a0c9c |
|
22-Apr-2009 |
Jeff Hamilton <> |
AI 147255: am: CL 147253 am: CL 147250 Fix a nasty typo in the docs for ContentResolver.update(). No code changes.
Original author: jham
Merged from: //branches/cupcake/...
Original author: android-build
Automated import of CL 147255
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 348c1796d460e43e45e582739956c02c5bc8f602 |
|
22-Apr-2009 |
Jeff Hamilton <> |
AI 147253: am: CL 147250 Fix a nasty typo in the docs for ContentResolver.update(). No code changes.
Original author: jham
Merged from: //branches/cupcake/...
Automated import of CL 147253
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 9066cfe9886ac131c34d59ed0e2d287b0e3c0087 |
|
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
/frameworks/base/core/java/android/content/ContentResolver.java
|
| d83a98f4ce9cfa908f5c54bbd70f03eec07e7553 |
|
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 076357b8567458d4b6dfdcf839ef751634cd2bfb |
|
03-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@132589
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 3dec7d563a2f3e1eb967ce2054a00b6620e3558c |
|
03-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@137055
/frameworks/base/core/java/android/content/ContentResolver.java
|
| 54b6cfa9a9e5b861a9930af873580d6dc20f773c |
|
21-Oct-2008 |
The Android Open Source Project <initial-contribution@android.com> |
Initial Contribution
/frameworks/base/core/java/android/content/ContentResolver.java
|