Searched refs:triggers (Results 1 – 13 of 13) sorted by relevance
| /system/core/init/ |
| D | action_parser.cpp | 135 std::vector<std::string> triggers(args.begin() + 1, args.end()); in ParseSection() local
136 if (triggers.size() < 1) { in ParseSection()
149 ParseTriggers(triggers, action_subcontext, &event_trigger, &property_triggers); in ParseSection()
|
| D | action.cpp | 225 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()
|
| D | README.md | 379 Triggers are subdivided into event triggers and property triggers.
381 Event triggers are strings triggered by the 'trigger' command or by
385 Property triggers are strings triggered when a named property changes
388 'property:<name>=\*' respectively. Property triggers are additionally
392 An Action can have multiple property triggers but may only have one
|
| /system/sepolicy/private/ |
| D | migrate_legacy_obb_data.te | 22 # any open file descriptors to this domain, so anything that triggers this
|
| /system/sepolicy/prebuilts/api/29.0/private/ |
| D | migrate_legacy_obb_data.te | 22 # any open file descriptors to this domain, so anything that triggers this
|
| /system/sepolicy/prebuilts/api/30.0/private/ |
| D | migrate_legacy_obb_data.te | 22 # any open file descriptors to this domain, so anything that triggers this
|
| /system/sepolicy/prebuilts/api/31.0/private/ |
| D | migrate_legacy_obb_data.te | 22 # any open file descriptors to this domain, so anything that triggers this
|
| /system/apex/tests/testdata/ |
| D | trigger_watchdog.rc | 26 # Simulate a situation when userspace reboot fails to remount userdata. Since triggers in
|
| /system/core/bootstat/ |
| D | bootstat.rc | 61 # triggers (e.g. due to userspace reboot) won't retrigger
|
| /system/core/rootdir/ |
| D | init.usb.rc | 14 # adbd is controlled via property triggers in init.<platform>.usb.rc
|
| /system/apex/docs/ |
| D | howto.md | 324 The `adb install --staged` command triggers a verification for the staged APEX
404 cannot have action triggers in APEXes.
|
| D | README.md | 480 triggers aren't supported in APEXs.
|
| /system/bt/doc/ |
| D | power_management.md | 148 triggers `bta_dm_pm_btm_status`, with the timeout field set to TRUE. HCI
|