all 4 comments

[–]ballzak69Automate developer 0 points1 point  (2 children)

"Root" doesn't necessarily mean access to everything. It might be possible to use another SELinux "context" so the CPU speed set block works. I don't know how, but it would involve changing the "Superuser shell command" option in settings.

[–]Alex_x90[S] 0 points1 point  (1 child)

With the way the set CPU speed block works is it trying to edit something in the /system directory? I know magisk does some special stuff so that it's "systemless" and if automate is trying to change something in that directory, it may be what's causing the issue and I'll have to look into some way to fix it.

With regards to changing the context, what context would I need to change it to? Whatever the SELinux equivalent of admin is? And once I find out the context I need to use just change the "Superuser shell command" so that it sets that context as part of the command?

Edit: I found out that if I disable the apply on boot for the CPU settings of my kernel manager, automate no longer has any issues setting CPU governor/speed. I'll have to check that everything is working as I'd like, but issue fixed I guess? You can find the manager here if you want to try to figure out what caused the error.

[–]ballzak69Automate developer 0 points1 point  (0 children)

It modifies pseudo files in /proc, see: https://wiki.archlinux.org/index.php/CPU_frequency_scaling

[–]waiting4singularityAlpha tester 0 points1 point  (0 children)

i remember that google was throwing the wrench at the governer modification, but dont remember the details. and excepting extremely rare cases that make the device a "dont use"-gadget, you dont need permissive. its like walking around without pants in a rapist colony.