7c59fc4fb4
- Cherry pick of aosp/1228482 As of aosp/1224611, there is a new step in the preparation of APEXes where init calls back into apexd after DE user data is unencrypted to allow DE apex data to be snapshotted or restored. aosp/1228581 introduces a new apexd.status value of "activated" that is set once APEXes are activated but before this snapshot has occurred. init may execute "perform_apex_config" once this has occurred, so this CL changes init to wait for "activated" rather than "ready" before doing this. Bug: 148672144 Test: build & flash, check boot completes and check in logs that init waits on the correct status value. Merged-In: I339580bf593d3b09a5dff749ac2a5d1952bcb210 Change-Id: I71b62c9dd2f7951811606002f38612784d3d9086 |
||
---|---|---|
.. | ||
avb | ||
etc | ||
adb_debug.prop | ||
Android.bp | ||
Android.mk | ||
asan.options | ||
asan_extract.rc | ||
asan_extract.sh | ||
init-debug.rc | ||
init.environ.rc.in | ||
init.rc | ||
init.usb.configfs.rc | ||
init.usb.rc | ||
init.zygote32.rc | ||
init.zygote32_64.rc | ||
init.zygote64.rc | ||
init.zygote64_32.rc | ||
OWNERS | ||
ueventd.rc |