Difference between revisions of "Constraint: ADB Hacked"

 
Line 32: Line 32:
 
''' See Also '''
 
''' See Also '''
  
* [[Constraint: Rooted Device|Rooted Device]]
+
* [[Constraint: Rooted Device|Rooted Device Constraint]]

Latest revision as of 10:34, 9 January 2026

This constraint allows or prevents a macro/feature from running based on whether the device has the ADB hack applied.

Options

  • ADB Hack Applied: Constraint passes only when the ADB hack is applied
  • Not ADB hacked: Constraint passes only when the ADB hack is not applied
  • ADB Permissions to Check: Choose one or more permissions to verify. All selected permissions must match the chosen state.
    • WRITE_SECURE_SETTINGS - Access to secure system settings
    • READ_LOGS - Read system log output
    • SET_VOLUME_KEY_LONG_PRESS_LISTENER - Detect volume key long-press events
    • CHANGE_CONFIGURATION - Change certain system configuration settings
    • DUMP - Access additional system debug information

Example

Example 1: Turn off data when screen is on if the ADB hack is applied

Triggers

Screen On/Off - Screen On
Actions

Set Wi-Fi State (Enable)
Mobile Data On/Off (Disable)
Constraints

ADB Hacked - ADB Hack Applied (WRITE_SECURE_SETTINGS)

Notes

  • Use this constraint to gate macros that should only run after the ADB hack setup is completed

See Also