[APP][ALL ROOT SOLUTIONS][6.0+]ViPER4Android FX 2.7

[shadowstep]

As I am sure you are aware, the majority of post-fs-data.sh fixes I have seen are SELinux allows. Your ZIP uses the sepolicy.rule file to achieve the same.

Yes, I'm aware. I should've been more clear. I just meant the SELinux allows are being taken care of in the recommended way (using sepolicy.rule) without moving them to post-fs-data.sh and using magiskpolicy (which is the old, traditional way).

 

[DiamondJohn]

Yes, I'm aware. I should've been more clear. I just meant the SELinux allows are being taken care of in the recommended way (using sepolicy.rule) without moving them to post-fs-data.sh and using magiskpolicy (which is the old, traditional way).

The other thing I noted, but forgot to mention, which obviously is fine for you, but others running different ROMs may need to add, is the removal of existing pre-installed equalizers in their ROMs. In the module I use, it removes MusicFX and AudioFX , at least one of which has been used previously in LOS based ROMs I have run. Don't know if they include it in more recent Android builds. Its not required in my Pixel device either, but its there by default.

I also compared your permissions XML with the one installed (and working) on my device, and found the following weren't in yours.

android.permission.ACCESS_SUPERUSER
android.permission.BLUETOOTH
android.permission.WRITE_EXTERNAL_STORAGE

The one I am running was missing android.permission.FOREGROUND_SERVICE which sounds pretty instrumental, but hasn't appeared to cause issues. I haven't run APPT against the APK to check (ie manually create the permissions file from the APK). I understand we are running different versions, and there is no use assigning a permission if its not requested/used by the APK, and superuser is only used to install the driver, which the module already solves.

Its all just an FYI.

 

[shadowstep]

The other thing I noted, but forgot to mention, which obviously is fine for you, but others running different ROMs may need to add, is the removal of existing pre-installed equalizers in their ROMs. In the module I use, it removes MusicFX and AudioFX , at least one of which has been used previously in LOS based ROMs I have run. Don't know if they include it in more recent Android builds. Its not required in my Pixel device either, but its there by default.

That's correct. This Audio Mod Troubleshooting Guide is pretty comprehensive as well, and may prove to be beneficial if anyone is having trouble getting V4A to work.

I also compared your permissions XML with the one installed (and working) on my device, and found the following weren't in yours.

android.permission.ACCESS_SUPERUSER
android.permission.BLUETOOTH
android.permission.WRITE_EXTERNAL_STORAGE

The one I am running was missing android.permission.FOREGROUND_SERVICE which sounds pretty instrumental, but hasn't appeared to cause issues. I haven't run APPT against the APK to check (ie manually create the permissions file from the APK). I understand we are running different versions, and there is no use assigning a permission if its not requested/used by the APK, and superuser is only used to install the driver, which the module already solves.

I generated the permissions XML using AAPT only; used it against latest available version of the app, i.e. v2.7.2.1 (which is also the version present in my module).

 

[vibrantliker]

That's correct. This Audio Mod Troubleshooting Guide is pretty comprehensive as well, and may prove to be beneficial if anyone is having trouble getting V4A to work.


I generated the permissions XML using AAPT only; used it against latest available version of the app, i.e. v2.7.2.1.

I wondered if either @shadowstep or @DiamondJohn may be able to help me.
I've been using viper for probably at least 10 years? Since getting into a more high-fidelity/audiophile world, I have continued to use my phone as the source as I don't know anything else that can sound as good as Viper.

On it's own (straight from phone to headphones) viper works fine but when I use an external dac (RME ADI-2 DAC) or any other external dac, occasionally I get unbearable sounds when skipping tracks. It comes in a variety of different ways, like a squelching feedback, or an unusual distortion among others. I have to unplug my phone from the dac to clear it. I've learned to deal with it but wondered if either of you (or anyone) has ever experienced this or knows a fix.

I've never experimented if it happens without Viper enabled but will try that today.

Update: Does not happen without Viper enabled.

 

[shadowstep]

I wondered if either @shadowstep or @DiamondJohn may be able to help me.
I've been using viper for probably at least 10 years? Since getting into a more high-fidelity/audiophile world, I have continued to use my phone as the source as I don't know anything else that can sound as good as Viper.

On it's own (straight from phone to headphones) viper works fine but when I use an external dac (RME ADI-2 DAC) or any other external dac, occasionally I get unbearable sounds when skipping tracks. It comes in a variety of different ways, like a squelching feedback, or an unusual distortion among others. I have to unplug my phone from the dac to clear it. I've learned to deal with it but wondered if either of you (or anyone) has ever experienced this or knows a fix.

I've never experimented if it happens without Viper enabled but will try that today.

Update: Does not happen without Viper enabled.

I've never used an external DAC, so this is out of my wheelhouse. Sorry!

 

[Wishmasterflo]

I wondered if either @shadowstep or @DiamondJohn may be able to help me.
I've been using viper for probably at least 10 years? Since getting into a more high-fidelity/audiophile world, I have continued to use my phone as the source as I don't know anything else that can sound as good as Viper.

On it's own (straight from phone to headphones) viper works fine but when I use an external dac (RME ADI-2 DAC) or any other external dac, occasionally I get unbearable sounds when skipping tracks. It comes in a variety of different ways, like a squelching feedback, or an unusual distortion among others. I have to unplug my phone from the dac to clear it. I've learned to deal with it but wondered if either of you (or anyone) has ever experienced this or knows a fix.

