yashsingh1/xdaforums huggingface dataset:
[Magisk] Jecmenn:
Disabling it doesn't do the trick, need to fully uninstall.
[Magisk] TahirZX:
Same issues
[Magisk] AlexxAnders:
At least V4A is working for you;)
[Magisk] Homeboy76:
Blind in one eye can't see out of the other. lol Overlooked 'with Pixel Support' in the OP. :eek:
[Magisk] Josey Wales:
Have the FIREqualizer sliders been fixed, this is what I've been seeing with the last few updates?
[Magisk] Zackptg5:
That's something with your device. This contains the official 2.5 app which I've never seen so that before
[Magisk] DrNinjaa:
The problem of the latest v4Android who are using the old v4Android (not the materialized) not working was most probably the new audio modification library 1.5.4,I used the 1.5 version and all good and I'm able to load profiles too.
[Magisk] Zackptg5:
AML has nothing to do with that stuff (v4a part of it didn't change at all). That's all due to v4a zip
[Magisk] Zackptg5:
Although I love the new material apk, I recognize that some users still prefer the old material one and so with v1.7.2, I added it back as an option. So there's now a whopping 4 apks in this zip :eek:

For those who use the zipname option instead of the volkeys, some of the options have changed so see the OP for the new options
[Magisk] agplugged:
Well, I'm back with an old question of mine.

Since Compatibility mode has been removed, every time I listen to music with v4a enabled and a system sound comes on, the mod restarts processing. It takes a moment but it stops the music completely, and makes listening to music unbearable atm. Is there anyone here who has experienced this and knows the solution?
[Magisk] neekless:
does the old material install as system or data? with the new material installed to data, it gets killed when swiped away from recents and restarts itself a few seconds later. this causes it to have a few seconds gap where it is not processing, which sounds terrible.
[Magisk] nanchilanto:
Where can i download 1.5.8 version ?
[Magisk] neekless:
there's no 1.5.8. if you're talking about 1.5.5, go to the download link in the OP and click on "Old Builds".
[Magisk] Josey Wales:
Thanks for adding back the old material theme. Can you fix the FIREqualizer sliders, I have the toggles but do NOT the blue slides in my previous pic post?

Galaxy Note 5 SM-N720T

Stock rooted 7.0
[Magisk] KorokHidup:
Yep , i did realize this too , when v4a swiped off from recents , audio effects disabled for a few moments the it restart , but that's doesn't bother much.
[Magisk] neekless:
He already answered you:

How can he fix your device's problem?
[Magisk] b00ster:
Confirm. I hava a gap in the beggining of each track in Spotify, it is horrible, using v 1.7.1. Also I do not like new Viper app, old was much better in terms of settings and stable work (material version).

Switching back to 1.5.5 which works flawlessly on my OP3T with Nitrogen OS (Oreo).
[Magisk] Didgeridoohan:
Use v1.7.2 and choose the old material app. It'll be just like before.
[Magisk] kopitalk:
How do you guys update the V4A magisk module? I have Ainur, Dolby Atmos and V4A with AML; every time I update V4A I always uninstall the old before installing the new and then reboot, but that resulted Dolby FC. My work around is to uninstall ALL sound mods and reinstall them again one by one with AML being the last :silly:
[Magisk] neekless:
So old material installs to system?
[Magisk] Didgeridoohan:
Yes: https://github.com/therealahrion/Vi...ad57be144a26309082665f/common/install.sh#L187
[Magisk] agplugged:
This happens to me on both 1.5.5 and the latest builds.

I asked around about this on several v4a threads but got no answer.
[Magisk] neekless:
I'm using 1.5.5 and I'm not facing this issue, because it's installed as a system app. Is yours installed as system in 1.5.5?

---------- Post added at 05:23 PM ---------- Previous post was at 05:21 PM ----------

So if I'm using 1.5.5 old material there's no reason to update to 1.7.2 old material right? Since it will be the same?
[Magisk] agplugged:
I honestly haven't checked but I've flashed through the Magisk repository so I believe it installed as a system app which, to my knowledge, is what caused the whole FC issue in later versions.
[Magisk] D-m-x:
In theory yes. However I'm unsure if something has changed underneath. I'm also interested in this.
[Magisk] Zackptg5:
Depends on your device but since 1.5.5 worked for you, it'll probably end up the same

Only switching between the new material and another v4a (if all are installed to system) causes FCs, hence why k ly new material is installed to data

In terms of old material, it'll be just like before except there's dynamic output session processing effect removal which should increase compatibility
[Magisk] pehlm:
@Zackptg5, thank you for adding back the old material system app option. If having had the old material app installed before and then trying to revert to the original system v4a app (if I don't want the new material app) for unknown reasons it can't be opened because of FCs. And thanks for your work! :good: :good:
[Magisk] Didgeridoohan:
Take a look at the changelog... Seems like the only thing that doesn't have to do with the new/old apk's is the dynamic effect removal. If that doesn't feel important to you, there's probably no need to update. If it works, it works...

But then again, it looks like v1.7.2 works too. :p

Edit: Ninja'd!
[Magisk] Pro4TLZZ:
Guys it's working but what settings should I use for my headphones, I listen to hip-hop /rap
[Magisk] 123lisa:
Error

Hey there,

so, I own a Moto X Play, codename lux. It runs on the unofficial Resurrection Remix 6.0.0 (based on Oreo 8.1), is rooted with Magisk (16.0 Stable) and Xposed is installed (latest 90.1 Beta). I installed Viper (Unity, 1.7.2), Dolby Atmos (Oreo Port, Unity) and Ainur Sauron (MK II.II 24.03.2018) (and of course AML 1.5.4). Both, Dolby and Ainur are processing music from Youtube, Tidal and other streaming services well, while Viper keeps saying Processing: No. So I tried to fix it by installing the compability patch, but that didn´t help. After turning off the AudioFX, I get a toast, saying error communicating with the Viper4Android service. Any idea how to fix it? If logs are necessary, I am more than happy to provide them.
[Magisk] manpildo:
Depends on your phone, headset, other installed sound mods (if any) and personal preference. Conclusion: Nobody can tell you.

I personally use simple settings with my Nexus 5X and Sony XBA-C10 earphones:

SRS_2_2.irs convolver

Natural bass boost 40Hz 10dB

Natural clarity 3.5 dB

You can try if that satisfies you, but I'm 99% it won't since we use different setups and have different personal preferences.
[Magisk] kzhkr:
tried installing old material via 1.7.2, still force closes.
[Magisk] jandia7381:
+1
[Magisk] DarkPJV:
Friend could help me install viper4android in emui 8.0 I have a p10 huawei. Please try many ways and it does not work for me
[Magisk] Zackptg5:
Try removing all of the audio mods. Then remove audiofx and any other system eqs. Then flash v4a, acp, sauron, and aml. See if it works, then add dolby if it does. Dolby oreo doesn't always play nicely with v4a so my guess is that that's the issue

What steps did you do? Logs?

What steps did you do? Logs?

Unfortunately, no audio mods work with that device/rom. All of the audio mods I'm aware of that are oreo compatible are 32 bit and the p10 requires 64 bit :(
[Magisk] kzhkr:
1. did an uninstall on current viper4android (original)

2. install 1.7.2

3. chose material >> old then rebooted.

4. open viper4android, force close occur until uninstall.
[Magisk] Zackptg5:
Can you post a full logcat? What android version are you on? oreo 8.1?
[Magisk] kzhkr:
i can't post a full logcat, once it force close i can't do anything apart from uninstalling it after reboot before i can use the phone.

OP5, Oreo 8.0
[Magisk] Trupen:
Same here rolled back to 1.5.5
[Magisk] kzhkr:
i tried using 1.5.5 also resulted in force close. i can only use the original.
[Magisk] Zackptg5:
You could do it via adb, also, can you post the v4a magisk folder?

You do realize that v1.7.2 is identical to v1.5.5 other than the addition of the new material apk and the full removal of old installs. Also, without going through the OP troubleshooting guide, I can't help you (I need logs and stuff or it's just guesswork)
[Magisk] Shriac:
The old material version (1.7.2) with 2.5.0.4 gets detected by malware as play protect. Which version do I install to avoid this and how do I reinstall
[Magisk] Sneheth:
Uninstall by deleting the module in magisk and reinstall the new material app
[Magisk] Shriac:
Thanks. Play protect problem solved but it got installed as data app now. Gets killed after sometime. Can't have best of both?
[Magisk] Sneheth:
I didn't get such issue. Try unistalling by flashing the same zip again. Reboot the device and install the zip again.
[Magisk] Kingfisher25:
Try turning battery optimising off for v4a should stop it getting killed off.
[Magisk] Zackptg5:
PSA:

So I've been looking into the FC issue and it only seems to happen with this scenario:

Device is on an Oreo 8.1 encrypted rom

User switches to a different V4A apk

V4A is installed as a system app

The current solutions are:

Don't switch v4a apks

Install v4a apk as a data app, then after opening v4a, reinstall as a system app

This happens regardless of zip version (happens with v1.7.2 and v1.5.5)

Really not sure how to address this problem at this point a I'm not even sure what the exact problem is at this point but I'm looking into it. If anyone figures anything out, let me know
[Magisk] erak606:
Hmm, I'm having the problem where my audio works for my music player (Blackplayer EX) with Viper enabled, but once I try playing something else like Youtube, my audio doesn't work at all until I disable Viper.

I've looked at the main post and tried all the fixes. The Audio Compatibility Mod just breaks all my sound. Any help?
[Magisk] D-m-x:
Interestingly it doesn't happen in all cases, didn't to that on my Pixel 2 where I switched forth and back while it did it on my Nexus 5, both on 8.1.

Easiest Solution for now would be to not allow switching Apps when updating a existing Installtion imho. One could however Uninstall it before but it would eliminate at least most cases where it will fail.
[Magisk] Zackptg5:
That's just it. During the upgrade process, the mod is completely uninstalled first. It appears that when an app is installed to system, some remnants are left over somewhere when it's removed while with a data app, all of it is removed on uninstall.

Due to that, there's no way for me to accurately detect that. My test device has been my nexus 5x on 8.1
[Magisk] cichy.:
[MENTION=6037748]Zackptg5[/MENTION] I updated V4A 1.6.1 to 1.7.2, everything works fine, but during the update (without removing the previous one manually) the phone has been reset and didn't want to boot :(

I removed battery, the phone booted, app was be installed but without drivers and without file on Magisk Manager.

I removed the app and installed the zip file again via Magisk Manager and it works!

I don't know if I broke something or this is bug in update script - anyway, just I wanted to tell you :D
[Magisk] D-m-x:
Mhm thats quite interesting. So the only reliable way is a Factory Reset. But switching between the old App and the new Material has never been a problem?

The thing is, as time progresses it will sort itself out because more people will have reset there device (we're at XDA after all, it isn't that uncommon) and won't have Problems.

Gesendet von meinem SHIELD Tablet K1 mit Tapatalk
[Magisk] jcmm11:
The only thing I can think of is that the viper entries in /data/misc/profiles/[cur/0 and ref] don't get erased and the old entry causes a conflict with the new version.

I'm totally guessing here.
[Magisk] Zackptg5:
I suspected that too so I had the installer erase all of that but it still didn't make a different. The files were recreated during boot. I had it literally remove every viper related file/folder from data and it still happened. I'm thinking it has to do with encryption as well
[Magisk] Juansega99:
Hi men

I am reporting a error with the new UI has data app and the error is the app doesn't load the convolver FX and sometimes not process the audio i am with the latest magisk and the manager.

THX

Sorry for my bad english but this is not my native language
[Magisk] Zackptg5:
[MENTION=4025179]D-m-x[/MENTION], [MENTION=4487388]jcmm11[/MENTION] and anyone else victim to this goofy android behavior, I got a beta build with the hackiest "works for me" logic ever. I have it set so that if you're on oreo 8.1+ and are on an encrypted device, you can choose to do the hacky workaround so you can switch v4a version and have them always installed to system :)

If by some strange chance you're phone reboots endlessly, delete the /data/v4a.sh and /system/etc/init/v4a.rc files in twrp

Are there any users who have the FC issue when switching system v4a versions that aren't on oreo 8.1+ and are encrypted?

Edit: Reattached new beta build
[Magisk] MrBrady:
Pixel 2 XL (Taimen) withV1.7.2 of this module on stock Android 8.1 April Security Release. Using the 'new' Viper app selection.

Today while driving I noticed both Waze and Google Maps would lower the music volume during navigation directions, but the voice itself wouldn't play.

Uninstalling this module and the nav audio worked fine.
[Magisk] Zackptg5:
This is due to notification_helper. Just reflash v4a, then comment out (or delete) the notification_helper effect in the audio_effect files in the module folder
[Magisk] kzhkr:
will give this a try when i'm back from work.. godspeed!

---------- Post added at 12:17 PM ---------- Previous post was at 12:16 PM ----------

possible to request permanently comment this out for every update if not how do we do that? TIA ;)
[Magisk] dalepothen:
Is that the latest version can you share the module with me i was stuck with the new material design i used to use the design which u have so im familiar with it
[Magisk] Ragnar Eldur:
Here's the last module before the change that you can theme with my AMOLED APK. Make sure to remove all existing modules first then flash this zip in TWRP. After reboot you can install the APK.
[Magisk] Ragnar Eldur:
And here's the APK
[Magisk] TENN3R:
I don't get why after flash I still have to install manually the apk in latest versions. Is it possible to add a /system installation for the new material apk? Like the older version I mean
[Magisk] II_DiE_4:
Dont know about all the problems ppl facing, but i love the new material! You can even choose the driver, and i have it with the old 2.3 one that i like better.

