commit | 162558382b768a4120b3e41090a4c7b53f11469a | [log] [tgz] |
---|---|---|
author | Tianjie Xu <xunchang@google.com> | Sat Apr 30 11:49:59 2016 -0700 |
committer | Tianjie Xu <xunchang@google.com> | Fri May 20 13:56:53 2016 -0700 |
tree | 7e0d268233fc6bea07a361cf6913fc3a5e524063 | |
parent | dd874b1c87eb04f28db0db2629df0adde568a74c [diff] |
Allow recovery to return error codes Write error code, cause code, and retry count into last_install. So we can have more information about the reason of a failed OTA. Example of new last_install: @/cache/recovery/block.map package name 0 install result retry: 1 retry count (new) error: 30 error code (new) cause: 12 error cause (new) Details in: go/android-ota-errorcode Bug: 28471955 Change-Id: I00e7153c821e7355c1be81a86c7f228108f3dc37
mm -j && m ramdisk-nodeps && m recoveryimage-nodeps # To boot into the new recovery image # without flashing the recovery partition: adb reboot bootloader fastboot boot $ANDROID_PRODUCT_OUT/recovery.img
# After setting up environment and lunch. mmma -j bootable/recovery # Running the tests on device. adb root adb sync data # 32-bit device adb shell /data/nativetest/recovery_unit_test/recovery_unit_test adb shell /data/nativetest/recovery_component_test/recovery_component_test # Or 64-bit device adb shell /data/nativetest64/recovery_unit_test/recovery_unit_test adb shell /data/nativetest64/recovery_component_test/recovery_component_test