Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit b5254635 authored by Mike McTernan's avatar Mike McTernan
Browse files

init: set a new trigger when a vold checkpoint is committed 

Add post-fs-data-checkpointed trigger when vold completes checkpointing
after an OTA update.

Bug: 350362101
Test: ABTD
Change-Id: I647a73a942174015b46c5f40bd8f8d3347977ecd
parent 9c77e66d

init/README.md

+5 −3
Original line number Diff line number Diff line
@@ -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

--------

rootdir/init.rc

+3 −0
Original line number Diff line number Diff line
@@ -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