platform_bootable_recovery/uncrypt/uncrypt.rc

service uncrypt /system/bin/uncrypt
    class main
    socket uncrypt stream 600 system system
    disabled
    oneshot

service setup-bcb /system/bin/uncrypt --setup-bcb
    class main
    socket uncrypt stream 600 system system
    disabled
    oneshot

service clear-bcb /system/bin/uncrypt --clear-bcb
    class main
    socket uncrypt stream 600 system system
    disabled
    oneshot
move uncrypt from init.rc to uncrypt.rc Move uncrypt from /init.rc to /system/etc/init/uncrypt.rc using the LOCAL_INIT_RC mechanism Bug 23186545 Change-Id: Ib8cb6dffd2212f524298279787fd557bc84aa7b9 2015-09-04 01:32:39 +02:00			`service uncrypt /system/bin/uncrypt`
			`class main`
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 2016-02-25 21:38:53 +01:00			`socket uncrypt stream 600 system system`
move uncrypt from init.rc to uncrypt.rc Move uncrypt from /init.rc to /system/etc/init/uncrypt.rc using the LOCAL_INIT_RC mechanism Bug 23186545 Change-Id: Ib8cb6dffd2212f524298279787fd557bc84aa7b9 2015-09-04 01:32:39 +02:00			`disabled`
			`oneshot`

uncrypt: add options to setup bcb and clear bcb. Bug: 26696173 Change-Id: I3a612f045aaa9e93e61ae45b05300d02b19bb3ad 2016-01-27 01:50:15 +01:00			`service setup-bcb /system/bin/uncrypt --setup-bcb`
			`class main`
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 2016-02-25 21:38:53 +01:00			`socket uncrypt stream 600 system system`
uncrypt: add options to setup bcb and clear bcb. Bug: 26696173 Change-Id: I3a612f045aaa9e93e61ae45b05300d02b19bb3ad 2016-01-27 01:50:15 +01:00			`disabled`
			`oneshot`

			`service clear-bcb /system/bin/uncrypt --clear-bcb`
			`class main`
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 2016-02-25 21:38:53 +01:00			`socket uncrypt stream 600 system system`
uncrypt: add options to setup bcb and clear bcb. Bug: 26696173 Change-Id: I3a612f045aaa9e93e61ae45b05300d02b19bb3ad 2016-01-27 01:50:15 +01:00			`disabled`
uncrypt: Retire pre-recovery service. The framework CL in [1] removes the use of "pre-recovery" service which is basically to trigger a reboot into the recovery. [1] commit e8a403d57c8ea540f8287cdaee8b90f0cf9626a3 Bug: 26830925 Change-Id: I131f31a228df59e4f9c3024b238bbdee0be2b157 2016-02-23 02:33:14 +01:00			`oneshot`