yashsingh1/xdaforums huggingface dataset:
[Magisk] MEHDIMYADI:
Hi,

In magisk v13.3 if viper driver status is abnormal.

The problem is from selinux.

For fix issue you should disable selinux, go to settings disable selinux.

My device is note4.

Note:

1. every time if reboot device you should again disable selinux in viper settings.

2. Go to settings > app manager and enable show system app find sound alive disable it.

2. Go to viper setting and fx compatible change it to compatible.

3. Reboot phone.
[Magisk] appman1234:
Viper works but the SafetyNet can't pass with Magisk v13.3.

It seems that SN can't pass whenever the Viper (or Dolby Atmos) is working :)

Any solution? Thanks!
[Magisk] ngtung84:
Use Universal SafetyNet Fix magisk module
[Magisk] appman1234:
Actually, I did use the USNF module. However the v4a or any sound modules break the SN for my Redmi Note 4X global stable rom.
[Magisk] TheAtheistOtaku:
Had problem of not processing (specifically google music) and adding these lines to the build prop fixed the issue. Running lineage os on a nexus 6p
[Magisk] rclksr:
Did you find that flash able file for Samsung device? I'd like to try it on my note 4
[Magisk] RoadToNever:
Is it possible to set sample rate manually? I'm asking because on my Nexus 5X the driver reports 44100. This unlike other V4A versions I've used that reported the native 48000 which is optimal for the device
[Magisk] kresnadetea:
i've been combine this module with am3d zirene and dolby

the result is awesome guys

running on magisk v13.3
[Magisk] disip:
Unfortunately still not able to get Viper to work with Magisk 13.3. SELinux disabled, those lines to build.prop added, Sound Alive disabled, compatible mode chosen...
[Magisk] Jerry SQ:
Wow, u can make am3d work with magisk 13.3!!!!! Please tell me how???? I have tried for days since the updated of magisk, much thanks
[Magisk] kresnadetea:
i just download it from official thread of am3d by ahrion and i'm using v2.4

idk how to tell you

did you try re-installing the module?
[Magisk] Jerry SQ:
Lucky you, yes, i have tried so many times, and the results are the same, am3d boot up with white screen of nothing and then crash. Someone confirmed in the official thread that it would not work with the lastest magisk. So confused!!!!
[Magisk] kresnadetea:
ViPER4ANDROID COLLECTIVE PROFILES

Here it comes!

Bunch of profiles for V4A.

V4A Collective Profiles

Just put it into V4A folder and feel the difference.
[Magisk] koko115:
When update for magisk 13.3 ? Because this version break safetynet.
[Magisk] Zackptg5:
Doesn't break safety net for me
[Magisk] koko115:
Restart phone, go to viper and change some settings, like turn on equalizer. Then exit from viper, wait 5 min, and check safetynet..

For me a wait for test +-30sec, after this time no pass, no false, but info " for now serice unavailable"

After uninstall viper, and reboot, safety pass quiqly.
[Magisk] Didgeridoohan:
That sounds device/ROM dependent.

I've been using this module (slightly modified as outlined in the thread) since v13.0 beta on Nexus 6 and OnePlus 3T. No issues.
[Magisk] whalesplaho:
Same here... Just for asking!

Mind sharing yur best profile please....
[Magisk] adarshadhungel1:
Module not installed.

It says

/data/magisk_merge.img mount failed

and magisk manager apps stops working
[Magisk] ahrion:
Been busy with my new mod specific stuff and then work. The problem is that I have to update like 13ish update binaries because this new Magisk changed quite a bit. Usually I just do batch editing which allows me to make changes in minutes. This will take like a good days worth of work for one of my days off.

It's not just for this mod though. Thank you for your patience.
[Magisk] danvrez:
Does the magisk module zip installs viper as system app or user app?
[Magisk] vrolok:
Thanks. Installed but it doesn't work. Upon opening the app, there's a window saying that the controller isn't installed. There is then the option of installing it and rebooting, but it never manage to do it.

I am on pocophone F1, latest global stable miui, latest stable Magisk.

Edit: back to legacy which is working just fine.
[Magisk] hurray:
I played aground a few days ago with the converter and found out that it throws errors if you have spaces in your profile names. Just exchange the spaces in the profile name with underscores and everything should work.

Another error I found was that some of my profiles have the content 2 times in it. So the main part are capsuled by xml and were 2 times in the profile. I solved this with Notepad++ on my pc but deleting the second main part of the profile.

