Before You Begin
- I am reporting an issue with Shizuku itself, NOT an issue about compatibility with another app
- I read the wiki and followed all relevant troubleshooting steps
- I searched through all issues and confirmed that this is a new bug
- I am using the latest version of Shizuku
Requirements
- Shizuku is not running in a virtual environment or broken ROM (e.g., GrapheneOS)
- Xposed is not installed/enabled for Shizuku
Mode
adb
Shizuku Version
13.7.0
Android Version
17
Device
Google pixel 7
Issue Description
When I need to connect using Wireless debugging it requires the USB debugging to be enabled although it's already enabled
Steps To Reproduce
No response
Activity
7
ParasauarPal25d agoSame issue here, Pixel 9
AstromanGaming24d agoSame for my Pixel 10 with the lastest Android version
Sikatsu22d agoSame on Pixel 10 Pro. Must be due to the update from last week.
Zoefiro21d agoHi everyone, I was facing the same issue where the OS forcibly disables the ADB status and blocks the Start/Pair buttons.
I compiled a fork that bypasses the adbEnabled UI check by forcing it to return true. This allows you to bypass the visual lock and start the service normally via TCP.
You can check the source code or download the compiled APK from my release here: https://github.com/Zoefiro/Shizuku-Stable-Debugg-Fix
PelsonBMW10d ago5. Hi everyone, I was facing the same issue where the OS forcibly disables the ADB status and blocks the Start/Pair buttons. I compiled a fork that bypasses the
adbEnabledUI check by forcing it to return true. This allows you to bypass the visual lock and start the service normally via TCP. You can check the source code or download the compiled APK from my release here: https://github.com/Zoefiro/Shizuku-Stable-Debugg-Fix
unfortunately , WiFi doesn't work ...
panecondoin4d agoAlso affected by this. No amount of reinstalling shizuku and reseting dev mode/debugging options did anything.
Same issue for me on pixel 6a running android 17