Question Anyone get viper4android worked on A13 (Pixel 6 series)?
- Thread starter llsl
- Start date
Strange it's not working, as it's working fine for me using v4.6 (and BusyBox 1.34.1)
@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.
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.
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.
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?
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.
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?
I tried JamesDSP as well, but I liked Wavelet better. Isn't Wavelet developed by the same person that created Viper?
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
Wavelet is a usable Viper replacement for me as well. Even with the free version.
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)....
I'm just keeping my phones on A12 until it works on newer Pixel phones
Sadly mine came (second hand) with A13 on it, so im just looking forward to some resolution
I'd probably fool around with James DSP if I had to.Sadly mine came (second hand) with A13 on it, so im just looking forward to some resolution
Yeah, i feel you....i saw this post the other day, i think ill grab James DSP Manager from Zacks website and give it a crack later...want to do the December update first
JamesDSP Audio Manager [MMT-EX]
Description: This is a reformed audio effect digital signal processing engine for Android. The GUI is copy from Omnirom DSPManager, but the internal audio engine is enhanced and reformed! Features: Pro dynamic range compression Bass...
forum.xda-developers.com
I tried JamesDSP yesterday, lasted 10 minutes before i uninstalled it. Truly awful bit of gear....every setting gave harsh overprocessed output
Not a fan
Top Liked Posts
-
11
Gain control is a main benefit of viper4android so hopefully that issue will be solved. Good to get 64-bit support going as it is essential to the survival of viper. -
4This is working on my 6 Pro. I am running the stock OS (December update, rooted obviously). I simply installed the Magisk module, rebooted, installed the APK, and I was up and running. No legacy mode, Audio Modification Library, or permissive SELinux required.
V4A (Viper4Android) on Pixel 7 Pro
So I know we're still in the early stages of...
forum.xda-developers.com
322This is an exciting development. Previously, I was using two other mods, Moto Waves 5g Plus Equalizer and the Adus DTSX Ultra--both were okay. I simply turned them off in Magisk, flashed this, and all is well on my end (PSP). Thanks for sharing this with the Community.1
Are you playing music? Viper shows no driver/not processing for me if there is no music playing. -
8
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 yet8I'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.5I 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.5I 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".5
hopefully soon then 
