APK versions
APK files are served by the original repository.
Release notes
Turning Developer Options on now switches USB debugging and wireless debugging off first, so it no longer brings back a debugging session you left enabled. Note that this ends any active adb connection. Long-pressing the Quick Settings tile now opens Loophole instead of the system App Info screen. Adding the tile now tells you whether it was added or is already there. The app, tile and widget now follow Developer Options live.
SHA-256 checksum
3e879776ea92632a88b89a064e48c4a45cdd03599d3ffe189076c255a0c31e3fRelease notes
Fixed permission disclosure in app description (network-related permissions come from the Glance widget framework, not app network activity). Enabled reproducible builds. Enabled code and resource shrinking, reducing APK size.
SHA-256 checksum
24cc7707414fc5e4f00c8cb295a665466dd12eab4f973f241baf05311cac0d22Screenshots
About this app
Loophole is a one-tap Quick Settings toggle for Android Developer Options. If you're an Android developer, Developer Options is basically always on. But a lot of banking and fintech apps treat that as a red flag and refuse to open, or silently degrade, while it's enabled -- even though you're not doing anything shady, you're just building. The normal fix is: open Settings, find Developer Options, toggle it off, open your banking app, then remember to turn it back on later. Loophole turns that into one tap from the notification shade. Features: * Reads and toggles Developer Options directly via a Quick Settings tile * Optional home screen widget as an alternative to the tile * Simple in-app switch as a fallback / status view * No ads, no analytics, no tracking Setup note: toggling Developer Options programmatically requires the WRITE_SECURE_SETTINGS permission, which Android only allows to be granted manually once via adb (it cannot be requested through a normal runtime permission dialog): adb shell pm grant android.permission.WRITE_SECURE_SETTINGS Full setup instructions are in the project README. A note on permissions: the app does not make network requests and holds no INTERNET permission. However, the manifest does include ACCESS_NETWORK_STATE, WAKE_LOCK, RECEIVE_BOOT_COMPLETED, and FOREGROUND_SERVICE. These come from Jetpack Glance, the framework used to build the home screen widget, which relies on WorkManager internally to schedule widget updates and survive process death. They are a byproduct of the widget framework itself, not of any network or background activity Loophole performs.








