c2bcd967ebff0fb3a027d75a3b941b62db631456
Do not use USES_POLICY_PROFILE_OWNER / USES_POLICY_DEVICE_OWNER. Instead, use explicit methods for checking if the caller is the Device Owner or Profile Owner. USES_POLICY_PROFILE_OWNER is confusing since internally in the DevicePolicyManagerService, it implied a Device Owner is also a Profile Owner, which is not always what the caller expected. This is the first phase of the refactoring, removing external calles' dependency on these constants. The next phase will remove them internally completely in favour of an implementation that accesses mOwners directly. There are no functional changes in this CL. Bug: 163028934 Test: atest FrameworksServicesTests:DevicePolicyManagerTest Change-Id: I57c8465d190a3b4b130d57fd622cc93eaeb9c717
Description
android_packages_modules_Connectivity
Languages
Java
81.4%
Kotlin
7.7%
AIDL
4.5%
C++
4.5%
C
1.7%
Other
0.1%