Requirements
Shizuku Version
r27
Operation Mode
ADB Mode
Device Model & OS Version
Pixel 9 Pro Android 17
Steps to Reproduce
I triad debugging with Claude, in Termux rish -c "echo test" won't return the Shizuku popup window to allow. I am not root, and only Termux is the problem.
Confirmed: Termux/rish never got authorized by Shevery — shizuku.json shows zero Termux entry, and the permission popup never fires, even after full data reset + re-pair. Ruled out: battery optimization, phantom process killing, overlay permission, package visibility.
Untested: whether the popup issue is Shevery-fork-specific (vs stock Shizuku) — worth trying stock Shizuku app side-by-side sometime, since Shevery is a third-party rebrand and could have a bug in its authorization-request flow that stock.
Logcat / Crash Logs
logcat -c
❯ rish
Request timeout. The connection between the current app (com.termux) and Shizuku app may be blocked by your system. Please disable all battery optimization features for both current app (com.termux) and Shizuku app.
❯ logcat -d | grep -iE "shevery|hamondev|rikka|permission|denied"
07-05 19:45:18.612 27792 27792 W libc : Access denied finding property "ro.debuggable"
07-05 19:45:18.612 27792 27792 W libc : Access denied finding property "ro.debuggable"
07-05 19:45:18.612 27792 27792 W libc : Access denied finding property "ro.debuggable"
07-05 19:45:18.613 27792 27792 W libc : Access denied finding property "ro.debuggable"
07-05 19:45:18.617 27792 27792 W libc : Access denied finding property "odsign.verification.success"
07-05 19:45:18.617 27792 27792 W libc : Access denied finding property "ro.debuggable"
07-05 19:45:18.678 27792 27792 W libc : Access denied finding property "ro.product.name_for_attestation"
07-05 19:45:18.678 27792 27792 W libc : Access denied finding property "ro.product.device_for_attestation"
07-05 19:45:18.678 27792 27792 W libc : Access denied finding property "ro.product.manufacturer_for_attestation"
07-05 19:45:18.678 27792 27792 W libc : Access denied finding property "ro.product.brand_for_attestation"
07-05 19:45:18.678 27792 27792 W libc : Access denied finding property "ro.product.model_for_attestation"
07-05 19:45:18.678 27792 27792 W libc : Access denied finding property "ro.debuggable"
07-05 19:45:18.687 27792 27792 D AndroidRuntime: Calling main entry rikka.shizuku.shell.ShizukuShellLoader
07-05 19:45:18.690 27792 27792 I AconfigPackage: com.android.permission.flags is mapped to com.android.permission
07-05 19:45:18.690 27792 27792 I AconfigPackage: com.android.permissioncontroller.flags is mapped to com.android.permission
❯ dumpsys package com.hamondev.shevery | grep -A2 "android.permission.SYSTEM_ALERT_WINDOW|POST_NOTIFICATIONS" No command dumpsys found, did you mean:
Command dcmpsmk in package dcmtk
Command dumpe2fs in package e2fsprogs
Command dumpsexp in package libgcrypt
Command dumpcap in package tshark from the root-repo repository
Command dumpcap in package wireshark-qt from the x11-repo reposito
Requirements
Shizuku Version
r27
Operation Mode
ADB Mode
Device Model & OS Version
Pixel 9 Pro Android 17
Steps to Reproduce
I triad debugging with Claude, in Termux rish -c "echo test" won't return the Shizuku popup window to allow. I am not root, and only Termux is the problem.
Confirmed: Termux/rish never got authorized by Shevery — shizuku.json shows zero Termux entry, and the permission popup never fires, even after full data reset + re-pair. Ruled out: battery optimization, phantom process killing, overlay permission, package visibility.
Untested: whether the popup issue is Shevery-fork-specific (vs stock Shizuku) — worth trying stock Shizuku app side-by-side sometime, since Shevery is a third-party rebrand and could have a bug in its authorization-request flow that stock.
Logcat / Crash Logs
logcat -c
❯ rish
Request timeout. The connection between the current app (com.termux) and Shizuku app may be blocked by your system. Please disable all battery optimization features for both current app (com.termux) and Shizuku app.
❯ logcat -d | grep -iE "shevery|hamondev|rikka|permission|denied"
07-05 19:45:18.612 27792 27792 W libc : Access denied finding property "ro.debuggable"
07-05 19:45:18.612 27792 27792 W libc : Access denied finding property "ro.debuggable"
07-05 19:45:18.612 27792 27792 W libc : Access denied finding property "ro.debuggable"
07-05 19:45:18.613 27792 27792 W libc : Access denied finding property "ro.debuggable"
07-05 19:45:18.617 27792 27792 W libc : Access denied finding property "odsign.verification.success"
07-05 19:45:18.617 27792 27792 W libc : Access denied finding property "ro.debuggable"
07-05 19:45:18.678 27792 27792 W libc : Access denied finding property "ro.product.name_for_attestation"
07-05 19:45:18.678 27792 27792 W libc : Access denied finding property "ro.product.device_for_attestation"
07-05 19:45:18.678 27792 27792 W libc : Access denied finding property "ro.product.manufacturer_for_attestation"
07-05 19:45:18.678 27792 27792 W libc : Access denied finding property "ro.product.brand_for_attestation"
07-05 19:45:18.678 27792 27792 W libc : Access denied finding property "ro.product.model_for_attestation"
07-05 19:45:18.678 27792 27792 W libc : Access denied finding property "ro.debuggable"
07-05 19:45:18.687 27792 27792 D AndroidRuntime: Calling main entry rikka.shizuku.shell.ShizukuShellLoader
07-05 19:45:18.690 27792 27792 I AconfigPackage: com.android.permission.flags is mapped to com.android.permission
07-05 19:45:18.690 27792 27792 I AconfigPackage: com.android.permissioncontroller.flags is mapped to com.android.permission
❯ dumpsys package com.hamondev.shevery | grep -A2 "android.permission.SYSTEM_ALERT_WINDOW|POST_NOTIFICATIONS" No command dumpsys found, did you mean:
Command dcmpsmk in package dcmtk
Command dumpe2fs in package e2fsprogs
Command dumpsexp in package libgcrypt
Command dumpcap in package tshark from the root-repo repository
Command dumpcap in package wireshark-qt from the x11-repo reposito