diff options
| author | Pavel Grafov <pgrafov@google.com> | 2017-10-03 15:11:52 +0100 |
|---|---|---|
| committer | Pavel Grafov <pgrafov@google.com> | 2017-12-06 17:43:17 +0000 |
| commit | 28939988f0da2f37bac87a6929a1584ad18fdeba (patch) | |
| tree | f79197c70ae1d770faaebf8a271207ac7a95d82c /tools/aapt2/java/JavaClassGenerator.cpp | |
| parent | f5cf390e416e964b915b8dcf3339230c93756547 (diff) | |
Profile lock timeout.
When a managed profile has separate lock (a.k.a work challenge)
and maximum screen off timeout set by admin, this timeout will
only cause the profile to get locked, not the whole device.
PowerManagerService now tracks some per-profile state for profiles
that have lock timeout set by admin and have separate lock:
1. timeout set by admin.
2. wake lock summary
3. last activity time
4. whether the profile is considered active
5. whether the profile got locked last time it went inactive.
Wake lock summaries and last activity times are updated at the
same time as global wake lock summary/user activity is updated.
Test: cts-tradefed run commandAndExit cts-dev -a armeabi-v7a -m CtsDevicePolicyManagerTestCases -t com.android.cts.devicepolicy.ManagedProfileTest
Test: runtest -c com.android.server.devicepolicy.DevicePolicyManagerTest frameworks-services
Bug: 63908311
Change-Id: Ief7be4e0bf12bdbedef94a129a13d07a9f98e75c
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator.cpp')
0 files changed, 0 insertions, 0 deletions