Skip to content

1.2.4

Choose a tag to compare

View all tags
@Sharif-bot-cmd Sharif-bot-cmd released this 22 Oct 21:15
· 2 commits to main since this release
1.2.4
c2748df

Fixed

Smart-foreground no longer re-enables ADB mid-session.

The old design saved the prior adb_enabled value on enter and restored it on exit. If the monitor mis-detected the exit — a dialog, an overlay, an activity pause without a resume — the restore ran while the app was still open, and ADB came back on a few seconds into the session. Banking apps saw it.

The restore is gone. ADB goes to 0 on enter and stays there until the user restarts Shizuku, which sets it back to 1 as part of starting the ADB server. No restore code, no flip-flop, no window where the app sees ADB return.

The trade-off: leaving a scoped app doesn't turn ADB back on. The user restarts Shizuku to get it back. With Shizuku-Next's "ADB without Developer options" switch this is transparent; on upstream Shizuku it's a manual step after each scoped session.

Assets 4
Loading