| f6e9b95127bc2fbe663407f274de5f485ce9973c |
|
21-Sep-2016 |
Jeff Sharkey <jsharkey@android.com> |
Check if anyone could possibly provide service.
If no service is present that could satisfy a given ServiceWatcher,
then return false. For example, on devices were there is no Geocoder
service implementation, we need to avoid claiming that the API is
supported.
Test: booted
Bug: 30837973
Change-Id: Ib0834cf1a12623733f8b472dc3da7b3e2adc4515
/frameworks/base/services/core/java/com/android/server/ServiceWatcher.java
|
| c7bacab20fa8a0e603726f4f8ebafd3a96babeb1 |
|
09-Feb-2016 |
Jeff Sharkey <jsharkey@android.com> |
More encryption-aware triaging.
Most of these callers are okay having results omitted when a package
is uninstalled or encryption unaware. For example, jobs and
notifications can only be enqueued by already running apps.
When clearing zen rules, keep around rules inserted by apps on
ejected external storage devices.
Make ServiceWatcher stricter by requiring that the matching package
be in the system image.
Bug: 26471205, 27105254
Change-Id: Ie41ea8042ac1a54e9cbe0c35cec89e70521e9bed
/frameworks/base/services/core/java/com/android/server/ServiceWatcher.java
|
| 58482c55d0848f9675b551cf2fea4990336f0b31 |
|
09-Feb-2016 |
Jeff Sharkey <jsharkey@android.com> |
Make ServiceWatcher encryption-aware.
This utility class automates the process of binding to the best
matching service, including rebinding as packages change over time.
This design means it's easy to become encryption-aware: we use the
default PackageManager behavior that filters components based on
their encryption-aware status, and we just kick off another
evaluation pass once the user is unlocked.
This change cleans up some of the internal logic so we only rebind
when the implementation switches, and it fixes several bugs along
the way. For example, we would never trigger a rebind if a service
was refactored to a different ComponentName. Another subtle bug was
that we'd never fallback to an older implementation if a higher
version was uninstalled/disabled. And finally, if all implementations
were uninstalled/disabled, we'd leave the last connection bound.
Bug: 26280056
Change-Id: I259af78e6564d61353a772ac03cf5799a398d535
/frameworks/base/services/core/java/com/android/server/ServiceWatcher.java
|
| 3326c526bc84a1529613b5333502c2dcb64d966d |
|
07-Aug-2015 |
Xiaohui Chen <xiaohuic@google.com> |
Clean up USER_OWNER in ServiceWatcher
Bug: 19913735
Change-Id: I1d9fe26efe7ec2abb6b164efb0af04416cc0f7fb
/frameworks/base/services/core/java/com/android/server/ServiceWatcher.java
|
| 49782e46c0eb85a25ae2abcf80880c48dbab5aea |
|
20-Dec-2013 |
Amith Yamasani <yamasani@google.com> |
am 9158825f: Move some system services to separate directories
* commit '9158825f9c41869689d6b1786d7c7aa8bdd524ce':
Move some system services to separate directories
|
| 9158825f9c41869689d6b1786d7c7aa8bdd524ce |
|
22-Nov-2013 |
Amith Yamasani <yamasani@google.com> |
Move some system services to separate directories
Refactored the directory structure so that services can be optionally
excluded. This is step 1. Will be followed by another change that makes
it possible to remove services from the build.
Change-Id: Ideacedfd34b5e213217ad3ff4ebb21c4a8e73f85
/frameworks/base/services/core/java/com/android/server/ServiceWatcher.java
|