d36dd15d9b
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