yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Lughnasadh:
Working for me on A14B3 with Canary Magisk 26102. Did you enable Legacy Mode? Might want to try it without Wavelet as well.
[Google Pixel 6 Pro] pentium0:
Thank you... I'll try without Wavelet installed and with canary magisk.
[Google Pixel 6 Pro] SchmilK:
After months of being annoyed that I could only process audio via internal speaker, I went through the dev settings and got it working on Bluetooth!
[Google Pixel 6 Pro] fil3s:
I used rootless jamesdsp on my Samsung a34 before I rooted it.

It's actually got really good reverb.

GitHub - timschneeb/RootlessJamesDSP: An implementation of the system-wide JamesDSP audio processing engine for non-rooted Android devices

An implementation of the system-wide JamesDSP audio processing engine for non-rooted Android devices - timschneeb/RootlessJamesDSP

github.com
[Google Pixel 6 Pro] statustray:
You used this and viper at the same time?
[Google Pixel 6 Pro] chrisss5000:
Hi,

It does work with Magisk 26.1. Install this one instead. Flash the zip and reboot. Then install the apk. Then reboot and now it should be working.

https://github.com/AndroidAudioMods/ViPER4Android/releases/tag/v0.5.0
[Google Pixel 6 Pro] Cheetah_Development23:
This worked 110% on Android 14 AOSP. Make sure you follow the steps to a "T" :

I got it working on Android 14 beta 3.1 :

Download the magisk .zip (ViPER4Android-RE v0.6.1.zip) and .apk (V4A_App_0.6.2.apk) file from the link : https://github.com/AndroidAudioMods/ViPER4Android/releases

Install ViPER4Android-RE v0.6.1.zip via magisk manager

Install .V4A_App_0.6.2.apk file

Reboot

Enable Master limiter and Legacy mode in V4A

Open a music app and enjoy it!

*edit*

I am also using the latest Magisk Canary.and BusyBox NDK
[Google Pixel 6 Pro] vibrantliker:
All functions / features working properly? and on what phone?
[Google Pixel 6 Pro] Cheetah_Development23:
Everything that is highlighted and not greyed out...
[Google Pixel 6 Pro] HueyT:
Works for rooted latest stock A14 with latest [Kernel][07.12.2023][Android 14.0.0]Kirisakura 2.1.0_Raviantah for Pixel 6/Pro aka "RAVIOLE" kernel 👍
[Google Pixel 6 Pro] fillwithjoy1:
You can try RootlessJamesDSP and see how that goes
[Google Pixel 6 Pro] card13:
I moved a long time ago to Poweramp Equalizer.
[Google Pixel 6 Pro] card13:
@vibrantliker Sadly yes it appears no one here or in the main app thread has gotten it working yet. I'm thinking it's going to take a lot more work this time round unlike in versions past.

I'm currently working on decompiling the apk so I can figure out how the one feature I use is done, that way I can compare Apples to Apples in my tests. So far blindly testing PowerAmp's Stand-alone EQ app has done an ok job of being a workaround.
[Google Pixel 6 Pro] ecera:
I think someone mentioned this before, but it seems that the devs of JamesDSP probably could guide us in the right direction. They have their module using the "lib64" files instead of "lib" files like viper. On A12 all audio processing is done through the regular lib files and on A13 all audio is being processed through lib64.

First screenshot is the pixel 6 pro running A13. Notice that James Dsp is utilizing lib64 folder. The second one is the OnePlus 9 pro A12. It's running both viper and James dsp, but they are utilizing regular lib folders. Apparently viper is trying to use the lib folder, but all the audio processing is being done through lib64 now.
[Google Pixel 6 Pro] rafik25:
So JamesDSP works on A13 ?
[Google Pixel 6 Pro] Lughnasadh:
Yes. Just choose "Yes" when it asks if you have a Huawei device.
[Google Pixel 6 Pro] Suavie103:
Guess we're all still waiting.
[Google Pixel 6 Pro] card13:
Took and decompiled the apk to source for anyone else who wants to take a peak.

In case anyone is interested in the ViPER Bass feature, here is the description in Source:

