Question Anyone get viper4android worked on A13 (Pixel 6 series)?

[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.

 

[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.

 

[rafik25]

So JamesDSP works on A13 ?

 

[Lughnasadh]

So JamesDSP works on A13 ?

Yes. Just choose "Yes" when it asks if you have a Huawei device.

 

[Suavie103]

Guess we're all still waiting.

 

[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.

 

[Suavie103]

Idk what happened over night, but VIPER IS PROCESSING ON ANDROID 13 Pixel 4 XL!

 

[fil3s]

Idk what happened over night, but VIPER IS PROCESSING ON ANDROID 13! View attachment 5699855View attachment 5699857

Mind walking us through the steps to get v4a working on a13?

 

[Suavie103]

Mind walking is through the steps to get v4a working on a13?

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.

 

[llsl]

Idk what happened over night, but VIPER IS PROCESSING ON ANDROID 13 Pixel 4 XL!

View attachment 5699877 View attachment 5699879

My friend also told me V4A can work on pixel 4 with A13 but not pixel 6, no idea why

 

[vibrantliker]

My friend also told me V4A can work on pixel 4 with A13 but not pixel 6, no idea why

Interesting. Staying on 12 until it's fixed.

 

[State.of.mind]

Has anyone else experienced this? P6P. A13

 

[cd993]

Has anyone else experienced this? P6P. A13

What does the driver status say?

 

[State.of.mind]

What does the driver status say?

The usual. "Driver not installed."

 

[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

 

[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".

 

[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.

 

[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

 

[vibrantliker]

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

Would LOVE to know that!

 

[KHANrad_SIN]

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

Was wondering about this too, maybe they aren't even aware of this issue.