yashsingh1/xdaforums huggingface dataset:
[Magisk] shadowstep:
[MENTION=6037748]Zackptg5[/MENTION] Thanks for the update! I have a request. Would it be possible for you to include the V4A-FX 2.5.0.5 Black 'n Red edition as well as the Inverted edition (latest ones here) in this zip as well? That way, this unity zip will have all the possible versions of V4A and will be the most complete zip. :)
[Magisk] Gerard15799:
Does it work on ROMs running 8.1 Oreo?
[Magisk] Badger50:
It does on the P2XL. However, your device may vary.
[Magisk] whitewallman:
Thanks for the update!

I noticed that with 1.6.5, when you clear away v4a in recents (either by itself or with other recents), it kills v4a processing of audio until you either launch v4a app again or reboot. I don't recall this behavior with previous builds. Pixel 2 XL 8.1 stock/rooted April security update.
[Magisk] tpuserhp:
Same problem here. Thx.
[Magisk] Lughnasadh:
Same here. I'm wondering if it has to do with the assigned OOM grouping of 2.6.0.4. I noticed that its assigned grouping is for Content Providers, while the old V4A (2.5.0.5) is assigned to Foreground Applications.

Anyways, last week I pointed this out to [MENTION=9073985]Team_DeWitt[/MENTION] over at their official thread and he said he was gonna do some research on it.
[Magisk] shadowstep:
+1, reverted to v2.5.0.5 for now. It also stops processing when swiped away from recents, but starts again automatically in a second.
[Magisk] Zackptg5:
That'd be too many apks in 1 zip unfortunately. Only way for that would be aroma but lots of devices don't work with it and it's twrp only
[Magisk] shadowstep:
No problem, thanks for the consideration. Keep up the good work! :)
[Magisk] cichy.:
new version the new material app fix problem with Spotify on speaker, thank you [MENTION=6037748]Zackptg5[/MENTION] and app developers :D
[Magisk] Zackptg5:
V4A updated to v1.6.6! Changelog: Updated new material apk - should fix issues with the app closing when swiped away (and other stuff too, check that app thread)
[Magisk] jugoslavpetrovic:
Could this run well with latest supersu?
[Magisk] Nitz327:
The newest version breaks convolver for me :'(. I noticed this immediately because I've been using viper for a long time and the previous version was the only one where its ever worked properly haha. It has to be toggled off and on individually while viper is processing to get it to work, just the convolver setting. Toggling the main switch doesnt work for it :S. I'm reverting to a backup but I grabbed a log if that helps!

Newest Material UI, Newer Driver.

Edit: Also, I just noticed a weird coincidence. Could be nothing I dunno, but the most recent update changed something so Viper would contunue to process uninterrupted when swiped away from recents. The previous version it stopped processing but only for a second, then comes back on and all is well (including convolver). The ONLY time it's ever worked for me properly was the previous version so maybe whatever was changed for the newest update has something to do with it? Sorry, hopefully that makes sense haha.
[Magisk] Zackptg5:
Yup. This one fixed the closing issue so it'll always be running. The convolver issue has been around for a while with the new material. Its not broken, just different. With other v4as you needed to toggle master power. With new marterial, you need to toggle convolver instead. Its also helpful to resave your profile with the new material too cause some of the backend for that changed (happened a few versions ago but not sure which you were on).

Post the convolver stuff on the material app thread (link in op) so the devs can take a look at it
[Magisk] Nitz327:
Oh I see I see, thanks I'll resave my profile and check out the material thread. Love your version of it tho!
[Magisk] abhi021:
Hi can someone tell why new materialized V4a does not work with old driver. When I select old driver it install old UI in spite of selecting new materialized version.
[Magisk] crumble6:
Anyone else getting a persistent "ViPER4Android FX is using battery" notification with latest version?
[Magisk] FullWipe:
Put viper in optimized apps and notification will gone.
[Magisk] crumble6:
It's not in my app list.
[Magisk] bademjooon:
Does anyone have this problem?

How does this fix?
[Magisk] jugoslavpetrovic:
I just flashed the latest update and during flashing process I have chosen material app with latest driver and latest app version but it seems to me it is not the material version.

Note: it runns well when closing app, without stopping.

---------- Post added at 12:15 PM ---------- Previous post was at 12:14 PM ----------

Not on my side.
[Magisk] Zackptg5:
The new material is based off of the 2.4 app gui so it looks older but isn't. Just go to the help and about section in the side app pane and you'll see
[Magisk] jugoslavpetrovic:
That makes sense then. Thanks.

