I accidentally installed an older version, can I just flash the newer version over the top of it or do I need to do something else first?
Freeze option with titanium backup. Freeze it then when you want to revert back just defrost it.Hi, im using a custom ROM preinstalled with audiofx, how can I disable that, use this, and revert back if I'm not satisfied with v4a?
Any free option?Freeze option with titanium backup. Freeze it then when you want to revert back just defrost it.
I just installed it on my oneplus 2 on stock rom and all is fine up until I activate v4a. The sound after the volume is more than about 70% it distorts very very bad. Can someone help me
Hello I am having a strange problem. I use AOSiP6.3 on my OnePlus 2 and when I try to install V4a, I manage to get the driver installed but it doesn't actually do anything. Upon checking the driver status I notice it states that it is not enabled and that its status is abnormal (see screenshot). Any suggestions?
EDIT: I don't know if it is relevant but I'm also using magisk 13.3
How would I go about doing that, if you don't mind my asking?
I've tried it, same thing happens. I think it is the rom tho. When I was on the LineageOS I had no problem with v4aHave you set the clarity setting too high? That usually causes the distortion and hissing in the background. If not then try using compatible mode.
---------- Post added at 06:54 PM ---------- Previous post was at 06:52 PM ----------
Link2SD can also freeze apps. Try that
---------- Post added at 07:03 PM ---------- Previous post was at 06:54 PM ----------
I had the same problem. I replaced my audio_config file
I tried it, no dice. It changed nothingHave you set the clarity setting too high? That usually causes the distortion and hissing in the background. If not then try using compatible mode.
---------- Post added at 06:54 PM ---------- Previous post was at 06:52 PM ----------
Link2SD can also freeze apps. Try that
---------- Post added at 07:03 PM ---------- Previous post was at 06:54 PM ----------
I had the same problem. I replaced my audio_config file
How did you go about it? Did you rename your original file as audio_config.bak ? I have a Samsung so I found the audio file on this page (https://xdaforums.com/s7-edge/how-to/guide-viper4android-enforcing-stock-t3337148). If you did everything right, do you have SElinux on permissive?
I've tried it, same thing happens. I think it is the rom tho. When I was on the LineageOS I had no problem with v4a
I don't think I did, I don't even know how to do that. I might try installing lineageOS and see if I have the same problemDid you freeze audio.fx? That usually interacts with v4a to cause distortion
… Just bear with me, I've been in the hospital the past two days hanging out with my brand new son, Beau, who was born Friday morning victory
I assure you guys I am not trying to frustrate you or flood this thread with another update, but I realized the Magisk installation was doomed if an existing Magisk module of any kind had an audio effects configuration symlinked to /system.
Today's build includes a lightweight and efficient audio effects configuration protocol for an audio framework for Magisk that I prepared a couple months ago that essentially "slipped in between the seats" while working on more than I should have at one time.
It took until today for it to dawn on me how essential such a component in /magisk is when dealing with the presence of anything added there by anyone and by any method.
I had to rewrite it from scratch tonight so it might be vulnerable to breaking by the flashing of additional modules that include an audio effects configuration, HOWEVER, my experience with Magisk suggests that the existing audio effects configuration(s) symlinked from /magisk to /system always prevail over future attempts (the reason why this audio effects configuration protocol is necessary) but likely prevents future modules using their audio effects configurations or just their edits (standard behavior anyway, not introduced from my protocol, just describing the landscape here).
My original framework included a script to handle the various configurations that may appear (from future installs) and merge additions as necessary upon boot, so this still needs to be done. Just bear with me, I've been in the hospital the past two days hanging out with my brand new son, Beau, who was born Friday morning victory. I realized the previous builds were only successful (for Magisk) if no audio effects configuration already existed anywhere in /magisk, so I wanted to provide something that not only overcomes that obstacle, but preserve/restore the others as well. :good:
v4a_fx {
path /system/lib/soundfx/libv4a_fx_xxx.so
}
#NECESSARY FOR XHIFI
v4a_xhifi {
path /system/lib/soundfx/libv4a_xhifi_xxx.so
}
v4a_standard_fx {
library v4a_fx
uuid 41d3c987-e6cf-11e3-a88a-11aba5d5c51b
}
#NECESSARY FOR XHIFI
v4a_standard_xhifi {
library v4a_xhifi
uuid d92c3a90-3e26-11e2-a25f-0800200c9a66
}