Adding sanity check for VBMeta device state
This test should will flag builds running as eng or userdebug that report back the device is locked during development. This will also catch the case where the device is a user build but reporting that it isn't locked. This should help to avoid instances in the future where userdebug builds report a locked device in the VBMeta information. This patch also does a little bit of cleanup of the surrounding VBMeta checking code. Test: atest VtsHalKeymasterV4_0TargetTest Change-Id: I3b387ade5eeee6a68b9ff307e503417d264ecbfe
Loading
Please register or sign in to comment