Develop Bugs

[MOD] - WETA Audio 9.1 - [aroma][V4A][DolbyAtmos][xloud][srs][beats][+++]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You flash this MOD at your own risk,
i take no responsibility for any mishaps.​
Subscribe to update notifications and general chat by clicking the button below
PIXEL TELEGRAM CHANNEL​
This here is my personal setup and thought i'd share. Usually i test extensively before releasing to public, but if you do find something detrimental to the usage of your device that is either Force Closing or simply not working, let me know and i will in turn inform whether that is something i will tend to.
WETA is a rom for Music geeks like me, though because we are still waiting on TWRP to become available i'd thought i'd make this MOD to flash in the meantime. Its main focus is Audio. ​
This mod installs the following...
V4A 2.5.0.5 or 2.3.4.0
Dolby Atmos
Sony Xperia™ Z5 Premium audio system
Beats™ libraries and effects
WETA Reboot app
​
How to install...
As of 9.0 moving forward, you will need to flash this mod using TWRP.
NOTE: There have been some issues with systemui crashing after install. This results in having to flash back to stock and in some cases having to wipe phone completely.
I advise running an un-encrypted file system at this stage, which may or may not help. Just be aware that things are basically experimental at these early stages.
1. Make sure you are on Stock firmware and have rooted device
2. Download mod zip
3. Install this app "Root Browser"
4. Extract the zip (click and hold, select extract) using Root Browser directly into Download folder. (you should have /sdcard/Download/WETA_*** as folder with files in it)
5. Go into Download/WETA_*** folder and select WETA-flash.sh
6. Tick "Execute script as root"
7. Then select the Execute button
8. It will say "Executing script"
9. Once complete you should have a popup box with no errrors.
10. Reboot device and mods should be installed....
Changes...
31st Oct
Fixed some things in audio_effects.conf
Added a new mod, 3minit battery to download page
#3 1st Nov
Modified build.props
Added System wide audio
#5 + #5b
Script modifications to be more universal for build.prop mod
- no longer replaces build.prop, now appends to file instead, keeping existing mod lines
V4ADA1 + V4ADA2
V4ADA1 - V4a 2.5.0.5
V4ADA2 - V4a 2.3.4.0
Both these versions have all audio mods omitted as to help with echoing while gaming.
Only V4A and Atmos present.
Fyi.. this can be flashed over the top of previous audio mods
12th NOV
WETA Audio 7 + 7b + V4ADA1_V5 + V4ADA2_V5
removed modification of audio_policy_config file
12th NOV
WETA Audio 8 + 8b + V4ADA1_V6 + V4ADA2_V6
More audio_policy_config tweaks for spotify
WETA Audio 9.0
This version is an Aroma installer version. TWRP only.
WETA Audio 9.1
Fixed V4A convolver and profile permissions
– FYI this will wipe out your /sdcard/ViPER4Android folder
Added Sony music player
Weta reboot option
BusyBox Install option
Weta audio remover
MOD Download Page
If you like my work, please consider buying this poor guy a craft beer for his efforts
?? --->

Downloading now. Will test as soon as I get to work. Thanks!

All the ports are coming left and right for device... we'll see how this one goes

I downloaded the zip and followed the instructions. Already rooted, had busybox and Root browser. Restarted and everything was installed. I keep getting FC on Dolby and when I enabled Viper it didn't change anything. I am not sure what I am missing.

ExcuseTheN00b said:
I downloaded the zip and followed the instructions. Already rooted, had busybox and Root browser. Restarted and everything was installed. I keep getting FC on Dolby and when I enabled Viper it didn't change anything. I am not sure what I am missing.
Click to expand...
Click to collapse
Did you start off with a clean system and vendor? The files going to vendor are important. Also are you using a custom kernel?
Selinux needs to be permissive, if you go into a terminal emulator and type su , allow root, then type getenforce , does it say permissive?

Mentalmuso said:
Did you start off with a clean system and vendor? The files going to vendor are important. Also are you using a custom kernel?
Selinux needs to be permissive, if you go into a terminal emulator and type su , allow root, then type getenforce , does it say permissive?
Click to expand...
Click to collapse
Yes they were clean and it is permissive. I'm on ElementalX 0.05.
---------- Post added at 08:18 PM ---------- Previous post was at 07:20 PM ----------
What is the easiest way to uninstall the mods? I would like to uninstall them and try to reinstall again.

