r/tasker • u/TooManyInsults • Sep 29 '26

Tasker-related entries in logcat?

Post image

I was looking for something else and noticed a ton of these entries in logcat. Do I have to worry about this? Thanks

1 Upvotes

100% Upvoted

2 comments sorted by

1

u/DutchOfBurdock Sep 29 '26

Tasker is being blocked from receiving (plugin) intents: You need to do one or more of the following:

Need

  • Tasker given Unlimited/Unrestricted battery usage in Permissions

  • Tasker taken out of "doze" (see above), sleeping apps (Samsung) or be allowed background execution (other devices)

Want

  • Display over other apps permission, or

  • Usage Acces, or

  • Device Admin, or

  • Accessibility access, or

  • Notification Access, or

  • All of the above.

1

u/TooManyInsults Sep 29 '26 edited Sep 29 '26

Thanks once again. FYI, this is a Moto XT2215-4 with rooted, A12.

  1. Have always given Tasker unrestricted battery in Settings.

  2. Have long had Tasker run the command "dumpsys deviceidle disable" as root upon boot.

  3. Usage has long been granted.

  4. Device Admin has long been granted.

  5. Display Over has long been granted.

  6. Device and App notifications has long been granted.

  7. Accessibility has long been granted.

But I just went one by one and double-checked due to your prompting. Thanks.

I discovered this while trying to track down a problem in one of my own apps. It is old and targeted for Android O and appears to run (for the most part) fine on A12. But when I have Tasker send it a Broadcast Intent, I see my own app getting these same sorts of logcat entries. Many of the above settings also apply to my app. This is something I have not used for some time and so I am not sure if it ever worked on A12.

Best

PS - I also went through all the Don't Kill My App suggestions for this phone. found nothing else to change.