Even though I more liked the older material cuz with this way there is way more scrolling though and is easier to loose focus, lol.

I'm new to this mod, does it survive the dirty flash of rom?
[Magisk] Zackptg5:
It depends. If you're on magisk, yes (since it's installed to magisk img in data). Otherwise, if your rom has addon.d support, it'll survive
[Magisk] jugoslavpetrovic:
Is there a way I can check myself if ROM has addon.d support?

I use AICP rom, custom kernel, supersu...
[Magisk] jcmm11:
See if /system/addon.d exists
[Magisk] jugoslavpetrovic:
There is. Thanks.
[Magisk] dvishalkhatri:
Latest material version ... Viper4a is using the battery... Is appearing the notification even after optimisation
[Magisk] Zackptg5:
It means nothing, side effect of the persistent notification (which can be hidden btw)
[Magisk] sjamie:
To me is easier to toggle Master Power on/off than to have to scroll down to toggle Convolver. Maybe that's just me...
[Magisk] marklm725:
I am on Oreo 8.1 rom pixel experience 64bit with a Moto g5 plus (Potter). Receiving an error message error communicating with viper4android service. Any ideas? I am using Magisk and have installed AML and audio compatibility patch and tried different install methods and nothing works.
[Magisk] ianbassi:
I can't hide the icon now. The setting disappeared on the viper menu.

Enviado desde mi Z2 Plus mediante Tapatalk

---------- Post added at 05:10 PM ---------- Previous post was at 05:06 PM ----------

I think this material to viper is nice but it shows everything and is a mess. That would be a good change. Manage modules like before but with this new material design.

Enviado desde mi Z2 Plus mediante Tapatalk
[Magisk] mistermojorizin:
do you happen to know why this wasn't happening with 1.65, which also had the notification option and I was using it.

Well, I think the quote was "it can be hidden," not "it can be hidden from settings in viper like in 1.6.5".

Just open notification drawer, long press on the viper notification itself, and a slider should appear. slide it to the left ot hide. the notification will be hidden, but the viper is using battery message doesn't go away.
[Magisk] Zackptg5:
That's just a part of the android system. It says that for most persistent notifications (like my music player for instance). It's just letting you know that it's running in the background
[Magisk] sjamie:
Friends, you can simply disable the "X app is draining battery" notification by following these steps.

https://www.techrepublic.com/article/how-to-disable-persistent-notifications-in-android-oreo/
[Magisk] jugoslavpetrovic:
I was having weird active media icons on navbar even with no sound playing like there was some kind of active sound going on with latest material version, and as users reported permanent notification, also device was heating and deaining battery without anything playing which lead to slow down the device due to thermal. Flashed 2.5.0.5 and it seems fine now.
[Magisk] bobbarker2:
That's funny, my experience is the exact opposite. Old drivers don't work and new drivers do. Using material app.
[Magisk] kirt231:
Drivers will not install

trying to use old material v4a. i can not get the drivers to install. v4a says to install them, i click yes, and it says i.o error.

i have tried completely uninstalling and reinstalling the module.

this is stupid that i have to fight with this all the time. i have to kill v4a, uninstall reinstall, enable disable the master switch or something. it does not ever just work when i turn on my phone or music app. serisously annoying that i cant get it to a point of set it and forget it.

ive tried old driver new driver old material app new material app, and just old old app.

im on oreo 8.1. pixel 2 based rom.

---------- Post added at 04:49 PM ---------- Previous post was at 04:24 PM ----------

There are 3 choices of apps to choose. Old material new material and old old app.

There are 2 choices for drivers new and old.

It must be hard to get all 6 choices to work some what flawlessly on every device and os.

Why not just stick to 1 or 2 choices and streamline the development a bit? Options are nice but just having **** work is so much nicer.
[Magisk] sjamie:
I can totally understand your frustration; however, let's remember this is a FREE mod the devs support on their free time at no charge to us yet they make it available to all of us to enjoy. I am confident all bugs will eventually be squashed.
[Magisk] groverXIII:
Ever since the 1.6.5/1.6.6 update, I've run into issues where if Viper is idle for a bit (usually longer than a couple minutes), when I start listening to something again I have to pull up the app, manually exit it, and then reload it before it starts processing again. I'm on 8.1, have Viper installed through Magisk, and didn't have the issue before the 1.6.5 update. I've tried this with both the old and new Material interface and have uninstalled/reinstalled Viper several times. Any ideas?
[Magisk] Zackptg5:
Have you run through the troubleshooting guide in the OP? It address this problem. The driver is installed but just not being detected by the app. The likely reasons are either sepolicy or another mod conflicting with it. Can you post a full logcat and magisk log?

