diff options
| author | Esteban Talavera <etalavera@google.com> | 2016-12-15 08:51:45 +0000 |
|---|---|---|
| committer | Esteban Talavera <etalavera@google.com> | 2017-01-16 11:13:01 +0000 |
| commit | d36dd15d9bf9f65270b9bee16d6419b96b18bd86 (patch) | |
| tree | 63508b7881a6d98ddb68686da2d9854436f6c762 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | b9dd3d6a4d0dc429787ed2d1c846d1174a8e633f (diff) | |
Make device wide DO features available if all users affiliated
Currently, those features are available on single user devices only
(since they collect privacy sensitive data device wide). Now making
them available as long as all users are affiliated.
It'll take a certain amount of time between user creation and the DPC
of that new user setting the appropriate affiliation ids. The DO won't
be able to access the logs during that time (and won't get any "logs
ready" callback). Once the affiliation ids are set, if they match,
logs become available again - this includes logs collected while the
user was being setup. Some logs might be lost though if the amount of
data exceeds the internal limit.
Test: runtest -c com.android.server.devicepolicy.DevicePolicyManagerTest frameworks-services
Test: cts-tradefed run cts -a armeabi-v7a --module CtsDevicePolicyManagerTestCases --test com.android.cts.devicepolicy.DeviceOwnerTest
Bug: 32326223
Change-Id: Idfe881dd6497d3ad2bead10addfd37b98b8a6e2b
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions