am: aefec202de
* commit 'aefec202de2a94ce2a624d72bd2036f7141b1af7':
OP_ACTIVATE_VPN should not map to DISALLOW_CONFIG_VPN
Change-Id: I88bba620c3a3212ebf74ee0f884febc3ec923c1f
am: fff6650de4
* commit 'fff6650de4ac847db61ffdf3fbc82a39e3878313':
OP_ACTIVATE_VPN should not map to DISALLOW_CONFIG_VPN
Change-Id: Id88584fff3f69e554793ea1e99dd491796a470ff
am: 33d03a9e43
* commit '33d03a9e435eb474e3bdd3e958943e0057866477':
OP_ACTIVATE_VPN should not map to DISALLOW_CONFIG_VPN
Change-Id: Ib8e3b7fae441adf95b928d7139455d3ca13c1fb6
am: 33d03a9e43
* commit '33d03a9e435eb474e3bdd3e958943e0057866477':
OP_ACTIVATE_VPN should not map to DISALLOW_CONFIG_VPN
Change-Id: I2de02ec6febdc58ff9a79562059cc11e7d617be5
They are two different things.
OP_ACTIVATE_VPN means can we allow a vpn app to establish without user
interaction while DISALLOW_CONFIG_VPN means can the user modify vpn
config.
Testing:
1. Turn on DISALLOW_CONFIG_VPN, user cannot modify vpn config through
setting
2. Turn on DISALLOW_CONFIG_VPN, Dpm.setAlwaysOnVpn works.
3. Reboot after 2, vpn established automatically.
Bug: 29086229
Change-Id: I24899d6c7f0dd62bf441a44c6ee66fee35973a11
When ejecting a storage device, the system process needs to rapidly
release any open FDs to prevent itself from being killed by vold.
This change examines all ResourceImpls cached inside the system
process and evicts any that reference the storage device being
ejected. (ResourcesManager will gladly recreate any evicted entries
when asked again in the future.)
Also replace broken use of WeakHashMap, since we want the values to
be weak references, not the keys.
Bug: 28867548
Change-Id: Ib9cfc66497149b6d3f8d49213e9779408a331d2a
We now have a new settings key that provides all of the existing
tuning parameters, plus some newly redone ones for dealing with
different memory levels.
Changed the minimum batching for overall jobs from 2 to 1, so
we will never get in the way of immediately scheduling jobs
when the developer asks for this. We should now be able to rely
on the doze modes to do better batching of jobs for us when it
is really important.
Also work on issue #28981330: Excessive JobScheduler wakeup alarms.
Use a work source with scheduled alarms to blame them on the app
whose job they are being scheduled for, and add a check for whether
a job's timing constraint has been satisfied before considering it
a possible candidate for the next alarm. (If it is satisified,
the time is in the past, so we should not schedule an alarm for it.)
Finally clean up a bunch of the dumpsys output to make it easier
to understand.
Change-Id: I06cf2c1310448f47cf386f393e9b267335fabaeb
am: 09c17150f9
* commit '09c17150f95dfdde2d737049dcecb3b04a160db5':
Don't bother with WeakHashMap for direct alarm bookkeeping
Change-Id: I77e998c444e5cd92422b9e176f5c9aea8526e6ce
am: 494529318a
* commit '494529318a0a8952ed5dc7bc00786f74f39b2612':
Don't bother with WeakHashMap for direct alarm bookkeeping
Change-Id: I23fef9e69fb5aa0ec57d32e19d1fc513611018fd
am: cd0aa9cda8
* commit 'cd0aa9cda8e57c224b473198a345fb008fe30b5a':
Don't bother with WeakHashMap for direct alarm bookkeeping
Change-Id: Ia86b5f27d511bb8da2bd8982ffe35d4d2906da54
am: cd0aa9cda8
* commit 'cd0aa9cda8e57c224b473198a345fb008fe30b5a':
Don't bother with WeakHashMap for direct alarm bookkeeping
Change-Id: I3b28a8c03cee7fe6f85540f1f679de10de09923c
Call cancel() explicitly before dropping local references to your
callback objects; they won't just quietly go away.
Bug 28987260
Change-Id: Id9da66ed86a46b4fb38127e2ddd7a7d84fd2313a
Bug 28347277
When an activity calls startActivity with makeSceneTransitionAnimation
and then calls finishAfterTransition, it should not do any transition
and just finish.
Change-Id: I00e537638fa6f24c95605f09bbafd843b569bb4d
