997
edits
Changes
no edit summary
<span style="color: #0E9549; font-size: 24px;">'''About this constraint '''</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>
This constraint can be used to allow/prevent actions being run only when the device has been ADB hacked.
''' 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''
<br/>
<pre class="trigger-style">Triggers
<br/>
Screen On/Off - Screen On</pre>
<pre class="action-style">Actions
* ''DUMP''
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]]