commit | 9a6f5204190cda6bb6aecb59dff0293cc90ab0b7 | [log] [tgz] |
---|---|---|
author | katao <ustckato@gmail.com> | Mon Dec 19 11:22:30 2016 +0800 |
committer | tao ka <ustckato@gmail.com> | Mon Dec 19 08:51:07 2016 +0000 |
tree | 567c1e301e3e40486e427a0ce6bd9d02cd21f957 | |
parent | 26d972c9d2d75a2a96d63123f0313e5c9e70a73f [diff] |
Bugfix:updater always retry apply patch failed,when memcpy failed. https://code.google.com/p/android/issues/detail?id=230602 On the second attempt, open the file with O_RDONLY, which causing a write failure。 Change-Id: If89165b8c7619fe25722073a46b3cc7c61530a71 Signed-off-by: katao <ustckato@gmail.com>
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
recovery-refresh
and recovery-persist
executables exist only on systems without /cache partition. And we need to follow special steps to run tests for them.
Execute the test on an A/B device first. The test should fail but it will log some contents to pmsg.
Reboot the device immediately and run the test again. The test should save the contents of pmsg buffer into /data/misc/recovery/inject.txt. Test will pass if this file has expected contents.