yashsingh1/xdaforums huggingface dataset:
[Magisk] D-m-x:
Just to maybe help I will share my observations.

I have 3 Devices:

Pixel 2 XL on Android 8.1 Stock Rom, Arm64 > New Version worked but had trouble processing sometimes, seemed more unreliable than 1.5.5

Shield K1 on Nvidia Stock Rom Nougat 7.0, ARM > New Version installed fine but processing is unreliable, often showing as No and 5 seconds later as yes

Nexus 5 on Dirty Unicorns 8.1, ARM > Cryptic Name and crashing.

For now I'm going back to 1.5.5 on all my Devices because of reliability. As the Nexus 5 is my spare phone I can Test on it if it's necessary.

Gesendet von meinem SHIELD Tablet K1 mit Tapatalk
[Magisk] matt1313:
I'm getting this also what did you do to resolve it?
[Magisk] baku2313:
New version 1.6.1 Force closed on Nitrogen OS Oreo Redmi note 3
[Magisk] Zackptg5:
Anyone having weird issues, can you try this beta build? It'll install v4a as a data app rather than system. Use twrp for now if you can
[Magisk] D-m-x:
That did the Trick for my Nexus 5 (only one of my 3 Devices having the Problem with constant Force Closes and the cryptic symbols). I'd have to test the Processing on my other Devices to see if that is back to normal also and the Battery Drain. But from what I could test these few Minutes maybe it is.
[Magisk] JBolho:
I don't know if this is going to be a stupid question but... Is there any 64bit Viper driver?

"su -c dumpsys media.audio_flinger" shows that although the audio drivers are also present on vendor/lib, the system only loads the ones on lib64, and Viper is clearly rejected because it shows right on top of the list in "Libraries not loaded"

So the system knows it's there, tries to load it but can't, and as a user already suggested some time ago, it may be because the driver is not 64bit and EMUI 8 only loads 64bit audio libs.

The audio_effects.conf file points to vendor/lib but somehow all those entries are redirected to lib64 by something that I cannot pinpoint.
[Magisk] Dante Enoshima:
Zack, idk if i want to try this one yet, as 1.6.1 with Materialized V4A is always destroy AM3D ( it made AM3D got the classic white screen ), but just in case, what kind of issues that other users before me got?
[Magisk] tom.android:
no driver installed (v.2.6.0.2)
[Magisk] Vatsal157:
This is working for me on my mido. Just like it used to. Thanks [MENTION=6037748]Zackptg5[/MENTION]

---------- Post added at 07:07 PM ---------- Previous post was at 07:05 PM ----------

Uninstall all audio mods and flash viper followed by the rest. Did the trick for me.

Order I followed was - Viper>Dolby>Sauron>AML

---------- Post added at 07:08 PM ---------- Previous post was at 07:07 PM ----------

How did you install AM3D? I always get a white screen. Would appreciate your help on this. Thanks
[Magisk] Dante Enoshima:
For me, it just works, if I don't install the Materialized V4A, but it'll be fine if i install normal V4A. Although i haven't tried it with other sound mod.

I'm on AEX 4.6. My device is samsung galaxy grand prime.
[Magisk] prathu30:
Nothing much hit ok once and select it again it works :laugh: although you have to do it for all the profiles once
[Magisk] Zackptg5:
Viper is 32 bit only but works on 64 bit devices. If emui only loads 64 bit drivers, that'd be exactly why no audio mods that I know of work for it. That's really good to know, I'll add that to the OP. Thanks man!

---------- Post added at 08:35 PM ---------- Previous post was at 08:33 PM ----------

If you're using multiple audio mods with magisk, you need to flash AML as well

It depends on the rom. There are some framework dependencies (not sure exactly what) it requires.
[Magisk] reference2myself:
I switched to this. Works great. Looks awesome. https://xdaforums.com/android/apps-games/app-viper4android-fx-2-6-0-0-t3774651
[Magisk] JBolho:
Here is the output in Terminal of that command. I have put the driver in lib64 as well and checked the paths on the audio_effects.conf files.