Also i managed to change a couple of times, while deciding which to keep, between the new and old one. Just hit the delete button of both, v4a and aml, in the magisk manager, reboot, and reinstall both of them. Just deleting v4a resulted in some strange behaviour.
[Magisk] cichy.:
I back to 1.5.5, in version 1.7.2, the effects suddenly stop working when I leave the application
[Magisk] Zackptg5:
Can you guys try the beta build here and let me know how it works for you? https://xdaforums.com/showpost.php?p=76203663&postcount=2770
[Magisk] cichy.:
the same problem that is in 1.7.2

I open Spotify and I start play music

I turn on the effects in V4A and effects work

I stop music/switch to Spotify and V4A tells me that the effects aren't turned on but in the app they are still selected :/

When I play music again all effects gone

I hope that you understand me :d
[Magisk] Zackptg5:
Try selecting a different v4a app and/or install audio Compatibility Patch
[Magisk] TENN3R:
He says: "Are there any users who have the FC issue when switching system v4a versions that aren't on oreo 8.1+ and are encrypted?"

Unfortunately I'm on 8.1 and I'm not experiencing crashes for now
[Magisk] gil80:
They don't have 755, they only have rw-r-r. This is usually the default. I don't understand why it's not 755 if it should be.

Anyway, I'll give it a shot but I doubt it.

