The app does not enable Wireless ADB and USB Debugging automatically

[kitsumed]

问题描述

Stellar grants itself WRITE_SECURE_SETTINGS to enable and disable certains global settings like wireless ADB, however I had a scenario where this would not happen.

复现步骤

1. Disable Wireless Debugging
2. Inside Stellar, disable TCP/IP, stop stellar if running
3. Reboot the device
4. Try starting stellar, will not work

期望行为

Stellar will show an error message telling the user to enable Wireless Debugging, however, since Stellar now has WRITE_SECURE_SETTINGS from the original "setup/pairing", it should do it by itself and then upon failure disable it back.

This reduce the actions needed by the user. Similar apps like thedjchi shizuku forks does this. I also documented it more in details here.

Once connected via Wireless ADB, the application should also offer to automatically disable Wireless ADB but keep USB Debugging enabled. Once a connection is estabilished, disabling Wireless ADB prevent others third-party connections requests, but on most phone, the current connections stays alive until USB Debugging itself is turned off.

The same should also happen with USB Debugging. If it is disabled and Stellar hold WRITE_SECURE_SETTINGS, it should, upon the user request, enable USB Debugging for the user.

启动方式

ADB 无线调试

Stellar 版本

1.0.17

Android 版本

Android 16

设备型号

Emulator

日志信息

补充信息

No response

[lovelmxa]

Silently enabling system features may raise compliance and user-consent concerns.

In a future commit, when Stellar has permission to modify secure settings, we plan to show a one-tap button for enabling wireless debugging instead of redirecting the user to system settings.

Automatically disabling wireless debugging after a wireless ADB connection is established raises similar concerns. It goes beyond Stellar’s current design scope and is not strictly necessary for its core functionality. Adding another toggle specifically for this behavior may also make the settings unnecessarily complicated, so we’ll need to consider this feature further.

[kitsumed]

Silently enabling system features may raise compliance and user-consent concerns.

There could be a toggle in the user settings like, Allow Stellar to automatically enable USB Debugging/Wireless at startup request. There are very nice users cases, some applications detect when USB Debugging / Wireless Debugging is enabled, forcing users to disable it. This would also be practicle with the proposed feature at #80.

Automatically disabling wireless debugging after a wireless ADB connection is established raises similar concerns. It goes beyond Stellar’s current design scope and is not strictly necessary for its core functionality. Adding another toggle specifically for this behavior may also make the settings unnecessarily complicated, so we’ll need to consider this feature further.

Automatically disabling wireless debugging after a wireless ADB connection is established causes ADBD to stop listening for new wireless connections, thus preventing other third parties from attempting to connect to the device.

This is useful, because there have sometimes been CVEs like the recent CVE-2026-0073 (PoC here) that allowed bypassing the authentication process and immediately gaining remote ADB access.

Disabling USB Debugging itself when it is no longer necessary can also address physical device exploits like Android 4.4.2 Secure USB Bypass along with fully stopping the adbd daemon on the device. This is an old CVE, but I think it makes it easier to understand why I would wish for Stellar to offer safer behavior. The real goal would be to help prevent the worst-case scenario before it is too late.

This is the approach other Shizuku forks have taken, and I was hoping Stellar would also consider this in some ways. Of course, your application has much more granular permission control, but I think it would be nice to also have good default security. I think it may be nice to have thoses available under some kind of security section in Stellar settings.

[lovelmxa]

ok,we will do it