"<string name="description_65574">&lt;p&gt;ViPER bass is a substitution for XHiFi’s Audio Reconstruction. It processes bass boost at lower frequencies&lt;/p&gt;&lt;br/&gt; &lt;p&gt;&lt;h5&gt;Bass mode&lt;/h5&gt;&lt;/p&gt;&lt;p&gt;Defines the bass mode. Natural bass is alike ViPER XHiFi’s Lo Contour, pure bass+ gives clean bass and subwoofer gives huge bass.&lt;/p&gt;&lt;br/&gt; &lt;p&gt;&lt;h5&gt;Bass frequency&lt;/h5&gt;&lt;/p&gt;&lt;p&gt;Defines the bass cut-off frequency&lt;/p&gt;&lt;br/&gt; &lt;p&gt;&lt;h5&gt;Bass gain&lt;/h5&gt;&lt;/p&gt;&lt;p&gt;Defines the volume of ViPER bass&lt;/p&gt;</string>"

***EDIT***

I did lots of reading on how to achieve this in an EQ. Basically using High and Low Passes or High and Low Shelves equates to the Natural Bass, Pure Bass+ and Subwoofer. Then set the Frequencies for High/Low. Then how much Gain. For Subwoofer I did a Negative Gain on the Highs and a Positive Gain on the Lows.
[Google Pixel 6 Pro] Suavie103:
Idk what happened over night, but VIPER IS PROCESSING ON ANDROID 13 Pixel 4 XL!
[Google Pixel 6 Pro] fil3s:
Mind walking us through the steps to get v4a working on a13?
[Google Pixel 6 Pro] Suavie103:
Honestly, bro. I won't even lie to you. I don't know what happened. I had the initial driver bug. Mind you. That was my pixel 4 XL running 13. My daily driver is the 6 Pro. My 6 Pro has the exact same setup, yet viper is not processing. See the screenshots below. It honestly was just a fluke.
[Google Pixel 6 Pro] llsl:
My friend also told me V4A can work on pixel 4 with A13 but not pixel 6, no idea why 😂
[Google Pixel 6 Pro] vibrantliker:
Interesting. Staying on 12 until it's fixed.
[Google Pixel 6 Pro] State.of.mind:
Has anyone else experienced this? P6P. A13
[Google Pixel 6 Pro] cd993:
What does the driver status say?
[Google Pixel 6 Pro] State.of.mind:
The usual. "Driver not installed."
[Google Pixel 6 Pro] KHANrad_SIN:
So is the consensus right now that V4a is working on A13 for every other device EXCEPT the pixel 6 and pixel 6 pro? lol
[Google Pixel 6 Pro] chafedbm:
I have a Pixel 6 Pro running A13 and Magisk 25.1. I installed V4A using the magisk module ViPER4Android_FX-v2_7_2_1-2721.zip and like everyone else I get the driver loop. I added the following lines to the

post-fs-data.sh

file:

magiskpolicy --live 'allow audioserver audioserver_tmpfs file { read write execute }'

magiskpolicy --live 'allow audioserver system_file file { execmod }'

magiskpolicy --live 'allow mediaserver mediaserver_tmpfs file { read write execute }'

magiskpolicy --live 'allow mediaserver system_file file { execmod }'

magiskpolicy --live 'allow audioserver unlabeled file { read write execute open getattr }'

magiskpolicy --live 'allow hal_audio_default hal_audio_default process { execmem }'

magiskpolicy --live 'allow hal_audio_default hal_audio_default_tmpfs file { execute }'

magiskpolicy --live 'allow hal_audio_default audio_data_file dir { search }'

magiskpolicy --live 'allow app app_data_file file { execute_no_trans }'

magiskpolicy --live 'allow mtk_hal_audio mtk_hal_audio_tmpfs file { execute }'

The the location of the

post-fs-data.sh

file is /data/adb/modules/ViPER4AndroidFX

When I got in my car and Android Auto started playing music I instantly noticed a difference. V4A was indeed processing the audio, however, I couldn't open the app to make any changes to any of the settings because as soon as I open the v4a app I get the message "Driver not installed blah, blah". As far as I can tell there is no way to clear the message off the screen to be able to make any settings changes in the app. I wanted to listen to music in my car so I uninstalled V4A right then and rebooted. When my phone connected to AA and started playing music the sound was back to "normal".
[Google Pixel 6 Pro] Undeadwolfy:
Glad to have seen this thread. My P6 Pro force updated from a November 2021 build (I know) to July 2022 without my permission (which really annoyed me) and lost root. I figured i'd upgrade to A13 while im this recent to make use of some of the new features and lo and behold, V4A isn't working.

