Wireless ADB Switch: a Quick Settings tile for Android's Wireless Debugging toggle

The toggle Android hides three menus deep

Wireless Debugging on Android is not a normal switch. It lives inside Developer Options, it has to be enabled once per device, and once enabled it exposes a pairing flow with a port and a code that changes between sessions. For anyone who connects a phone to a workstation over Wi-Fi rather than USB, the path to that screen is the friction. WADBS exists to remove it: the README describes the app as one that "allows you to switch Android's Wireless Debugging feature on and off quickly," and the delivery mechanism is a quick settings tile plus home screen widgets. That is the whole product thesis. It is aimed at Android developers and power users who already know what Wireless Debugging is and have decided they want it, and who want the on and off action to cost one gesture instead of a navigation sequence. If you connect over USB, or you leave Wireless Debugging on permanently, the app has nothing to offer you.

Root or Shizuku, not the public SDK

The README credits two dependencies that explain the mechanism: libsu, described as "a library that makes performing root-requiring operations easier," and Shizuku, "a framework WADBS can use as an alternative to root access." The v1.1 release is titled "Rootless Shizuku and more!", which is the point at which Shizuku support appears to have landed. So the app does not toggle Wireless Debugging through a documented public Android API. It performs a privileged operation, either as root through libsu or through the Shizuku service, which runs with elevated permissions granted over ADB. The widgets and the quick settings tile are the front end; the actual state change happens in a privileged context. That design decision is what makes the app possible at all, and it is also what constrains who can use it. An unrooted device with no Shizuku installed has no path to the toggle through this app, and the README does not describe a fallback.

Widgets, a tile, and a clipboard shortcut

The feature list in the README is presented as images rather than prose: a quick settings tile, home screen widgets, widget customization, an instant connection flow, Shizuku support, and OneUI integration. The instant connection item is the one concrete workflow described in text. The README states you can "instantly connect to your PC using KDE Connect's clipboard sharing feature" and points at a scripts directory in the repository. Read that as a companion script rather than an in-app feature: the app toggles the radio, and a separate script pushes whatever connection detail (an address or port, most likely) to your desktop through KDE Connect's clipboard sync. The repository layout supports this, since scripts is a top-level directory alongside media. The customization and OneUI entries are listed without explanation, so how much control the widgets expose, and what the OneUI integration actually changes on Samsung devices, cannot be determined from the supplied material.

Installing from F-Droid or GitHub, and what the README does not say

Distribution is two-channel. The README links a GitHub releases page and an F-Droid listing at f-droid.org/packages/com.smoothie.wirelessDebuggingSwitch. Note the package identifier: com.smoothie.wirelessDebuggingSwitch, which does not match the repository owner name Smooth-E. That is worth checking before you install from a third-party mirror, because the package name is the only identifier the README gives you for the F-Droid build. Beyond that, the README provides no setup instructions. There is no section explaining how to grant Shizuku permission, no configuration keys, no documented widget options, and no explanation of what the scripts directory expects as input. The repository has a translate.md file and translated READMEs in Russian, Brazilian Portuguese, and Simplified Chinese, which tells you the project has a translation workflow, but it tells you nothing about runtime configuration. Anyone evaluating this app has to read the source or the release notes to learn how the Shizuku handshake works.

The failure mode is a permission that is not there

Because the toggle depends on root or Shizuku, the most likely failure is not a crash but a dead control. If Shizuku is not running, or the app has not been granted access through it, the widget and tile have no privileged context to act in. The README does not document what the app shows in that state, so whether you get an error message, a silent no-op, or a prompt to start Shizuku is unknown from the supplied material. There is a second, quieter problem: Wireless Debugging state is tied to the device, not to the app, and Android itself can revoke or reset it. Nothing in the README describes how the widgets detect the real current state rather than a cached one. A toggle that shows "on" while the system has it off is worse than no toggle at all, because you will trust it. Verify the state display on your own device before relying on it.

Where it sits next to plain adb and Shizuku's own tooling

The obvious alternative is not another app. It is adb itself: run adb tcpip 5555 from a workstation and pair once, or keep a terminal app on the phone and issue the commands directly. That approach requires no privileged helper, no GPL-3.0 app, and no widget, but it requires a terminal or a cable every time you want to change state, which is exactly the friction WADBS removes. The second alternative is Shizuku's own ecosystem. Shizuku is a general framework for granting apps elevated permissions, and WADBS is one consumer of it. If you already run Shizuku for other tools, WADBS adds a narrow convenience layer on top. If you do not, installing Shizuku solely to get a Wireless Debugging tile is a large dependency for a small gain, and you should weigh that before adopting. The difference in approach is real: adb gives you the raw command and full control with no app installed, WADBS gives you one gesture and takes a privileged dependency in exchange.

Maintenance, licence, and what the release cadence implies

The repository is not archived, and the last push is dated 2026-05-26. The most recent release listed is v1.3 from 2024-09-19, described as "New translations and new design!" The gap between the last release and the last push suggests ongoing work that has not been cut into a release, though the supplied material does not say what that work is. Treat the release page, not the commit activity, as the thing you are installing. Upgrading means reinstalling from GitHub or waiting for F-Droid to pick up the build, and the README does not describe a migration path or a settings export, so assume widget and tile configuration is redone after a reinstall. The licence is GNU GPL version 3. The README summarises it as: "you can redistribute and modify it, but should give a credit to the original author." That summary is the author's, not a legal interpretation. GPL-3.0 carries source distribution obligations if you redistribute a modified build, and the README also states the app is distributed "as is" with no responsibility for damage. If you plan to ship a fork, read the actual licence text rather than the README summary.

Editorial conclusion

Adopt WADBS if you already run root or Shizuku on a device where you toggle Wireless Debugging often enough that digging through Developer Options has become annoying, and if you are comfortable with a GPL-3.0 Android app that performs privileged operations. Do not adopt it if your device is unrooted and you have no intention of installing Shizuku, or if you need a documented, versioned API surface you can depend on. Before installing, verify the F-Droid package listing at f-droid.org/packages/com.smoothie.wirelessDebuggingSwitch matches the GitHub release you intend to use, and confirm the release notes for v1.3 are the newest entry on the releases page.

Official sources

1. Issues
2. License: GPL-3.0
3. README
4. Releases
5. Smooth-E/wireless-adb-switch on GitHub