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)
Hi. Does other stuff that uses Shizuku work after boot?
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.
Hi, so I've found a workaround and I thought I'd share it as it may help you diagnose the issue and find a solution in code on your end. What I've found is you can set up a 'Device Boot' event profile to turn off all the logcat entry profiles then you can use a 'Shizuku Available' event profile to turn the logcat entry profiles back on. This makes it work every time.
From my understanding, it appears that the logcat is not being ran inside Shizuku once the service is available; continuing to attempt running it in Tasker's own shell instead. I hope this helps.
My Tasker version as of writing this: 6.7.1-beta
Thank you! Just to confirm, do you have the option to use ADB Wifi for logcat enabled or disabled in the settings?
I have it disabled
Ok, I think I fixed it.
Can you please try this version? https://www.dropbox.com/scl/fi/gyxfw8kimxyb0b1d1yaqu/Tasker.35.apk?rlkey=yacgs4ykb5c3rxb1wgn46a6oa&dl=0
Hi, I don't know if this is a Dropbox issue or a file issue but after downloading the apk it seems to be corrupted.
Hhmm, weird I tried it and it worked for me. Can you please try again?
It turns out it was Dropbox giving me a corrupted file. I've been able to try it now and it unfortunately only worked once or twice, but both this build and the earlier builds will always work for logcat event profiles that are turned off before Shizuku is available and turned back on after it becomes available, regardless of if those profiles were turned off before reboot or after reboot.
I apologise, please disregard what I said; I spoke too soon. It turns out I bypassed the actions for turning on the logcat entry profiles for testing this fix but didn't bypass the actions for turning the profiles off, meaning they weren't even on when I was testing. This fix works actually works fine, thank you for your time!
Awesome! Glad it works!! :)