Weird thing is, the soundfx folder and drivers are present on both lib and lib64, the paths on audio_effects.conf files all point to lib instead of lib64, but the audioflinger and huaweiaudioflinger drivers are ONLY present on lib64, and that may be the reason why it only loads lib64 audio drivers.

HWSTF:/ $ su

HWSTF:/ # dumpsys media.audio_flinger

Libraries NOT loaded:

Library v4a_fx

path: /vendor/lib64/soundfx/libv4a_fx.so

Libraries loaded:

Library loudness_enhancer

path: /vendor/lib64/soundfx/libldnhncr.so

Loudness Enhancer / The Android Open Source Project

UUID: fa415329-2034-4bea-b5dc-5b381c8d1e2c

TYPE: fe3199be-aed0-413f-87bb-11260eb63cf1

apiVersion: 00020000

flags: 00000008

Library downmix

path: /vendor/lib64/soundfx/libdownmix.so

Multichannel Downmix To Stereo / The Android Open Source Project

UUID: 93f04452-e4fe-41cc-91f9-e475b6d1d69f

TYPE: 381e49cc-a858-4aa2-87f6-e8388e7601b2

apiVersion: 00020000

flags: 00000008

Library visualizer

path: /vendor/lib64/soundfx/libvisualizer.so

Visualizer / The Android Open Source Project

UUID: d069d9e0-8329-11df-9168-0002a5d5c51b

TYPE: e46b26a0-dddd-11db-8afd-0002a5d5c51b

apiVersion: 00020000

flags: 00400008

Library reverb

path: /vendor/lib64/soundfx/libreverbwrapper.so

Insert Preset Reverb / NXP Software Ltd.

UUID: 172cdf00-a3bc-11df-a72f-0002a5d5c51b

TYPE: 47382d60-ddd8-11db-bf3a-0002a5d5c51b

apiVersion: 00020000

flags: 00000048

Auxiliary Preset Reverb / NXP Software Ltd.

UUID: f29a1400-a3bb-11df-8ddc-0002a5d5c51b

TYPE: 47382d60-ddd8-11db-bf3a-0002a5d5c51b

apiVersion: 00020000

flags: 00000001

Insert Environmental Reverb / NXP Software Ltd.

UUID: c7a511a0-a3bb-11df-860e-0002a5d5c51b

TYPE: c2e5d5f0-94bd-4763-9cac-4e234d06839e

apiVersion: 00020000

flags: 00000048

Auxiliary Environmental Reverb / NXP Software Ltd.

UUID: 4a387fc0-8ab3-11df-8bad-0002a5d5c51b

TYPE: c2e5d5f0-94bd-4763-9cac-4e234d06839e

apiVersion: 00020000

flags: 00000001

Library bundle

path: /vendor/lib64/soundfx/libbundlewrapper.so

Volume / NXP Software Ltd.

UUID: 119341a0-8469-11df-81f9-0002a5d5c51b

TYPE: 09e8ede0-ddde-11db-b4f6-0002a5d5c51b

apiVersion: 00020000

flags: 00000050

Equalizer / NXP Software Ltd.

UUID: ce772f20-847d-11df-bb17-0002a5d5c51b

TYPE: 0bed4300-ddd6-11db-8f34-0002a5d5c51b

apiVersion: 00020000

flags: 00000048

Virtualizer / NXP Software Ltd.

UUID: 1d4033c0-8557-11df-9f2d-0002a5d5c51b

TYPE: 37cc2c00-dddd-11db-8577-0002a5d5c51b

apiVersion: 00020000

flags: 00000250

Dynamic Bass Boost / NXP Software Ltd.

UUID: 8631f300-72e2-11df-b57e-0002a5d5c51b

TYPE: 0634f220-ddd4-11db-a0fc-0002a5d5c51b

apiVersion: 00020000

flags: 00000248
[Magisk] Zackptg5:
Hmm, if there are any custom roms out yet for that device, maybe snag the audioflingers and other required components from it and see what happens?

---------- Post added at 16:26 ---------- Previous post was at 16:10 ----------

Okay everyone, since v1.6.2 test build was a success (worked on my bullhead when I recreated the problem too), I tweaked it and dropped a new stable build - v1.7 (I upped the number since a lot changed under the hood). So the big change is:

V4A apk will be installed as a data app now. This will fix any weird issues users may have by switching v4a versions.

If you're doing this through magisk manager, the installer will do this automatically. It'll also detect if any other v4as are installed as data apps and uninstall them.

If you're in twrp, it'll copy the apk to your sdcard and you'll need to do it yourself after booting. If it detects any other v4a installed as data apps, it'll tell you and abort. You will need to uninstall them yourself once booted and then flash it

This is because package manager (what's used to install/uninstall apps) is only functional when the system is booted (makes sense right?) so I can't do anything with it in twrp

Another nice thing is when a new material v4a build is dropped, you can just update the apk like any other app since it's all data

Edit: Rereleased v1.7, changed the material apk version to one with working convolver (it's being worked on)
[Magisk] Trupen:
[MENTION=6037748]Zackptg5[/MENTION] this time in version 1.7 there is no app in drawer
[Magisk] Zackptg5:
Did you read the last post? Also, the installer clearly tells you to install the apk manually if you flashed from anything other than magisk manager
[Magisk] Trupen:
I installed from magisk itself magisk repo
[Magisk] Zackptg5:
Is the app installed? You should have a viper folder in your /data/app folder
[Magisk] Jman420:
Doesn't look like the app got installed when I upgraded. I don't have a viper folder in /data/app
[Magisk] Zackptg5:
Did you install from magisk manager? Can you send the recovery log?
[Magisk] Jman420:
Yup, and working on pulling it now.

---------- Post added at 09:24 PM ---------- Previous post was at 09:10 PM ----------

Hu... well, I tried to recreate the issue with a clean install to take a closer look at the Magisk Install Logs, but on a clean install everything installed fine. I've got the materialized app in my app drawer, although I don't have a viper folder in /data/apps/

Everything is processing as it was before though... so I'm happy. Let me know if you would still want logs from me.
[Magisk] Zackptg5:
You should have a folder like this but if it works, then it's there. Thanks!
[Magisk] peter9811:
In versión 1.7, I can't find the app (I selected the normal version)
[Magisk] Jman420:
Ah, I do have a similar folder called 'com.pittvandewitt.viperfx-1' in /data/app/. Totally missed that cause I was looking for 'viper' in the part after 'com'. Everything is definitely working perfectly off a clean install.
[Magisk] peter9811:
I installed the zip from Magisk
[Magisk] Zackptg5:
Tap the save logs button after flashing
[Magisk] peter9811:
I'm going to do a clear install
[Magisk] peter9811:
Log, installing 1.7
[Magisk] TahirZX:
No app in drawer and no app in /data/app even after clean install of viper original and new.

Flashed through magisk and app is not installed I guess.

(it did say that it's installing app as data app)

I have my sd made as internal storage (so I guess if it stored app there it might not load after a reboot)

Flash order:

1-v4afx 1.7

2-acp

3-aml

Reboot.

I'll try to manually install apk.

EDIT: Exactly as I suspected. Anyhow, I manually installed ViPER4Android_FX_v2505_A7.x_Nougat_IO_test_fix.apk

And app works fine now processing and all.

EDIT 2: app is not working fine... If I remove v4afx from recent I lose processing(I can hear the difference in sound)

I open it back and it starts processing again ?

Didn't had this issue before on version 1.5.5

So going back to it until 1.7 is fixed
[Magisk] Mithias:
Just to confirm v1.7 works for me. I did have a bit of a scare, was on v1.5.5 before and tried a direct upgrade but the app wasn't showing so decided to disable and remove v1.7 before doing a fresh install. After removing then reboot I got stuck on boot screen. Thankfully was able to reboot into recovery, wiped the dalvik cache and phone booted fine after that. V1.7 installed fine after that.

Seems old profiles aren't compatible with the new material app though, not a massive one but wouldn't allow me to upgrade my old profiles to the new format so had to re-create them

Thanks Zack! I got Viper back!
[Magisk] Zackptg5:
There are some weird chcon errors at the end of it but other than that everything looks good (no chcon errors on my end so not sure what happened there). Still no app in the app drawer? Do you have a viper folder in /data/app?
[Magisk] peter9811:
I found the app, but see
[Magisk] Zackptg5:
Can you go through the troubleshooting guide on the OP? This issue should be address in it
[Magisk] peter9811:
I used the module since 4 months. Ever work to me, I don't know...
[Magisk] peter9811:
I removed the module, I restarted, I made a cache wipe, I installed the module, I restarted and I think everything is working fine
[Magisk] Herk718:
It's actually not working fine, your still not processing, so your not hearing viper at work.
[Magisk] Badger50:
Maybe he's not playing music? ?
[Magisk] Herk718:
Well... I am, and it's still not processing on latest version 1.7
[Magisk] flitzz:
I want to report some strange problem with convolver IRS effects. When I am in the program this effect is working fine but when the program goes in background it stops making its magic. Someone with this problem? This was not present in the last version.
[Magisk] kopitalk:
It's time to read the troubleshooting guide in OP!
[Magisk] Herk718:
[MENTION=4476875]kopitalk[/MENTION], all is well now! Thanks bro!
[Magisk] flitzz:
I reinstalled it also with AML and now is Ok with cash and dalvik cash wipe on TWRP.
[Magisk] choukawaii:
1.7 here. But I can't access any profile and I can't check whether the driver is installed correctly or run properly. It says error communicating with V4A services. Kindly check it.
[Magisk] Redhawk2000:
Was finally able to get 1.7 to work. Couldn't get it to successfully install a driver despite multiple tries until I used twrp to remove and then reinstall AML and then wipe cache and davlik. Then I had to toggle the master power (as noted in the OP) to get it to work.

One thing that doesn't seem to work for me is the playback gain control. It doesn't seem to change the volume whether I enable it or not. Even on extreme setting.
[Magisk] Dante Enoshima:
[/COLOR]

I did flash AML, but it still happens. Is there a way to get logs for both V4A and AM3D ( and i'm assuming that could help )? Currently i'm on Magisk v16.3

Edit : O here's the log, hopefully it'll help

For now, i'll return to the original V4A
[Magisk] Zackptg5:
I think this craziness is about to come to an end with the final update for the day for me: v1.7.1

Here's the scoop on the problem:

For reasons still unknown, if a user switches from the new material v4a to any other v4a, they'll be met with constant FC's due to android system not distinguishing it as a different app from the previous v4a installed. The only way to fix this is to switch from a system app to a data app or the other way around (for example: user has original 2.5.0.5 installed to system. They then install new material to system -> constants FC's. Solution: user installs material to data, android system figures everything out somehow).

So what v1.7.1 does is kill 2 birds with 1 stone:

Original v4a (2.5.0.5 and 2.3.4.0) will be installed to system like how we've always done it. This should prevent it from being killed off by swiping away in recents for the most part

Material v4a (2.6.0.3) will be installed to data. It's been updated so that it shouldn't get killed off by a recents swipe and if it does, it should restart itself.

This should hopefully fix all of the issues we've have been having
[Magisk] zigbye82:
Why does it install as a user app now?
[Magisk] Zackptg5:
I tried to explain it in the last post. Only the material v4a is installed as a user app. It works fine (and was designed to be) a user app. It's a workaround for the FC issue people were having when switching between v4a versions
[Magisk] zigbye82:
My bad, cant believe i didnt notice your post just above. i use the original but it gets installed as user also.

Edit: i was using 1.7 i see there is 1.7.1 now.

Working great. Thanks to you guys.
[Magisk] Zackptg5:
Confirmed success! Yes! :D
[Magisk] neekless:
Why did the UI for the material version change to all the settings on one page? Each setting used to open it's own page, which was better imo.
[Magisk] NE0HP:
Yes! 1.7.1 works perfectly on my device Mido running PixelExperience (8.1). In addition your latest DA Axon7 unity build also works great side by side! Thank you ?
[Magisk] dalepothen:
Yeah me to facing the same problem the ui for material design is not there i was used to it so i dont have a clue how to change it in here that was more easy hope devs check on the issue
[Magisk] agplugged:
Flashed 1.7.1, with the latest material app through magisk. On reboot, indeed no app was installed but an apk showed up in my data folder. Installed it, currently no FCs and running smoothly.

Thank you so much for your hard work. It is much appreciated.
[Magisk] kopitalk:
You need to understand that the new material design is done by different devs. See viper menu help & about and go to their xda thread, and make your feedback known there :good:
[Magisk] hurray:
[MENTION=6037748]Zackptg5[/MENTION]:

If have Magisk 16.3 and the following behavior:

- V1.6.1 works very well (driver 2.5.0.4 and V4A 2.5.0.5)

- V1.7 I don't see any of the V4A-apps so I can't check the driver status

- V1.7.1 V4A is there (I use 2.5.05) but tells me to install a driver

So for now I am back on 1.6.1 which runs fine.

This behaviour is under OP3 with OOS and a Samsung galaxy Tab S2 with LineageOS 14.1. The installation goes smooth on every version without any errors.

This was written just as an information. :)

V4A is for me one of the most important apps, keep up the good work! :)
[Magisk] Ferbee:
[MENTION=6037748]Zackptg5[/MENTION] Materialised 2.3.4.0 driver, everything works but Playback gain control do you know why?
[Magisk] rippledrums:
Updated from 1.6.2-beta to 1.7.1 and everything is perfect. Great work! :good:
[Magisk] fahric74:
1.7.1 works perfectly on my S7 edge oreo port rom with magisk 16.3! Thanks!!
[Magisk] Pablo.x:
1.7.1 running great on lastest NitrogenOS for my 3T with Magisk 16.3.

Thanks a lot for the amazing work!
[Magisk] neekless:
Yeah I've sent them a feedback. Couldn't stand the clutter so I went back to non-material 2.5.0.5
[Magisk] DrNinjaa:
Magisk 16,v4Android 1.7.1, OnePlus 3T,

Viper works but can't load any profiles
[Magisk] Trupen:
[MENTION=6037748]Zackptg5[/MENTION] this app is installed
[Magisk] Pablo.x:
Try load it a few times, it didn't work for me at first...
[Magisk] Trupen:
[MENTION=6037748]Zackptg5[/MENTION] In downloads section of magisk viper is showing different name and in module section it is showing different name
[Magisk] potan:
ok, so the last time work 1.6 version. on this new version both 1.7.0 or 1.7.1 when i close the app from recent app ( just slide it so it not seen from recent app with out clearing cache) it effect gone. when i use 1.6 the effect still there even after reboot clear dalvik and cache but i can only use 2.3.4.0 old version when i install the new version i must install the app manually then it ask me to install driver.

my problem is i hope in this new version when the app closed the effect still work. thx
[Magisk] TahirZX:
Finally 1.7.1 works perfectly (upgraded from 1.5.5 original new 2.5.0.5 to 1.7.1 original new 2.5.0.5)

It removes all the remnants of old v4a installation so be sure to back up/save your profiles guys.

Here is log and screenshot.
[Magisk] TahirZX:
Just a quick question what's the difference between 2.5.0.5 and 2.6?
[Magisk] potan:
this is the log from 1.6 version, i hope you sir can enlight me, where i do wrong
[Magisk] GohanBurner:
April 10th not working correctly. Every time I switch tracks it stops working until I open Viper and uncheck and check enable again.

4/8 was working just fine

Pixel 2 walleye
[Magisk] Trupen:
Same here [MENTION=6037748]Zackptg5[/MENTION]
[Magisk] DaveedDB:
What font do you use

Sorry for ot
[Magisk] Trupen:
I install fonts from typeface fonts available on playstore
[Magisk] Zackptg5:
Thats cause Android is killing off the v4a service. Get rid of any battery Saving apps like greenify
[Magisk] Taebom:
The latest version is working perfectly on my Pixel 2 XL running April security update.
[Magisk] GohanBurner:
Issue seems to be with the FireEqualizer. Everything else seems to be working but when you switch tracks you have to manually re-enable the fireequalizer so that it works. All the other options seem to work so I'll have to substitute ViperBass and Clarity in for now until its fixed :(
[Magisk] kzhkr:
a qns.. the new ones have an exit option to quit and restart app when no processing occur. how do we exit for the old version v4a?
[Magisk] whitewallman:
Does it survive reboot? Installed and worked great until reboot. After that, driver status says

Enabled: No and Processing: No. Same setup as you, Pixel 2 XL April security update.
[Magisk] xxxreyxxx:
i have installed latest version along with dolby atmos by Ahrion but it seems dolby not processing while v4a installed but when i uninstall it, dolby remain processing
[Magisk] rippledrums:
Please read the OP, the thread or use search. That is a known issue, you have to re-enable after boot.

If you are using Oreo, Dolby and V4A use different ways of processing the sound and don't always work well together.

Also for people who claim V4A stops processing, if you are on Oreo (maybe Nougat too) you have to set V4A to not optimize in the system battery optimization settings and lock it in recents so it doesn't get closed there either. Also if you have battery saving apps like [MENTION=6037748]Zackptg5[/MENTION] mentioned, you have to configure them to not kill V4A.
[Magisk] Trupen:
Viper not working with you tube

Also after some time again no processing

Removed from greenify

But still no processing frequently
[Magisk] Trupen:
[MENTION=6037748]Zackptg5[/MENTION] confirmed viper not working with YouTube

Viper works only with music app
[Magisk] Didgeridoohan:
That all depends on your setup, because I've got V4A processing just fine with YouTube. V4AFX v1.7.1 installed on my OnePlus 3T (OOS 5.0.2), no other sound mods.
[Magisk] sjamie:
V4AFX v1.7.1 is also working on YouTube for me. (OnePlus 5 - xXxNoLimits 10.3 ROM)
[Magisk] Trupen:
Did clean install what m I missing ?
[Magisk] Ragnar Eldur:
I'm reverting back to your original module before the 2.6

Yours was solid with the system type app and the module coded nicely into the system ensuring flawless processing without any hiccups no matter if selinux is in permissive or enforcing. Also I could theme the materialised version with nice black background that I uploaded here. Just installing that APK as update for the system app, then reboot and everything works just fine.
[Magisk] Trupen:
[MENTION=6037748]Zackptg5[/MENTION] I think I noticed that viper is running but when checked status it shows not processing,

But in background it is running,

That's y may be I thought that it is not running with YouTube
[Magisk] Ragnar Eldur:
Ok here is the materialized magisk module with the system type app that you just flash trough TWRP just make sure to uninstall any existing ViperFX modules. Reboot and if you want the AMOLED theme just download the APK I made and it will update the system app with the new theme.
[Magisk] Ragnar Eldur:
Here's the AMOLED APK
[Magisk] Ragnar Eldur:
This is just for those needy who really want this now. Then we can give the hardworking developers the time they need to do their thing.
[Magisk] D-m-x:
I have to agree on that, good that the choice is given. Wish I could disable Updates for certain Modules in Magisk. 1.5.5 seems to be the most reliable Version without hiccups in processing.

Thanks for all the work and continues support to everyone who is involved here. This is great work and really the first Module o flash on every Device I own! Felt this was necessary to say :)

Gesendet von meinem SHIELD Tablet K1 mit Tapatalk
[Magisk] Ragnar Eldur:
Oh forgot them screenshots
[Magisk] Ragnar Eldur:
The only minor bug with this theme is the section where you choose the Viper Bass and Clarity mode. The colors are the same so you can't really see what mode is active but you'll notice the button click animation effect when click on the desired mode. Total nightmare finding that bloody color value in the APK editor, even after hours of trial and error.
[Magisk] Jecmenn:
Hi, i have this weird problem and i tried searching for it but really couldn't any solution or even someone with same problem.

So basically after installation, in certain apps (mostly games, but also some standard apps) the sound that comes from the speaker is very distorted with a lot of crackling. I am 100% certain it's this mod because when i uninstall it, the problems are gone. Is anyone having same issue? I'm on Android 8.1.
[Magisk] AlexxAnders:
I would love to see some progress here.

---------- Post added at 09:51 PM ---------- Previous post was at 09:41 PM ----------

Did you try to just disable it or do you really need to uninstall it to have the problems gone?