commit | 3a2bb594df4b48c6afb1f029041dd6db0735de58 | [log] [tgz] |
---|---|---|
author | Tao Bao <tbao@google.com> | Thu Feb 25 12:38:53 2016 -0800 |
committer | Tao Bao <tbao@google.com> | Wed Mar 02 23:23:32 2016 -0800 |
tree | 6459344ce70a011cbf3352b6ebc872e808a0a93d | |
parent | 9db7964834694e10ce0945e17ac7fefc066d8deb [diff] |
uncrypt: Communicate via /dev/socket/uncrypt. We used to rely on files (e.g. /cache/recovery/command and /cache/recovery/uncrypt_status) to communicate between uncrypt and its caller (i.e. system_server). Since A/B devices may not have /cache partitions anymore, we switch to socket communication instead. We will keep the use of /cache/recovery/uncrypt_file to indicate the OTA package to be uncrypt'd though. Because there is existing logic in ShutdownThread.java that depends on the existence of the file to detect pending uncrypt works. This part won't affect A/B devices without /cache partitions, because such devices won't need uncrypt service (i.e the real de-encrypt work) anyway. Bug: 27176738 Change-Id: I481406e09e3ffc7b80f2c9e39003b9fca028742e
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