I hope this helps a little bit. :)
[Magisk] nirogu325:
Aw man...if only I'd read this a bit sooner. I already made each profile manually. Many thanks though! :highfive:
[Magisk] knpk13:
I uninstalled your 2.5 V4A from magisk manager. Then I installed the 2.7 zip using magisk manager. Then it asked me to install the driver from the V4A app unlike previous versions, so I did that. There are no inbuilt DDC profiles available though for some reason. There is no DDC-Orig folder anywhere either. Am I missing something? Why aren't they included in the official 2.7 app (installed from XDA labs) by default? It seems to get redirected to a telegram group to get a VDC/DDC file, and you have to pay for it now?

Edit: I saw a separate zip for VDC's on your website. I'm going to try and use that, although your post said earlier the VDC or DDC would get installed automatically.

Also, where can I read more about how V4A (the DDC feature in particular) works? Because that one feature makes a huge difference to the sound and I would like to understand why/how it does that and why it sounds awful without it. It makes me wonder what's wrong with stock audio settings on Android, and why we need a mod to make it sound clear. I don't understand much about the details of digital music reproduction or what is accurate, neutral sound, although I tried reading whatever I could find on the viper website and threads.

Edit 2: the VDC files zip on your website worked. The audio sounds really muddy without it. I have an ATH-M50 if the model of the headphones matters.
[Magisk] Zackptg5:
There should be a DDC-Orig folder in your v4a folder. I'm not sure, documentation isn't very good for v4a. Ddcs were removed cause a lot of them sucked and it's annoying to scroll through all of those ddcs that you don't use

---------- Post added at 12:56 PM ---------- Previous post was at 12:49 PM ----------

That's been a problem device for a while now. Hopefully the next v4a 2.7 build will fix it for you

---------- Post added at 12:58 PM ---------- Previous post was at 12:56 PM ----------

That could mean a lot of things but older v4as actually did sometimes bug out when making or editing profiles so they were no longer proper xml files.

---------- Post added at 01:14 PM ---------- Previous post was at 12:58 PM ----------

Thanks for the tip! I'll see what I can do about spaces in file names. Ya, original v4a was buggy with profiles and that kind of thing tended to happen. It was way to difficult to add in a workaround for that into the converter since there was no consistency to it, so I just skip it and tell the user their profile is bugged (which it is)

---------- Post added at 08:35 ---------- Previous post was at 08:14 ----------

Whenever the magisk bot quits bugging out (it's being looked into)

The new v4a 2.7 app has been designed to actually work like a normal app - so it's installed as a user app. It has persistent notification (which you can hide if you don't want) which prevents it from being killed off like in older v4a apps. If you recall with original v4a, when installed as a system app, some convolvers won't work so user app is ideal if it doesn't get killed off by system (like in 2.7)

Actually, I just realized the problem. There's 1 workaround that was missing or not working in current v4a 2.7.1: killall audioserver. I have a service script in the module for the module removes it. I'll push a fix for that and let you know when it's up
[Magisk] vrolok:
Great, thanks!
[Magisk] Zackptg5:
Uploaded fix, try redownloading the new one and giving it a go :)

There should be a v4afx.sh script in /data/adb/service.d folder that should run at boot and should fix the issue you were having (you need to kill audioserver after boot is completed so v4a effect can register on some roms)
[Magisk] nirogu325:
Nah, they were .XMLs alright. This post here pointed the issue. Tested with another phone and that user is right.
[Magisk] vrolok:
Installed successfully! Everything running just fine and the new app looks great. Thank you
[Magisk] nagi_007pk:
Viper becomes unsupported after boot (Magisk 19.1)

Ever since updating to the new magisk version, Viper becomes unsupported after boot. I've been using the same modules since forever and this is the first time I'm experiencing it. Is there something I'm doing wrong? Please any help would be appreciated!

For reference I'm using a OnePlus 3T on Oxygen OS v5.0.8 Oreo!
[Magisk] Tyakrish:
I am having the exact same issue as you. If possible provide some magisk installation logs...

So devs can look into it further...

You can also look at the dev's troubleshooting guide...

https://gist.github.com/Zackptg5/35183200c71df3f5b3255ffaa8dc1158

