android_device_samsung_msm8.../recovery/root/init.recovery.qcom.rc

on fs
    wait /dev/block/platform/msm_sdcc.1
    symlink /dev/block/platform/msm_sdcc.1 /dev/block/bootdevice

    setprop sys.usb.ffs.aio_compat 1
    setprop persist.adb.nonblocking_ffs 0
    setprop ro.adb.nonblocking_ffs 0
msm8974-common: Set sys.usb.ffs.aio_compat in recovery as well Change-Id: I36d76f74ceae3029f49c3cb564cd876bbb6b5b81 2019-07-28 00:56:25 +02:00			`on fs`
msm8974-common: Symlink bootdevice for Lineage Recovery * It is needed by OpenGApps install script. Change-Id: Idb90a6ecaae541e74a9878c1ca93459cc2fdd949 2020-06-25 04:15:33 +02:00			`wait /dev/block/platform/msm_sdcc.1`
			`symlink /dev/block/platform/msm_sdcc.1 /dev/block/bootdevice`

msm8974-common: Set sys.usb.ffs.aio_compat in recovery as well Change-Id: I36d76f74ceae3029f49c3cb564cd876bbb6b5b81 2019-07-28 00:56:25 +02:00			`setprop sys.usb.ffs.aio_compat 1`
msm8974-common: Disable nonblocking_ffs to avoid recent crashes with adbd Recent changes to adbd have enabled nonblocking_ffs by default. These have seeminly uncovered some bad memory corruption in the kernel ffs gadget driver on every kernel I've tried so far. Unfortunately I've not been able to diagnose what is going wrong, so for now, lets disable the nonblocking_ffs. We still need to root cause the issue as its a problem even with the mainline kernel on HiKey, so its likely a generic kernel issue. Change-Id: I7a0797cc9e8e5f263e533beea23642f768c0f017 Signed-off-by: John Stultz <john.stultz@linaro.org> 2019-03-19 05:47:18 +01:00			`setprop persist.adb.nonblocking_ffs 0`
			`setprop ro.adb.nonblocking_ffs 0`