I've never experimented if it happens without Viper enabled but will try that today.

Update: Does not happen without Viper enabled.

I have a Audioquest Dragonfly blue DAC which I can use with Viper4Android without issues.

 

[tehrzky]

I am using OnePlus 9R (and was using the OnePlus 5 before this). Unfortunately, both these devices needed extra fixes/hacks for V4A to work. So I ended up making a Magisk module for myself which installs V4A as a system app, installs the drivers and applies fixes that are needed for it work (at least on my device). If you want to give it a shot, I've attached it.

after long search how to fix infamous "remount system rw" finally this module fixed the problem. (idk why dev of v4a not fixing this problem on their module, magisk has changed maybe that broke the module).

 

[lindahl85]

I tried to install Magisk module one oneplus 9 with crdroid, rebooted and started the app. Install it and rebooted. Started the app but it still want to install the driver. Any suggestions?

 

[lindahl85]

I am using OnePlus 9R (and was using the OnePlus 5 before this). Unfortunately, both these devices needed extra fixes/hacks for V4A to work. So I ended up making a Magisk module for myself which installs V4A as a system app, installs the drivers and applies fixes that are needed for it work (at least on my device). If you want to give it a shot, I've attached it.

I tried it on my OP9 with Crdroid. Drivers didn´t install from Magisk so it pops up every time I start viper. Install and reboot does not install it.

 

[Littlemether]

I am using OnePlus 9R (and was using the OnePlus 5 before this). Unfortunately, both these devices needed extra fixes/hacks for V4A to work. So I ended up making a Magisk module for myself which installs V4A as a system app, installs the drivers and applies fixes that are needed for it work (at least on my device). If you want to give it a shot, I've attached it.

Also needs smalipatcher options used

 

[DeMiane]

Hello everyone! Tired help! Tried many methods [APP] [FIX] 100% working Viper4Android for Android 10-11-12 devices. OnePlus Nord 2. Magisk 23. Help switch seLinux - permessive... Or leave enforced. But for Viper to work. Please help, no strength...

 

[DeMiane]

Also needs smalipatcher options used

Hello, can you share your mod? Might fit my Nord 2

 

[DeMiane]

I am using OnePlus 9R (and was using the OnePlus 5 before this). Unfortunately, both these devices needed extra fixes/hacks for V4A to work. So I ended up making a Magisk module for myself which installs V4A as a system app, installs the drivers and applies fixes that are needed for it work (at least on my device). If you want to give it a shot, I've attached it.

Hello, I tried your mod on OnePlus Nord 2. Hangs when the application starts. Tell me, maybe there are options to revive. SELinus = enforcing

 

[zzenyoo]

I am using OnePlus 9R (and was using the OnePlus 5 before this). Unfortunately, both these devices needed extra fixes/hacks for V4A to work. So I ended up making a Magisk module for myself which installs V4A as a system app, installs the drivers and applies fixes that are needed for it work (at least on my device). If you want to give it a shot, I've attached it.

Uff, it worked on my POCO X3 nfc (arrowos a12) without extra steps (except legacy mode on and off).

 

[DeMiane]

Quite simple.

1. Install Viper4Android version 2.7.2.1 module zip
2. Don't reboot
3. Open Viper app
4. Select yes to install the driver now
5. The phone will reboot
6. After reboot open Viper and enable Master limiter and, on settings, enable Legacy mode
7. Close Viper
8. Install my Fix module zip
9. Reboot
10. Wait for about a minute
11. Reboot again

That should be enough. If it wasn't...reboot again.

Cheers!

OnePlus Nord2 .11 andr. oxygen. During the installation process, zip. Doesn't install the app anymore. fix doesn't help. The previous operations have not been completed.

 

[Bourjois]

Hello, I hope this isn't a stupid question.. Is there an updated download link? XDA Labs has shut down so the link on page 1 is dead.

 

[Lord Sithek]

Hello, I hope this isn't a stupid question.. Is there an updated download link? XDA Labs has shut down so the link on page 1 is dead.

Oficially only from Telegram channel at the moment

 

[Lughnasadh]

Hello, I hope this isn't a stupid question.. Is there an updated download link? XDA Labs has shut down so the link on page 1 is dead.

For APK: https://www.apkmirror.com/?post_type=app_release&searchtype=apk&s=viper4android

For Magisk Mod: https://zackptg5.com/android.php#jdsp

 

[SkaboXD]

I experience audio stutter whenever I start to play audio in any application with V4A.

Poco X3 NFC, ArrowOS, Legacy mode (as that's the only thing that it works)

I use @shadowstep version since original Magisk module doesn't install audio driver properly.

JamesDSP doesn't have that issue but it doesn't apply it's processing to alarm, calls & ringtone unlike V4A, so I'm stuck with this.

 

[multiwirth]

Hi guys,
i have some issues recently getting v4a working on my old legacy devices Samsung Galaxy S3 i9305 and Note II N7100 running a treble-enabled lineage 18.1 build by html6405.
On my S3 i9300 however, it runs a standard 18.1 build by rINanDO and v4a works here flawlessly.
V4a was working on the other devices aswell so i wonder if treble = trouble here.
So basically after flashing the magisk module and opening the app, i followed the prompt to install the driver.
However after a reboot, the app still prompts me to install the driver so it either failed to install or doesn´t load at startup.
Any ideas?
smdk4412 devices are extremely old but they have a very capable headphone DAC after enabling some boeffla-tweaks on the kernel side of things.
Thanks