#2596
Issues/RikkaApps/Shizuku/#2596

shizuku automatically disconnects when wireless debugging is enabled on Android 16 phones.

Openleij0318opened 16d ago

Requirements

  • Shizuku is downloaded from official channels (GitHub release or Google Play)
  • Shizuku is not running in a virtual environment or broken ROM (GrapheneOS)
  • (Root users) No Xposed installed / Xposed is not enabled for Shizuku

Latest Shizuku version

13.6.0.r1086.2650830c

Version in use

13.6.0.r1086.2650830c

Mode

adb

Android version

16

Device

Samsung S25 Ultra S9380,ONEUI8.5

What did you do

Recently, when using shizuku to authorize an app, I used wireless debugging to launch shizuku. However, when I switched to the background to use an app, it occurred that shizuku was no longer connected, and I had to restart it repeatedly. I had to restart several times to successfully use the authorized app. I had never encountered this situation before. I have set the shizuku background to permanently start to prevent shizuku from being disabled by background optimization, but this situation still occurs.

What happened

No response

What do you expect

No response

Activity

1
kukirin-ui16d ago

Same phone family here (Samsung, Android 16, Shizuku over wireless debugging), so a few things worth checking, mostly from the "Shizuku randomly stops" section of the official setup guide:

  1. Developer options -> enable "Disable adb authorization timeout" (Android 11+).
  2. Developer options -> "Default USB configuration" -> "No data transfer".
  3. Don't toggle "USB debugging" or "Developer options" off at any point, even briefly.
  4. Battery -> set Shizuku to "Unrestricted", and add it to "Never sleeping apps" in Device care.

Two questions that might narrow it down:

  • Does it drop exactly when your phone switches Wi-Fi networks or Wi-Fi goes to sleep? Wireless debugging is tied to the current Wi-Fi.
  • Is Samsung's Auto Blocker turned on (Settings -> Security and privacy -> Auto Blocker)? I'm not sure it affects wireless debugging on One UI 8.5, but it's worth ruling out.

If you can grab adb logcat | grep -i shizuku around the moment it disconnects, that would show whether the server process is being killed or the adb connection itself is closing.