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
am: 740a5f0
* commit '740a5f023eea7b2fdb3e31efe8b8d5ac18aa8302':
Add the print service recommendation service
Change-Id: Ie58ade9356f591781496581259b6d8a876780ac9
This service connects through the print manager to the print spooler:
PrintSpooler.AddPrintersActivity <-> PrintManager <-> PrintManagerService <-> UserState <-> RemotePrintServiceRecommendationService <-> PrintRecommendationService <-> PrintRecommendationServiceImpl
Hence there is a lot of mindless plumming.
The actual changes are only in the AddPrintersActivity which is extended
to show another list of services: The recommended services.
The PrintServiceRecommendationService is based on the experimenal print
service stubs provider. This provider was contributed the Android by
Mopria. As this services uses Android own network discovery service most
code from the experimental provider goes away. In fact the only logic
left over is the selections of mdns-txt fields to look at and the
printer vendor configuration.
This relies on the Android MDNS to get fixed (Bug: 27696905). This also
does not deal with how to update the recommendation service.
Bug: 24533249
Change-Id: I6edc6e25fc08a50d478b61c71bb8ea158b08624c
Now that CE data isn't available until after a user is unlocked, we
need to delay the PRE_BOOT_COMPLETED broadcasts. This is done by
adding a new RUNNING_UNLOCKING user state to the UserController
lifecycle.
We now track the last fingerprint a user was logged in under, and we
dispatch PRE_BOOT receivers when that fingerprint changes. To work
around battery pull issues, we only persist the updated fingerprint
once all PRE_BOOT receivers have finished. This is less granular
than the original solution, but it's still correct. We only consider
a user as "logged in" once it transitions into the RUNNING_UNLOCKED
state.
When starting a process, track if the user was "unlocked" when
started, so that we only spin up unaware providers in processes
started before user unlock.
Add generic IProgressListener to communicate PRE_BOOT progress and
strings up to lock screen. For now, LockSettingsService just blocks
until finished, but it could display these strings in the future.
Bug: 27220885
Change-Id: I349439776b885acd32f6a578d8951ffd95640be2
- Pull most of the inner classes out into their own files.
- Move everything to a new android.app.procstats package.
- Move all of the code that was manipulating the big list
of longs to use the new SparseMappingTable class rather
than doing everything by hand. The logic is unchanged.
- Add a sequence number check to SparseMappingTable so
when the big list of longs and the individual tables are
reset, which happens somewhat independently, we can
assert when one of them doesn't get reset.
Replace some custom rules with BUILD_PREBUILT.
Move tools from ALL_PREBUILTS to BUILD_PREBUILT. All of them are already
in PRODUCT_PACKAGES in build/target/product/base.mk.
Remove uses of ACP and replace with core build system macros or 'cp'
Change-Id: I529e7c6c50fc64ad36b75bb47142f6bde909d141
am: 24b8e43
* commit '24b8e43f699e5c4baa5116542c8723b3997fe389':
switch offline docs back to standard templates that now have a condition for 'referenceonly' bug: 27667787