Currently the best way to deal with this is getting rid of Sauron... Or setting SELinux as permissive (If your kernel has support for it)
[Magisk] Zackptg5:
Try the new v4a module
[Magisk] knpk13:
That doesn't answer my other questions, but I downloaded 2.7 again and reflashed it. Like I said, there is no DDC-Orig folder in the V4A folder. I had to use the ones from your VDC zip.
[Magisk] BHUSHAN7988:
Noob question difference between legacy and XHiFI
[Magisk] Tyakrish:
As some user pointed out about the profile converter, that is a problem...

But that aside, I renamed one of my profiles to remove spaces and then tried the new v4a zip... The profile converted successfully and I was also able to load it as a preset in the new app...

But the sound is vastly different from what I expected... The sound seemed to be less louder and sound balance more towards the left ear...

Then I installed the old app and loaded the profile and it sounds proper as usual...

I just installed the new zip in magisk without removing the old module... Am I supposed to remove it first ?

I can share the profile and the files associated with it if you want...
[Magisk] Paschfire:
Read the post on the previous page from Zackptg5 regarding problems after Magisk update.

In the future Pls search the thread before posting to find answers to commonly asked questions.

https://xdaforums.com/sho...postcount=4768

As there should be zero issues install the latest V4A module(s) on the OnePlus 3/3T running Oreo, OOS 5.0.8.

Uninstall/delete all Magisk modules and reinstall.
[Magisk] Zackptg5:
Ok, I see the problem. Working on a fix now

Legacy is v4a FX, Xhifi is Xhifi - not much of a use for this anymore
[Magisk] Fullmetal Jun:
I've been using this kernel (convolver with 100% cross channel) for the speaker on all my devices on the non material 2.5.0.5. It makes the speaker sound better for most of the songs I listen. They sound less monotone & richer.

Don't use for headphones though.

https://drive.google.com/file/d/1RIRgQZfCytr_mDlAXzj1HrF6-07S3Hoe/view?usp=drivesdk
[Magisk] Zackptg5:
Pushed fix for this problem and for profiles that have spaces in the name
[Magisk] gubacsek:
Hey guys!

Does Viper work for anyone on the original pixel with Android Q beta 3?

For me it is always "please install the driver" even after saying it was successful. I was trying to search the thread, but found nothing.

Please let me know if it is a known problem and there is already a solution!

Thanks!
[Magisk] nirogu325:
That new v4a needs to have the option to be systemized like the Legacy version. It would also be neat if it had an Exit button just to restart the service in case it has problems.
[Magisk] hurray:
[MENTION=6037748]Zackptg5[/MENTION]: I just found a little typo in the current version of your installer. The left side was converted with the first version (without considering spaces in profile names) and the right side was converted with the current version.

You can see that there is on the right side a wordwrap too much at the DDC-name. :)
[Magisk] DrCow:
Anyone got idea how yo reduce the bass? I have the bass option disabled but every song with drums or something just go full silent when the bass hits
[Magisk] Zackptg5:
The new v4a 2.7 app has been designed to actually work like a normal app - so it's installed as a user app. It has persistent notification (which you can hide if you don't want) which prevents it from being killed off like in older v4a apps. If you recall with original v4a, when installed as a system app, some convolvers won't work so user app is ideal if it doesn't get killed off by system (like in 2.7).

In short, there's no need to systemize it and doing so will actually break some functionality.

Exit button would also be nice but the bugs that required that have all been fixed in 2.7 so not much of a need for that either

---------- Post added at 12:38 PM ---------- Previous post was at 12:36 PM ----------

Ugh, I'll push a fix for it. Thanks!

Edit: Actually, nothing changed with that vdc stuff so I'm not sure what the issue is there
[Magisk] Seagold:
For proper installation and most efficient sound ? system ;

Download Application uninstaller. (like Root Uninstaller)

How to proceed?

Search ? With the Application Uninstaller remove Adapt Sound and SoundAlive.

Reboot your phone ? and goto Equalizer from your Audio ? player which will take you to ViPER4Androidfx and set it as default.

You can now make all your essential changes and enjoy a world ? of music ? blast.

That's what am using right now.

