diff options
| author | Tianjie Xu <xunchang@google.com> | 2019-10-30 10:37:32 -0700 |
|---|---|---|
| committer | Tianjie Xu <xunchang@google.com> | 2019-11-04 16:12:00 -0800 |
| commit | a933b43c02726c9ec412d3074833d941cd8c1ec2 (patch) | |
| tree | 503d513157261b933c9613273e46addd65d5bd16 /trusty/coverage/coverage_test.cpp | |
| parent | 8578a8a8ec3b28209ba0b9e2d1f1eda39c35f885 (diff) | |
Grant adb auth under recovery for unlocked & userdebug devices
During automatic tests, we sometimes want to reboot the device out of
the rescue party remotely. And per http://go/recovery-adb-access, we
need to grant the adb authorization to enable the adb access. The auth
are only granted for userdebug devices and those with an unlocked
bootloader. Since the user can always flash a custom recovery image if
the bootloader is unlocked.
This cl ignores the ro.adb.secure property under recovery. The other
option is to default this property to 0 when building the boot/recovery
image.
Bug: 141247819
Test: unlock bootloader, run adb under recovery in user build
Change-Id: I424cfed5bf51a1e31d8687256ae4c6eaaa5e6249
Diffstat (limited to 'trusty/coverage/coverage_test.cpp')
0 files changed, 0 insertions, 0 deletions