3b8b46f3a46ccf35a6bb6a828af0f2d011cc9abe
The new service separates OEM lock management from the implementation. Currently, a user restriction (DISALLOW_OEM_UNLOCK) and the persistent data block have been used to implement OEM lock management. In future, other implemention will be used e.g. a secure element. The new API also allows for a signature to be passed when changing whether the device is allowed to be OEM unlocked by the carrier which can be used for cryptographic protection of the flag. Bug: 34766843 Test: gts-tradefed run gts -m GtsOemLockServiceTestCases -t com.google.android.oemlock.gts.OemLockServiceTest Test: cts-tradefed run cts -m CtsPermission2TestCases -t android.permission2.cts.PrivappPermissionsTest Change-Id: I01660d7605d297f273d43436ca03d64ff611b6cf
…
Description
No description provided
Languages
Java
73.7%
Kotlin
14%
PowerBuilder
5.8%
C++
5.2%
AIDL
1%