Hit like button ? if i help you in anyway...
[Magisk] gk1984:
I found the YouTube vlogger!
[Magisk] hurray:
Okay, I have only installed and converted on my TabS2 with the current version. But in case someone has such problems with the converted profiles too I will leave the post as it is.
[Magisk] krkhaha:
Hi. After update to v 4.3 I've got some problem. After reboot when I unlock my s8, viper is already open. Always, I tried many times.
[Magisk] svnhvn:
Maybe it skipped from me, but how to apply profiles?
[Magisk] zecabra:
same thing here, it's a bug or a function?
[Magisk] Zackptg5:
Don't use the FC workaround then or just use the new module (apk v2.7)
[Magisk] mistermojorizin:
Do I still need to keep USB Policy Patcher module installed? Also, if I don't want to have a notification, am I at risk of the new viper getting killed by system and ceasing to work at random times?
[Magisk] Zackptg5:
Not sure for USB. Best thing to do is go to notification settings for v4a app, uncheck notification dot. Then in status bar, long swipe v4a notification, click settings, then choose minimize
[Magisk] tapeworm4602:
Is it possible to add "Lock Effect Mode" so a preset can be applied across all the audio sources?
[Magisk] Zackptg5:
Not sure why you'd want to do that. Different devices all require different profiles since they all have different properties
[Magisk] insan_wicaksana:
Having weird issue on my device after flashing lastest version of viper4android FX legacy magisk module. The application opened automatically by itself after phone finished booting. I'm using xiaomi redmi note 4 (mido) with RR P 7.0.2. This issue happens after I switched rom from LOS 16.0 unofficial to ressurrection remix 7.0.2. Didnt have this issue on previous rom

Anyone having same problem? Had asked in specific rom thread, someone confirming having same issue also that the app opened itself after boot. Didnt know if this specific rom/device bug or from the module itself
[Magisk] knpk13:
I had the same issue, but I just ignored it. I use the new module (V4A 2.7) now.
[Magisk] Zackptg5:
I just answered this on the last page, use the search function in the future (don't use the FC workaround, or just use the new module instead)
[Magisk] hurray:
I have the "automatic awakening of the screen" with V4A from the package 4.3 and also the new 2.7.1 on my One Plus 6 with OOS. At my Samsung Galaxy TabS2 under LOS 15.1 this behaviour doesn't occur.

I thought this is a misbehavior of my music player... :D

If there is a workaround I am grateful for an information about this please as I don't have found it with a search.
[Magisk] Zackptg5:
Literally the post above this
[Magisk] BHUSHAN7988:
Would love a simple widget which closes the v4a and starts it again

And the v4a 2.7.1.0 does the same thing as the old v4a right or is there anything better in that ?
[Magisk] ColtonYYZ:
Any User Guide?

Hi! I've successfully installed FX on my LG V30, thank you.

Noob question here but do you have a user guide I can read on how to use your mod??

LOL sorry. I've tried looking in a few places but apparently not in the right ones.

EDIT: I can't seem to figure out how to delete this post. Moderators: feel free to delete this post. I was able to figure things out on my own afterwards. Thank you!
[Magisk] hurray:
Hmm, I am already on the new module (the zip file which will install V4A 2.7.1) but I will delete everything and start from the scratch. :)
[Magisk] BHUSHAN7988:
I installed as magisk module then followed the step it worked fine

But once I toggled the switch on and off it stop working

Kinda feels bad

And dark mode also not applied

V4a 2.7.0.1
[Magisk] mixlex:
You are in the wrong thread. This is for v4a versions 4.xx.
[Magisk] Zackptg5:
Toggle the audio session switch in settings when that happens. Not a v4a problem but a music app problem.

Dark mode follows system. Search the 2.7 v4a app thread for more info on it (the thread is for older v4a)
[Magisk] nagi_007pk:
No more issues

Works beautifully. Thanks!
[Magisk] bohemist:
I uninstalled the old module and install the new one. It works :svetius:

I don't even need to install the ACP(audio compatibility oatch) because V4A works with Spotify without ACP.

Thanks
[Magisk] Zackptg5:
Yup :)

If it doesn't process, try toggling the audio session switch in settings
[Magisk] bohemist:
Where can I find this setting, if ever... inside V4A or Spotify?

I tried finding this setting but can't find it.
[Magisk] Zackptg5:
It's in v4a settings (for v4a 2.7 apk) - the gear in the top right corner of the app
[Magisk] bohemist:
What about in V4A magisk module, where is this setting?
[Magisk] D-m-x:
Uh, I don't seem to get the hang of the new version. The Installer/Uninstaller worked when I flashed it twice via Magisk, I could open the new App and install the Driver. However it's not processing -> coming back to this Thread to find the Solution, enable the Switch in the settings (whatever the hell the switch does). Processing fine in Google Play Music, but in YouTube for example I don't have any sound if I keep the setting enabled. Is there something missing here? Legacy worked out of the box.
[Magisk] xlollomanx:
Is the same for me on YouTube and Souncloud. Only on Spotify works fine. New APK not working well. Hi back to this module and everything working perfectly.

