Home
last modified time | relevance | path

Searched refs:triggers (Results 1 – 14 of 14) sorted by relevance

/system/core/init/
Daction_parser.cpp135 std::vector<std::string> triggers(args.begin() + 1, args.end()); in ParseSection() local
136 if (triggers.size() < 1) { in ParseSection()
157 ParseTriggers(triggers, action_subcontext, &event_trigger, &property_triggers); in ParseSection()
Daction.cpp225 std::vector<std::string> triggers; in BuildTriggersString() local
228 triggers.emplace_back(trigger_name + '=' + trigger_value); in BuildTriggersString()
231 triggers.emplace_back(event_trigger_); in BuildTriggersString()
234 return Join(triggers, " && "); in BuildTriggersString()
DREADME.md185 When `ro.property_service.async_persist_writes` is `true`, triggers for these
449 Triggers are subdivided into event triggers and property triggers.
451 Event triggers are strings triggered by the 'trigger' command or by
455 Property triggers are strings triggered when a named property changes
458 'property:<name>=\*' respectively. Property triggers are additionally
462 An Action can have multiple property triggers but may only have one
482 Init uses the following sequence of triggers during early boot. These are the
483 built-in triggers defined in init.cpp.
492 Remaining triggers are configured in `init.rc` and are not built-in. The default sequence for
/system/sepolicy/private/
Dmigrate_legacy_obb_data.te22 # any open file descriptors to this domain, so anything that triggers this
Dvirtualizationmanager.te112 # For debug purposes we try to get the canonical path from /proc/self/fd/N. That triggers
Dvendor_init.te18 # Let vendor_init read ro.fstype.data to process init.rc triggers
/system/chre/apps/test/common/proto/
Dchre_audio_concurrency_test.proto41 // Also verifies that a gap between CHRE audio data events triggers the
/system/memory/lmkd/
Dlmkd.rc21 # setting persist.device_config.* property either triggers immediate lmkd re-initialization
/system/apex/tests/testdata/
Dtrigger_watchdog.rc26 # Simulate a situation when userspace reboot fails to remount userdata. Since triggers in
/system/core/bootstat/
Dbootstat.rc51 # triggers (e.g. due to userspace reboot) won't retrigger
/system/extras/profcollectd/
DREADME.md29 Profcollect collects profiles periodically, as well as through triggers like app launch events. Only
/system/core/rootdir/
Dinit.usb.rc14 # adbd is controlled via property triggers in init.<platform>.usb.rc
/system/apex/docs/
Dhowto.md330 The `adb install --staged` command triggers a verification for the staged APEX
410 cannot have action triggers in APEXes.
DREADME.md480 triggers aren't supported in APEXs.