General [Bounty] Viper4android fix

[austick]

U can use offical viper4ndroid module. Just extract it and do changes .u can found more information in magisk documentary.

I will try tomorrow with more oxygen on my brain

 

[austick]

U can use offical viper4ndroid module. Just extract it and do changes .u can found more information in magisk documentary.

On my mobile it is impossible, I have discovered that it is one of the few xiaomi that has the EOFS file system that will be implemented in Android 13, so if no one else can give a solution, it seems to me that at the moment it is difficult to install viper4android.

 

[austick]

Nothing costs you to try the second I listed - somebody else reported it worked for his Poco (maybe diff model than yours, but who knows)

I tried today, its not possible because I have discovered that my system is EOFS :/

 

[metrixx02]

I tried today, its not possible because I have discovered that my system is EOFS :/

maybe u can get help official viper4ndroid telegram group

 

[mesabogiii]

removed

 

[mesabogiii]

I no longer have the 10 pro as I switched to another device. I think I remember installing AML, jamesDSP, and the following dolby atmos to get jamesDSP working:

GitHub - reiryuki/Dolby-Atmos-Magic-Revision-Magisk-Module

Contribute to reiryuki/Dolby-Atmos-Magic-Revision-Magisk-Module development by creating an account on GitHub.

github.com

Dolby Atmos Magic Revision Magisk Module

Described here: https://github.com/reiryuki/Dolby-Atmos-MagicRevision-Magisk-Module

www.pling.com

Thank you for the guide.
Working on Realme GT2 Pro - Realme UI 3.0 11_A.19

Following the order,
1. AML
2. JamesDSP 4.6 (Chose the Huawei route, tired playing around the combination)
3. Dolby Atmos revision
4. Reboot

Probably tried almost all the methods for Viper and nothing works.

 

[spiral777]

So I'm not sure if I'm doing this the right way, but I think in an effort to get experienced devs to take a look into our viper4android driver loop issue a bounty is in order.

I have tried every method I could find to get viper4android to work on our OnePlus 10 pro with no success.

Below I'll start a list of pledgers who are willing to pay the bounty when/if a fix is found. I'll add to the list as other pledgers come forward. Any pledge amount helps.

This worked for me

 

[metrixx02]

This worked for me

This worked for me

which device and rom ?

 

[spiral777]

which device and rom ?

Moto X4 (payton) pixel experience 13

 

[zgfg]

Unfortunately, Issues cannot be reported to GitHub for that project:

But I got in contact with the dev by Telegram...

Now, his Viper4AndroidRepackaged is updated on the GitHub and it searches for additional folders on /vendor with audio_effects conf and xml files to properly patch them

It works excellent on my Xiaomi (A12), I don't need to add the post-fs-data.sh script anymore to mount the patched conf and xml files

GitHub - programminghoch10/ViPER4AndroidRepackaged: A refined ViPER4Android installer.

A refined ViPER4Android installer. Contribute to programminghoch10/ViPER4AndroidRepackaged development by creating an account on GitHub.

github.com

Read also the Readme there

Thanks to the programminghoch10 dev, and @dladz for pointing here earlier about his GitHub project

 

[Velho_Velho]

try this:
remove all sound mods you have added, including the module from magisk and the viper app!
reboot!

Install attached Audio-Modification-Library_v4_0-OS12-op10
reboot!
install com.pittvandewitt.viperfx_2.7.2.1-2721.apk
open the viper app, and click install drivers.
phone auto reboot.

copy attached post-fs-data.sh to /data/adb/modules/ViPER4AndroidFX/ (use adb or rooted file manager)

REBOOT, do not open the app!!!!

now if we hit the FIX, if you will open the app it's should not ask to install drivers.

if it's stop asking, check the state, if it's not NORMAL then tick the Legacy Mode, and check state.
should be Status Normal.

I hope this will work for you.

I do can update Audio Modification Library to version 4.1?

 

[memocatcher]

So does Viper work for anyone with a 10 Pro yet?

 

[metrixx02]

İ don't think so

 

[austick]

But I got in contact with the dev by Telegram...

Now, his Viper4AndroidRepackaged is updated on the GitHub and it searches for additional folders on /vendor with audio_effects conf and xml files to properly patch them

It works excellent on my Xiaomi (A12), I don't need to add the post-fs-data.sh script anymore to mount the patched conf and xml files

GitHub - programminghoch10/ViPER4AndroidRepackaged: A refined ViPER4Android installer.

A refined ViPER4Android installer. Contribute to programminghoch10/ViPER4AndroidRepackaged development by creating an account on GitHub.

github.com

Read also the Readme there

Thanks to the programminghoch10 dev, and @dladz for pointing here earlier about his GitHub project

thanks, I have tried but again, this version patch audio_effects.xml correctly but I still have driver bootloop. I think it's because I have the EROFS system.

 

[zgfg]

thanks, I have tried but again, this version patch audio_effects.xml correctly but I still have driver bootloop. I think it's because I have the EROFS system.

