[MODULE][TERMINAL EMU] Increase Volume Steps + UI - Magisk

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?

Related

ViPER4Android 2.5.0.5

Please note, this requires SELinux Permissive (included init.d script/instructions for PHH). It will not work on Enforcing, even with supolicy (I've tried. If anyone has an idea how to get it working with "soundserver" and setting supolicy "read write execute", please let me know)
Setting SELinux to Permissive is a security risk.
ViPER4Android for Mate 9
Slightly modified guitardedhero script.
Contains "Kernel" and "Profile" for V4A from auras76 kang rom
Note:
The following files are backed up automatically so you can easily revert with the removal script:
/system/lib/soundfx/libeffectproxy.so -> /system/lib/soundfx/libeffectproxy.so.bak
/system/etc/audio_effects.conf -> /system/etc/audio_effects.conf.bak
/vendor/etc/audio_effects.conf -> /vendor/etc/audio_effects.conf.bak
If those .bak files are not found the removal script won't run (to prevent running it without V4A installed, it would simply just remove the files leaving you with no files at all.)
It does not edit audio_policy.conf as it doesn't have the deep_buffer section in it, so no point in having it edited.
Requirements:
SuperRoot/SuperSU (No verity is probably needed as we're modifying both /system and /vendor)
A way to set SELinux to Permissive (SuperSU init.d/phh 'su --init' or SELinuxToggler, see 'Alternative'.)
If you're on Magisk use the V4A module instead
For SuperSU
If you use the one posted above
Simply flash the zip in TWRP and you should be good to go. It copies the 00selinux script directly to /system/etc/init.d/ and runs at boot so you'll have SELinux set to Permissive after flashing.
For PHH su
Flash the zip in TWRP, boot up fully.
Now open a terminal and issue the command
Code:
su --init /system/etc/init.d/00selinux
Then reboot.
To remove the phh init use 'su --init !/system/etc/init.d/00selinux'.
For Magisk
Search for Viper4Android in the Downloads section in Magisk Manager, it's a module so no need to download anything in this thread
Alternative:
(You still need root for this but no init script.)
SELinuxSwitch by @Ibuprophen
Download:
ViPER4Android 2.5.0.5
Dropbox Mirror
Removal script download:
Removal script
Removal script Dropbox Mirror
Thanks to V4A team,
guitardedhero for his script,
auras76 for the profiles/makers of said profiles,
Ibuprofen for The SELinux Switch.
@ante0 bro thanks for porting it... have a question, we have to mount system in terminal for writting in system partition,,, can i use init to mount system rw for all time so that i dont need to give command everytime
HassanMirza01 said:
@ante0 bro thanks for porting it... have a question, we have to mount system in terminal for writting in system partition,,, can i use init to mount system rw for all time so that i dont need to give command everytime
Click to expand...
Click to collapse
Yes, if you use supersu, make a script in /system/etc/init.d/
Code:
#!/system/bin/sh
mount -o rw,remount /system
Make sure it runs after any other scripts if they remount system to read only. Scripts are loaded in order, so name it accordingly.
If you use phh, place script where you want and from a terminal
Code:
su --init /path/to/script
I wanna put all this in my Kernel... Or boot.img...
I have root in my kernel using phh superuser... I dont want to add anything in system by myself, i want that a zip should do it... Will be best if kernel did all this... In MM, we dont need to do rw ourself, in N we needed...
Also, am not a dev, just a pro member, know how to edit and understand commands etc...
May I ask whats the difference between this and Viper4Arise.
HassanMirza01 said:
I wanna put all this in my Kernel... Or boot.img...
I have root in my kernel using phh superuser... I dont want to add anything in system by myself, i want that a zip should do it... Will be best if kernel did all this... In MM, we dont need to do rw ourself, in N we needed...
Also, am not a dev, just a pro member, know how to edit and understand commands etc...
Click to expand...
Click to collapse
I sent you a pm instead
ante0 said:
I sent you a pm instead
Click to expand...
Click to collapse
Sure bro... Am waiting... And i have somehow injected phh superuser r275 in boot.img... I will be thankful if u tell me the whole correct procedure to inject files of superuser zip in boot.img.... By flashing superuser r275 on stock boot, we can have root but on that root, titanium like apps didnot work :/
SlyUK said:
May I ask whats the difference between this and Viper4Arise.
Click to expand...
Click to collapse
Arise is based off of V4A, but with their own audio effects and a modified V4A app.
https://www.reddit.com/r/androidapps/comments/5dpvcz/slug/da6ux9k
SlyUK said:
May I ask whats the difference between this and Viper4Arise.
Click to expand...
Click to collapse
It's just a skin difference. Viper4Arise is themed by an arise member. The only difference is the theme.
ante0 said:
Arise is based off of V4A, but with their own audio effects and a modified V4A app.
https://www.reddit.com/r/androidapps/comments/5dpvcz/slug/da6ux9k
Click to expand...
Click to collapse
Hello,
Will V4A work on P9, P9 plus and P9 lite if we flash those files?
Coolyou said:
Hello,
Will V4A work on P9, P9 plus and P9 lite if we flash those files?
Click to expand...
Click to collapse
I don't know. But I don't see why it wouldn't.
Backup system and try.
You'll have to use the phh init script though as I don't think supersu works with P9 on emui5?
Edit: actually, if your audio_effects.conf file is not in /system/etc/ or /vendor/etc/ the script needs to be modified. And if your audio_policy.conf contains the deep_buffer section.
You guys can use this app for switching SELinux to Permissive - https://forum.xda-developers.com/android/apps-games/app-selinuxtoggler-t3574688
It was featured a few days back on XDA blog, hope it will help the users.
DJBhardwaj said:
You guys can use this app for switching SELinux to Permissive - https://forum.xda-developers.com/android/apps-games/app-selinuxtoggler-t3574688
It was featured a few days back on XDA blog, hope it will help the users.
Click to expand...
Click to collapse
Oh, he finally released it
I'll update OP, thanks for heads-up.
Works like a charm, thanks
hi..I'm on aura's rom. and I can't install drivers. can you please teach me how can I make it work..thanks
s2pfie said:
hi..I'm on aura's rom. and I can't install drivers. can you please teach me how can I make it work..thanks
Click to expand...
Click to collapse
assuming everything else but the driver is installed,
simply download Viper4android_2.5.0.5_mate9.zip, extract.
go to customize/lib, rename libv4a_fx_jb_NEON.so to libv4a_fx_jb_ics.so
copy it to your phone.
Use a root file manager and copy and paste to /system/lib/soundfx/libv4a_fx_jb_ics.so.
And set permissions of that file to 0644 (RW-R--R--).
Then reboot and open up viper4android again and see if still complains.
If it doesn't, go to "hamburger" menu in V4A and tap on Driver Status, it should say Status: Normal. If it says abnormal something else is wrong.
ante0 said:
assuming everything else but the driver is installed,
simply download Viper4android_2.5.0.5_mate9.zip, extract.
go to customize/lib, rename libv4a_fx_jb_NEON.so to libv4a_fx_jb_ics.so
copy it to your phone.
Use a root file manager and copy and paste to /system/lib/soundfx/libv4a_fx_jb_ics.so.
And set permissions of that file to 0644 (RW-R--R--).
Then reboot and open up viper4android again and see if still complains.
If it doesn't, go to "hamburger" menu in V4A and tap on Driver Status, it should say Status: Normal. If it says abnormal something else is wrong.
Click to expand...
Click to collapse
thanks bro but still an error occurred..still abnormal
update:
just flashed your zip now its normal..thank you
@ante0, I just wanted to give you a quick heads up...
There's a new app (currently being beta tested) that will supercede/replace The SELinux Toggler....
It's a new app called "The SELinux Switch". Though, it will look like "The SELinux Toggler" but, I had to recreate, pretty much, the whole app.
The reason i had to do this is, primarily, to completely sever it from the older package name (or Installation Directory) that was also being used by the "SELinuxModeChanger" app.
I also had made some minor enhancements and a few compatibility improvements but, there's still some more improvements to be made.
In addition, the app has been passing the beta testing extremely well (thankfully after about 6 +/- months into it) and it should be released soon but, when the app has completed the beta testing and, ready for its debut, it will be released under a whole new thread.
Thank you all for your time, understanding and, especially, your support for my development.
Please let me know if you have any questions or concerns.
______________
PLEASE NOTE: I welcome any member to help with further valuable information/clarification for any of my posts.
Has anybody used the ARISE aroma installer (twrp flashable zip)? I've used it on a few other devices, coming to the M9 from a Le Pro 3 and it works nice and easy and patches selinux permanently. It seems the way Huawei does things is much different though, so I'd be suprised if it works as easily as on other phones.
In the end, it's just installing 2.5.0.5 anyway with a few other tweaks and a whole bunch of IRS response profiles. So that part's not very different.
Just a quick heads-up @ante0...
The SELinux Toggler has now Officially been Discontinued for the launching of the new app...
[APP][TOOL][4.2+][OFFICIAL]The SELinux Switch by Ibuprophen
Those of you who currently has The SELinux Toggler, and want to switch to The SELinux Switch, please be sure to read the OP for instructions.
Thank you ALL!
______________
PLEASE NOTE: I welcome any member to help with further valuable information/clarification for any of my posts.

[MODULE][DISCONTINUED] Magisk SELinux Permissive Script

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.

[GUIDE] Viper4android on oreo 8.0 stystem

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?

Viper4Android for Mate 10 Pro

Anyone had any luck getting viper4android to work with Mate 10 Pro
I tried several methods but the driver does not install
Thanks
waiting for it
Tried several things like flashing Viper4android with pre-installed drivers, which did not work as the app tells me to install the drivers again but fails at busybox not found.
Bordo_Bereli51 said:
Tried several things like flashing Viper4android with pre-installed drivers, which did not work as the app tells me to install the drivers again but fails at busybox not found.
Click to expand...
Click to collapse
What recovery did you try flashing with?
I used the app FlashFire from Chainfire. You can find it on Play Store. Make sure when you flash something with that app, select mount system R/W
Bordo_Bereli51 said:
I used the app FlashFire from Chainfire. You can find it on Play Store. Make sure when you flash something with that app, select mount system R/W
Click to expand...
Click to collapse
Where do you get the option to select mount system R/W, once you start flashing?
vibrantliker said:
Where do you get the option to select mount system R/W, once you start flashing?
Click to expand...
Click to collapse
Yes, when you select the zip-file it will automatically show you some Misc-Options, where you can select to mount system read write.
No One else getting anywhere with this?
Bordo_Bereli51 said:
Yes, when you select the zip-file it will automatically show you some Misc-Options, where you can select to mount system read write.
Click to expand...
Click to collapse
I just tried flashing with flash fire and it looked like it went through fine but it's nowhere to be found on phone after the reboot.
vibrantliker said:
I just tried flashing with flash fire and it looked like it went through fine but it's nowhere to be found on phone after the reboot.
Click to expand...
Click to collapse
Did you select Mount System R/W? Otherwise it will not work. If its still not working, then I do not know why. For me it worked but viper4android asked my always for installing busybox even though it is installed.
Bordo_Bereli51 said:
Did you select Mount System R/W? Otherwise it will not work. If its still not working, then I do not know why. For me it worked but viper4android asked my always for installing busybox even though it is installed.
Click to expand...
Click to collapse
I did Mount System R/W
vibrantliker said:
I just tried flashing with flash fire and it looked like it went through fine but it's nowhere to be found on phone after the reboot.
Click to expand...
Click to collapse
If you haven't removed Verity on system it would remove what was flashed on reboot. You can do this in /vendor/etc/fstab.kirin970
And you should remove verity off of the other partitions as well.
Etoerh way it probably won't work. I manually installed everything yesterday, including driver. This worked fine on Mate 9 Nougat without even installing driver.
And make sure you have busybox. I can't remember if it had busybox or su as a hardcoded path... I have su in /sbin/ and busybox applets symlinked to /sbin/ from su.d. Still no go. :/
I'll try some more later.
And a question, permissive is usually required, can you guys type in a terminal: setenforce 0
Or setenforce permissive?
I get invalid parameter, so Huawei might've tightened security.
With P10plus oreo setenforce do not work in terminal. I try to install viper4android too.
Gesendet von meinem VKY-L29 mit Tapatalk
ante0 said:
If you haven't removed Verity on system it would remove what was flashed on reboot. You can do this in /vendor/etc/fstab.kirin970
And you should remove verity off of the other partitions as well.
Etoerh way it probably won't work. I manually installed everything yesterday, including driver. This worked fine on Mate 9 Nougat without even installing driver.
And make sure you have busybox. I can't remember if it had busybox or su as a hardcoded path... I have su in /sbin/ and busybox applets symlinked to /sbin/ from su.d. Still no go. :/
I'll try some more later.
And a question, permissive is usually required, can you guys type in a terminal: setenforce 0
Or setenforce permissive?
I get invalid parameter, so Huawei might've tightened security.
Click to expand...
Click to collapse
Don't know why but Viper is having a hard time with Oreo. No problems on any phone with Nougat.
has anyone tried https://forum.xda-developers.com/nexus-6p/general/guide-installing-viper4android-t3250579 ?

Gigantic X - I detected the Root Magisk

Hello.
This game (GIGANTIC X) Me detects the access root Magisk, the hidden through "Magisk Hide" and when I restart it again detects me again and does not work.
https://play.google.com/store/apps/details?id=com.ActionSquare.GiganticX
D-Mak said:
Hello.
This game (GIGANTIC X) Me detects the access root Magisk, the hidden through "Magisk Hide" and when I restart it again detects me again and does not work.
https://play.google.com/store/apps/details?id=com.ActionSquare.GiganticX
Click to expand...
Click to collapse
Have you tried the v19.0 Beta ?
lahceneamine said:
Have you tried the v19.0 Beta ?
Click to expand...
Click to collapse
I just tried the V19.0 and the same thing happens.
any root-using apps installed or magisk.zip still in storage?
D-Mak said:
I just tried the V19.0 and the same thing happens.
Click to expand...
Click to collapse
Do you pass SAFETYNET with v19.0 ? If not, there's something wrong in your config.
Oh... it's using Lockin Company's Liapp(https://liapp.lockincomp.com/ )...
It's not a problem like misconfig since it detects Magisk itself. Liapp updates frequently to apply new root (especially Magisk) detection methods, so it's hard to bypass it.
(Magisk 17.3+ bypasses 5.0.0, 18.2+ bypasses 5.0.1, but 5.0.2+ cannot be bypassed currently.)
same here.cantplay it on root device,well that sucks.Im not gonna sacrifice my magisk for this game,not worth it
I made a bypass script for it (and all other apps using Liapp and UDS detection method)!
Download it on https://github.com/Ingan121/UDSBypass/blob/master/udsbypass and run 'su -c sh /sdcard/Download/udsbypass com.ActionSquare.GiganticX/com.epicgames.ue4.GameActivity'. Make sure you added this app to MagiskHide.
Ingan121 said:
I made a bypass script for it (and all other apps using Liapp and UDS detection method)!
Download it on https://github.com/Ingan121/UDSBypass/blob/master/udsbypass and run 'su -c sh /sdcard/Download/udsbypass com.ActionSquare.GiganticX/com.epicgames.ue4.GameActivity'. Make sure you added this app to MagiskHide.
Click to expand...
Click to collapse
Thanks! How do i use this script? i tried in terminal but it keep saying no such file or directory
Predatorhaze said:
Thanks! How do i use this script? i tried in terminal but it keep saying no such file or directory
Click to expand...
Click to collapse
Did you download it in Download folder? Then it should be started by 'sh /sdcard/Download/udsbypass' (without quotes).
Also, you can copy it to /sbin, chmod 755, and then just run 'udsbypass'.
Ingan121 said:
Did you download it in Download folder? Then it should be started by 'sh /sdcard/Download/udsbypass' (without quotes).
Also, you can copy it to /sbin, chmod 755, and then just run 'udsbypass'.
Click to expand...
Click to collapse
I copied the text and made a text file saved .sh..or do I something wrong here
Predatorhaze said:
I copied the text and made a text file saved .sh..or do I something wrong here
Click to expand...
Click to collapse
sh /sdcard/path/to/udsbypass.sh
Ingan121 said:
sh /sdcard/path/to/udsbypass.sh
Click to expand...
Click to collapse
I am a noob with this,I don't get it.Cant get it to work.I think will uninstall magisk
Predatorhaze said:
I am a noob with this,I don't get it.Cant get it to work.I think will uninstall magisk
Click to expand...
Click to collapse
Termux can't be used for this.
Use other terminal app.
Ingan121 said:
Termux can't be used for this.
Use other terminal app.
Click to expand...
Click to collapse
It can be used if you adjust the script to check for /sbin in $PATH and then add it if it isn't already there.
Or adjust the script to use the absolute paths to the Magisk binary, but that is a lot less elegant and won't work if the paths change.
Ingan121 said:
Termux can't be used for this.
Use other terminal app.
Click to expand...
Click to collapse
well then i try material terminal.
by the way im running pie gsi.
How is the game btw? is it good? bored fast?
Predatorhaze said:
well then i try material terminal.
by the way im running pie gsi.
How is the game btw? is it good? bored fast?
Click to expand...
Click to collapse
I didn't play it, just deleted immediately after succeeding to bypass.
Alright.i really want to play this game but i cant get this bypass to work.Can someone explain more clear steps?
Ingan121 said:
Did you download it in Download folder? Then it should be started by 'sh /sdcard/Download/udsbypass' (without quotes).
Also, you can copy it to /sbin, chmod 755, and then just run 'udsbypass'.
Click to expand...
Click to collapse
I managed to run the script by putting the file in /sbin but the game is still detecting root
Ingan121 said:
I didn't play it, just deleted immediately after succeeding to bypass.
Click to expand...
Click to collapse
can u explain with a short video the game has official release yesterday

Categories

Resources