Related
Perhaps someone can clarify for me...
I use Magisk and I've noticed that it was recently updated and there are mentionings about SELinux/sepolicy and pseudo enforced, etc. in the changelog.
Whenever I run SambaDroid it will fail to start unless I open the SELinuxModeChanger app and change the mode to Permissive first, which of course ruins SafetyNet, so I can't just leave it in that mode all the time.
I have to go back and change it to Enforcing when I am done.
An extra step I'm hoping won't be required in the future. Perhaps on a per-app basis like MagiskHide.
Should the recent changes to Magisk allow me to run SambaDroid without having to manually change the SELinux Mode?
If so, it doesn't work yet, but maybe I am misunderstanding the changelog references.
andrewsfm said:
Perhaps someone can clarify for me...
I use Magisk and I've noticed that it was recently updated and there are mentionings about SELinux/sepolicy and pseudo enforced, etc. in the changelog.
Whenever I run SambaDroid it will fail to start unless I open the SELinuxModeChanger app and change the mode to Permissive first, which of course ruins SafetyNet, so I can't just leave it in that mode all the time.
I have to go back and change it to Enforcing when I am done.
An extra step I'm hoping won't be required in the future. Perhaps on a per-app basis like MagiskHide.
Should the recent changes to Magisk allow me to run SambaDroid without having to manually change the SELinux Mode?
If so, it doesn't work yet, but maybe I am misunderstanding the changelog references.
Click to expand...
Click to collapse
The update in v11 you're talking about should be able to hide permissive SELinux from SafetNet. In other words: you should be able to leave SELinux permissive and still pass SafetyNet with the help of Magisk Hide.
Didgeridoohan said:
The update in v11 you're talking about should be able to hide permissive SELinux from SafetNet. In other words: you should be able to leave SELinux permissive and still pass SafetyNet with the help of Magisk Hide.
Click to expand...
Click to collapse
Ahh okay, I get it. Just tested it now and it works exactly like you described. It wouldn't pass SafetyNet before on the previous version but apparently does now after the upgrade when left in permissive. Thanks!
Nevermind my last post... Picked up the phone again, and opened SELinuxModeChanger and found that it had reverted back to enforcing on its own. Changed it to permissive, and then went back to Magisk Manager, and SafetyNet fails until I revert the setting back to enforcing. Seems like it works the first time, and then stops?
andrewsfm said:
Nevermind my last post... Picked up the phone again, and opened SELinuxModeChanger and found that it had reverted back to enforcing on its own. Changed it to permissive, and then went back to Magisk Manager, and SafetyNet fails until I revert the setting back to enforcing. Seems like it works the first time, and then stops?
Click to expand...
Click to collapse
Hmm... Interesting. I think I'll do some tests myself.
andrewsfm said:
Nevermind my last post... Picked up the phone again, and opened SELinuxModeChanger and found that it had reverted back to enforcing on its own. Changed it to permissive, and then went back to Magisk Manager, and SafetyNet fails until I revert the setting back to enforcing. Seems like it works the first time, and then stops?
Click to expand...
Click to collapse
Ok. I've tested and it seems to work as expected.
What I did was add a file in /magisk/.core/post-fs-data.d named 08setperm (doesn't matter what the file is named). In that file I added:
#!/system/sh
setenforce 0
This way SELinux is set to permissive at boot.
Disabled Magisk Hide, rebooted and verified that SELinux now was set to permissive on boot (typed getenforce in Teminal Emulator).
Enabled Magisk Hide again and voila! Typing getenforce in Terminal emulator now reported Enforcing and SafetyNet passed.
No idea if this will make SambaDroid work though...
I found a way to somewhat replicate what I am experiencing.
You'll need SELinuxModeChanger (SELMC) to see if you get the same results.
Although I'm wondering if it may be the cause of the problem...
Open recent apps and clear everything out.
Open SELMC and change to permissive.
Hit the home button.
Launch Magisk Manager and check SN. Should pass.
Hit the home button.
Clear recent apps.
Open SELMC, and it's back to enforcing.
Change back to permissive.
Hit the home button.
Re-launch MM and check SN, and it comes back CTS fail.
If you stay in MM and wait for a while, occasionally clicking check SN, eventually, it'll pass without changing anything.
If you change tasks over to SELMC, you'll see it's still in permissive as well.
It appears the transition from enforcing to permissive causes SN to fail for a while, and SELMC reverts back to enforcing if cleared from recent tasks, and re-activating it causes SN to fail for a period of time?
andrewsfm said:
I found a way to somewhat replicate what I am experiencing.
You'll need SELinuxModeChanger (SELMC) to see if you get the same results.
Although I'm wondering if it may be the cause of the problem...
Open recent apps and clear everything out.
Open SELMC and change to permissive.
Hit the home button.
Launch Magisk Manager and check SN. Should pass.
Hit the home button.
Clear recent apps.
Open SELMC, and it's back to enforcing.
Change back to permissive.
Hit the home button.
Re-launch MM and check SN, and it comes back CTS fail.
If you stay in MM and wait for a while, occasionally clicking check SN, eventually, it'll pass without changing anything.
If you change tasks over to SELMC, you'll see it's still in permissive as well.
It appears the transition from enforcing to permissive causes SN to fail for a while, and SELMC reverts back to enforcing if cleared from recent tasks, and re-activating it causes SN to fail for a period of time?
Click to expand...
Click to collapse
Sounds like MagiskHide deamon takes a short wile to start up after the change, or something like that. Seems normal to me... If you wan't a more permanent solution than SELMC, try using the script I posted earlier.
Didgeridoohan said:
Sounds like MagiskHide deamon takes a short wile to start up after the change, or something like that. Seems normal to me... If you wan't a more permanent solution than SELMC, try using the script I posted earlier.
Click to expand...
Click to collapse
I gave your script a try, but it didn't work.
I created the file with the same contents/name by copy/paste, and put it in the folder you specified using Root Explorer.
Rebooted the phone, and checked selinux status using "sestatus" and it said enforcing.
Tried manually typing in the commands in your post into terminal emulator...
#!/system/sh (which didn't show a response.)
setenforce 0 (responded "Couldn't set enforcing to 0. Permission denied.")
So I tried...
su
setenforce 0
After that it shows permissive.
Ran SambaDroid, and it works fine, and SN passes.
Suggestions as to what is stopping permissive from applying at boot using your method?
What does #!/system/sh do?
Sorry, I don't know much about Linux, but I'm open to learning.
andrewsfm said:
...
Suggestions as to what is stopping permissive from applying at boot using your method?
What does #!/system/sh do?
Sorry, I don't know much about Linux, but I'm open to learning.
Click to expand...
Click to collapse
https://en.wikipedia.org/wiki/Shebang_(Unix)
MagiskHide sets pseudo-enforcing since Magisk 11 because enforcing is needed to pass SafetyNet
andrewsfm said:
I gave your script a try, but it didn't work.
I created the file with the same contents/name by copy/paste, and put it in the folder you specified using Root Explorer.
Rebooted the phone, and checked selinux status using "sestatus" and it said enforcing.
Tried manually typing in the commands in your post into terminal emulator...
#!/system/sh (which didn't show a response.)
setenforce 0 (responded "Couldn't set enforcing to 0. Permission denied.")
So I tried...
su
setenforce 0
After that it shows permissive.
Ran SambaDroid, and it works fine, and SN passes.
Suggestions as to what is stopping permissive from applying at boot using your method?
What does #!/system/sh do?
Sorry, I don't know much about Linux, but I'm open to learning.
Click to expand...
Click to collapse
Could be that your file doesn't have the proper line endings. What text editor did you use (Notepad doesn't work)?
I'm attaching the file I used. Unzip it and place it in /magisk/.core/post-fs-data.d, reboot and see if that works.
By the way, I just realised I mistyped earlier. Not at all what i had named the file... Fingers going on auto I guess. Updated my earlier post.
Didgeridoohan said:
Could be that your file doesn't have the proper line endings. What text editor did you use (Notepad doesn't work)?
I'm attaching the file I used. Unzip it and place it in /magisk/.core/post-fs-data.d, reboot and see if that works.
By the way, I just realised I mistyped earlier. Not at all what i had named the file... Fingers going on auto I guess. Updated my earlier post.
Click to expand...
Click to collapse
Yeah, I used notepad... Should have used UltraEdit I guess?
Just downloaded your script and installed it, and it works fine now.
SambaDroid worked right off the bat without needing to remember to open SELMC every time before and after.
Thanks!
Didgeridoohan said:
Could be that your file doesn't have the proper line endings. What text editor did you use (Notepad doesn't work)?
I'm attaching the file I used. Unzip it and place it in /magisk/.core/post-fs-data.d, reboot and see if that works.
By the way, I just realised I mistyped earlier. Not at all what i had named the file... Fingers going on auto I guess. Updated my earlier post.
Click to expand...
Click to collapse
Is this a bug in Magisk?
Meowdib said:
Is this a bug in Magisk?
Click to expand...
Click to collapse
No. Why do you think that?
andrewsfm said:
Nevermind my last post... Picked up the phone again, and opened SELinuxModeChanger and found that it had reverted back to enforcing on its own. Changed it to permissive, and then went back to Magisk Manager, and SafetyNet fails until I revert the setting back to enforcing. Seems like it works the first time, and then stops?
Click to expand...
Click to collapse
I have an S7 and a modified stock kernel with SELinux permissive. I enabled Magisk hide and only enabled SystemUI and SafetyNet passed.
Sent from my S7.
andrewsfm said:
Yeah, I used notepad... Should have used UltraEdit I guess?
Just downloaded your script and installed it, and it works fine now.
SambaDroid worked right off the bat without needing to remember to open SELMC every time before and after.
Thanks!
Click to expand...
Click to collapse
Sorry for reviving a somewhat old thread. I was just curious if with this script, do apps that need SELinux Permissive work, AND SafetyNet still passes? Thanks!
jbw716 said:
Sorry for reviving a somewhat old thread. I was just curious if with this script, do apps that need SELinux Permissive work, AND SafetyNet still passes? Thanks!
Click to expand...
Click to collapse
Magisk Hide have a pseudo-enforcing feature that will make SELinux seem enforcing to hidden apps, even though it's permissive. Including SafetyNet.
So the answer to your question is: yes.
I request a thread regarding this issue. The script is very helpfull and i currently dont know any other way making selinux stay permanently on permissive. Many people are having this issue with soundmods like arise which require permissive selinux. Thnaks!!
nadejo said:
I request a thread regarding this issue. The script is very helpfull and i currently dont know any other way making selinux stay permanently on permissive. Many people are having this issue with soundmods like arise which require permissive selinux. Thnaks!!
Click to expand...
Click to collapse
Are you asking for a module to install the necessary script? Like I've provided here https://forum.xda-developers.com/apps/magisk/module-magisk-selinux-permissive-script-t3577549.
AS OF 03/07/2018
Support and development of this module have been discontinued.
A replacement module can be found here : https://forum.xda-developers.com/apps/magisk/module-magisk-selinux-manager-t3760042
This is a very simple module that installs a post-fs-data.sh script which enables SELinux Permissive Mode. This is useful for certain audio mods and removes the need to understand Magisk's file system & boot logic. No need to create your own scripts, just flash and forget.
I have only tested this on my Verizon HTC 10, but this module is so simple and generic that it should work on any Android device with SELinux.
This module has been tested on and is compatible with Magisk v11.6-15.2.
Disclaimer & Recommendations: This module should be used as a last resort only if appropriate SELinux Permissions can not be generated and injected into the SELinux Policy using selinux-inject, supolicy or magiskpolicy. Putting your device into Permissive Mode will essentially disable all of the operating system level security built into Android and allow any app in any context to do whatever it wants. Actions requiring root access will still trigger your SU Manager App, but all apps have elevated privileges due to permissive and may be able to take malicious actions on your device without needing root access. If you find that this module fixes issues you are experiencing with an app I recommend contacting the app developer and trying to work with them to isolate the necessary SELinux Permissions and have them injected into the SELinux Policy at startup.
Here is a discussion of some of concerns to consider when running your device in Permissive Mode : https://forum.xda-developers.com/general/general/discussion-root-selinux-risks-t3607295
Github Repo : https://github.com/Jman420/magisk-permissive-script
Change Log :
v1.0 - Initial Release
v1.1 - Update to Module Template v1400
v1.2 - Update to Module Template v1500
thank you brother!
LeEco LePro 3 Atmos can work finally!
huaiyue said:
thank you brother!
Can you tell me how to install LeEco LePro 3 Atmos ?
I hava supersu systemless.
Click to expand...
Click to collapse
These two things are completely unrelated.
If you want to install something, you install it. There's not much more to that.
huaiyue said:
thank you brother!
Can you tell me how to install LeEco LePro 3 Atmos ?
I hava supersu systemless.
Click to expand...
Click to collapse
In Magisk, go to the Modules section, and select the "+", and select the zip you downloaded.
Jman420 said:
This is a very simple module that installs a post-fs-data.sh script which enables SELinux Permissive Mode. This is useful for certain audio mods and removes the need to understand Magisk's file system & boot logic. No need to create your own scripts, just flash and forget.
I have only tested this on my Verizon HTC 10, but this module is so simple and generic that it should work on any Android device with SELinux.
Github Repo : https://github.com/Jman420/magisk-permissive-script
Click to expand...
Click to collapse
LeEco LePro 3 Atmos can work
however
xposed systemless failed.
---------- Post added at 01:32 ---------- Previous post was at 01:31 ----------
ahrion said:
These two things are completely unrelated.
If you want to install something, you install it. There's not much more to that.
Click to expand...
Click to collapse
http://imgur.com/a/Sbf9p
dolby fc.
---------- Post added at 01:36 ---------- Previous post was at 01:32 ----------
jhedfors said:
In Magisk, go to the Modules section, and select the "+", and select the zip you downloaded.
Click to expand...
Click to collapse
thank you brother!
Thanks a lot
huaiyue said:
thank you brother!
LeEco LePro 3 Atmos can work finally!
Click to expand...
Click to collapse
Regarding your other post mentioning Xposed (which I'm not quoting cause it's a mess). I'm running on Nougat so I can't use Xposed and haven't tested with it. If you give me more details I can try to determine what the issue is. Logs, error messages, symptoms would all be helpful.
Thor™ said:
Thanks a lot
Click to expand...
Click to collapse
I aim to please
I don't understand why this mod is usefull. In the latest version of magisk, there is a semi enforce/permissive linux bypass. The system thinks it's enforced, but in reality is permissive. Or maybe I didn't fully understand it?
its working with s5neo?
I've just flashed this zip. This allows Viper4Android to run in enforcing mode:
https://www.dropbox.com/s/k9cnruw2e1t1d4t/ViPER4Android-supolicy.zip?dl=0
I forgot the source. Maybe Google it
matssa said:
I don't understand why this mod is usefull. In the latest version of magisk, there is a semi enforce/permissive linux bypass. The system thinks it's enforced, but in reality is permissive. Or maybe I didn't fully understand it?
Click to expand...
Click to collapse
I agree that Magisk hides the actual SELinux Mode in such a way that if Magisk Hide is enabled the 'getenforce' command always returns 'Enforcing'. But if you do not run the 'setenforce 0' command the SELinux mode will still be set to 'Enforcing' rather than 'Permissive'. This script puts the SELinux mode into 'Permissive' at startup. Magisk Hide will still hide the fact that you are in Permissive Mode, which I believe is the 'pseudo permissive' mode that Magisk describes. But I can not find any settings or commands within Magisk that enable Permissive Mode.
htr5 said:
I've just flashed this zip. This allows Viper4Android to run in enforcing mode:
https://www.dropbox.com/s/k9cnruw2e1t1d4t/ViPER4Android-supolicy.zip?dl=0
I forgot the source. Maybe Google it
Click to expand...
Click to collapse
It's just a shell script, the source is in the zip file. This is really helpful and is the direction I want to take this project. Permissive Mode is great in that it gets the Apps/Mods that we want to run to work, but I consider it the equivalent of using a sledgehammer to hammer in a finishing nail. I would much rather be able to grant the specific permissions that each App needs rather than enable all permissions for all apps (which is what permissive mode does).
I plan on trying to develop an App which will assist in managing and generating a script which uses 'supolicy' to inject individual SELinux Policy Permissions. I had planned on using the Dolby Atmos LePro3 build as a guinea pig to try to isolate which permissions it needs and put together the supolicy command for them. I've hit a bit of a roadblock in verifying my supolicy command due to the format that the SELinux Policy is stored in on the device. I've found a project called sedump (https://ge0n0sis.github.io/posts/2015/12/exploring-androids-selinux-kernel-policy/) which claims to deserialize the Binary SELinux Policy to a readable format, but I can't seem to get it to work... the process seems to complete, but it generates an empty file... If anyone has experience with SELinux I'd really appreciate any feedback.
cosmin691 said:
its working with s5neo?
Click to expand...
Click to collapse
Dunno, I've only got an HTC 10 for testing. Give it a shot, if it doesn't work just uninstall the Magisk Package. Remember to disable Magisk Hide if you are testing to make sure it actually put your phone into Permissive Mode by using the 'getenforce' command.
It works for oneplus 3t on freedom OS rom.
Jman420 said:
This is a very simple module that installs a post-fs-data.sh script which enables SELinux Permissive Mode. This is useful for certain audio mods and removes the need to understand Magisk's file system & boot logic. No need to create your own scripts, just flash and forget.
I have only tested this on my Verizon HTC 10, but this module is so simple and generic that it should work on any Android device with SELinux.
Github Repo : https://github.com/Jman420/magisk-permissive-script
Click to expand...
Click to collapse
this zip must be flashed using twrp rite ? or stock recovery also will do fine ? because i tried many times to flash recovery for samsung e5 5.1.1 but ended up with boot loop. now running all stock !!
X_GOD said:
this zip must be flashed using twrp rite ? or stock recovery also will do fine ? because i tried many times to flash recovery for samsung e5 5.1.1 but ended up with boot loop. now running all stock !!
Click to expand...
Click to collapse
Should be able to install it through Magisk Manager or TWRP. Let me know if you have problems.
matssa said:
I don't understand why this mod is usefull. In the latest version of magisk, there is a semi enforce/permissive linux bypass. The system thinks it's enforced, but in reality is permissive. Or maybe I didn't fully understand it?
Click to expand...
Click to collapse
Now, I have magisk 11.6 on EMUI marshmallows V4A driver was abnormal because Enforcing selinux. Same happened with SuperSU 2.79. When I changed to permissive mode using terminal emulato/kernerl aduitor init.d script emulator/su.d SuperSU script, V4A driver was normal and it was processing. I like Magisk a lot because of its xposed like modules. Now using jman420's permissive magisk module.
Thor™ said:
Now, I have magisk 11.6 on EMUI marshmallows V4A driver was abnormal because Enforcing selinux. Same happened with SuperSU 2.79. When I changed to permissive mode using terminal emulato/kernerl aduitor init.d script emulator/su.d SuperSU script, V4A driver was normal and it was processing. I like Magisk a lot because of its xposed like modules. Now using jman420's permissive magisk module.
Click to expand...
Click to collapse
Without this module, ARISE is working fine, processing in 48000 on my side, so for V4A I don't think this is necessary, at least on my side.
Sent from my OnePlus3 using XDA Labs
matssa said:
Without this module, ARISE is working fine, processing in 48000 on my side, so for V4A I don't think this is necessary, at least on my side.
Click to expand...
Click to collapse
For ARISE I used to flash permissive script by osm0sis. Otherwise no luck with V4A, AM3D and Dolby.
Thor™ said:
For ARISE I used to flash permissive script by osm0sis. Otherwise no luck with V4A, AM3D and Dolby.
Click to expand...
Click to collapse
Strange... Did you enable magisk hide? If not, that is the reason.
Sent from my OnePlus3 using XDA Labs
matssa said:
Strange... Did you enable magisk hide? If not, that is the reason.
Click to expand...
Click to collapse
No, I was using SuperSU 2.79. Same happened with MagiskSU.
INCREASE VOLUME STEPS
Yep, that's just it. It increases volume steps, but it doesn't make your sound louder.
By default, it increases vol steps by 30.
You can customize the volume steps by doing this command in terminal emulator:
Code:
vol_magisk
You can then enter your choice.
And then reboot to apply the change.
GitHub
Downloads
Changelogs
v1 - Initial release
v1.2 - Fixed a couple of issues
- New UI (vol_magisk)
- Now shows Value to be applied
- Now shows current version and version code
v2 - Update module template
mine2
Good mate?
Inviato dal mio LEX720 utilizzando Tapatalk
N1m0Y said:
Good mate
Inviato dal mio LEX720 utilizzando Tapatalk
Click to expand...
Click to collapse
Thanks, this is just a test module for me. I'm new to magisk
After installation, rebooted and then my supersu says I need to update my binary. I try to update but failed. I go to magisk manager and then the magisk framework (12.0) didn't detect correctly. I disable the module and it back to normal.
vhick said:
After installation, rebooted and then my supersu says I need to update my binary. I try to update but failed. I go to magisk manager and then the magisk framework (12.0) didn't detect correctly. I disable the module and it back to normal.
Click to expand...
Click to collapse
I don't know about that. I don't think it affects su since it just sets a build property and a script in /system/bin. I use magisk su but no problems.
veez21 said:
I don't know about that. I don't think it affects su since it just sets a build property and a script in /system/bin. I use magisk su but no problems.
Click to expand...
Click to collapse
I don't use magisksu because I have a problem sticking permissive selinux status, if you know how to stick permanently permissive selinux in magisksu, please let me know and I will glad to shift to magisksu.
Sent from my AndroidOne SEED using Tapatalk
vhick said:
I don't use magisksu because I have a problem sticking permissive selinux status, if you know how to stick permanently permissive selinux in magisksu, please let me know and I will glad to shift to magisksu.
Sent from my AndroidOne SEED using Tapatalk
Click to expand...
Click to collapse
Put the following in a file (name doesn't really matter) in /magisk/.core/post-fs-data.d:
Code:
#!/system/bin/sh
setenforce 0
That'll set SELinux to permissive at boot.
vhick said:
I don't use magisksu because I have a problem sticking permissive selinux status, if you know how to stick permanently permissive selinux in magisksu, please let me know and I will glad to shift to magisksu.
Sent from my AndroidOne SEED using Tapatalk
Click to expand...
Click to collapse
Didgeridoohan said:
Put the following in a file (name doesn't really matter) in /magisk/.core/post-fs-data.d:
Code:
#!/system/bin/sh
setenforce 0
That'll set SELinux to permissive at boot.
Click to expand...
Click to collapse
What @Didgeridoohan said
Didgeridoohan said:
Put the following in a file (name doesn't really matter) in /magisk/.core/post-fs-data.d:
Code:
#!/system/bin/sh
setenforce 0
That'll set SELinux to permissive at boot.
Click to expand...
Click to collapse
veez21 said:
What @Didgeridoohan said
Click to expand...
Click to collapse
Thanks guys. I having a hard time to get it work. Now my problem is the permission of the script. When I set it to 777, it always go back to 755.
Sent from my H220 using Tapatalk
vhick said:
Put the following in a file (name doesn't really matter) in /magisk/.core/post-fs-data.d:
Thanks guys. I having a hard time to get it work. Now my problem is the permission of the script. When I set it to 777, it always go back to 755.
Click to expand...
Click to collapse
why set it to 777? 755 is good enough since we have root and all the execute permissions are granted.
vhick said:
Thanks guys. I having a hard time to get it work. Now my problem is the permission of the script. When I set it to 777, it always go back to 755.
Sent from my H220 using Tapatalk
Click to expand...
Click to collapse
You shouldn't have to worry about permissions on the scripts placed in post-fs-data.d and 755 should be enough. What is it that doesn't work?
Edit: Dammit! To slow this time...
veez21 said:
why set it to 777? 755 is good enough since we have root and all the execute permissions are granted.
Click to expand...
Click to collapse
I don't know. When it comes to permission for permissive, it never work on 755, it work on 777.
Sent from my H220 using Tapatalk
vhick said:
I don't know. When it comes to permission for permissive, it never work on 755, it work on 777.
Click to expand...
Click to collapse
Ok, I'll update it to 777 in the next release. Also, for it to probably work for you for now, extract the zip and then edit config.sh. Then go to the bottom, you should find this line:
set_perm $MODPATH/system/bin/vol_magisk 0 0 0755
replace 0755 with 0777 and repack and then flash. See if it works
EDIT: What's the output when you try to run vol_magisk in terminal emulator while in 755?
veez21 said:
Ok, I'll update it to 777 in the next release. Also, for it to probably work for you for now, extract the zip and then edit config.sh. Then go to the bottom, you should find this line:
set_perm $MODPATH/system/bin/vol_magisk 0 0 0755
replace 0755 with 0777 and repack and then flash. See if it works
EDIT: What's the output when you try to run vol_magisk in terminal emulator while in 755?
Click to expand...
Click to collapse
There's a slight misunderstanding here sir. The module is working in enforce. It just that I need to set my selinux to permissive because my other modules didn't work in enforce like sd write access module that only work on permissive selinux. And I only achieve stable permissive in edited boot.img with supersu.
Sent from my H220 using Tapatalk
vhick said:
There's a slight misunderstanding here sir. The module is working in enforce. It just that I need to set my selinux to permissive because my other modules didn't work in enforce like sd write access module that only work on permissive selinux. And I only achieve stable permissive in edited boot.img with supersu.
Click to expand...
Click to collapse
So this module doesn't work on permissive? The volume steps only increased while on enforcing?
vhick said:
There's a slight misunderstanding here sir. The module is working in enforce. It just that I need to set my selinux to permissive because my other modules didn't work in enforce like sd write access module that only work on permissive selinux. And I only achieve stable permissive in edited boot.img with supersu.
Click to expand...
Click to collapse
Also, keep in mind that it only works on media volume. Go to any music player app and play a song and see if it works.
veez21 said:
So this module doesn't work on permissive? The volume steps only increased while on enforcing?
Click to expand...
Click to collapse
Now I get it work.[emoji1]
Suggestion: make a selection if I decided to change. For example, enter number or type c to cancel.
Sent from my Android One SEED using Tapatalk
vhick said:
Now I get it work.[emoji1]
Click to expand...
Click to collapse
Cool, what did you do to make it work?
Hello all
viper4android refreshes very rarely and can not keep up with nexus / pixels.
I have seen many guides that suggested deleting the configuration file in /etc/audio_effects.conf.
I think it's a horrible thing! in fact, just insert few strings into another file in /vendor/etc/audio_effects.conf
Under libraries sections:
v4a_fx {
path /system/lib/soundfx/libv4a_fx_ics.so
}
Under effects sections:
v4a_standard_fx {
library v4a_fx
uuid 41d3c987-e6cf-11e3-a88a-11aba5d5c51b
}
it is very important that selinux is set to permissive mode.
Open a Shell :
$ su
# setenforce 0
P.S. install busybox first
MT88 said:
Hello all
viper4android refreshes very rarely and can not keep up with nexus / pixels.
I have seen many guides that suggested deleting the configuration file in /etc/audio_effects.conf.
I think it's a horrible thing! in fact, just insert few strings into another file in /vendor/etc/audio_effects.conf
Under libraries sections:
v4a_fx {
path /system/lib/soundfx/libv4a_fx_ics.so
}
Under effects sections:
v4a_standard_fx {
library v4a_fx
uuid 41d3c987-e6cf-11e3-a88a-11aba5d5c51b
}
it is very important that selinux is set to permissive mode.
Open a Shell :
$ su
# setenforce 0
Click to expand...
Click to collapse
Good guide but that setenforce 0 command doesn't stick after reboot as far as I know. To get it to stick you should use an app that does it or create a .sh file and add the permissive kernel code to it. Can't remember where the file goes though.
DEVILOPS 007 said:
Good guide but that setenforce 0 command doesn't stick after reboot as far as I know. To get it to stick you should use an app that does it or create a .sh file and add the permissive kernel code to it. Can't remember where the file goes though.
Click to expand...
Click to collapse
In viper's app there is an option "disable selinux".
You only have to go permissive with magisk and there's an module for it.
With SuperSU you can stay enforced.
Delete musicfx or audiofx and you're good.
Been trying for days to get viper to work,thanks man.works for me
coremania said:
You only have to go permissive with magisk and there's an module for it.
With SuperSU you can stay enforced.
Delete musicfx or audiofx and you're good.
Click to expand...
Click to collapse
personally I prefer to add two lines of code instead of installing an application that allows another application to work
Right very good guide, but you have to go and live permissive with it. The question is, what's better. If you root anyway ???
coremania said:
Right very good guide, but you have to go and live permissive with it. The question is, what's better. If you root anyway ???
Click to expand...
Click to collapse
this is a problem to be submitted to the viper developer
MT88 said:
personally I prefer to add two lines of code instead of installing an application that allows another application to work
Click to expand...
Click to collapse
Dev,you wouldn't happen to know how to get ATMOS working would you?
I prefer to go permissive as well, besides the fact that I'm always permissive even when I don't have V4A installed.
Also, you don't have to install an app, you just put a permissive script in your init.d(if not using Magisk). For Magisk, you put it in /magisk/.core/service.d/.
I've created my own flashable zips to do this, and since it's Magisk, as long as I don't clean flash, I never have to worry about it. [emoji41]
Sent from my Nexus 6P using Tapatalk
Curiousn00b said:
I prefer to go permissive as well, besides the fact that I'm always permissive even when I don't have V4A installed.
Also, you don't have to install an app, you just put a permissive script in your init.d(if not using Magisk). For Magisk, you put it in /magisk/.core/service.d/.
I've created my own flashable zips to do this, and since it's Magisk, as long as I don't clean flash, I never have to worry about it. [emoji41]
Click to expand...
Click to collapse
here we talk about viper. Magisk and company should be treated elsewhere. Just create an init file for selinux.
Not a Magisk module. If you're using Magisk, you can't stick the init.d script in /system/etc/init.d/ since the system won't being using that location IF you're using Magisk. That's why I included both locations just in case someone that's using Magisk came across the post.
Either way, I was still talking about Viper.
Sent from my Nexus 6P using Tapatalk
I've been using latest Magnum opus on 8.1 without any problems or changes needed to the system. And it works perfectly fine with viper+Dolby config
coremania said:
You only have to go permissive with magisk and there's an module for it.
With SuperSU you can stay enforced.
Delete musicfx or audiofx and you're good.
Click to expand...
Click to collapse
Maybe you can. Have never had ARISE or Viper work without permissive, on either Magisk or SuperSU.
Not maybe, supersu makes it possible to stay enforced with viper and dolby. With magisk Viper might be possible enforced but dolby will run only permissive with magisk.
Tested so many times.
coremania said:
Not maybe, supersu makes it possible to stay enforced with viper and dolby. With magisk Viper might be possible enforced but dolby will run only permissive with magisk.
Tested so many times.
Click to expand...
Click to collapse
Wrong.
snsone said:
Wrong.
Click to expand...
Click to collapse
After every reboot I guess
coremania said:
After every reboot I guess
Click to expand...
Click to collapse
Works after any reboot with enforcing, no need for permissive
Deleted
@snsone are you using android oreo? And if so, how are you doing that?
I have installed a xposed's module that requires Selinux in permissive mode to work.
How do I know what status Selinux is in on my Note 9?
pupido said:
I have installed a xposed's module that requires Selinux in permissive mode to work.
How do I know what status Selinux is in on my Note 9?
Click to expand...
Click to collapse
Depending on how is kernel see if kernel has seelinux permissive