The actual question was the other way around: How can I make viper4android work with other players and pure viper4android and nothing that has got interferences? I spent many weeks. It was my challenge at XDA forums. I wanted a clean mod.....(other username there, though) When /system hadn't DM verity yet I modified those files directly....and since SE Android has enforcing mode as default....the viper Neon driver (the best) needs its own policy to run... In other words to get viper4android to run it required more and more efforts besides of root account... V4A actually does not need root at all. It only needs an own lib placed at /system/lib/soundfx. And to do that one needs 'root' one time...and of course to modify the configs you need root as well... By doing that you break DM-verity and safety net check detects root which means root checking apps refuse to start...the keyword: modify the system systemless-ly (Magisk) Samsung has own DSP libraries. And two tools (sound alive and adapt sound) which interfere with viper's own lib. The players 'do not know' what's 'after' when they deliver the stream.....but before it reaches the internal DAC there's own DSP...and it's the place where viper has to chime in... The file that controls that is the audio_effects.conf (on some newer Android devices it's a XML). As any conf it has got a strict structure you can find out how it works. Since it also has own sound processing at voice calls and recordings and wind-noise suppressing stuff and the like..I left that alone and original. I only redirected the effects which are relevant for music playing to the viper lib. Some crude mods just removed anything or deleted the own libs without to take care about calls from the conf.... In other words.....when you have managed to run viper4android with stock player (driver status: normal, Neon enabled: Yes, processing: yes, audio format supported: yes) then UAPP works as well. It's nothing bitchy, the contrary it just delivers it bit perfect to viper4android using its own hires drivers.... There are many people using viper4android which is still interfering with internal DSP or are using mods which remove DSP that makes sense at voice calling and recording and the like... And there are people who combine viper4android with other stuff such as Dolby Atmos or other fancy lib sets.. I only can say...... A proper mod and the understanding what viper4android can do is by far enough. One needs a bit time to figure how to setup viper properly.... Many are overwhelmed and try to alter any virtual rotary buttons and sliders at once...lol....some effects just do not go together or are neutralizing each others... Does it not work for you? It simply works if V4A works with stock player or any other 'common' player...... V4A is not 'external'...and not just an equalizer (I even do not use V4A fire equalizer)... If you have special tech questions concerning how to run v4a properly I try to answer them. I can share at MDL what I have learned myself by experiments and tests and at XDA... It was fun and I was very motivated to realize that...It was a sort of hobby to me...I realized to let run v4a with NEON support at SE enforcing mode while others still said you need permissive...lol... And I love V4A. The dev of it is a genius.