Sent from my Zenphone Max Pro M1

---------- Post added at 09:25 ---------- Previous post was at 09:24 ----------

Sent from my Zenphone Max Pro M1
[Magisk] gkornaks:
Hi,

I'm on Xiaomi Mi A2 lite. After installing latest May security patch V4A keeps prompting me to install the driver. Any help appreciated.

Thanks!

Germans.
[Magisk] Tyakrish:
Nice... The new V4A works with Sauron and AML perfectly :D... Thank you and [MENTION=9073985]Team_DeWitt[/MENTION], very much for working hard to keep this awesome mod alive...

Actually I prefer using Profiles, so what I did is I installed the new V4A zip, opened V4a app, let it install the new V4A module along with its driver then after a reboot, I installed the old V4A app with Profiles... And it works like charm...
[Magisk] mixlex:
Same here, this one works all the time no matter what source. 2.7.0 version works okay but the 2.7.1 release with that switch, can't be messing with that while driving down the road.
[Magisk] vrolok:
Yep, that would be great!
[Magisk] mistermojorizin:
I don't know what i'm doing wrong.

using the new 2.7.1 module, says driver enabled, status normal, but processing is a "NO" and Viper is not working.

Was using the older version and never had issues.

Pixel 2 xl oreo 8.1, by the way.

What should I try?
[Magisk] mixlex:
Try going back to 2.7.0 or try magisk version. Both work well for me, 2.7.1 has issues for me
[Magisk] BrahmaGandhi:
Hi, anyone can help me.. i was using old v4.3 (and legacy ver. also) magisk zip version with chosen apk ver. 2.5.0.5. i uninstalled it, because i got issue the "flashlight" won't turned on when viper installed.

So i try to upgrade to v2.7 materialized apk, it was successfully installed and works. but how do i transfer my old profile into the new one. i open the apk but here's no option in app for "load profile or even save profile" unlike the old ver. and i just try flash the profile converter zip, but doesn't seem working. i have to setting manual and start over again every installation? any help? thank you
[Magisk] Zackptg5:
Clear data for v4a app. Then when you first open it, follow the tutorial you skipped through
[Magisk] BrahmaGandhi:
Thank you. it works.
[Magisk] Lycon70492:
I'm interested in purchasing bluetooth earphones with aptx/aptx hd codecs. I like to know if V4A works and functions correctly (especially with convolvers) with aptx/aptx hd wireless earphones?
[Magisk] kalpik:
All codecs work, as long as sample rate is not higher than 48khz.
[Magisk] Lycon70492:
Thank you for the reply. How about the convolvers? Any issues with them and aptx?
[Magisk] kalpik:
Sorry, can't say anything about those, since I don't use them.
[Magisk] hurray:
A little feedback: I deleted all audio packages (audio compatibility patch, audio modification library and V4A itself) and installed them again. One thing I found at the reinstall is that I have first have to finish the whole setup from V4A including the driver installation before installing AML.

Now everything works well and the display stays off during plaything music with activated V4A. :)
[Magisk] Zackptg5:
New v4a 2.7 zip is now on the repo! I highly recommend switching to it rather than using the legacy one. I'll update the OP with some details on it
[Magisk] Francescorm76:
Don't install it... With 4.3 work and install... With 7.1 don't install

Enviado desde mi SM-N950F mediante Tapatalk
[Magisk] Zackptg5:
Helpful. What doesn't work with v4a 2.7.1?
[Magisk] Francescorm76:
My problem... With v7.1View attachment 4764976

Enviado desde mi SM-N950F mediante Tapatalk
[Magisk] SVR:
My internet is fine. But getting this error.
[Magisk] iestynapmwg:
I didn't see these details...

What did it actually do? I updated a few magisk modules, this one included. I saw some messages about converting profiles, and left it running. When i came back, the install had finished without prompting me with the usual questions about which version, where to install, etc. I rebooted and V4A is gone, and the module doesn't show in magisk manager any more.

Near as i can figure, the installer ran some conversions, moved some files around, and then deleted its own module. What do i do next to get V4A back? I'm on Pie, if it matters. Thanks!
[Magisk] Paschfire:
Did you do as instructed within the message of your screenshot by Installing AML?