Adding additional apks is easy, all of that dev stuff was figured out a while ago. The hard part is making an app designed for nougat compatible with all oreo devices

Nothing changed in those updates other than the new material apk so if you're having issues with any other apk, then it's likely your system or another app killing the v4a service. Disable any battery saving features or apps like greenify and see if that fixes it
[Magisk] groverXIII:
Weird. I disabled battery optimization and don't have Greenify or anything else running, so no idea why it's suddenly doing this.
[Magisk] cmo220:
I have driver problems unless I uninstall all sound mods, then reboot, then install Viper. That seems to be the best way to get to work, at least for me.
[Magisk] Zackptg5:
Im assuming you're using aml? If so, uninstalling and reinstalling aml is probably all you need if weird stuff starts happening
[Magisk] cmo220:
I was using it before, I stopped for now. I was just telling the other person what I did to fix it when I had the driver problem. Good to know that it's probably only AML. Thanks!
[Magisk] kheltek:
I have an odd issue with 1.6.6 on pixel 2 xl running rooted with magisk on stock. I have no other mods installed (i.e. greenify or anything else). I'm running flash kernel. 1.6.6 installs fine (both new and old interface, new and old driver), but defaults to the speaker setting, regardless of whether I have a pair of headphones or bluetooth connected. I don't see anything in the logs causing it. When I manually switch to bluetooth, for example, it stops processing. Once I exit, and open viper again, it goes right back to speaker. I installed 1.6.5 and don't have nay issues.
[Magisk] Zackptg5:
The only thing that changed between those builds is the new material apk so if you're using it, post thr bug report on the app thread
[Magisk] kheltek:
Will do. I'm going to try it again this afternoon and grab a log.
[Magisk] g0d0fmischief:
Nexus 6P ElementalX kernel, stock 8.1, magisk v16, substratum with Swift black theme.

I've read here others with my device and rom had this working, but I for the life of me can't. I'm using the magisk module, going through the install flashing from magisk manager, I've tried both drivers new and old, with and the new material design plus old. Seems to go fine with both, except one major thing. It says driver isn't enabled. I tried different v4as in the past to no avail either, causing bootloop ect, but this time from what I've read in this that this should work. Thanks in advance, any insight would be appreciated.
[Magisk] Zackptg5:
Can you install it again, choose new original (2.5), reboot, then post your magisk log and /sbin/.core/img/ViPER4AndroidFX folder?
[Magisk] g0d0fmischief:
Sure can, I'll get it in just a bit. New original? Material and 2.5 driver?
[Magisk] P-Griffin:
I have the same problem!
[Magisk] Love Dhir:
Not working on my moto g4 plus rr oreo 64 bit
[Magisk] Badger50:
Logs man...he wants the logs :cool:
[Magisk] Love Dhir:
It was showing driver wasnot installed i yried several times then i uninstalled it installed dolby any suggestions?
[Magisk] kopitalk:
Has viper ever worked in your 64-bit rom before?
[Magisk] caryle:
Will Viper4Android work fine with LDAC?:) It didn't work on my phone with LDAC.
[Magisk] Love Dhir:
Nope
[Magisk] kopitalk:
-_-!
[Magisk] g0d0fmischief:
Sorry it took so long, did the original install with new 2.5 driver. Think this is what you want, I've left it installed for now as well.
[Magisk] Zackptg5:
I mean like actually posting the zipped folder and saving the magisk log. But can you try removing app systemizer and seeing what happens after a reboot?
[Magisk] g0d0fmischief:
App systemizer removed, still not enabled. The full log is in the previous response, tell me which zip and I'll post it and anything else you need thanks.
[Magisk] Zackptg5:
That looks completely normal. It's not enabled because you didn't enable it...
[Magisk] g0d0fmischief:
How do I enable it then? I don't see any choices or settings for that

NVM..

.... Are kidding me.... All this trouble and got to turn it on to enable it. Well at least I can say for certain in the past I turned in on and played with it, it wouldn't ever work. Thought it was more of the same this time, didn't see the need to play with it.
[Magisk] g0d0fmischief:
Ok last question and thank you for your time