Update: Nothing it working...

any other ideas?
[Magisk] Didgeridoohan:
You're using beta software. Expect bugs.
[Magisk] gil80:
I would generally agree. However, it seems that everyone has it working for them.
[Magisk] Didgeridoohan:
The bug with boot scripts not getting the correct Execution permissions not being set automatically should apply to all newly installed scripts on v13+beta, it'll be fixed eventually. It's as intended and you'll have to do it manually. And everyone does not have this module working for them on the v13.0 beta. The module needs to first be updated for the new unified Magisk daemon. It probably also work if you set SELinux to permissive, but that's usually not advicable.

While waiting for a new version of the module, you can do the changes yourself... In the post-fs-data.d and service.d folders, in /magisk/.core, open up the two audmodlib.sh scripts and change this line:

SEINJECT=/data/magisk/sepolicy-inject

to this:

SEINJECT=sepolicy-inject

That should work...
[Magisk] LazerL0rd:
Ah, I'm sorry it was for the latest beta. Things need changing for older magisk and SuperSU.

---------- Post added at 05:49 PM ---------- Previous post was at 05:46 PM ----------

Ah, great thanks. ??
[Magisk] gil80:
Still not working.

I made the changes to both files as you suggested.

The permission settings they have is the default rw-r-r.

I used the zip file to uninstall all v4afx files from the OP and then reboot and then used v4afx_v1.4.zip to install via twrp and reboot once again.

