ACPR/android_system_core
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Merge "init: set a new trigger when a vold checkpoint is committed" into main

Browse source
This commit is contained in:
Treehugger Robot 2024-07-22 09:12:29 +00:00 • committed by Gerrit Code Review
commit d909570786
2 changed files with 8 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
init/README.md
View file

@ -499,9 +499,11 @@ have been omitted.
4. `late-fs` - Mount partitions marked as latemounted.
5. `post-fs-data` - Mount and configure `/data`; set up encryption. `/metadata` is
reformatted here if it couldn't mount in first-stage init.
6. `zygote-start` - Start the zygote.
7. `early-boot` - After zygote has started.
8. `boot` - After `early-boot` actions have completed.
6. `post-fs-data-checkpointed` - Triggered when vold has completed committing a checkpoint
after an OTA update. Not triggered if checkpointing is not needed or supported.
7. `zygote-start` - Start the zygote.
8. `early-boot` - After zygote has started.
9. `boot` - After `early-boot` actions have completed.
Commands
--------

3
rootdir/init.rc
View file

@ -1087,6 +1087,9 @@ on post-fs-data
# Update dm-verity state and set partition.*.verified properties.
verity_update_state
on property:vold.checkpoint_committed=1
trigger post-fs-data-checkpointed
# It is recommended to put unnecessary data/ initialization from post-fs-data
# to start-zygote in device's init.rc to unblock zygote start.
on zygote-start