Originally Posted by rekamyenom
Why does this work? What does it do? I had several phones that were dropping calls after 20 seconds and this cured it, but would love to know why it cured it.
I'm not an expert, but here's what I've read here here
SELinux is a sandbox environment. When a domain is enforced, only policies with certain whitelist programs can run. Plus, there can be multiple domains (root, user, system, etc.) which contain their own set of policies.
What this means to us: the modem (or whatever else is dropping signal) may not be in a whitelist or might be trying to execute code in a different domain. It may not even be the modem (or whatever else is dropping signal), there could be hundreds of other factors. This happens when SELinux is in enforcing mode. When you set SELinux to permissive, nothing is enforced, but its still logged to dmesg by the kernel. So, all of the policies are in effect, but nothing is stopped, only logged. There's another mode called disabled, which as you can guess, disables the whole thing (nothing is logged nor stopped).
So, theoretically, one may be able to look though dmesg to find out what is causing the problem and what needs to happen to stop it from dropping signal while still retaining enforcing mode. Otherwise, the simplest fix is to not implement it at all.
Thats what I got from that read. I'm not sure how accurate my explanation is.
Unofficial Official Jedi Master X FAQ (link here)
Donate to your dev. Do it.