I've tried every combination of Audio Compatibility Patch, Audio Modification Library, Ainur Narsil, SE Linux change and changing the post-fs-data.sh file.

I can't confirm if the audio has changed like @chafedbm above says but the driver definitely is stuck in an install loop which really sucks.

Nothing is as good as V4A. Hoping the geniuses at V4A Repackaged could address this since they're actively developing.

Github: https://github.com/programminghoch10/ViPER4AndroidRepackaged

Edit: Looks like the EQ values are remembered from my last install from when V4A was working but they're behind the driver install prompt. There values aren't actually doing anything.
[Google Pixel 6 Pro] memocatcher:
Some offtopic, but has anyone reached out to Team DeWitt yet? What are they saying about Android 12/13 support?

Honestly not in the loop
[Google Pixel 6 Pro] vibrantliker:
Would LOVE to know that!
[Google Pixel 6 Pro] KHANrad_SIN:
Was wondering about this too, maybe they aren't even aware of this issue.
[Google Pixel 6 Pro] Sense7606:
I got viper4android working on Derpfest A13. All I did was flash both

ViPER4AndroidFX-repackagedhoch21 and Viper4AndroidFXRepack with Magisk, rebooted my phone, installed the V4A apk and that was it. No driver loop and it's processing well. No Audio Modification Library needed. Only problem is that it cannot read my old profiles from A12, not sure why.
[Google Pixel 6 Pro] Vincent_40:
You're on Pxl 6P ?
[Google Pixel 6 Pro] pa.pn2:
Did someone test the new Hoch version 24 on A13 yet?
[Google Pixel 6 Pro] yyz71:
I'm still running A12 for that reason. Was on A13 but no viper.. then went back to A12 cuz viper works. And the guy who has it install on derpfest A13 can't answer if has the pixel 6 Pro 🙄
[Google Pixel 6 Pro] phaino00:
Yes. Cannot get the driver to install. Running factory image A13 with Radioactive kernel.
[Google Pixel 6 Pro] rhetorician:
Same
[Google Pixel 6 Pro] mustang_ssc:
I've been some weeks debugging this issue for A13, might be close to solve it. I need someone with the following requirements:

- Pixel 6 or Pixel 6 Pro

- Android 12. Preferably stock, if not in stock mention your custom ROM.

- Stock kernel

- Viper installed from the latest Magisk module: https://github.com/programminghoch10/ViPER4AndroidRepackaged/releases/tag/v24

What I need after all requirements met is to send me the following files from your system:

/system/etc/audio_effects.conf

/vendor/etc/audio_effects.xml

Update:

I also need you to let me know if the driver installation is already done after installing the module and restarting (no driver pop-up message in app) or after pressing driver installation in the app.
[Google Pixel 6 Pro] CharliexCharger:
Did you obtain this information?
[Google Pixel 6 Pro] mustang_ssc:
Got it from an A12 custom ROM but I would like to get it from the stock ROM for a cleaner revision.
[Google Pixel 6 Pro] CharliexCharger:
Sent. A12 developer build.
[Google Pixel 6 Pro] Sense7606:
Sorry for my late reply. I'm on Derpfest 13. My device is Xiaomi Redmi Note 9S. No driver pop-ups after flashing both packages.
[Google Pixel 6 Pro] lunalsmojo:
I've been messing with this for a while. I figured out why it won't work, but I don't have a solution yet... maybe someone on this thread can help.

Every version of Android thus far has loaded audio effects from /vendor/lib/soundfx. Android 13, however, apparently loads the audio effects libs from /vendor/lib64/soundfx. While audio_effects.xml may look identical, the default path is lib64 instead of lib.

V4A only provides /vendor/lib/soundfx/libv4a_fx.so, so when EffectsFactoryConfigLoader starts parsing audio_effects.xml, it can't find libv4a_fx.so because it's looking for it in /vendor/lib64/soundfx (logcat gives...)

