Callbacks
- DataUsageCallback renamed to UsageCallback
- DataUsagePolicy removed; passing in params directly to register method
- making it an abstract class
- passing in (networkType, subscriberId) that reached its threshold
- renaming onLimitReached to onThresholdReached to match existing naming
- only monitor single network,subscriberId
- no monitoring of specific uids; using device or user wide instead
Tags
- only owner uid can read its tags
- exposing only TAG_NONE to match service side
BUG: 27530098
Change-Id: I2b2664da71806868a1e937d2bf4d1f234637509b
We should hide the notification asap before setting
managed profile lock, to reduce the time that user is unlocked
while the notification is still showing.
Bug: 28689675
Change-Id: I289302302e3079726998adefebe2e8b113b2e52a
The white list of permitted directories is applied for every
classloader namespace by libnativeloader. LoadedApk no longer
needs to do that.
Add mDataDir to permitted paths in the case if for any reason
it is outside of the whitelisted dirs.
Bug: http://b/28639227
Change-Id: I5b61ac64e281ecee3e3e9b1fe56cf04dc6ee7b25
Problem was introduced in ag/960365. We need to properly set the
temp variable to the current task bounds before trying to use it.
Bug: 26962445
Change-Id: I3cded03582e1379e16fa48f69da6ceadb92d8d4b
We were thrwing undocumented runtime exception when
one gets the permission flags - now we just return
default result of the package is gone.
bug:28657926
Change-Id: I42554a86b9304ff83fe9385f3eea930b8ebf0c63
In preparation for using MetricsLogger.histogram / count. The main
purpose of this change is to remove the (now bogus) action IDs
associated with this logging.
bug: 28528058
bug: 28544474
Change-Id: Id79de2d34c3f937a327ac21d44e55c18047bce85
- add new landing page for F Preview
- add new supporting pages for F Preview
- Update TOC file to list new pages
b/28004352
Change-Id: I3a4de8b3c756f1bbee91e136d67a413a5953277a
Settings were persisted on the system background thread but during
first boot the device is under heavy load and persisting settings
competes with other system components using the shared background
thread. As a result persisting settings can be delayed much longer
than the expected 200ms. This can cause issues with setup wizard
being skipped/went over and its component disaabled being persisted
but the setting whether the device is provisioned not being
persisted - now if the device boots it will have no SUW but also
the home button would be missing. Generally, we need a tansactional
abstraction in the system process to peform all delayed operations
atomically.
bug:25472484
Change-Id: Icf38e72403b190a8fa9d0554b8dd83ce78da3bc8
