Welcome to Shizuku Discussions! #135

My apologies, but perhaps this will help others. I forgot the most basic thing to do, that is restart the device. It worked just fine after a restart.

I want to share a workaround that finally got Shizuku starting automatically on boot on a Realme device running Realme UI (ColorOS base), where every other documented fix failed.

The problem

On ColorOS/Realme UI, the wireless debugging authorisation dialog reappears after every reboot, even when "Always allow on this network" is ticked. The checkbox is simply never persisted. This means "Start on boot" can never complete: Shizuku waits for wireless debugging, the system throws up the authorisation dialog, and without a human tapping "Allow" the service never starts.

I tried everything in the Troubleshooting wiki page and more:

Re-enabling "Start on boot"
Per-app Auto-start enabled
Battery optimisation disabled, app locked in recents
pm grant moe.shizuku.privileged.api android.permission.WRITE_SECURE_SETTINGS
cmd appops set moe.shizuku.privileged.api RUN_IN_BACKGROUND allow
cmd appops set moe.shizuku.privileged.api RUN_ANY_IN_BACKGROUND allow
settings put global adb_wifi_enabled 1, adb_allowed_connection_time 0
Revoking USB debugging authorisations and re-pairing from scratch
Enabling wireless debugging from Developer Options first, ticking the box there
TCP mode on and off
adb tcpip 5555 for a fixed port instead of the random wireless debugging port
Switching the Wi-Fi network from randomised MAC to device MAC

None of it made the authorisation stick. The dialog came back on every single boot.

The workaround

Use an automation app to tap the dialog for you. I used MacroDroid; Tasker or Automate would work the same way. An accessibility service can interact with system permission dialogs, so a coordinate tap on "Start" and then on "Allow" does the job.

Macro:

Trigger: Device Boot
Actions:
Wait 45 seconds (let Wi-Fi connect)
System Setting → Global → adb_wifi_enabled = 1
Wait 10 seconds
Send Intent → Broadcast Receiver
Action: moe.shizuku.privileged.api.START
Package: moe.shizuku.privileged.api
Extra: name auth, type String, value = your token from "View intents"
Wait 5 seconds
Launch Application → Shizuku (brings it to the foreground so coordinates match)
Wait 5 seconds
UI Interaction → Tap at the coordinates of the "Start" button
Wait 3 seconds
UI Interaction → Tap at the coordinates of the "Allow" button

The coordinates are device-specific — read them off your own screen with Developer Options → "Pointer location".

Two notes: the auth token shown in the "View intents" sheet is truncated on screen, so use the copy button rather than typing what you see. And the automation app's accessibility service must be kept alive, which on ColorOS needs its own battery and auto-start exemptions.

Suggestion

It might be worth adding a line to the Troubleshooting wiki for ColorOS/Realme/Oppo users, pointing out that the authorisation dialog is never persisted on these ROMs and that an automation app tapping the dialog is currently the only way to get unattended boot. Right now the page lists firewall, VPN and battery causes, but nothing covers a ROM that simply refuses to remember the authorisation.

Happy to answer questions if anyone wants to reproduce this.