This is an AI-assisted analysis of Shizuku-related usages in the app's public source code. It is best effort, so it may not catch every single usage.

How this app uses Shizuku

Shizuku powers an alternative capture and scrolling engine for long screenshots of games, plus automatic permission grants and foreground detection.

• Capture screen without recording: takes each stitch frame with the screencap -p shell command through Shizuku instead of screen recording, used for the scrolling capture loop, region learning samples and template saves.
• Auto scroll game pages: performs the scroll gesture by injecting touchscreen down, move and up events through Shizuku, driving automatic page turns during capture and region learning.
• Enable floating controls automatically: grants the app's own display over other apps permission with an app operations command through Shizuku when the user enables it from the main screen.
• Enable notifications automatically: grants the app's own notification permission with a package manager or app operations command through Shizuku when the user enables it from the main screen.
• Find the game to capture: reads the currently visible app and window state with system status dumps through Shizuku to target the overlay, keep polling during capture and stop when the target is unsafe.

Android APIs or commands used

• screencap -p
• cmd appops set --user SYSTEM_ALERT_WINDOW allow
• cmd appops set --user --uid SYSTEM_ALERT_WINDOW allow
• pm grant --user android.permission.POST_NOTIFICATIONS
• cmd appops set --user POST_NOTIFICATION allow
• dumpsys window
• dumpsys activity activities
• dumpsys input
• android.hardware.input.InputManagerGlobal.getInstance()
• InputManager.injectInputEvent
• MotionEvent.obtain

Notable details

Shizuku mode is optional. The app can also capture with MediaProjection and request overlay and notification access manually, so the same long screenshot flow can work without Shizuku with extra user steps.