Now that we've gotten it enabled, I really mainly stream music these days, is this going to make any difference or work at all using a service like Spotify/Google play music/YouTube music?

I've noticed under the processing it says No, and it doesn't really seem to make any difference when I change settings, I've seen others in this thread mention using a streaming service like Spotify, so it lead me to think it could.

Thanks again, You've been a great help thus far.
[Magisk] Zackptg5:
If you're using the new material (v2.6) apk, then it might work on it's own. Otherwise, you may need to install audio compatibility patch: https://xdaforums.com/apps/magisk/module-universal-deepbuffer-remover-t3577067
[Magisk] peterlee928:
when i updated v4a in mm from 1.6.5 to 1.6.6, then rebooted, then opened v4a, i got the notification to install driver.

after attempting to install the driver, i got the error message "driver is not installed. an error occurred while obtaining the device's fingerprint. please try again. contact the developers if this problem persists."

then i closed the app... when i tried to restart, i got the error message "com.pittvandewitt.viperfx.viper4android has stopped." i wasnt able to open the app thereafter and continued to get this error message.

i had to do a full uninstall of 1.6.5, then reinstall of 1.6.6 to get v4a working.

attached is the magisk log for reference.
[Magisk] g0d0fmischief:
I found the v 1.4 patch, magisk module that you've done. Trying that now.
[Magisk] Didgeridoohan:
You had to change SELinux to enforcing to make it work? That's interesting...

Is your kernel permissive by default? In that case you'll have to change back to enforcing after a reboot.
[Magisk] whalesplaho:
I have Sony Xperia Z5 7.1.1, i think its permissive by default. Buh it doesnt change in selinux changer. I just have to reboots like twice to make it work again. On first reboot doesn't always works except on second reboot.
[Magisk] marbertshere:
[MENTION=4667597]Didgeridoohan[/MENTION]

Maybe you can help me. I tried uninstalling this mod using the uninstaller zip in the OP. I wanted to try TopJohnWu's Viper module since it worked for me in the past, but every time I open Viper or just asks me to install the driver again. Status shows as abnormal.

I tried to edit those files you mentioned earlier by changing the lines about SePolicy and changing permissions. That hasn't helped. I'm wondering if I messed up during the uninstallation process (when flashing the zip). Any ideas? Or know if a better place for me to ask?

Angler, Resurrection Remix ROM 7.1.2, Magisk v13, Franco Kernel
[Magisk] Zackptg5:
Flash audmodlib uninstaller. The audmodlib folder contains vendor config files which are conflicting with the regular viper module
[Magisk] marbertshere:
Oh I thought the zip in the op would have uninstalled all the mods, not just viper. Thanks!
[Magisk] appman1234:
When the v4a working, my Redmi Note 4X cannot pass the SafetyNet and vice versa.

Is it normal? I think it is related to disabling SELinux.

Any advice? Thanks!
[Magisk] Zackptg5:
You need to keep selinux as enforcing or safetynet will fail. Also, if you modify system, safetynet will fail. So only way to pass it is using magisk v13 betas
[Magisk] whalesplaho:
No workaround yet for Viper4Android showing No in processing.... Without it processing, sound effect doesnt work.
[Magisk] Nye-uhls:
Try adding the build.prop lines i mentioned in the post at the bottom of the previous page
[Magisk] whalesplaho:
I have added dah... Whats yur android version?

On Android 7.0 it was working perfectly.... Buh now on 7.1.1 its not processing.
[Magisk] zoel.fahmi:
Tested, working good
[Magisk] bomblader:
You're the man. I had the same problem and those lines fixed it. Cheers!
[Magisk] Nye-uhls:
I think its more related to magisk than android version, although I'm not sure cuz I'm on 7.0 (thanks samsung)

Did you set permissions for the files in /magisk/.core/ post-fs-data.d & service.d to 755?

Otherwise i have no idea, you might want to just try flashing the v4a+audmodlib uninstaller and using the v4a module from the magisk repository (from topjohnwu) instead.
[Magisk] whalesplaho:
I might try dat and see... Tha issue im having is processing showing NO.
[Magisk] eclipseo:
Good lord thank you so much, I have spend the afternoon trying to install Viper4Android and kept getting Status: abnormal until I've found this thread and the Magisk v13 problem.
[Magisk] whalesplaho:
i have tried tha module from magisk repository, installed but not showing on phone... dnt know why!!!