I don't understand what would be the catch with your EROFS.
But your problem is maybe in the missing 64-bit audio drivers/lib in V4A

All of us have read-only system (on all the new devices)

That is what for the systemless rooting by Magisk and the systemless modules serve for - they mount changes on every reboot, they do not do any hard change on the system

However, JamesDSP requires to use Huawei mode on Huawei phones (and some other devices) and that option does actually nothing else but forcing to install the 64-bit libjamesdsp.so

And that option is missing in V4A (it installs only the 32-bit libv4a_fx.so). That could be the problem on your Huawei (is it Huawei), or other device(s) using 64-bit audio libs

You could reach the dev of this V4A Repackaged module by Telegram and ask him if he could add the 64-bit V4A audio driver - TG, he seems to be willing to update V4A for the new devices

 

[austick]

I don't understand what would be the catch with your EROFS.
But your problem is maybe in the missing 64-bit audio drivers/lib in V4A

All of us have read-only system (on all the new devices)

That is what for the systemless rooting by Magisk and the systemless modules serve for - they mount changes on every reboot, they do not do any hard change on the system

However, JamesDSP requires to use Huawei mode on Huawei phones (and some other devices) and that option does actually nothing else but forcing to install the 64-bit libjamesdsp.so

And that option is missing in V4A (it installs only the 32-bit libv4a_fx.so). That could be the problem on your Huawei (is it Huawei), or other device(s) using 64-bit audio libs

You could reach the dev of this V4A Repackaged module by Telegram and ask him if he could add the 64-bit V4A audio driver - he seems to be willing to update V4A for the new devices

Thank you very much for answering. In the JamesDSP forums the dev told me that V4A is most likely missing that 64bit library, in JamesDSP the Huawei option is 64bit and the other 32. Another person told me to install the magisk delta since (literally ) "EROFS need an early init to modify it's system", I think the first option is the right one since the second is somewhat riskier.

My mobile is a Pocophone f4 gt (Xiaomi) but I know that the problem is repeated with Oneplus 10 pro since it uses the same file system.

 

[zgfg]

Thank you very much for answering. In the JamesDSP forums the dev told me that V4A is most likely missing that 64bit library, in JamesDSP the Huawei option is 64bit and the other 32. Another person told me to install the magisk delta since (literally ) "EROFS need an early init to modify it's system", I think the first option is the right one since the second is somewhat riskier.

My mobile is a Pocophone f4 gt (Xiaomi) but I know that the problem is repeated with Oneplus 10 pro since it uses the same file system.

Systemless mounting works the same way for all modules - does eg AdAway with Systemless hosts work on your device (it has to patch /system/etc/hosts file) - if it does, then the same mounting must work for V4A

Also, use any root file explorer and go to /vendor/etc (on your phone, according to your later screenshot, it seems to be /system/etc), open (as text files) audio_effects.xml and audio_effects.conf and compare against my screenshots

Also, use Terminal emulator to execute:

su
find /vendor/etc -type f -name audio_effects.*

See the screenshot for my device

Go to and open all the found conf and xml files

If you see the v4a patches inside - then patches are mounted and there should be no problem related to EROFS

 

[austick]

Systemless mounting works the same way for all modules - does eg AdAway with Systemless hosts work on your device - if it does, then the same mounting must work for V4A

Also, use any root file explorer and go to /vendor/etc, open (as text files) audio_effects.xml and audio_effects.conf and compare against my screenshots

Also, use Terminal emulator to execute:

su
find /vendor/etc -type f -name audio_effects.*

See the screenshot for my device

Go to and open all the found conf and xml files

If you see the v4a patches inside - then patches are mounted and there should be no problem related to EROFS

I'm not at home now but I have this screenshot from yesterday. This time J4A I think has found the correct path to the audio_config.xml which it didn't do before. When I get home I'll investigate the xml and post the screenshots but I think if JamesDSP got it I guess V4A too.

 

[zgfg]

I'm not at home now but I have this screenshot from yesterday. This time J4A I think has found the correct path to the audio_config.xml which it didn't do before. When I get home I'll investigate the xml and post the screenshots but I think if JamesDSP got it I guess V4A too.

Please test as I described in the previous answer (I just edited and added some stuff)

Your (second) screenshot only proves that V4A, at the time of installation, found audio_effects conf and XML files and prepared their patched versions to:
/data/adb/modules/ViPER4AndroidFX/system/...

(You can also go there by root file explorer - I highly recommend MiXPlorer)

But the point is, does Magisk at the boot time, mount them over the corresponding /system and /vendor... target files (since you are questioning does mounting work for your EROFS file system) - that is, what is needed then to have 'drivers installed'

 

[Prant]

GitHub - programminghoch10/ViPER4AndroidRepackaged: A refined ViPER4Android installer.

A refined ViPER4Android installer. Contribute to programminghoch10/ViPER4AndroidRepackaged development by creating an account on GitHub.

github.com

Tinkered around with this a bit last night, still has the drivers not installed issue on my NE2215.