(

09-24 01:32:51.487 2648 2648 E EffectsFactoryConfigLoader: Could not find library in effect directories: libv4a_fx.so

)

You can *find* libv4a_fx.so by changing the patch in the module's install.sh to

sed -i "/<libraries>/ a\ <library name=\"v4a_fx\" path=\"..\/..\/lib\/soundfx\/libv4a_fx.so\"\/>" $AUDIO_EFFECTS_FILE

but this only works to find it, not open it (logcat gives....)

(

09-25 02:53:20.184 841 875 E EffectsFactoryConfigLoader: Could not dlopen library /vendor/lib64/soundfx/../../lib/soundfx/libv4a_fx.so: dlopen failed: "/vendor/lib/soundfx/libv4a_fx.so" is 32-bit instead of 64-bit

)

The change to looking for audio effects libs in /vendor/lib64/soundfx matters because lib64 is full of 64-bit *.so files, whereas lib is full of 32-bit, and apparently the audio effects are being run as 64-bit binaries now.

So where I've gotten is how to find and try to open libv4a_fx.so. Where I'm stuck is how to actually open it.... I feel like there has to be a way to run just that one audio effect as 32-bit, but I have no idea how to do it yet
[Google Pixel 6 Pro] Lughnasadh:
Don't know if you've looked into JamesDSP. The only way it works on A13 with the Pixel 6 series is to choose Yes when it asks you if it is a Huawei device during installation. At the time this option was made, only Huawei devices were using 64-bit drivers. So I believe enabling that option (loading 64-bit drivers) in JamesDSP allows the effects to load from lib64, thus making JamesDSP work on A13.

Maybe talk to James Fung over at JamesDSP and see if he can help?
[Google Pixel 6 Pro] CharliexCharger:
Currently there's two processes taking place per the Viper telegram channel. 2 developers are looking to reverse engineer the app.

Thomas De Witt is looking into A13 installation issues, but there's no solution timeline because viper isn't open sourced, so it takes time.
[Google Pixel 6 Pro] shiftr182:
Here is the install script when you choose Huawei in JamesDSP

ui_print " "

ui_print "- Select Huawei -"

ui_print " Is this a Huawei device?"

ui_print " Vol Up = Yes, Vol Down = No"

if chooseport; then

QARCH="huawei"

cp_ch $MODPATH/common/files/$QARCH/libjamesdsp.so $MODPATH/system/lib64/soundfx/libjamesdsp.so

else

QARCH=$ARCH32

fi

cp_ch $MODPATH/common/files/$QARCH/libjamesdsp.so $MODPATH/system/lib/soundfx/libjamesdsp.so

You can see it changes the patch to /lib64/
[Google Pixel 6 Pro] llsl:
I think the point is that the driver file provided by the original developer of V4A is 32-bit, so it cannot be loaded by the software which required 64-bit driver. To solve this, we have to obtain 64-bit driver (almost impossible, we cannot reach the origin developer anymore) or there maybe a way to load the 32-bit driver in the software. I am not an expert on android, hope I am wrong
[Google Pixel 6 Pro] xerel89:
Strange this v4a can not find my ddc file!
[Google Pixel 6 Pro] mustang_ssc:
Same findings as well, what was interesting to me was whether on A12 it does show the driver pop-up message after Magisk installation, it is not the case (thanks to @CharliexCharger for confirming), so installation is completed with the module itself.

Viper may install the driver by two ways: Magisk module's installer or viper app itself, both are missing 64 bits library.

That's probably why JamesDSP works when installing the 64 bits library (Huawei option).

What I found interesting is viper driver's installation reverts back audio_effects.con to default values while rooting the path to the library either by its own (library stored inside the app) or somewhere I cannot identify.

Also, for some reason, the module upon installation does point into the audio_effects.conf the library to /system/lib/soundfx/libv4a_fx.so instead of /vendor/lib/soundfx/libv4a_fx.so where it is really stored (A13 tested), either was I forced it to /vendor and same result.
[Google Pixel 6 Pro] pentium0:
These steps work for A13 on pixel 4xl and should probably work on pixel 6

