{"package_name":"com.shubhang.loophole","name":"Loophole","summary":"One-tap Quick Settings toggle for Android Developer Options.","category":"System","icon_url":"/api/icon/com.shubhang.loophole","latest_version_code":4,"latest_version_name":"1.1.0","apk_url":"/api/apk/com.shubhang.loophole","apk_size":2207386,"apk_sha256":"3e879776ea92632a88b89a064e48c4a45cdd03599d3ffe189076c255a0c31e3f","source_kind":"fdroid-repo","repo_slug":"fdroid-main","last_updated":1787367639,"release_timestamp":1787313768,"description":"Loophole is a one-tap Quick Settings toggle for Android Developer Options.\n\nIf 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.\n\nThe 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.\n\nFeatures:\n* Reads and toggles Developer Options directly via a Quick Settings tile\n* Optional home screen widget as an alternative to the tile\n* Simple in-app switch as a fallback / status view\n* No ads, no analytics, no tracking\n\nSetup 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):\n\nadb shell pm grant <applicationId> android.permission.WRITE_SECURE_SETTINGS\n\nFull setup instructions are in the project README.\n\nA 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.","categories":["System"]}