I edited the files.

Reboot once more and still have this abnormal issue.
[Magisk] Didgeridoohan:
The scripts need to have permission 755, rwxr-xr-x, or they won't execute (that's what the x stands for).

Try again.
[Magisk] gil80:
Thanks. I gave all scripts 755 cause I had enough :)

It's working now.

Will this be fixed when Magisk 13 will be out of beta?
[Magisk] Epikarus:
Thanks for your response!

I think this is just a magisk problem. Im using magisk 13 beta on a Galaxy S6 on Nougat 7.0. I think the beta magisk 13 just doesnt play well with Touchwiz. I noticed the problem is that once Magisk Manager is cleared from memory (manually or automatically) magisk looses root. It works well right after boot, but if its cleared from memory root is lost. Even though root is lost viper still works, so i think the problem will be solved with subsequent Magisk updates.

On another note, I've installed deep_buffer remover but i cannot get processing to work with google play music. It works with youtube and apple music, but google play music is the only app it doesnt seem to process. Is anyone else getting this problem?
[Magisk] Didgeridoohan:
The v13.0 beta is very much aimed at finding compatibility issues with Samsung.

It's not supposed to be like that (I can force stop the Manager, clear it from memory, etc and still have root). Capture a logcat and share it in the beta thread (with a detailed description). There's already been some reports on this, but it doesn't hurt to have more logs.
[Magisk] Epikarus:
Yeah, I've reported a logcat to the magisk beta thread, but for now I have viper working so I'm satisfied. Thanks again for your support. Really love viper when listing to music.
[Magisk] marbertshere:
Howdy. When I was using JohnWu's Viper module on my old rom, all I had to do was rename audioeffects.conf and reboot to get it working. I'm on a new rom (Resurrection Remix) which doesn't have that file, bit comes with AudioFX and MusicFX installed. I've turned off AudioFX but it's still not working.

