Description
Currently, AppLock relies on detecting apps through the standard app drawer (using UsageStatsManager or package visibility). However, this fails to detect apps that are deliberately hidden from the launcher, most notably Magisk Manager when the "Hide the Magisk app" feature is enabled.
The Problem
When a user hides Magisk Manager, it changes its package name to a random string (e.g., com.android.chrome or something obscure) and removes itself from the launcher. It is then accessed via a secret dialer code (*#*#...#*#*) or a custom shortcut placed on the home screen.
Because the hidden app doesn't trigger standard app launch intents that AppLock monitors, it is impossible to put a PIN/Fingerprint lock on Magisk Manager. This leaves the root management interface completely exposed if someone accidentally taps the hidden shortcut.
Proposed Solutions
It would be great if AppLock could support locking hidden apps. This could be implemented in one of a few ways:
- Manual Package Name Entry: Allow power users to manually type the randomized package name (e.g.,
com.example.settings) into AppLock to force it to monitor that specific package, even if it's not in the standard app list.
- Shortcut Locking: Allow users to long-press a specific shortcut on the home screen and select "Lock with AppLock", intercepting the intent when that specific shortcut is tapped.
- Activity-level Locking: Instead of locking the whole app package, allow locking specific Activities (e.g., the main activity class that Magisk uses for its hidden UI).
Use Case
Security-conscious users who root their devices with Magisk and hide it to bypass banking app detections (like Outlook, banking apps, etc.) still want a basic layer of physical security so a friend or a finder doesn't accidentally disable root or access Superuser settings.
Thank you for your work on this app!
Description
Currently, AppLock relies on detecting apps through the standard app drawer (using
UsageStatsManageror package visibility). However, this fails to detect apps that are deliberately hidden from the launcher, most notably Magisk Manager when the "Hide the Magisk app" feature is enabled.The Problem
When a user hides Magisk Manager, it changes its package name to a random string (e.g.,
com.android.chromeor something obscure) and removes itself from the launcher. It is then accessed via a secret dialer code (*#*#...#*#*) or a custom shortcut placed on the home screen.Because the hidden app doesn't trigger standard app launch intents that AppLock monitors, it is impossible to put a PIN/Fingerprint lock on Magisk Manager. This leaves the root management interface completely exposed if someone accidentally taps the hidden shortcut.
Proposed Solutions
It would be great if AppLock could support locking hidden apps. This could be implemented in one of a few ways:
com.example.settings) into AppLock to force it to monitor that specific package, even if it's not in the standard app list.Use Case
Security-conscious users who root their devices with Magisk and hide it to bypass banking app detections (like Outlook, banking apps, etc.) still want a basic layer of physical security so a friend or a finder doesn't accidentally disable root or access Superuser settings.
Thank you for your work on this app!