if you using AUDIO MODIFICATION LIBRARY (AML) you may have to go to data/magisk/AML/v4a/yeah but im not able to find it "/magisk/v4a/system/etc/audio_effects.conf" is it located in the root directory.. In my freedom rom i can find only magisk folder with some arise sound config files, no v4A folder.
For v126.96.36.199Hello guys! I am with my OP3T and android 9 stock 9.0.6. I am root with magisk 20.4 and when I install the V4A it won't let me use it, I have the problem mentioned in the post. I have SOLID PRO installed but I don't see the path /magisk/v4a/system/etc/audio_effects.conf to be able to copy and paste the file, in which folder is it?
I think you are looking for files that would be under /data/adb/modules/ViPER4AndroidFX. But if its there, then magisk will mount it where it is destined to be.
This thread is FULL of advice, which part in particular are you referring to?Is this advice still current?
A hard link cannot cross partitions. ie you cannot do a hard link from data to system, so it would already need to be on system to hard link it to the system partition. This is what the Magisk module enables. EDIT: To be clear, Magisk mounts from the data partition, onto the system partition, not a hard link.Will replacing it with a hard link work too?
Thanks friend for answering.
It turns out that the path / magisk / v4a I don't see, so I went directly to the path SYSTEM / ETC ..... and there was the file in question, but I copy or cut it and overwrite it in the destination path and nothing, remains the same in PROCESS: NO.
I have also done something else that a colleague said to replace a file with .sh extension by .bak, and it has not worked for me either because when I restart and open the V4A, it asks me to install the driver again, so it did not help me.
Can somebody help me? is that my OP3T is very weak, only on calls, if I put videos and others, it is perfectly heard.
Someone could put the steps from 0, I want to do it from 0 and delete everything that doesn't work for me.
If you look at your logcat, you can determine which selinux policies are being violated, and "punch a hole" specific for those, and then you should be able to run enforcing.Solution
The only thing that works for me is setting Selinux as permissive!