RikkaApps
Shizuku stops working daily/have to reinstate wireless bugging every morning.
Please report bugs of Shizuku itself.
Requirements:
- [x] Shizuku version is up-to-date
- [x] Shizuku is downloaded from official channels (GitHub release or Google Play)
- [x] Shizuku is not running in a virtual environment or broken ROM (GrapheneOS)
- [ ] (Root users) No Xposed installed / Xposed is not enabled for Shizuku
Change "[ ]" to "[x]" if it meets the requirements.
Reports not meet the requirements will be immediately closed.
Information:
- Shizuku version:
- Mode: [adb, root]
- Android version:
- Device: (optional)
Logs:
Related full logcat.
Describe the bug:
A clear and concise description of what the bug is.
Additional context:
Add any other context about the problem here.
https://shizuku.rikka.app/guide/setup/#start-via-wireless-debugging-start-by-connecting-to-a-computer-shizuku-randomly-stops
Have you followed all the steps listed here? For example, "Disable adb authorization timeout" option in developer options needs to be enabled.
Have the same issue. Stops no matter what settings I have and when the WiLAN network is consistent
Same issue here. I've followed the steps documented, but I still have to enable once a day. Pixel 6 Pro running stock Android 13 with the May 2023 security update.
I received an OS update for the OnePlus Nord CE a couple of days ago, and I'm now finding Shizuku to be not running each morning (the OS update only claims to include the 5 March 2023 security update, however).
I'm using Ambient Music Mod and its daily backups are failing at 3am, which suggests Shizuku stops running after a few overnight, unattended hours.
https://shizuku.rikka.app/guide/setup/#start-via-wireless-debugging-start-by-connecting-to-a-computer-shizuku-randomly-stops
I've confirmed all the settings described here are set, as well as both "Allow background activity" and "Don't optimise" battery usage options.
solve https://github.com/RikkaApps/Shizuku/issues/277#issuecomment-1476985243
Try disabling adb authentication timeout in Dev Options.
On Sat, 27 May 2023, 7:32 am Terrance, @.***> wrote:
I received an OS update for the OnePlus Nord CE a couple of days ago, and I'm now finding Shizuku to be not running each morning (the OS update only claims to include the 5 March 2023 security update, however).
I'm using Ambient Music Mod and its daily backups are failing at 3am, which suggests Shizuku stops running after a few overnight, unattended hours.
https://shizuku.rikka.app/guide/setup/#start-via-wireless-debugging-start-by-connecting-to-a-computer-shizuku-randomly-stops
I've confirmed all the settings described here are set, as well as both "Allow background activity" and "Don't optimise" battery usage options.
— Reply to this email directly, view it on GitHub https://github.com/RikkaApps/Shizuku/issues/294#issuecomment-1565358621, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABJ7GR3FV6GYOUOOUVHAUATXIHQ6HANCNFSM6AAAAAAXHQXYEE . You are receiving this because you are subscribed to this thread.Message ID: @.***>
That is one of the settings listed on the guide page, which I've already confirmed is set as described.
(I should note this is an Android 12 device, so all of the settings listed apply.)
I'm keeping an eye on this, but it seems to be behaving for me again now (no further OS updates, so I'm not sure what changed).
Unfortunately this has started being an issue again as of last week -- AMM notices and warns that Shizuku has become unavailable about a few hours after (re)starting it.
this happens to me but can vary from hours to seconds. Before you ask I have triple checked the FAQ and disabled battery optimizations (My UX)
Actually after reinstalling i'm starting to get false postives(?). Wireless debugging shows as off in android settings but shizuku and the apps I use with it all say shizuku is running perfectly fine
I am having same issue followed every guide out there.
OnePlus Nord 2 Android 13
Same here, OnePlus 11 Android 14 OxygenOS CPH2449_14.0.0.501(which brought it up to the Feb Android security patch). NO ROOT or other mods. Wi-Fi always turned ON.
Battery optimisation: dont optimize, background running enabled. Disable ADB authorisation time-out: enabled. Disable permission monitoring: enabled Background process limit: default.
Already a few updates ago I've been using Shizuku and it would sometimes turn off itself within 10 mins, while the QS wireless debugging toggle was still on and I wouldn't be able to press start in Shizuku again without dis- & re-enabling the toggle, or it would ask me to do pairing. Could be Shizuku or could be the toggles showing wrong state.
Much more often though (90%) wireless debugging turns off every ~3 to 10 minutes. These two were the only outcomes after having used Shizuku >50 times. I've never had it stay on, even while using it to write new permissions for user apps with a command at least every <1 min using aShell.
Now that I've updated to 14.0.0.501 the wireless debugging toggle refuses to turn on at all... (both QS toggle as well as dev options toggle). If I keep smashing it I get like 100ms flashes of the wireless debugging settings, showing an entry for Shizuku and changing just the port for every flash. This was like this for a few days.
Then today it finally turned on! But to my surprise both Shizuku and App Manager entries in it's settings were removed so I had to pair again. This worked but then Shizuku hang in the terminal at the last stage (shizuku_starter exit with 0) and when checking the toggle it refused to turn on again. It feels to me like they're breaking Shizuku on purpose? I hope not 🤞
Any logs useful? (and if through ADB over USB please describe exact location for pull command, as I have no idea)
Same here, OnePlus 11 Android 14 OxygenOS CPH2449_14.0.0.501(which brought it up to the Feb Android security patch). NO ROOT or other mods. Wi-Fi always turned ON.
same me I use some automation tools (tasker) ,enter the adb command after each mobile phone unlock
sh /storage/emulated/0/Android/data/moe.shizuku.privileged.api/start.sh