1

Shizuku logcat not working on boot as expected

I am using the thedjchi fork of Shizuku and when Shizuku is available, Tasker does not seem to be starting to read the Logcat; I have to trigger it manually (i.e. through either turning on the ADB WiFi Logcat setting on then off again or creating a new Logcat entry profile then cancelling)

1 reply

Hi. Does other stuff that uses Shizuku work after boot?

D

Hi, yes, other features work fine (I tested using Run Shell with 'Use Shizuku') whlst confirming that the Logcat Entry event was not working beforehand and also found that the Logcat Entry event starts working after applying changes. The issue also appears to be intermittent; sometimes the Logcat Entry event works after boot without doing anything in Tasker and sometimes it does not.