Do I need to install BusyBox? It's my understanding that Magisk comes with BusyBox, I don't want to mess anything up.

Should I uninstall booth AudioFX and MusicFX? I don't want to break something.

Nexus 6P, Resurrection Remix 7.1.2, Franco Kernel, Magisk b13.

Thanks!
[Magisk] Didgeridoohan:
Working fine over here on v13.0 beta with this slight modification. No Busybox installed either...

I've no idea about AudioFX or MusicFX. Make a TWRP backup and give it a go...
[Magisk] marbertshere:
Okay I edited those files, I'll reboot and give it a go!
[Magisk] Aditya H:
Thanks a ton for the support mate. I've been searching for v4a on selinux enforcing for days. After using the module and changing that line in the script and setting correct permissions it's working! Awesome!
[Magisk] marbertshere:
Thanks, it worked after disabling those packages
[Magisk] e-cl:
Latest magisk 13, doesn't help. Also put attached file in post-fs. V4a driver is only active if selinux set to permissive. Is there any other workaround?
[Magisk] Didgeridoohan:
I'm using that modification to this module on v13.0 (54e6a79) beta with no issues (SELinux enforcing). What attached file?
[Magisk] e-cl:
vipersupportfix.txt

I renamed it to sh, put in post-fs-data folder, set permissions. I even tried to run it manually, but in terminal emulator it says

<

(Android M policy compatibility mode)

source type audioserver does not exist

Error in: allow audioserver audioserver_tmpfs file read

source type audioserver does not exist

Error in: allow audioserver audioserver_tmpfs file write

source type audioserver does not exist

Error in: allow audioserver audioserver_tmpfs file execute

(Android M policy compatibility mode)

source type audioserver does not exist

Error in: allow audioserver audioserver_tmpfs file read

source type audioserver does not exist

Error in: allow audioserver audioserver_tmpfs file write

source type audioserver does not exist

Error in: allow audioserver audioserver_tmpfs file execute
[Magisk] Didgeridoohan:
Just to make sure: You are using the V4A module from this thread, right? Not any of the other ones floating around?

If you do the modifications I mention you don't need that script in post-fs-data.d. Just do the two simple edits to the audmodlib scripts and you should be good to go.
[Magisk] cichy.:
Compatibility Patch doesn't fix anything for me but... old material works correctly :o

I hope you can fix new material!
[Magisk] Zackptg5:
I'm not the dev of the app itself but that's a known bug and a fix is in the works
[Magisk] AlexxAnders:
So when will Viper4Android x64 be released?
[Magisk] Zackptg5:
Couldn't tell you. It only gets updated every few years so probably not for a while if ever :(

---------- Post added at 13:26 ---------- Previous post was at 13:24 ----------

Okay everybody, after extensive testing, I've inadvertently found the cause. It seems that oreo 8.1 encrypted devices (and maybe more) don't like v4a being in vendor/app. Not sure why, but simply moving it back to /system/priv-app fixed all of the FC issues. As such, I changed the version number back to v1.6, and removed all builds after v1.5.5 since they were bugged.

Anyways, v1.6 is out! Changelog:

Backtracked version numbers - removed buggy/broken builds

Add jni for all v4as

Use priv-app only for v4a

Various bug fixes and improvements

Updated new material apk

Unity v1.5 update
[Magisk] Shriac:
1.7.2 new version requires every time to turn on and off the effects to start processing. Went back to 1.5.5 non material version and all is well. Why did I upgrade when everything was working fine....
[Magisk] Zackptg5:
Try 1.6, should fix all of that
[Magisk] kzhkr:
nice job! working for me :)
[Magisk] Shriac:
Will the material app trip play protect? I need play protect for banking apps.
[Magisk] Zackptg5:
Old will, new won't
[Magisk] cichy.:
v1.6 new material works very well, really great job [MENTION=6037748]Zackptg5[/MENTION] !
[Magisk] zigbye82:
Latest version fixed convolver not processing all irs files. Convolver is working now with all of my irs files. Great!
[Magisk] sjamie:
Awesome! Can we just flash 1.6 over a previous version or should we really uninstall the previous one first?
[Magisk] Zackptg5:
You can just flash it over like always
[Magisk] sjamie:
Dude, I must say this business with the volume keys is very dope in my opinion.
[Magisk] Zgadnijcie:
What is it? I have 1.7.2 version of viper and can update to 1.6. Is it possible? [emoji848]

Wysłane z mojego Redmi Note 4 przy użyciu Tapatalka
[Magisk] sjamie:
What is the secret to getting profiles to load correctly. Some will and some won't.