USB debugging not enabled while it is

Same for me

Same here too

Good evening. Just updated and the same issue :-( You can start Shizuku via Tasker (intent), Termux (adb shell) or PC but the app reports USB Debug is not enabled even when it is. I hope ther is an "easy" way to solve it, Shizuku is my life saver since I don't root my phone. Thanks in advance.

https://github.com/RazGame/Shizuku/releases/tag/v13.7.0.r1366-razgame-beta

@RazGame Thank you so much!

https://github.com/RazGame/Shizuku/releases/tag/v13.7.0.r1366-razgame-beta

I'm getting app not installed

https://github.com/RazGame/Shizuku/releases/tag/v13.7.0.r1366-razgame-beta

I'm getting app not installed

Never mind, I figured it out, I needed to run adb uninstall moe.shizuku.privileged.api

adb_enabled

Whether ADB over USB is enabled. (0 = false, 1 = true). This will always return 0 for all third-party apps.

development_settings_enabled

Whether user has enabled development settings. (0 = false, 1 = true). This will always return 0 for all third-party apps.

Same issue for me, Pixel 9 Pro with latest updates.

Official Shizuku (https://play.google.com/store/apps/details?id=moe.shizuku.privileged.api&hl=en) is working.

Same with me, pixel 9 pro latest September update.

Play store version works, but get a warning from smartspacer about outdated version

https://github.com/RazGame/Shizuku/releases/tag/v13.7.0.r1366-razgame-beta

@RazGame thanks for your Fix, it works like charme on my Pixel 10 with A17 and also on my Pixel 7 with A16 and last but not least on my AndroidTV Box with A14 - good job!

NOTE FOR ATV 14: you have to disable Play Protect, or you cannot install any kind of shizuku, Google blocks it relentlessly — no hidden text link like "install on your own risk" or anything. It simply fails. Disable Play Protect on AndroidTV: Play Store → profile icon → Play Protect → Settings → disable “Scan apps with Play Protect” and after installing you can re-enable Play Protect again, if you need them for some reasons.

Same issue with my pixel 6a latest update. Shizuku 13.7.0-thedjchi. Build number CP3A.260905.009

Same issue with my pixel 6a latest update. Shizuku 13.7.0-thedjchi. Build number CP3A.260905.009

@smabid Sure, the latest Pixel update (September 26) changed a lot of things behind the scenes around Shizuku, Developer Options and so on. The version from @RazGame works fully for me again. If you are interested in the details: Google bumped the API level from 33 to 37 (Android 17), and this broke quite a few things. I'm pretty sure d4rken (e.g. SD Maid SE) will also adapt this in his Shizuku/Porter migration as soon as possible (#22).

@MarkyMarkDE Thanks. This version works for me as well.

Do try with a17

https://github.com/rushiranpise/Shizuku-Next

Do try with a17

https://github.com/rushiranpise/Shizuku-Next

This is what I just installed, works great so far

you can also use the new Porter App from @d4rken aka SD-Maid. https://github.com/d4rken-org/porter/releases/tag/v0.8.1-rc0 It is tested on:

• Google Pixel 10 (Android 17 / September Patches -> SDK 37) with Device Owner permission
• Google Pixel 7 (Android 16 / September Patches -> SDK 36) & NEW: same Pixel 7 (Android 17 / October Patches -> SDK 37)
• AndroidTV (AndroidTV 14 -> SDK 34) on a waipu.tv Box
• emulator tested under some really harsh conditions 🫣

For the maintainer, or anyone who wants a minimal fix on top of thedjchi 13.7.0 rather than a different fork: I tried to open a PR, but this repo only accepts PRs from collaborators. The patch is ready to merge or cherry-pick:

Commit: https://github.com/trevornk/Shizuku/commit/3c0de08c (branch fix/301-android17-adb-enabled, based on current master 15ade0e)

Cause: since the September Android 17 QPR1 update (CP3A.260905.009), Settings.Global.ADB_ENABLED reads 0 for third-party apps even when USB debugging is on (adb shell settings get global adb_enabled still returns 1). The manual Start, start-on-boot and AdbStarter paths all check that value, so they fail with "USB debugging is not enabled". Starting the server from a PC still works.

Fix: adds EnvironmentUtils.isAdbEnabled(), which trusts a non-zero value and otherwise assumes ADB is enabled on API 37+. If ADB really is off, the following connection attempt fails through the existing error path. It's used in AdbStarter, StartWirelessAdbViewHolder and SettingsHelper: 4 files, +18/−6. Same approach as @RazGame's 0b3611a, without the build/versioning changes.

Tested: built against compileSdk 37 and installed on a Pixel 10 Pro Fold, Pixel Tablet and Pixel 10a on CP3A.260905.009. Start-on-boot over wireless debugging/TCP now works again after a reboot on all three, and existing app authorizations carry over.

Migrating from any other build still means a one-time uninstall/reinstall and re-pair, because the signing key differs. If you reinstall, re-allow your apps in Shizuku's authorized-apps list before the next reboot, or they come back as unauthorized.