Shizuku keeps stopping exactly after 1 minute of running on One UI 8.5 (S24 Ultra)

[kingevil-ace]

Hi everyone,
​I'm facing a very frustrating issue with Shizuku on my Galaxy S24 Ultra running the new One UI 8.5.
​I can successfully start Shizuku via Wireless Debugging. It says "Shizuku is running". However, if I leave the app open in the foreground (even without doing anything or switching to another app like LSPatch), it automatically changes to "Not running" after exactly 1 minute. The IPC connection just drops abruptly.
​To save everyone's time, here is the list of things I have already tried (and none of them worked):
​Set Shizuku's (and LSPatch's) battery usage to Unrestricted.
​Locked the Shizuku app in the Recents screen (Keep open).
​Turned OFF "Don't keep activities" in Developer Options.
​Disabled Samsung's "Auto Blocker" in Security settings.
​Turned OFF Wi-Fi Power Saving mode.
​Successfully ran the ADB command to disable the Phantom Process Killer: /system/bin/device_config put activity_manager max_phantom_processes 2147483647 (The command executed perfectly without errors).
​Tried Split-screen mode to keep both Developer Options and Shizuku active on the screen simultaneously.
​Despite all these tweaks, the 1-minute timeout still happens. It seems like One UI 8.5 has a new hidden aggressive background killer or a strict timeout for Wireless Debugging connections.
​Has anyone experienced this on One UI 8.5? Is there any other hidden ADB timeout setting or permission I need to grant? Any help would be greatly appreciated!

Screen_Recording_20260709_231651_LSPatch.mp4

[F1NAM0RE]

Tried installing this today as well without succes. It's either TimeoutException; "Failed to recieve binder within 1 minute". or Can't connect to wireless debugging service.

[ErikaXGH]

Hi everyone,
​I'm facing a very frustrating issue with Shizuku on my Galaxy S24 Ultra running the new One UI 8.5.
​I can successfully start Shizuku via Wireless Debugging. It says "Shizuku is running". However, if I leave the app open in the foreground (even without doing anything or switching to another app like LSPatch), it automatically changes to "Not running" after exactly 1 minute. The IPC connection just drops abruptly.
​To save everyone's time, here is the list of things I have already tried (and none of them worked):
​Set Shizuku's (and LSPatch's) battery usage to Unrestricted.
​Locked the Shizuku app in the Recents screen (Keep open).
​Turned OFF "Don't keep activities" in Developer Options.
​Disabled Samsung's "Auto Blocker" in Security settings.
​Turned OFF Wi-Fi Power Saving mode.
​Successfully ran the ADB command to disable the Phantom Process Killer: /system/bin/device_config put activity_manager max_phantom_processes 2147483647 (The command executed perfectly without errors).
​Tried Split-screen mode to keep both Developer Options and Shizuku active on the screen simultaneously.
​Despite all these tweaks, the 1-minute timeout still happens. It seems like One UI 8.5 has a new hidden aggressive background killer or a strict timeout for Wireless Debugging connections.
​Has anyone experienced this on One UI 8.5? Is there any other hidden ADB timeout setting or permission I need to grant? Any help would be greatly appreciated!

Screen_Recording_20260709_231651_LSPatch.mp4

This has been happening to me too! (Z flip 5) on one ui 8.5

[dyphum4-dotcom]

Shizuku

[dyphum4-dotcom]

Hi everyone,​I'm facing a very frustrating issue with Shizuku on my Galaxy S24 Ultra running the new One UI 8.5.​I can successfully start Shizuku via Wireless Debugging. It says "Shizuku is running". However, if I leave the app open in the foreground (even without doing anything or switching to another app like LSPatch), it automatically changes to "Not running" after exactly 1 minute. The IPC connection just drops abruptly.​To save everyone's time, here is the list of things I have already tried (and none of them worked):​Set Shizuku's (and LSPatch's) battery usage to Unrestricted.​Locked the Shizuku app in the Recents screen (Keep open).​Turned OFF "Don't keep activities" in Developer Options.​Disabled Samsung's "Auto Blocker" in Security settings.​Turned OFF Wi-Fi Power Saving mode.​Successfully ran the ADB command to disable the Phantom Process Killer: /system/bin/device_config put activity_manager max_phantom_processes 2147483647 (The command executed perfectly without errors).​Tried Split-screen mode to keep both Developer Options and Shizuku active on the screen simultaneously.​Despite all these tweaks, the 1-minute timeout still happens. It seems like One UI 8.5 has a new hidden aggressive background killer or a strict timeout for Wireless Debugging connections.​Has anyone experienced this on One UI 8.5? Is there any other hidden ADB timeout setting or permission I need to grant? Any help would be greatly appreciated!

Screen_Recording_20260709_231651_LSPatch.mp4

Shizuku

[ClixTW]

Install the GitHub version rather than the severely outdated one on Google Play.