1. Viper4Android FX v2.7.2.1 module, no reboot;

2. Audio Modification Library v4.0, no reboot;

3. Entered Viper and hit Ok and the phone rebooted.

4. Processing not happening + Viper crashed when switching to Legacy.

Then I,

1. removed Audio Modification Library v4.0, but left Viper installed with Legacy mode enabled,

2. rebooted,

3. installed Audio Modification Library v4.0 again,

4. rebooted,

5. Baaaam..its working both with speaker and BT (AirPods, carstereo)."
[Google Pixel 6 Pro] rester555:
Does it have to be audio modification library 4.0? lastest is 4.1.
[Google Pixel 6 Pro] rester555:
How do you switch to legacy mode?
[Google Pixel 6 Pro] Xdevillived666:
Could you link the two files please ?
[Google Pixel 6 Pro] vibrantliker:
and this was on the Pixel 6 Pro?
[Google Pixel 6 Pro] Lughnasadh:
No. His device is Xiaomi Redmi Note 9S.
[Google Pixel 6 Pro] vibrantliker:
doesn't help us..
[Google Pixel 6 Pro] Lughnasadh:
Nope
[Google Pixel 6 Pro] vibrantliker:
I can't move to A13 without this working
[Google Pixel 6 Pro] Lughnasadh:
I'm using JamesDSP instead.
[Google Pixel 6 Pro] Ghisy:
How do you install it? I read on GitHub that it should be flashed through TWRP. And the latest release is an .apk, not a .zip file.
[Google Pixel 6 Pro] Lughnasadh:
Just flash the latest zip in Magisk. Make sure to choose "Yes" when it asks if you have a Huawei device.

Zackptg5 - Android

zackptg5.com
[Google Pixel 6 Pro] vibrantliker:
Not the same though, right?
[Google Pixel 6 Pro] Lughnasadh:
Similar
[Google Pixel 6 Pro] KHANrad_SIN:
It's enough to get me by for the time being, but it doesn't have the automatic profile switching like in V4a when you connect to your car speakers instead of your ear buds for example.
[Google Pixel 6 Pro] rhetorician:
Same. I just have almost no idea what I'm doing without presets so I have a difficult time with it. Considerably better than nothing, though.
[Google Pixel 6 Pro] KHANrad_SIN:
Not gonna hold out hope anymore tbh. Someone in another forum recommended Wavelet to me as an even better alternative than JamesDSP and it seems like this is good enough for a replacement for me. It has the automatic profile switching like V4A did. It doesn't have all of the same features as V4A but it has most of what I need and is very similar (because it's made by the same guy). Plus the upside is that it's just an app from the google play store so I don't have to jump through hoops every time there's a new system update just to get it to work. There is a paywall of 5.99 to get all the features though, but I think it's well worth it. I will miss spectrum extension and ViPER clarity though.
[Google Pixel 6 Pro] jgrubbs:
I downgraded back to 12 just to have it back lol. Running ancient os and it's running good. Just can't seem to find anywhere to dl derpfest 12.1 though. Think hurts already taken em down and is eol.
[Google Pixel 6 Pro] jamescable:
Install these, reboot, open viper, if asks to install drivers, yes, reboot. Most of the time it won't ask but for some it does
[Google Pixel 6 Pro] Lughnasadh:
So you actually got V4A to work on the Pixel 6 Pro running A13?
[Google Pixel 6 Pro] x1125:
Nope. Not working on A13. Keep on asking for driver installation.

Maybe there's a way to install the audio driver separately? Anyone in possession of this kind of magisk module?

For me JamesDSP is also not an option as the app crashes everytime I try to open it no matter what I do.

Tested on basically all released A13 stable builds with the same result.
[Google Pixel 6 Pro] Lughnasadh:
For JamesDSP, did you select Yes when it asks you if you have a Huawei device? That is required for this device on A13. Should then work without any problems.
[Google Pixel 6 Pro] x1125:
Yes I did.
[Google Pixel 6 Pro] Lughnasadh:
Strange it's not working, as it's working fine for me using v4.6 (and BusyBox 1.34.1)
[Google Pixel 6 Pro] acwcanada:
@Lughnasadh

