summaryrefslogtreecommitdiff
path: root/identity/support/src/cppbor_parse.cpp
diff options
context:
space:
mode:
authorBowgo Tsai <bowgotsai@google.com>2020-05-29 15:23:14 +0800
committerBowgo Tsai <bowgotsai@google.com>2020-06-01 13:20:52 +0800
commit307d2bba7df1b94540e64d5afd4e5e3736c8574b (patch)
tree41113a524b611a739a4ba01d0f63835e0c240f70 /identity/support/src/cppbor_parse.cpp
parentb035b6a80f90eb4a6cfc32d24687b833bf5e176f (diff)
Allow unlocked in VTS
VTS was running on a userdebug build GSI before Android 10. Starting from Android 10, VTS is switched to running on top of a user build GSI image, plus the device-specific boot-debug.img to allow adb root. https://source.android.com/compatibility/vts/vts-on-gsi So 'ro.build.type' will be 'user' because the value comes from /system/build.prop. Switching to using 'ro.debuggable' to decide whether we should check the device is locked or not. Note that 'ro.debuggable' will be '1' for userdebug/eng images or when a boot-debug.img is used. Bug: 154449286 Test: atest VtsHalKeymasterV4_0TargetTest Change-Id: If5a90d62f77489aa58f96e908553a052cf6d1e18 Merged-In: If5a90d62f77489aa58f96e908553a052cf6d1e18 (cherry picked from commit 43dd6e34bd2868cb9fae8e23e717e346d08caeea)
Diffstat (limited to 'identity/support/src/cppbor_parse.cpp')
0 files changed, 0 insertions, 0 deletions