[Android Apps and Games] Ibuprophen:
Your still confusing Root and SELinux...

FYI... The Implementation of "SELinux" (aka Security Enhanced Linux) was actually implemented upon the release of Android v4.3 (aka Lollipop or LP) back in, I think, bet. 2012-2013.

Anyways.... No worries, this is actually a common occurrence (in one form or another).

I don't believe that you really NEED to have your device in a "Permissive Mode". I believe that your actual situation is "Root" related (specifically one or more items not receiving its needed Superuser Access). If your device is not "Properly Rooted" then this can/may/might be related to that "some are obtaining root access and some are not" type of situation your in.

I'll try to help clarify the differences a bit for you the best way I can. This is a challenge for most individuals (like myself) because it's difficult to explain this without creating more confusion as there's so much to them both.

Just remember, even though someone can simply/easily state something like "Night & Day" (for example), there's more details that make it "Night & Day" and those reasons thereof.

~~~~~~~~~~~~~~~

ROOTING:

Rooting allows users to attain a devices "Privileged Control" (aka Root Access) over the various areas of the Root Android System (the Files/Folders pertinent in the operation of the Android Operating System).

The specific access/permission (that's granted/denied) to those said Privileged Area(s) of the Android Operating System is an Administrative Access (aka Superuser Access).

~~~~~~~~~~~~~~~

SELINUX:

A Quick Background info for SELinux (Security Enhanced Linux), to begin with, is as follows...

SELinux was actually created/enforced by the USA's "NSA" (yes... The National Security Agency - aka "The Man"... LOL! ).

The SELinux was/is technically the part of the devices MAC System (aka Mandatory Access Control System) to replace the DAC System (aka Discretionary Access Control System).

The technical difference between the "DAC System" and the "MAC System" is actually "the means" by which the users/applications are able to gain access to certain (sensitive) areas within the device (there's much more to this but, that's the basic/bottom line).

~~~~~~~~~~~~~~~

I believe that, technically, there's really very few reasons for the need to be in "Permissive Mode" UNLESS it's primarily for developmental purposes (that encompasses only a handful of items).

PLEASE NOTE:

If a developer(s)/anyone provides ANYTHING that requires a change in the/a devices "SEAndroid Policy" (aka SELinux State) to be in a "Permissive Mode", this developer(s) REALLY should be providing this information AND reason(s) solely for the users awareness.

I just see SO MANY individuals get that "Surprise Factor" after the fact that results in a number of unintended issues. These can/may include when an individual has an issue like trying to get back to Enforcing Mode and some apps stop working (as well as some others) resulting in various issues. What gets me is the various, but ultimately the same, response from the developers like "oh yeah" or "Oops, forgot to mention this" (and similar).

A member who doesn't know, understand, is aware of, etc... their device requiring to be in a Permissive Mode (for one reason or another) can be "Potentially Dangerous" to the device, and even, the individual themselves regarding certain personal items within the device itself.

I am actually in an "Enforcing Mode" about 98% (+/-) of the time. When there's a time/need, to be in a "Permissive Mode", I always know the reason(s) why and how long.

Okay... Enough of the ranting style education, explanation, etc... and I do hope that I had explained the above information okay via text... :eek:

If you have any further "SELinux" questions (of course including the Switch App too), please let me know and I'll try to answer it the best way I can.

I do wish you the Best of Luck! :)

~~~~~~~~~~~~~~~

Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.