Difference between revisions of "Constraint: ADB Hacked"

 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<span style="color: #0E9549; font-size: 24px;">'''About this restriction'''</span><br/>
+
<pre class="header-style">This constraint allows or prevents a macro/feature from running based on whether the device has the ADB hack applied.</pre>
<pre style="background-color: #ACC8E5; color: #112A46; border-radius: 10px; padding: 10px;">This constraint can be used to allow/prevent actions being run only when the device has been ADB hacked.
 
  
It is ideal for technically advanced users who require specific automations for devices that have been altered beyond the standard configurations.</pre>
+
''' Options '''
<span style="color: #0E9549; font-size: 24px;">'''ADB Hack Permissions'''</span><br/>
 
  
<pre style="background-color: #ACC8E5; color: #112A46; border-radius: 10px; padding: 10px;">
+
* '''ADB Hack Applied''': Constraint passes only when the ADB hack is applied
* WRITE_SECURE_SETTINGS
+
* '''Not ADB hacked''': Constraint passes only when the ADB hack is not applied
</pre>
+
* '''ADB Permissions to Check''': Choose one or more permissions to verify. All selected permissions must match the chosen state.
<pre style="background-color: #ACC8E5; color: #112A46; border-radius: 10px; padding: 10px;">
+
** '''WRITE_SECURE_SETTINGS''' - Access to secure system settings
* READ_LOGS
+
** '''READ_LOGS''' - Read system log output
</pre>
+
** '''SET_VOLUME_KEY_LONG_PRESS_LISTENER''' - Detect volume key long-press events
<pre style="background-color: #ACC8E5; color: #112A46; border-radius: 10px; padding: 10px;">
+
** '''CHANGE_CONFIGURATION''' - Change certain system configuration settings
* SET_VOLUME_KEY_LONG_PRESS_ LISTENER
+
** '''DUMP''' - Access additional system debug information
</pre>
+
 
<pre style="background-color: #ACC8E5; color: #112A46; border-radius: 10px; padding: 10px;">
+
''' Example '''
* CHANGE CONFIGURATION
+
 
</pre>
+
''Example 1: Turn off data when screen is on if the ADB hack is applied''
<pre style="background-color: #ACC8E5; color: #112A46; border-radius: 10px; padding: 10px;">
+
  <pre class="trigger-style">Triggers
* DUMP
+
 
</pre>
+
Screen On/Off - Screen On</pre>
 +
  <pre class="action-style">Actions
 +
 
 +
Set Wi-Fi State (Enable)
 +
Mobile Data On/Off (Disable)</pre>
 +
  <pre class="constraint-style">Constraints
 +
 
 +
ADB Hacked - ADB Hack Applied (WRITE_SECURE_SETTINGS)</pre>
 +
 
 +
''' Notes '''
 +
 
 +
* Use this constraint to gate macros that should only run after the ADB hack setup is completed
 +
 
 +
''' See Also '''
 +
 
 +
* [[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