Home
last modified time | relevance | path

Searched refs:post (Results 1 – 25 of 32) sorted by relevance

12

/system/core/fs_mgr/libsnapshot/
DPowerTest.md8 Start by creating two large files that will be used as the pre-merge and post-merge state. You can …
11 dd if=/dev/urandom of=post-merge count=1024 bs=1048576
16 adb push post-merge /data/local/unencrypted
23 /data/local/unencrypted/post-merge
34 run_power_test.sh /data/local/unencrypted/post-merge
36 … final check command to validate the contents of the snapshot against the post-merge file. It will…
/system/sepolicy/prebuilts/api/29.0/private/
Dapex_test_prepostinstall.te1 # APEX pre- & post-install test.
3 # Allow to run pre- and post-install hooks for APEX test modules
Dapexd.te83 # Apex pre- & post-install permission.
/system/sepolicy/prebuilts/api/30.0/private/
Dapex_test_prepostinstall.te1 # APEX pre- & post-install test.
3 # Allow to run pre- and post-install hooks for APEX test modules
/system/sepolicy/private/
Dapex_test_prepostinstall.te1 # APEX pre- & post-install test.
3 # Allow to run pre- and post-install hooks for APEX test modules
/system/gsid/
Dgsid.rc8 on post-fs
14 on post-fs-data
/system/apex/tests/
DTEST_MAPPING29 // The following changes are in post-submit to restrict to physical
40 // The following changes are in post-submit to restrict to physical
/system/core/fs_mgr/
Dclean_scratch_files.rc1 on post-fs-data && property:ro.debuggable=1
/system/core/bootstat/
Dbootstat.rc5 # before post-fs trigger
6 on post-fs && property:ro.boot.bootreason=*
9 on post-fs-data
47 # post-fs-data: /data is writable
50 on post-fs-data && property:init.svc.bootanim=running && property:ro.crypto.type=block
/system/core/rootdir/
Dasan_extract.rc2 on post-fs-data
Dinit.rc437 trigger post-fs
448 trigger post-fs-data
469 on post-fs
537 # This does not work correctly if it is called in post-fs.
544 on post-fs-data
792 # If there is no post-fs-data action in the init.<device>.rc file, you
826 # It is recommended to put unnecessary data/ initialization from post-fs-data
979 trigger post-fs-data
1107 trigger post-fs-data
/system/update_engine/init/
Dupdate-engine.conf39 post-start script
/system/nvram/hal/
Dfake-nvram.rc1 on post-fs-data
/system/extras/boottime_tools/bootio/
Dbootio.rc9 on post-fs-data
/system/core/debuggerd/tombstoned/
Dtombstoned.rc10 on post-fs-data
/system/core/logd/
Dlogtagd.rc4 on post-fs-data
/system/extras/profcollectd/
Dprofcollectd.rc7 on post-fs-data
/system/core/trusty/utils/rpmb_dev/
Drpmb_dev.rc2 on post-fs-data
/system/iorap/
Diorapd.rc27 on post-fs-data
/system/tools/hidl/c2hal/test/
Dtest.h215 int (*post)(struct framebuffer_device_t* dev, buffer_handle_t buffer); member
/system/core/logcat/
Dlogcatd.rc5 # post-fs-data state because otherwise behavior is undefined. The exceptions
/system/bpf/bpfloader/
Dbpfloader.rc2 # However, on some hardware it's started from post-fs-data as well, which is just
/system/core/cli-test/
DREADME.md55 setup/teardown but also for testing post conditions (as in the example above).
/system/update_engine/
Dupdate_metadata.proto234 // Whether this partition carries a filesystem with post-install program that
239 // The path of the executable program to run during the post-install step,
246 // filesystem to run the post-install program. If not set, a fixed list of
/system/update_engine/update_engine/
Dupdate_metadata.proto234 // Whether this partition carries a filesystem with post-install program that
239 // The path of the executable program to run during the post-install step,
246 // filesystem to run the post-install program. If not set, a fixed list of

12