Added Lockdown feature and Lock phone using QS Tile Fixes #631 - #651
Open
thekrdev wants to merge 7 commits into
Open
Added Lockdown feature and Lock phone using QS Tile Fixes #631#651thekrdev wants to merge 7 commits into
thekrdev wants to merge 7 commits into
Conversation
## Summary Adds two new automation trigger types: **Bluetooth device connected/disconnected** and **Wi-Fi network connected/disconnected**. Users can now build automations that fire an action when the phone connects to (or disconnects from) a specific paired Bluetooth device or a specific Wi-Fi network — the same way existing triggers like Charger Connected or Schedule work today. ## What's new - **`Trigger.kt`**: 4 new sealed subtypes — `BluetoothConnected`/`BluetoothDisconnected` (device address + name) and `WifiConnected`/`WifiDisconnected` (SSID), all configurable via a settings sheet like `Trigger.Schedule`. - **`BluetoothModule`** (new): dynamic `BroadcastReceiver` on `ACTION_ACL_CONNECTED`/`ACTION_ACL_DISCONNECTED`, filtered by MAC address. - **`WifiModule`** (new): `ConnectivityManager.NetworkCallback` on the Wi-Fi transport, resolving the active SSID via `WifiManager` and firing on connect/lost. - **`AutomationManager`**: wires both modules into the existing module lifecycle (same pattern as Power/Display/Time modules). - **Editor UI**: two new trigger entries in `AutomationEditorActivity`, each configurable through a bottom sheet: - `BluetoothDeviceSelectionSheet` — pick from the phone's paired devices (requests `BLUETOOTH_CONNECT` on Android 12+). - `WifiNetworkSelectionSheet` — if the app has **Shizuku** (or root) authorized, it runs `cmd wifi list-networks` under shell privileges and lets the user pick straight from the device's saved networks; otherwise it falls back to manual SSID entry with a "Use Current Network" helper (requests `ACCESS_FINE_LOCATION`, needed by Android to read the current SSID). - **Manifest**: added `ACCESS_WIFI_STATE` (the Bluetooth/location permissions needed were already present). ## Why Requested enhancement to make automations react to connectivity context (e.g. "turn on Wi-Fi calling when connected to home network", "mute when a specific headset disconnects") without needing a schedule or manual toggle. ## Test plan - [ ] Create a Trigger automation on "Bluetooth Device Connected"/"Disconnected" for a paired device and verify the linked action fires on connect/disconnect. - [ ] Create a Trigger automation on "Wi-Fi Network Connected"/"Disconnected". - [ ] Verify triggers still fire correctly after the app/service is killed and restarted (foreground service reattachment).
…iver registration context in BluetoothModule
…selection sheets to use RoundedCardContainer
sameerasw
requested changes
Aug 2, 2026
sameerasw
left a comment
sameerasw
left a comment
Owner
There was a problem hiding this comment.
Hi! Can you take a look at these concerns?
Potential Issues & Recommendations
1. Code Duplication with Existing Screen Locking Logic
- Issue: Screen locking logic (
input keyevent KEYCODE_POWERandScreenOffAccessibilityService.performGlobalAction) is duplicated inLockdownTileService.kt,ScreenOffWidgetProvider.kt, andAodForceTurnOffHandler.kt. - Recommendation: Refactor into a unified
DeviceLockUtilshelper soScreenOffWidgetProvider,LockdownTileService, andAodForceTurnOffHandlershare the exact same locking and permission checks without code duplication.
2. Lockdown Mode Does Not Turn Off Screen Immediately
- Issue:
cmd lock_settings require-strong-authsets the strong auth flag for the next lock event, but does not turn off or lock the screen by itself on many OEM builds. - Recommendation: Follow up the
require-strong-authcommand withinput keyevent KEYCODE_POWER(or AccessibilityGLOBAL_ACTION_LOCK_SCREEN) so tapping the tile turns off the display and locks the device instantly.
3. Hardcoded --user 0 Flag
- Issue: Hardcoding
--user 0incmd lock_settings require-strong-auth ... --user 0only targets the primary owner profile. - Recommendation: Resolve user ID dynamically via
android.os.Process.myUserHandle().hashCode()so it works correctly in Work Profiles and Secondary Users / Private Spaces (Android 15+).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
If you don't want lockdown, you can continue with accessibility permission, by just adding the qs tile.
Close #631