Shizuku stops when switching screen off on Xiaomi devices

[AlexeiCrystal]

Requirements

• Shizuku is downloaded from official channels (GitHub release or Google Play)
• Shizuku is not running in a virtual environment or broken ROM (GrapheneOS)
• (Root users) No Xposed installed / Xposed is not enabled for Shizuku

Latest Shizuku version

13.6.0

Version in use

13.6.0

Mode

adb

Android version

Android 12 (MIUI 14)

Device

Xiaomi Redmi Note 9 Pro

What did you do

As soon as I switch off the screen on my phone the Shizuku service stops. I have given the app permission to autorun and enabled ignore battery optimisation but it doesn't help. Shizuku service still stops when I switch off the phone screen. This is the only way it stops, only when the screen is switched on, and in all other cases it works normally

What happened

No response

What do you expect

No response

[GAMINGCHATS]

Same here on a Poco X5 5G with Xiaomi HyperOS and Android 14.

[AlexeiCrystal]

I understand this is an issue on Xiaomi. The system stops shizuku_server after switch off screen for optimisation.

But maybe there is a way to bypass it?

[GAMINGCHATS]

I've got no idea. I currently just have enabled autostart and locked the Shizuku app in recents. In some phones (in this case mine) that option is hidden under Security > Boost Speed > cog icon on the top right > Lock apps. And I'm currently logging how it behaves. I've allowed the restricted permissions just for safe measure. In a bit (~30 mins) I'm gonna upload the log here for info.

[AlexeiCrystal]

Well as far as I understand under normal circumstances Shizuku should run one and it should run until the device reboots.

But on Xiaomi (Xiaomi, Redmi, Poco) it stops after switching off the screen.

[GAMINGCHATS]

Hmm. This log I'm trying to make is interesting. Here it so far and I'm gonna try 2 or 3 more times. oh! Also, in developer options I've enabled (obviously) USB debugging and USB debugging (Security settings), as well as "Disable adb authorization timeout", which tbf, I don't fully know what it's meant to do. 🤷😅
Here's the log I'm making as far as now:

Try #1: Screen close and cable out with Shizuku locked in background: 18:59
19:16: locked in recent apps, service not running.

Try #2: 19:29 with cable connected
Result: 19:35 App open, cable connected, service running.

Try #3: 19:36, app locked in recents
Result: 20:15 App in background, service running, cable connected

Try #4: 20:16, app locked but off of recents, cable connected
Result: 20:30, cable connected Shizuku running.

[GAMINGCHATS]

Actually, because (as you can see in the log. btw, I'm using the 24 hour-format) it's evening for me. I'll try again tmrw or maybe the day after tmrw. I'll be keeping an eye on this issue.

[AlexeiCrystal]

Hmm. This log I'm trying to make is interesting. Here it so far and I'm gonna try 2 or 3 more times. oh! Also, in developer options I've enabled (obviously) USB debugging and USB debugging (Security settings), as well as "Disable adb authorization timeout", which tbf, I don't fully know what it's meant to do. 🤷😅

USB debugging - ability to send ADB commands from another device
USB debugging (security settings) - (not on all devices) needed for more opportunities to send commands (more privileges)
Disable ADB authorisation timeout - needed so that if a device is connected for USB debugging or Wi-Fi debugging you don't have to confirm the connection again after a while, and in case of Wi-Fi debugging you don't have to enter the connection code again.

Well, that's roughly the purpose of these settings.

The first two settings are needed, without Shizuku it probably won't run.

[AlexeiCrystal]

Actually, because (as you can see in the log. btw, I'm using the 24 hour-format) it's evening for me. I'll try again tmrw or maybe the day after tmrw. I'll be keeping an eye on this issue.

By the way, I also use the 24 hour format and I have evening too. And I realise that we probably have the same or similar time zones. I'm at 20:48.

[AlexeiCrystal]

I don't know if this is useful, but Shizuku starts its own process shizuku_server:
ps | grep shizuku
For example:
u0_a4919 908 880 7150272 153208 0 0 0 S moe.shizuku.privileged.api - Shizuku application (android application) (may work, but not necessary for shizuku_server to work).

shell 1197 1 5312760 129276 SyS_epoll_wait 0 S shizuku_server - Shizuku server (seems to be a special script or daemon), it is the one that stops when you switch off the screen.

And here is what these inscriptions mean (they go in order): USER PID PPID PPID VSZ RSS WCHAN ADDR S NAME

And it seems to me that if you fix and enable autorun for Shizuku, it won't help for shizuku_server, because autorun allows Shizuku application to run and work in the background, but not shizuku_server, because it is started from shell and the system doesn't think that this process is related to Shizuku application and doesn't allow shizuku_server to work in the background when the screen is off. These are my assumptions.

[AlexeiCrystal]

The Shizuku server can be stopped manually via adb using the command:
kill $(pidof shizuku_server)
, this shows that this process is responsible for the functionality of the Shizuku server once it is started.

[GAMINGCHATS]

Hmm. Interesting. So, the only way would be if you could access the shizuku_server process so you could enable autorun for that. Any ideas?

[AlexeiCrystal]

I used aShellYou to run the commands

And I don't have much of an idea yet, but I'll think about it. Maybe there's a way to give more permissions or autorun the process or something using shell/ADB commands.

[AlexeiCrystal]

I'll take care of the issue tomorrow.

[GAMINGCHATS]

Oh, btw i am unrooted. Just to be safe I wanted to mention it! 😊