Seems you are an experienced JamesDSP user, do you know if it is something wrong on my settings or it is the limit of this app: I couldn't make it auto switch between speaker, headset and bluetooth, I have to manually toggle between them. Please give some ideas and thanks for your help.
[Google Pixel 6 Pro] Lughnasadh:
I stopped using my Pixel 6 Pro so actually don't remember if it was auto switching or not but have a vague memory it wasn't. On my Pixel 7 Pro it's auto switching just fine so it may have something to do with the Pixel 6 series. Next time I get my Pixel 6 Pro out I'll check and report back if it is auto switching or not. Maybe do it later today.
[Google Pixel 6 Pro] Lughnasadh:
I just checked my Pixel 6 Pro and it does auto switch from speaker to headphones, and vice versa. Didn't check bluetooth though. I was using Poweramp and YouTube while checking. For Poweramp, I do have "Pause On Headset Disconnect" disabled and "Resume On Wired Headset" enabled. Not sure if that matters.

Maybe check the settings on the player you're using?
[Google Pixel 6 Pro] acwcanada:
I further test it after getting your confirmation, yes, it did work in most cases but normally it takes a few seconds for the switch to the proper header to be occurred. In some cases, the header would stay without change, i.e. bluetooth headsets is on and JamesDSP did already loaded my presets and working but the header would still stay as speaker. I couldn't find a pattern of this error as situations happened randomly in YTM, Spotify, TuneIn Radio, PowerAMP etc. I suspect my Samsung Galaxy Watch 4 bluetooth connection might have conflicts with JamesDSP and be the reason of this error, I'll have to testing it for a longer period and prepare to live with the situation. I am a V4A user longer than I can remember and since it is now not working in Pixel 6 Pro with A13 (V4A hasn't been update it's driver for more than 7-8 years and the original developer has given up on it, I believe it is the end of it unless someone want to stay with A12 and below), reading your recommendation of JamesDSP in XDA is the reason why I have switched. In the past couple months, I spent quite sometime to build a several presets for a few of my bluetooth headsets and a couple wired headphones, I would say I am now quite happy with the audio I am getting from the P6P. And you are the one to make me do this switching, thanks so much.
[Google Pixel 6 Pro] Face_Plant:
I do miss Viper, but once I finally sat down and put some effort into designing an EQ profile in Wavelet I actually prefer the audio I get from it over what I got from Viper. It wasn't as easy/straightforward as Viper where I could just flip a few toggles and be done, but it's definitely WAY better than nothing.

I tried JamesDSP as well, but I liked Wavelet better. Isn't Wavelet developed by the same person that created Viper?
[Google Pixel 6 Pro] v.konvict:
Wierdly on my pixel 6 installed the viper4android offline version and it seems to be working despite showing me the install driver option. I feel as though the sound quality is different. The wierd part is there are even profiles with various toggles switched on for all my devices so am not sure where the profiles came from since this is a brand new device
[Google Pixel 6 Pro] vibrantliker:
You're on A13?
[Google Pixel 6 Pro] v.konvict:
Yeah
[Google Pixel 6 Pro] vibrantliker:
What's the offline version?
[Google Pixel 6 Pro] fehrcomp:
Wavelet is a usable Viper replacement for me as well. Even with the free version.
[Google Pixel 6 Pro] 73sydney:
Worth pointing out that Wavelet tends to con people (im not saying theyre complete shysters, just broadly/fundamentally dishonest on several fronts) into paying for it to apply presets to headphones/ear buds that are already tuned/normalised/corrected.

I had that beef already with them several years ago, in that they were entiocing payments for normalised/correct profiles for things like Galaxy Buds+ that were already tuned out of the box, so you could actually make them sound worse using Wavelet....ask me how i know....

It was already bad enough they basically monetized viper code....

And ill probably be hunted down again for making those comments (again)....
[Google Pixel 6 Pro] vibrantliker:
I'm just keeping my phones on A12 until it works on newer Pixel phones
[Google Pixel 6 Pro] 73sydney:
Sadly mine came (second hand) with A13 on it, so im just looking forward to some resolution :)
[Google Pixel 6 Pro] vibrantliker:
I'd probably fool around with James DSP if I had to.