am: 4a9ae46de9
* commit '4a9ae46de97476e75d2f2e38989c5b93a272349b':
Pass -yaml to ds builds to generate _book.yaml version of reference TOC.
Change-Id: Iba70a1644719fefc08c83acb049ff826c5c98923
am: 4569e9515c
* commit '4569e9515c651616f7e24f563b52de98fb4bf258':
Pass -yaml to ds builds to generate _book.yaml version of reference TOC.
Change-Id: I83d230df7e8fb620ec9ea57621492261fbb236b7
am: c25a9b0104
* commit 'c25a9b0104802454487ee6c428f9f070d389c02f':
Pass -yaml to ds builds to generate _book.yaml version of reference TOC.
Change-Id: Ib8ff6165cbcb1d3fb52611e9f5e61ac69a0083b6
am: 6049306d8c
* commit '6049306d8c0f88f78dbc097bfcc971b095c6a9a3':
Pass -yaml to ds builds to generate _book.yaml version of reference TOC.
Change-Id: I6b6a65147254b0d2ba5ec6aa52429819ddca9b77
am: 0010741
* commit '0010741818127e6c9449fc49490f0bad14a76240':
Ensure local settings caches are not stale
Change-Id: I26c4f1f72eda3b2ebfb3ca6e086a0381d357471c
am: f71d7fe
* commit 'f71d7feef22db9e0cab2f32edc7440aedb86fdfe':
Ensure local settings caches are not stale
Change-Id: I356b9ad0b6dc1e91bfad140de1b9fc79ab6efef3
We used the system proterties as a shared memory mechanism
to propagate information to local settings caches when the
content has changed and the cache should be cleared. The
system properties are unfortunately updated asynchronously
leading to cases where clients may read stale data.
This change adds a simple int array data structure backed
by shared memory which guarantees individual values are
atomically read and updated without memory tear. Multi-
index opearations are not synchronized between each other.
The settings provider is using the new data structure to
propagate the settings generation which drives when caches
are purged.
We have a single memory array keeping the generation for
different settings tables per user. Since memory array is
not a compact data structure and the user space exceeds
the memory array size we use an in-memory map from keys
to indices in the memory array where the generation id of
a key is stored. A key is derived by the setting type in
the 4 most significant bits and the user id in the 28 least
significant bits.
The mapping from a key to an index is cleared if the user is
removed and the corresponding index in the memory arry is
reset to make it available for other users. The size of the
memory array is derived from the max user count that can be
created at the same time.
bug:18826179
Change-Id: I64009cc5105309ef9aa83aba90b82afc8ad8c659
am: 13da561
* commit '13da5613e2fce0ca2d5682fd202234856d2206e9':
Cleanup of the PackageInstaller API - Frameworks
Change-Id: Ibe4a6258c6437a9e86ed25e242301ca6d6635d26
am: c947ebd
* commit 'c947ebd66d397782af0870df457ccc4fe83c77cc':
Cleanup of the PackageInstaller API - Frameworks
Change-Id: I50e4c8357bb0c5abab9c37b6a39628f6e3e0ea1b
am: c5826ee
* commit 'c5826eebc50a6ffafe8cd20633b01b6ca27e8490':
Unbundle RemoteService on TV - part 3
Change-Id: If0dabbb8199132648fa9a791f46ee85e8970eb4b
The PackageInstaller app manages side-loading apps as well
as permission management. It should be updatable, hence
should rely on system APIs to talk to the platform. This
is the first step of defining an API boundary.
Change-Id: I9814eafd0b22ae03b4b847a7007cdbf14c9e5466
am: a2262b3
* commit 'a2262b3bb15497c6ee4854cfcf7a43fc07c2c876':
Unbundle RemoteService on TV - part 3
Change-Id: I45fbdda42aa5d9f5d9c25a027dd11eb7b0f560a1
am: 7981e8f
* commit '7981e8ff6509769a590f15b440f989437d732be5':
Unbundle RemoteService on TV - part 3
Change-Id: Ib5eb6363e904a1f66000d12263f66a8e5bd1f663
- New service TVRemoteService triggered by SystemServer
- Provider service proxy and watcher for maintaining connections to unbundled
services which have the BIND_TV_REMOTE_SERVICE permission.
- Shared library to facilitate connections between unbundled service and
TVRemoteService.
- Unbundled service needs TV_VIRTUAL_REMOTE_CONTROLLER
permission to be fully functional.
b/23792608
Change-Id: Ief5c6995883d1f7268a73bdd0c920c4c3f42cddb
Which owns the native UidRange.cpp, so it makes more sense for the
declaration to live there since frameworks/base depends on netd but not
vice versa.
Bug: 26694104
Change-Id: I0efda77713ee6f0ec8070fb0e09a694b95f6cd25
am: bc783e0
* commit 'bc783e038c17524c5182ad6b5e17ba95d0e1a319':
Add VrManager AIDL interface for use by system apps.
Change-Id: Ie3aaad8ef509f69c643638f8974a95e1f33a7a60
am: 50e229f
* commit '50e229f1f45a1550ba13ec3f81e864630fc3dc1c':
Add VrManager AIDL interface for use by system apps.
Change-Id: Ia0bbf2bbe778bef5773e5d7c43b25d3cb248fe23
If subscriber is in external app, its process can be killed. This would
lead to loss of events. To avoid that, we will be storing events in the
logger service. Clients can periodically pull data from it.
Another option for client apps is to register PendingIntent which will be
sent when certain number of new events has been received.
If events are logged at unexpectedly high rate from particular component,
then throttling mechanism will activate and new events will be blocked for
some time from that component.
Change-Id: I710409626eb5a42bcd3fe8126eac6b756fa1ab8b
am: fa04bc7
* commit 'fa04bc7a5d49415bc7cd397bb9678316d3824f85':
Add the print service recommendation service
Change-Id: I3da289dfe99e1caa3ed2ab3368902d597f16f738