Working great. I do prefer the old Viper though. I think it sounds better. Great job.

wow, I am super excited, I absolutely love your audio Mods coming from the nexus 6p! Thank you very much for bringing your mods forward to the Pixel XL.
2FunJags.

I have tried to get this to work with no success. I did double check and the newest version of busybox is installed. Selinux is set to permissive. I enable the Dolby app and the Viper app but nothing changes. I do not hear any difference with it turn off or on. The Dolby app will crash and FC if I click on play demo and let it sit for a few seconds. I am not sure what is wrong. I do have a custom kernel installed (ElementalX 0.05). I have used this on my Nexus 6p with no issues before but now it just doesn't work on my Pixel. I would like to uninstall it but do not know how to do that. Do I need to perform a full reset to the phone or is there another way to remove the mods and try to reinstall them?
EDIT: Finally got it to work. Came home and reflashed the stock boot.img to go back to stock kernel then reflashed ElementalX 0.05 and re-rooted and reinstalled the mod. Went into Viper and it started to work. Not sure why it wasn't working before but now it works 100%. Thanks again for the mod!

Hey would love to get this working however I seem to be having issues as well, I flashed the elementalx kernel then went through the install process as the instructions listed (using stericsons BusyBox) I note have dolby atmos and viper4android installed but neither are processing, I then read through these posts, checked that selinux was set to permissive (it is) and then cleared my audio_effects.conf that I found in the /etc/ folder and tried reinstalling via the script. Unfortunately still no processing from v4a. If you can think of anything else to check that would be awesome, v4a is the biggest thing I miss coming from my old note 4!
Sent from my Pixel XL using Tapatalk

Thanks for the great mod !
Dolby Works without any issues (except the demo)
Viper didn't work immediately with just on processing:no everything else was on yes , then it worked for a few minutes and went back to no.
I tested with Spotify and Play Music.
[edit]: It seems that it doesn't always know that music is playing and when it starts processing if the music finishes it stops again.
Compatible mode does nothing

exadeci said:
Thanks for the great mod !
Dolby Works without any issues (except the demo)
Viper didn't work immediately with just on processing:no everything else was on yes , then it worked for a few minutes and went back to no.
I tested with Spotify and Play Music.
[edit]: It seems that it doesn't always know that music is playing and when it starts processing if the music finishes it stops again.
Compatible mode does nothing
Click to expand...
Click to collapse
Thanks, ill try something to make the mod systemwide.
--->

I have been testing a lot, as there has been some instances of SystemUI crashing after flashing this, and other mods for that matter. I am adding to the op that at this stage it is advisable to have an unencrypted file system.
To achieve this you need to flash back to stock, (including data) and re root before you boot up into android.
I have also made some mods to the install package to modify vendor/build.prop as well as system/build.prop. This may have been an issue also.
If anyone has any more info on these systemui crashes that would be appreciated.
--->

DELETED
still getting systemui crash

Easiest way to go back to stock?
Sent from my Pixel XL using XDA-Developers mobile app

v2.2v said:
Easiest way to go back to stock?
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
I just pulled link. Just hold off for a bit. I got another systemui crash, but to flash back to stock, fastboot the stock firmware
-->

So i am still getting systemui crashes with these new changes and an un encrypted system... I am going to dumb down the audio mods to just v4a and dolby. and try that for a day,'
hold tight.
--->

So are there any people who have been running the mod successfully since yesterday?
If so i have one question.. have you activated SystemUItuner?
--->

SystemUI Crashes...
So after trying to figure out what he hell is wrong with my mods, ive gone to the SuperSU thread and have read people are having these crash issues, even with an unmodified system. So this is all related to root in general.
Looks like we are going to have to just wait for a fix on the root side of things..... ill be pulling links until there is an update to SuperSU
--->

Shouldn't be long, Chainfire is pretty active in the Pixel root thread and seems to be making some headway.

