Lines Matching refs:boot

143     on boot
147     on boot && property:true=true
151     on boot
155 Then when the `boot` trigger occurs and assuming the property `true`
165 If the property `true` wasn't `true` when the `boot` was triggered, then the
173 If the property `true` becomes `true` *AFTER* `boot` was triggered, nothing will
174 be executed. The condition `boot && property:true=true` will be evaluated to
175 false because the `boot` trigger is a past event.
181     on boot
221   boot animation and shutdown animation. As these services can be
238   _fatal crash window mins_ minutes or before boot completes, the device
344   intended to be used with the `exec_start` builtin for any must-have checks during boot.
393   Android logging during early boot and whose logs messages we want to capture. This is only enabled
411   the boot sequence by APEXes. When a service with updatable option is started
450 take the form of a simple string such as 'boot' or 'late-init'.
456 evaluated and triggered accordingly during the initial boot phase of
463 `on boot && property:a=b` defines an action that is only executed when
464 the 'boot' event trigger happens and the property a equals b at the moment. This
465 will NOT be executed when the property a transitions to value b after the `boot`
471    1. During initial boot if property a=b and property c=d.
479 Init uses the following sequence of triggers during early boot. These are the
486    4. `late-init` - Triggered if `ro.bootmode != "charger"`, or via healthd triggering a boot
500    7. `early-boot` - After zygote has started.
501    8. `boot` - After `early-boot` actions have completed.
558     on property:ro.boot.myfancyhardware=1
648 >  * `Require`: encrypt directory, abort boot process if encryption fails
655 >  * `per_boot_ref`: use the key freshly generated on each boot.
664   If the fstab parameter is not specified, fstab.${ro.boot.fstab_suffix},
738   If the fstab parameter is not specified, fstab.${ro.boot.fstab_suffix},
757   If the fstab parameter is not specified, fstab.${ro.boot.fstab_suffix},
801       `ro.boot.init_rc` during initial boot.
891 Init records some boot timing information in system properties.
894 > Time after boot in ns (via the CLOCK\_BOOTTIME clock) at which the first
910 > Time after boot in ns (via the CLOCK\_BOOTTIME clock) that the service was
919 On the emulator, use the -bootchart _timeout_ option to boot with bootcharting
965 used for obtaining performance analysis reports during boot
971           wm am --boot
974 the boot sequence has finished, the trace report is obtained from the device
1051 The early init boot sequence is broken up into three stages: first stage init, SELinux setup, and
1061 require using a ramdisk to boot Android. The recovery ramdisk can be used to boot to Android instead
1076 as 2). Note that the decision to boot normally into Android instead of booting
1085 argument. At this point the main phase of init runs and continues the boot process via the init.rc