General - [Bounty] Viper4android fix | Page 2 | XDA Forums

zgfg said:

Regarding the lib vs lib64:

Check in the patched audio_effects.conf file

There should be a number of libraries listed as:
path /vendor/lib/soundfx/*.so

Are they really listed with /vendor/lib/

or with
vendor/lib64/

---

Disable the V4A module (through Magisk app or by placing an empty file named disable into /data/adb/modules/ViPER4AndroidFX - Magisk app by itself disables a particular module that way) and REBOOT and then check the original, not-patched conf file in those 'real' folders and check if it refers to lib or lib64

PS: Check those not-patched conf files in all four locations you said you had them in the post #9

Also, with the disabled V4A module, run su and then your dumpsys command directly from Terminal app and look does it list /vendor/lib/soundfx/ or /vendor/lib64/soundfx/ libraries

Click to expand...

Here is a screenshot of one of the patched .conf files. I also attached the /data/adb/modules/Viper4AndroidFX folder with all the patched .xml's &.conf's.

ecera said:

@zgfg after disabling Viper, the untouched .conf files all show lib not lib64. Here are results of dumpsys media.audio_flinger with viper disabled.

Strange that your not-patched conf files refer to lib/soundfx while dumpsys list lib64/soundfx libraries

Sorry, I can not help you further, don't know is it about lib64 or something else

Btw, all 'normal' modules 'manipulate' with system files through the customize.sh, post-fs-data.sh or service sh scripts - and one could then see their logic (to debug and fix/adapt something if needed) only the V4A has its 'driver installation' hidden in the apk (one would need to study the Java source and rebuild to adapt for new devices like yours)

I'll send you later today through the private conversation, the module zip 'installation' that you can flash to easily return to this point with the patched XML and conf files

IMO, it's of general interest, if you experiment further and specially if you find how to fix V4A on your device, please post your results - good luck

zgfg said:

Strange that your not-patched conf files refer to lib/soundfx while dumpsys list lib64/soundfx

Sorry, I can not help you further, don't know is it about lib64 or something else

Btw, all 'normal' modules 'manipulate' with system files through the customize.sh, post-fs-data.sh or service sh scripts - and one could then see their logic (to debug and fix/adapt something if needed) only the V4A has its 'driver installation' hidden in the apk (one would need to study the Java source and rebuild to adapt for new devices like yours)

I'll send you later today through the private conversation, module zip 'installation' that you can easily return to this point with the patched XML and conf files

IMO, it's of general interest, if you experiment further and specially if you find how to fix V4A on your device, please post your results - good luck

Click to expand...

I can't thank you enough for taking time from your day to help out with this! I'm not sure what else to try. Hopefully others start digging around too.

hahimot483 said:

I was able to get JamesDSP working on the 10 pro by selecting "Is this a Huawei device?" = yes during the install. Maybe someone can compare the install script of JamesDSP.

wow! thank u, this worked for me to enable James DSP on Poco f4 gt

iLee said:

wow! thank u, this worked for me to enable James DSP on Poco f4 gt

Also for @hahimot483

Please use a root explorer like MiXPlorer and go to /data/adb/modules/ainur_jamesdsp/system
Inspect all subfolders (and their subfolders, etc) - don't worry, there are only a few

1) Do you find there lib and/or lib64 folders and at what location (like in vendor subfolder)?

2) Find audio_effects.conf file (probably you have a couple of them in different subfolders, but identical).
Open (as a text file), does it show (see my screenshot) for jdsp:
path /vendor/lib/soundfx/libjamesdsp.so
or:
path /vendor/lib64/soundfx/libjamesdsp.so