Shizuku on Samsung (One UI): Setup & Fixes
Shizuku works well on Samsung Galaxy phones once you stop One UI from killing it — set it to unrestricted battery, and fix the USB configuration if you activate over cable. The two Samsung-specific pain points are the service dying when the screen locks and wireless debugging stalling after a Smart Switch import. Both have clean fixes below.
Install v13.6.0 from the download page and read the activation basics first; this guide covers only the Samsung extras. Not sure which Android release your Galaxy is on? Check the Android version guide before troubleshooting further.
Activate Shizuku on a Galaxy phone
- Enable Developer options — Settings → About phone → Software information → tap Build number seven times.
- Turn on Wireless debugging (Android 11+) under Developer options while on Wi-Fi, then pair it with Shizuku using the pairing code.
- Tap Start in Shizuku. If you use USB instead, enable USB debugging and run the ADB start command from a PC.
Fix: service dies when the screen locks
One UI’s battery optimisation is the culprit — it suspends the ADB link when the display sleeps. Set Shizuku to unrestricted battery, and if you activate over USB, switch the USB configuration so ADB is always on.
- Unrestricted battery: Settings → Apps → Shizuku → Battery → Unrestricted.
- Stop deep sleep: Settings → Battery → Background usage limits → remove Shizuku from Sleeping apps and Deep sleeping apps; turn off Put unused apps to sleep.
- USB fix (if using cable): dial
*#0808#, set the mode to MTP+ADB, or set Default USB configuration to Debugging only under Developer options. - Lock in recents: open recent apps, tap the Shizuku app icon, and choose Keep open / lock.
The *#0808# screen is a Samsung service menu. Only change the USB selection to one that includes ADB (MTP+ADB is safe). Leave everything else alone and tap OK/Reboot.
Fix: stuck on “searching for pairing service”
This usually follows a Smart Switch settings import, which corrupts the wireless-debugging state copied from your old phone. Toggle the debugging features off and on, reboot, and re-pair; if it persists, reset Developer options or set up without a Smart Switch import.
- Turn Wireless debugging OFF, then turn Developer options OFF.
- Reboot the phone.
- Re-enable Developer options and Wireless debugging, confirm you are on Wi-Fi, and pair Shizuku again.
One UI version differences
Samsung moves the battery menus between One UI versions, so the exact path depends on your release:
- One UI 6 (Android 14): Settings → Battery → Background usage limits holds the Sleeping and Deep sleeping app lists.
- One UI 7 (Android 15): the same controls sit under Settings → Battery, with “Put unused apps to sleep” as a separate toggle.
- One UI 8 (Android 16): structurally the same, but this is where the frozen Play build finally breaks — switch to the GitHub release. The screen-off service kills were first reported around here (GitHub #1478, #1459).
Which activation method is best on Samsung?
On modern Galaxy phones, wireless debugging is the most reliable way to activate Shizuku — it sidesteps the USB
configuration quirks entirely. Use the PC/ADB route only when wireless debugging will not pair, and apply the
*#0808# USB fix if you must stay on a cable.
A note on Samsung Knox: Shizuku does not trip Knox and does not need it disabled, because it uses standard ADB rather than modifying the system. Secure Folder runs as a separate profile, so a Shizuku session started in your main profile will not carry into it.
Samsung FAQ
*#0808# opens Samsung’s hidden USB settings menu. Setting it to MTP+ADB (or selecting the ADB option) restores a reliable ADB connection when the normal USB configuration will not keep Shizuku running. Do not change other values in that menu.Based on the project’s Samsung reports (issues #1478, #1459 and #1072) and testing on One UI devices.