my workaroud is to insert handsfree jack & reboot den it will process.... it so frustrating!
[Magisk] Didgeridoohan:
For the repo module you'll have to install the app manually. Click the module in the Downloads section of the Manager and you'll find the link.
[Magisk] whalesplaho:
okay. will give dat i shot now & see.... i have v4a app!

thanks
[Magisk] whalesplaho:
Yeah, v4a in app drawer now but still stock with tha Processing:No bug!!!:crying::(:(:crying:
[Magisk] D1stRU3T0R:
Basically, what will this do? Better sound? Can i use it with PowerAmp?
[Magisk] g0d0fmischief:
It works for a little, says processing and effects certainly work, you call tell in changing them, but before a song even finishes it kicks off, and says processing: No. You call certainly tell when it stops, sound reverts. Have to reboot to get it to work again. Can't even make it through a song.
[Magisk] RedLikeSnow:
Dynamic bass for Bluetooth is acting weird, latest los 15.1, would provide a log if necessary. (old material apk)
[Magisk] sjamie:
Try using the old 2.3.4.0 driver.
[Magisk] Zackptg5:
V4A has been updated to unity v1.5.3. See unity thread for changelog. V4A specific changelog: Added 2.4 v4a for completeness since it was the only one missing :) Added compatibility to match what apks are compatible with (back to ics for all but 2.3 which goes back to gb) cause why not. I don't have any devices this old to test so if anybody is for some reason still using an ics or gb rom, let me know if it works

So you can now add 'mid' to the zipname for 2.4.0.1 apk

On another note, I made a unity installer for the old V4A XHiFi just because I can. It works fine for me but I still have no idea what other sepolicy patches it'll need (if any) so I'm calling it "beta" for now. Link is on the OP if you want to use it.
[Magisk] peeporzor:
App not showing in app drawer. Please help me with steps to get it back. See log file. Thanks
[Magisk] Zackptg5:
Steps are in the OP. Uninstalling and reinstalling all audio mods is a good troubleshooting step too
[Magisk] repey6:
Hi. I did this(uninstal DA oreo and reinstall) but after this V4A 2.6.0.4 asked driver installation again and after reboot V4A not showing in app drawer. Redmi 4x 8.1 . AML not helped. Original version not have this issue.
[Magisk] Zackptg5:
Ah, so its an app issue. You could try installing it as a data app if you want but first, can you send me a logcat so i can see what's causing the error?
[Magisk] repey6:
Thanks for reply. I tried both method installation Viper but the same issue. Logcat is so hard for me , sorry.:)

Upd. Sorry i forgot to say that Viper HiFi successfully was installed and worked on my NOS 8.1 Redmi 4x. And with Viper FX original 2.5.0.5 worked together too. Thanks .
[Magisk] whitewallman:
Hello. I just noticed that since updating from 1.6.6 to 1.6.7 in driver status, sampling rate is no longer 48000, but instead 44100..
[Magisk] Zackptg5:
There's nothing in the update that could have done that. That's all dependent on your device. Its typically 48000 for speaker and aux and 44100 for bluetooth but it can vary
[Magisk] whitewallman:
Sorry. I was unaware Bluetooth was active. No problems. Thanks for clarifying and the support!
[Magisk] Mithias:
Not sure if it was this or the latest AML update but since installing I'm getting no processing through v4a even though the app says it is. Able to confirm by putting some settings in then enabling/disabling in v4a and hearing no difference in sounds.

I also tried installing the ac but same result.

Removing and rolling back to 1.6.6 resolved for now, processing back again.

Shout if you need me to test and try producing a logcat to help out. Need to change to a different app for that though as catlog seems rubbish when it comes to getting exportable logs!
[Magisk] DarkSilentSC:
Still have to toggle EQ again to get it into effect in bluetooth. I guess the app issue still hasn't gone completely yet.
[Magisk] Jman420:
I just noticed some V4A funkyness on my commute today (not sure how long this has been going on, but i dont think it can be more than a couple of weeks). When I'm using my bluetooth headset the V4A Speaker settings are used as opposed to the Bluetooth Settings. I still need to experiment a bit to see if its a buggy install or related to some combination of new material app and drivers...

Driver : 2.5.0.4

App : Material 2.6.0.4

Phone : HTC 10

OS : Oreo

Rom : LeeDroid

Update : Seemed to just be a buggy install. Tested a whole bunch of combinations going back to the original app, all of them worked. When I went back to the above config it worked as expected also. *shrug*