| 6235a94ffaed1d82cee2317481c18776f601da1b |
|
15-Mar-2016 |
Michal Karpinski <mkarpinski@google.com> |
Unifying method names and comments to security logging, not device logging
Also move SecurityLog to android.app.admin package.
Bug: 27531824
Bug: 27532560
Bug: 27532564
Bug: 27532425
Change-Id: I2677afdb5685bc5d21e52c41b381b57a41e364b6
/frameworks/base/services/devicepolicy/java/com/android/server/devicepolicy/SecurityLogMonitor.java
|
| a0ea967d111b9f8e01ebbb1ac8d393270e1788b6 |
|
19-Feb-2016 |
Michal Karpinski <mkarpinski@google.com> |
Removing lock contention in SecurityLogMonitor
After being interrupted the monitor thread tried to acquire
a lock that is held by interrupting thread, resulting in timeouting
on join().
Bug: 27061904
Change-Id: Ifbd578d5f5a266083b207fedd8ebb6d26ab08c31
/frameworks/base/services/devicepolicy/java/com/android/server/devicepolicy/SecurityLogMonitor.java
|
| c3cd05f8a45ab789aae1cb553df86f94667d595a |
|
11-Jan-2016 |
Rubin Xu <rubinxu@google.com> |
Add DevicePolicyManager APIs for process logging.
Add Device Owner APIs for controlling and retrieving the logs. Retrieving the
logs should be rate limited unless we are at the risk of losing logs due to
constrained buffer space.
Bug: 22860162
Change-Id: I80658f5a14e86d7cfd42402fbc5e98dc11698c0e
/frameworks/base/services/devicepolicy/java/com/android/server/devicepolicy/SecurityLogMonitor.java
|