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

Search This thread
By:
Advanced…
HoosierFDaddy

HoosierFDaddy

Senior Member
Aug 3, 2010
222
138
Face_Plant said:
This 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.
forum.xda-developers.com

V4A (Viper4Android) on Pixel 7 Pro

So I know we're still in the early stages of this device. But I just wanted to get a thread going for V4A on our device. For those who came from the 6 Pro like I did, you're probably already aware of this, but for those who did not here's the...
forum.xda-developers.com forum.xda-developers.com
Click to expand...
Click to collapse
Confirmed "working"! Excited for further progress! I have a bad habit of buying the best equipment but usually turns out not the best for modifying to my liking, at least at the present moment. Was disappointed with lack of Viper and now I'm happy again. Great New Year gift!
 
  • Like
Reactions: Vincent_40
w_tapper

w_tapper

Senior Member
Sep 13, 2022
564
254
Samsung Galaxy Note 10.1
Lenovo K8 Note
is this normal for viper?
 

Attachments

  • Screenshot_20230103-184309_ViPER4Android.png
    Screenshot_20230103-184309_ViPER4Android.png
    253.1 KB · Views: 143
7

73sydney

Senior Member
Jul 21, 2018
3,056
3,226
Sydney
Google Pixel 6 Pro
Samsung Galaxy Watch 4
w_tapper said:
is this normal for viper?
Click to expand...
Click to collapse

did you really not read back half a dozen or so posts, where we all (especially me) found out what was normal for this test version?

forum.xda-developers.com

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

I followed these steps (https://forum.xda-developers.com/t/viper4android-pixel-6-pro-how-to-root-magisk-only.4382059/post-86183993) and it works on A12, but after the same steps on A13, the V4A cannot install the driver and didn't work. Does...
forum.xda-developers.com forum.xda-developers.com
 
  • Like
Reactions: Vincent_40
w_tapper

w_tapper

Senior Member
Sep 13, 2022
564
254
Samsung Galaxy Note 10.1
Lenovo K8 Note
73sydney said:
did you really not read back half a dozen or so posts, where we all (especially me) found out what was normal for this test version?

forum.xda-developers.com

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

I followed these steps (https://forum.xda-developers.com/t/viper4android-pixel-6-pro-how-to-root-magisk-only.4382059/post-86183993) and it works on A12, but after the same steps on A13, the V4A cannot install the driver and didn't work. Does...
forum.xda-developers.com forum.xda-developers.com
Click to expand...
Click to collapse
no
 
  • Haha
Reactions: EthanG_1988
J

jamiehawman

Member
Mar 26, 2020
42
1
I just can't access the playback gain and convoler does that mean it's not working then or do you know how I can access the 1s that won't open
 
J

jamiehawman

Member
Mar 26, 2020
42
1

Attachments

  • Screenshot_20230129-033113_ViPER4Android.png
    Screenshot_20230129-033113_ViPER4Android.png
    143.9 KB · Views: 29
You must log in or register to reply here.

Similar threads

Freak07
Development [Kernel][21.03.2023][Android 13.0.0]Kirisakura 1.0.0_Raviantah for Pixel 6/Pro aka "RAVIOLE"
Replies
3K
Views
334K
F
fk4mil
roirraW "edor" ehT
How To Guide March 20, 2023 TQ2A.230305.008.E1 Global | .F1 WINDTRE/Canada - Root Pixel 6 Pro [Raven] / all relevant links
Replies
2K
Views
250K
Nergal di Cuthah
Nergal di Cuthah
Typhus_
Themes / Apps / Mods [MOD][MAGISK][ANDROID 12] Addon Features for Pixel Devices - Pixel 6 Pro Thread
Replies
1K
Views
132K
Thebear j koss
Thebear j koss
V0latyle
How To Guide [GUIDE] Pixel 6 Pro "raven": Unlock Bootloader, Update, Root, Pass SafetyNet
Replies
2K
Views
154K
C
crisco654
Pekempy
How To Guide Working SafetyNet with Pixel 6 Pro Android 12
Replies
627
Views
86K
Izy
Izy

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 1
    L
    llsl
    Suavie103 said:
    Even with version 3.0 I keep getting driver not found error
    Click to expand...
    Click to collapse
    Try to enable the legacy mode, I got it worked both on v0.1 and v0.3 on my P6P.
    View
    1
    fil3s
    fil3s
    Suavie103 said:
    No driver found.. I can't even get pass the prompt to turn on legacy mode. Back to my original complaint. And I'm using 1.0 app and 3.0 module.
    Click to expand...
    Click to collapse

    Try the 1.0 module and 3.0 app. Works for me

    Edit: I'm using v.0.3.0 module , but the v.0.2.0 module didn't work for me

    I'm also using magisk delta on a14 beta 2

    Screenshot_20230317-164257.png
    View
  • 8
    L
    lunalsmojo
    mustang_ssc said:
    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.
    Click to expand...
    Click to collapse
    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
    View
    8
    mustang_ssc
    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.
    View
    5
    E
    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.
    View
    5
    chafedbm
    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".
    View
    5
    CharliexCharger
    CharliexCharger
    mustang_ssc said:
    Got it from an A12 custom ROM but I would like to get it from the stock ROM for a cleaner revision.
    Click to expand...
    Click to collapse
    Sent. A12 developer build.
    View

New posts