Bug 1214812 added support for always enabling SELinux Permissive. We will definitely need SELinux Permissive to run the normal reftest/mochitest unit tests on Android 5.x+. :alex_johnson ran into a case with a GS5 running CM12 where setenforce Permissive would not work and had to resort to echo 0 > /sys/fs/selinux/enforce. We may need to support that in devicemanagerADB and adb*.py if setenforce does not work.

setenforce seems to be working on the CM12 nightly. But, I can't run robocop tests even with SELinux set to permissive and I have no idea why.

(In reply to Alex Johnson (:alex_johnson) from comment #1) > setenforce seems to be working on the CM12 nightly. But, I can't run > robocop tests even with SELinux set to permissive and I have no idea why. We might be able to diagnose with mach output + logcat. You could post those here or in a separate bug.

I'm gonna post those in a separate bug since it's not related to SELinux permissions afaik. And I'm gonna set this to resolved worksforme since this was most likely a bug with CM.

Actually, this should remain open since devicemanagerADB has no code to set SELinux to Permissive.

devicemanager has been replaced.