How To Guide [ROOT] Enable Dolby Atmos EQ

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​
Hello everyone!
I am a big fan of audio equalizers, especially on the phone's speakers, so on each of my OnePlus phones, from OP7 Pro, through 8 Pro and now on 9 Pro, I'm looking for a way to get the most out of Dolby Atmos.
On each of these devices I had to look for a new solution, on OP 7 Pro and 8 Pro before updating to OxygenOS 11 it was enough to install Dolby Atmos apk, it just worked immediately, unfortunately, after my discovery, OnePlus blocked this possibility, since the OOS11 update the application does not work, it can be installed but does not start.
[NOTE] This solution works on OnePlus 9 and 9 Pro, tested on the EU ROM (BA).
Today I found a way around this problem, however it requires root but the way itself is very simple, here are the steps to follow:
Install the magisk module - JamesDSP Manager
install the magisk module - Audio Modification Library
download and install the Dolby Atmos app - Download Link
After restarting the phone, the application should start without any problems
However, there is one more optional step, but I advise you to do it, because if you don't do it, the equalizer settings may reset, e.g. after connecting headphones -you should debloat this app: com.oneplus.sound.tuner
If you have root on your phone, you probably know how to do it, but if not, here is a simple instruction on how to debloat an app using a computer:
Download "Minimal ADB and Fastboot" to your computer, then enable USB debugging on your phone, then connect the phone to the computer and run the file "cmd-here", which you will find in the folder with ADB and Fastboot.
Now you need to debloat the Dolby Atmos system controller, to do this, you must enter the following commands in the fastboot console: (don't forget to allow USB debugging on your phone! After connecting the phone to the computer, the phone will ask you if you allow it)
Code:
adb shell
pm uninstall --user 0 com.oneplus.sound.tuner
If all went well, then you should see the message "Success" in the console, now you need to restart the phone, when it reboots, you will not find the "Dolby Atmos" in the phone's settings and thats okay.
You can also restore Dolby system settings at any time using this command in adb shell, but I don't recommend doing it if you want to use another Dolby control app:
Code:
cmd package install-existing com.oneplus.sound.tuner
And that's all! Enjoy a better audio experience on your OnePlus 9!

Rayekk said:
View attachment 5364567​
Hello everyone!
I am a big fan of audio equalizers, especially on the phone's speakers, so on each of my OnePlus phones, from OP7 Pro, through 8 Pro and now on 9 Pro, I'm looking for a way to get the most out of Dolby Atmos.
On each of these devices I had to look for a new solution, on OP 7 Pro and 8 Pro before updating to OxygenOS 11 it was enough to install Dolby Atmos apk, it just worked immediately, unfortunately, after my discovery, OnePlus blocked this possibility, since the OOS11 update the application does not work, it can be installed but does not start.
[NOTE] This solution works on OnePlus 9 and 9 Pro, tested on the EU ROM (BA).
Today I found a way around this problem, however it requires root but the way itself is very simple, here are the steps to follow:
Install the magisk module - JamesDSP Manager
install the magisk module - Audio Modification Library
download and install the Dolby Atmos app - Download Link
After restarting the phone, the application should start without any problems
However, there is one more optional step, but I advise you to do it, because if you don't do it, the equalizer settings may reset, e.g. after connecting headphones -you should debloat this app: com.oneplus.sound.tuner
If you have root on your phone, you probably know how to do it, but if not, here is a simple instruction on how to debloat an app using a computer:
Download "Minimal ADB and Fastboot" to your computer, then enable USB debugging on your phone, then connect the phone to the computer and run the file "cmd-here", which you will find in the folder with ADB and Fastboot.
Now you need to debloat the Dolby Atmos system controller, to do this, you must enter the following commands in the fastboot console: (don't forget to allow USB debugging on your phone! After connecting the phone to the computer, the phone will ask you if you allow it)
Code:
adb shell
pm uninstall --user 0 com.oneplus.sound.tuner
If all went well, then you should see the message "Success" in the console, now you need to restart the phone, when it reboots, you will not find the "Dolby Atmos" in the phone's settings and thats okay.
You can also restore Dolby system settings at any time using this command in adb shell, but I don't recommend doing it if you want to use another Dolby control app:
Code:
cmd package install-existing com.oneplus.sound.tuner
And that's all! Enjoy a better audio experience on your OnePlus 9!
Click to expand...
Click to collapse
Or you could use core patch and lsposed.
Or use redskull hydras magisk module then disable OnePlus tuner

toolhas4degrees said:
Or you could use core patch and lsposed.
Or use redskull hydras magisk module then disable OnePlus tuner
Click to expand...
Click to collapse
would you mind elaborating on what you are suggesting here, I would like to try that

thirtythr33 said:
would you mind elaborating on what you are suggesting here, I would like to try that
Click to expand...
Click to collapse
Well I have a thread in themes and apps and search for redskul tg link on sent not allowed to post the links

toolhas4degrees said:
Or you could use core patch and lsposed.
Or use redskull hydras magisk module then disable OnePlus tuner
Click to expand...
Click to collapse
LSPosed takes a little more work than installing 2 magisk modules, other than that sometimes it causes SafetyNet issues.
As for the second module, I have nothing to say because I've never heard of it, but if it actually works the same way as my solution, that's good!

Rayekk said:
LSPosed takes a little more work than installing 2 magisk modules, other than that sometimes it causes SafetyNet issues.
As for the second module, I have nothing to say because I've never heard of it, but if it actually works the same way as my solution, that's good!
Click to expand...
Click to collapse
I can't post tg links here, search. One less step than what you posted for redskul mod. Also already use lsposed for other stuff and pass safety net...

@Rayekk thank you for this. My setup is a little different from yours but your method gives me some insights as to how I should proceed. I have Viper4All installed properly and am trying to install Dolby Atmos.
Is there a particular reason why you're using Dax2 and not Dax3? Is one better than the other for particular setups? I'm also curious as to why the original extraction from the Razer 2 phone is 60MB while all these other ports that I'm running into is a lot smaller (~3MB, I saw one for 10MB). There are so many versions. Does it make sense for me to install JamesDSP when I already have Viper4Android? I feel like I should have one or the other, but I have no idea.

Question Viper4Android drivers install in loop

Hello, I'm on Android12 (EvolutionX) and I've seen people have this problem, But I can't fix the problem, any idea please?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

please help me !!

Install ainur narsil in magisk

V0ltan said:
Hello, I'm on Android12 (EvolutionX) and I've seen people have this problem, But I can't fix the problem, any idea please? View attachment 5633897
Click to expand...
Click to collapse
I had the same problem with my Mi 11 Lite 5G NE, tried various guides, no luck
Finally I made V4A working for me the following way:
https://forum.xda-developers.com/t/...ndroid-10-11-12-devices.4213647/post-86870983
However, I'm on stock and MIUI 12.5.8/A11 - you can try does the same work for your custom ROM A12

zgfg said:
I had the same problem with my Mi 11 Lite 5G NE, tried various guides, no luck
Finally I made V4A working for me the following way:
https://forum.xda-developers.com/t/...ndroid-10-11-12-devices.4213647/post-86870983
However, I'm on stock and MIUI 12.5.8/A11 - you can try does the same work for your custom ROM A12
Click to expand...
Click to collapse
Thank you very much, I will try this now

zgfg said:
I had the same problem with my Mi 11 Lite 5G NE, tried various guides, no luck
Finally I made V4A working for me the following way:
https://forum.xda-developers.com/t/...ndroid-10-11-12-devices.4213647/post-86870983
However, I'm on stock and MIUI 12.5.8/A11 - you can try does the same work for your custom ROM A12
Click to expand...
Click to collapse
It doesn't work at all, I put the new post-fs-data.sh as you gave, and still the same, any idea?

this is how i put the files

V0ltan said:
It doesn't work at all, I put the new post-fs-data.sh as you gave, and still the same, any idea?
Click to expand...
Click to collapse
Read my post there, what I was looking for, how I found what changes I needed to apply to the sh file. Seems you have now different folders with audio drivers, etc

zgfg said:
Read my post there, what I was looking for, how I found what changes I needed to apply to the sh file. Seems you have now different folders with audio drivers, etc
Click to expand...
Click to collapse
Why I is not audio_effect.xml?

V0ltan said:
Why I is not audio_effect.xml?
Click to expand...
Click to collapse
Look also here - good luck:
[Bounty] Viper4android fix
So I'm not sure if I'm doing this the right way, but I think in an effort to get experienced devs to take a look into our viper4android driver loop issue a bounty is in order. I have tried every method I could find to get viper4android to work...
forum.xda-developers.com

I used these instructions on both xiaomi.eu and now PixelOS, Viper4Android works perfectly.
[APP] [FIX] 100% working Viper4Android for Android 10-11-12 devices
If you are someone like me who encountered countless problems while installing Viper4Android on your Android 10 or 11 device and have no idea what to do then you are in the right place. Just download and install the apk from the attachment below...
forum.xda-developers.com

guardian_uk said:
I used these instructions on both xiaomi.eu and now PixelOS, Viper4Android works perfectly.
[APP] [FIX] 100% working Viper4Android for Android 10-11-12 devices
If you are someone like me who encountered countless problems while installing Viper4Android on your Android 10 or 11 device and have no idea what to do then you are in the right place. Just download and install the apk from the attachment below...
forum.xda-developers.com
Click to expand...
Click to collapse
Btw, did your phone come or you upgraded to MIUI 13/A12?
Also, you used Xiaomi.eu ROM (Weekly or Stable) with A12?
I'm asking bcs I'm curious, you are quoting to my post for (stock) MIUI 12.5.8/A12 for Lisa, I'd like to know does it work for A12 as well (potentially different folders for audio drivers)

@zgfg
Phone came with MIUI 12.5 based on Android 11, I upgraded it to MIUI 13 / Android 12. Battery life was pathetic on stock for me, so unlocked and flashed the stable xiaomi.eu ROM.
Moved to an AOSP ROM (PixelOS) a week back because I prefer stock Android any day. Battery life is far better than even xiaomi.eu.
But I was able to successfully install Viper4Android on both xiaomi.eu and now PixelOS using these instructions. Although there is one additional step I did which is not mentioned here. I manually copied the audio_effects.xml file to all the locations mentioned in the instructions. You need to copy over the xml file which has v4a_fx mentioned inside the file after the copyright section. It is also the larger size file (7.93 KB for me). Unfortunately I don't remember where this file is originally stored for you to copy it. But you can search for it using a file manager that supports root. You need to copy this file to the locations mentioned after installing Viper plus the driver and rebooting for the first time.
Also make sure that all other audio mods like AudioFX, Dolby Atmos, etc are not installed before installing Viper. I am aware of Audio Modification Library which integrates multiple audio mods, however I have never used it. I suppose it will be even more difficult to install Viper with AML. I could be wrong though. Anyway, for me Viper is enough.

Apparently the problem is with the atom kernel, I say this because I installed the same OS on my two devices (Alioth and Lisa), on Alioth SuperiorOS uses n0kernel, on Lisa it uses atom kernel, and in Alioth a simple installation of the module audio modification library + V4A already worked, a pity that the same does not happen in Lisa, the same already happened in Evox.
Does anyone know which pixelOS kernel it uses?
I'm seriously thinking about going back to Memeui with Lisa, my last attempt will be AOSPA which apparently doesn't use atom kernel.

dude.. i need help
i use Samsung Galaxy A50 and CRDroid Custom ROM Android 11,
i have installed Viper4Android. when i use loud speaker. it worked very well, but when i play with my earphone plugged in.. driver status said processing : no
can you guys help me please?? thanks.. pardon my english

@unsavorypinkie
I also face this problem once in a while. Try toggling Legacy Mode on and off. You can also force close the app playing audio and Viper and then first open Viper, then your music app and resume playback. It should start processing again.

guardian_uk said:
@unsavorypinkie
I also face this problem once in a while. Try toggling Legacy Mode on and off. You can also force close the app playing audio and Viper and then first open Viper, then your music app and resume playback. It should start processing again.
Click to expand...
Click to collapse
sadly it's still didnt work processing is still no.. but thanks dude for the tips.. maybe it'll help in the future

Then paer
unsavorypinkie said:
sadly it's still didnt work processing is still no.. but thanks dude for the tips.. maybe it'll help in the future
Click to expand...
Click to collapse
Then perhaps it could be due to the audio_effects.xml file. The file found in /data/adb/modules/ViPER4AndroidFX/system/vendor/etc has to be copied over to /vendor/etc and /vendor/etc/audio/inside whatever folder you have there. For me on a 11 Lite NE 5G it is SKU_YUPIK.
The file in the original location (/data/adb/modules/ViPER4AndroidFX/system/vendor/etc) must have v4a_fx mentioned in it. You can search within the file for it to confirm. It is after the copyright section.
After all this is done, restart and you should be good. Also ensure Legacy Mode is enabled and Compatibility Mode is disabled. If all else fails, try starting from scratch using the instructions by user "zgfg" that I linked to.
If it still doesn't work, then I'm sorry, I really don't know. Hope you can get it running though. The difference Viper makes is really like night and day!

guardian_uk said:
Then paer
Then perhaps it could be due to the audio_effects.xml file. The file found in /data/adb/modules/ViPER4AndroidFX/system/vendor/etc has to be copied over to /vendor/etc and /vendor/etc/audio/inside whatever folder you have there. For me on a 11 Lite NE 5G it is SKU_YUPIK.
The file in the original location (/data/adb/modules/ViPER4AndroidFX/system/vendor/etc) must have v4a_fx mentioned in it. You can search within the file for it to confirm. It is after the copyright section.
After all this is done, restart and you should be good. Also ensure Legacy Mode is enabled and Compatibility Mode is disabled. If all else fails, try starting from scratch using the instructions by user "zgfg" that I linked to.
If it still doesn't work, then I'm sorry, I really don't know. Hope you can get it running though. The difference Viper makes is really like night and day!
Click to expand...
Click to collapse
that folder you mentioned is empty, and i've tried to search with my root explorer. unfortunately i don't have audio_effects.xml file on my phone.. how can i solve this sir?? can i download it from the internet??
EDIT : i have found it sir.. i have copied that file from data/adb/modules/VIPER4AndroidFX/system/vendor/edc to vendor/etc but i don't have folder named audio inside but i have folder called dolby

Sorry, I have no idea then. What I do know is Viper will not work with existing audio mods so you'll have to remove/disable those. There is a Magisk module for multiple audio mods, but I have never used it.
That yupik folder is specific to a 11 Lite NE. I have two other phones, they don't have a yupik folder in them. But they are also running Android 11, which is easier to get Viper working on compared to Android 12.
You'll have to research how to get it working specifically for your phone.

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

I followed these steps (https://forum.xda-developers.com/t/...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 anyone successfully install the V4A? Thanks in advance!
Update:
Can anyone help @mustang_ssc with the required files (https://forum.xda-developers.com/t/anyone-get-viper4android-worked-on-a13.4480467/post-87518703)
Just to be clear, I know V4A works on many phones on the A13, but we're actually talking about the Pixel 6 (or 7) series, and no matter what magisk mods we've tried, it keeps asking for driver install.
Happy new year with the V4A reborn!
Releases · AndroidAudioMods/ViPER4Android
ViPER4Android app configuration files. Contribute to AndroidAudioMods/ViPER4Android development by creating an account on GitHub.
github.com
I have got it worked on my 6 pro (Dec update). Here is what I did:
Download the magisk .zip and .apk file from the link above
Install .zip via magisk manager
Install .apk file
Reboot
Enable Master limiter and Legacy mode in V4A
Open a music app and enjoy it!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

It seems to be broken at this point, I've run into the same issue; when opening V4A on A13 it wants to install the driver (+ reboot), but after that's done the app still won't work.
Would be awesome to know if someone could share a workaround, or we can together work on one.

Same here. I switched to JamesDSP Audio Manager v4.6 and really like it so far.
When installing the module, don't forget to select "Yes" when asked if this is a Huawei device. Otherwise, the DSP manager will crash.

@xpdragon I'm using Viper for the function "ViPER Bass" to boost some of the bass frequencies to my Sub. Does JamesDSP have something similar that works (most EQ apps didn't work well)?

card13 said:
@xpdragon I'm using Viper for the function "ViPER Bass" to boost some of the bass frequencies to my Sub. Does JamesDSP have something similar that works (most EQ apps didn't work well)?
Click to expand...
Click to collapse
You can get more info about JamesDSP from Here.

xpdragon said:
Same here. I switched to JamesDSP Audio Manager v4.6 and really like it so far.
When installing the module, don't forget to select "Yes" when asked if this is a Huawei device. Otherwise, the DSP manager will crash.
Click to expand...
Click to collapse
Does JamesDSP automatically change your audio settings when you switch audio devices like V4A does? Like when you switch from bluetooth earbuds to your car speakers, on V4A it will auto switch the EQ, viper bass, viper clarity etc. to whatever you last set it as when using that specific audio device.

Anybody have tried this :
Releases · programminghoch10/ViPER4AndroidRepackaged
A refined ViPER4Android installer. Contribute to programminghoch10/ViPER4AndroidRepackaged development by creating an account on GitHub.
github.com
its works on A12 but on A13 i dont know (im on derpfest rom A12)

rafik25 said:
Anybody have tried this :
Releases · programminghoch10/ViPER4AndroidRepackaged
A refined ViPER4Android installer. Contribute to programminghoch10/ViPER4AndroidRepackaged development by creating an account on GitHub.
github.com
its works on A12 but on A13 i dont know (im on derpfest rom A12)
Click to expand...
Click to collapse
Dont work, driver loop

kimo1122 said:
Dont work, driver loop
Click to expand...
Click to collapse
Damn

KHANrad_SIN said:
Does JamesDSP automatically change your audio settings when you switch audio devices like V4A does? Like when you switch from bluetooth earbuds to your car speakers, on V4A it will auto switch the EQ, viper bass, viper clarity etc. to whatever you last set it as when using that specific audio device.
Click to expand...
Click to collapse
So for anyone else wondering, I went ahead and took the dive. Updated to A13 and tried out JamesDSP. It kind of(??) automatically changes your settings based on what your audio output is. It will switch between a speaker, headset(plugged in) and bluetooth profile. You can save different overall profiles (meaning it will save one speaker, headset and bluetooth profile) and load them but the problem for me is that it does not do it automatically. You have to manually load the overall profile yourself. This is unlike V4A, where it would switch the audio settings automatically when your audio output source changes. (This is actually how V4A used to be a while ago but now it auto switches)
Anyways, hope a fix for V4A comes out soon lol.

Anyone able to test this method out (with use of a Dolby magisk module too):
Post in thread '[APP][ALL ROOT SOLUTIONS][6.0+]ViPER4Android FX 2.7' https://forum.xda-developers.com/t/...-0-viper4android-fx-2-7.3774651/post-87131249

cd993 said:
Anyone able to test this method out (with use of a Dolby magisk module too):
Post in thread '[APP][ALL ROOT SOLUTIONS][6.0+]ViPER4Android FX 2.7' https://forum.xda-developers.com/t/...-0-viper4android-fx-2-7.3774651/post-87131249
Click to expand...
Click to collapse
It didn't work, V4A keeps ask for driver to be installed.

@xpdragon Just tried JamesDSP, it's bass boost is "Enable Dynamic Bass Boost" and how many db, not really an equiv to the function in Viper4Android, I'll pass on this app.
At this point I'm on A13 waiting for a fix to V4A or a good replacement.

card13 said:
@xpdragon Just tried JamesDSP, it's bass boost is "Enable Dynamic Bass Boost" and how many db, not really an equiv to the function in Viper4Android, I'll pass on this app.
At this point I'm on A13 waiting for a fix to V4A or a good replacement.
Click to expand...
Click to collapse
James dsp it's just crashing on my p6p with a13

@sas46 I made sure to remove all Audio Magisk Modules (I had V4A, Audio Mod Library and Compatibility), uninstall V4A App then reboot, then install JamesDSP. I went far enough to confirm that the singular function I was looking for wasn't there and went straight to uninstall.

card13 said:
@sas46 I made sure to remove all Audio Magisk Modules (I had V4A, Audio Mod Library and Compatibility), uninstall V4A App then reboot, then install JamesDSP. I went far enough to confirm that the singular function I was looking for wasn't there and went straight to uninstall.
Click to expand...
Click to collapse
I've tried everything, still force closing

sas46 said:
I've tried everything, still force closing
Click to expand...
Click to collapse
When installing, did you reply YES when it asked you if you have a Huawei device? If not, re-install and do so.

JamesDSP doesn't work with Android Auto like V4A but does just enough to get by.

Since we're on the subject, I'm curious if you guys have got any favorite profiles/presets you like to use with P6P.

Still nobody got it working?

Question V4A on OOS13

Hello,
has anyone managed to get V4A working on OOS13? If so, how?
Thanks for the answers, I won't be updating until someone confirms V4A works.

DashDashCZ said:
Hello,
has anyone managed to get V4A working on OOS13? If so, how?
Thanks for the answers, I won't be updating until someone confirms V4A works.
Click to expand...
Click to collapse
ViperFX for OxygenOS12/ColorOS12
1. Install AML and ViperFX 2. Reboot. 3. Launch Viper and install the driver. 4. Without running Viper: - From the archive AML.rar replace post-fs-data.sh along the path /data/adb/modules/AML - From the archive Viper.rar replace post-fs-data.sh...
forum.xda-developers.com
Followed this and it works fine, but sadly Dolby doesn't work anymore

Arcide said:
ViperFX for OxygenOS12/ColorOS12
1. Install AML and ViperFX 2. Reboot. 3. Launch Viper and install the driver. 4. Without running Viper: - From the archive AML.rar replace post-fs-data.sh along the path /data/adb/modules/AML - From the archive Viper.rar replace post-fs-data.sh...
forum.xda-developers.com
Followed this and it works fine, but sadly Dolby doesn't work anymore
Click to expand...
Click to collapse
Hi I know its an old thread but, which phone did you use. I tried on OP8 Pro and it didn't work.
Edit: nvm. I didn't realize which phone forum I was on.

JamesDSP has a working version for OOS13. Unfortunately V4A is not yet good.
But JamesDSP is probably even better, because it supports lossless format.

Got an OP 9RT on same hardware and make V4A works.
Spoiler: Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Maybe you should install BusyBox from Magisk repository first.
Install AML & V4A modules
Install V4A app (do not run it!!!)
Reboot
Run the app
Use "Legasy mode" in settings
Start any music
Go to Viper and turn it on/off/on
It may couse bootloop. Use it on your own risk!
Dolby works fine too.

polomalkin said:
Got an OP 9RT on same hardware and make V4A works.
Spoiler: Screenshots
View attachment 5836007View attachment 5836009
Maybe you should install BusyBox from Magisk repository first.
Install AML & V4A modules
Install V4A app (do not run it!!!)
Reboot
Run the app
Use "Legasy mode" in settings
Start any music
Go to Viper and turn it on/off/on
It may couse bootloop. Use it on your own risk!
Dolby works fine too.
Click to expand...
Click to collapse
Thank you!!! Works perfectly!
Did kill my Dolby however but I'm really just happy to have V4A again. A couple times it did stop working but clearing the app's data and opening it again works fine, no reboot needed.

polomalkin said:
Got an OP 9RT on same hardware and make V4A works.
Spoiler: Screenshots
View attachment 5836007View attachment 5836009
Maybe you should install BusyBox from Magisk repository first.
Install AML & V4A modules
Install V4A app (do not run it!!!)
Reboot
Run the app
Use "Legasy mode" in settings
Start any music
Go to Viper and turn it on/off/on
It may couse bootloop. Use it on your own risk!
Dolby works fine too.
Click to expand...
Click to collapse
Works! Thanks.
"Playback Gain Control" and some other controls are grayed out. Are you getting that too?

blackjackjokerz said:
Thank you!!! Works perfectly!
Did kill my Dolby however but I'm really just happy to have V4A again. A couple times it did stop working but clearing the app's data and opening it again works fine, no reboot needed.
Click to expand...
Click to collapse
Can someone explane to me what its used for. I see many people wanted it but im not sure for what? I mean i dont want to risk bootlook for something that maybe i dont need.

bubobih said:
Can someone explane to me what its used for. I see many people wanted it but im not sure for what? I mean i dont want to risk bootlook for something that maybe i dont need.
Click to expand...
Click to collapse
Viper4android is popularly considered to be the all time greatest android audio mod. Imagine an equalizer on steroids that requires ROOT and custom driver. Honestly other than a couple kernel tweaks here n there V4A is my only reason to root nowadays...

blackjackjokerz said:
Viper4android is popularly considered to be the all time greatest android audio mod. Imagine an equalizer on steroids that requires ROOT and custom driver. Honestly other than a couple kernel tweaks here n there V4A is my only reason to root nowadays...
Click to expand...
Click to collapse
Plus system-level adblocking with Adaway

polomalkin said:
Got an OP 9RT on same hardware and make V4A works.
Spoiler: Screenshots
View attachment 5836007View attachment 5836009
Maybe you should install BusyBox from Magisk repository first.
Install AML & V4A modules
Install V4A app (do not run it!!!)
Reboot
Run the app
Use "Legasy mode" in settings
Start any music
Go to Viper and turn it on/off/on
It may couse bootloop. Use it on your own risk!
Dolby works fine too.
Click to expand...
Click to collapse
Could you link the source of these APKs?
Thanks in advance.