ES-DE Overlay

Shizuku

Shizuku is optional. Android lets only system apps end another app. Shizuku runs a small helper with adb’s permissions, which is allowed to end apps. ES-DE Overlay uses it when it’s running and allowed:

Set it up

  1. Install one of them:
    • Shizuku, from Google Play or its GitHub releases. Without root, it has to be started again after every restart.
    • Shizuku-Next, from its GitHub releases. It’s a fork that can start itself on boot and restart itself if it stops. It’s signed with a different key, so uninstall Shizuku first. This is the one in the setup the screenshots come from.
  2. Start it, by one of the ways in Shizuku’s guide:
    • Wireless debugging (needs Wi-Fi):
      1. In Android’s developer options, turn on USB debugging and Wireless debugging.
      2. In Shizuku, start pairing.
      3. Tap Pair device with pairing code under Wireless debugging, and type the code into Shizuku’s notification.
      4. Tap Start in Shizuku.
    • From a computer: with USB debugging on and the device plugged in, run adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh.
    • On a rooted device, start it directly.
  3. Shizuku-Next only: turn on Start on boot, and Watchdog to have it restart itself. If it was started through wireless debugging, that needs Wi-Fi at boot; see below for starting without it.
  4. In ES-DE Overlay, look under Quitting games.
    • The Shizuku row reads Not installed, Not running (Open Shizuku opens it), Not allowed or Enabled.
    • Tap Allow and allow ES-DE Overlay in Shizuku’s dialog; the row turns Enabled.
    • Then turn on Quit games left with Home if you want it. The switch can’t be turned on while Shizuku isn’t Enabled.

Advanced: start Shizuku-Next without Wi-Fi

Some firmware lets adb listen on a network port from every boot. Shizuku-Next’s USB start method can then use that port, with no Wi-Fi and no computer.

  1. With USB debugging on and the device plugged into a computer, run adb shell setprop persist.adb.tcp.port 5555, then adb shell getprop persist.adb.tcp.port. It should print 5555; if it prints nothing, the firmware doesn’t allow it.
  2. In Shizuku-Next, choose the USB start method, turn on Start on boot, Watchdog and TCP mode, and start it. Allow the Allow USB debugging? prompt for Shizuku’s key.
  3. Restart to check. Shizuku-Next should be running a few seconds after boot, with Wi-Fi on or off.

To undo it, run adb shell setprop persist.adb.tcp.port "" and restart.