yashsingh1/xdaforums huggingface dataset:
[Magisk] desu1337:
I'm using a axon 7 a2017g running stock nougat b10(so Dolby is baked in).I am having the same issues with processing and also (even if it got better now through the updates) less bass/overall volume with the new 2.6.3.0 (using the same 2.3.4. Driver)Also I noticed that if Dolby is activated just once(which for the speakers is a must on the a7),processing in YouTube doesn't work anymore/no sound was there at all with v4 turned on,when switched off it immediately works again. So I reverted back to complete 2.3.4.for right now,more bass/volume,no hiccups, it even works fine with Dolby,dont matter if speaker or headset. .Just wanted to report.

-edit: I also tried it with ACM and ACP,only one at a time and both simultaneously,also installed in every possible order but didn't work out.
[Magisk] shindiggity:
Yeah 1.5.8 is last version that works on my Pixel XL 2.
[Magisk] AlexxAnders:
As mentioned a few times in this thread, Viper is 32 bit and EMUI 8 just needs 64 bit drivers. So we have to hope and probably wait, that there will be a 64 bits version of Viper4Android some day. :(
[Magisk] JBolho:
It's even stated in the OP now.

Although it mentions the P10, all Huawei / Honor devices running EMUI 8 only use 64bit audio flingers / drivers, thus every audio mod available right now will not work. Period.
[Magisk] agplugged:
+1

Are you using any other sound mods?
[Magisk] youtuber123:
OK thx for the info... Will wait so ?
[Magisk] mistermojorizin:
I have a pixel xl 2 also. I am also running 1.5.8, but I cannot find the install zip on my phone. Would you mind sharing it if you have access to it?
[Magisk] peterlee928:
DELETE
[Magisk] peterlee928:
zip files should be in your magiskmanager folder.

or see attached for latest version. this works for me and other p2xl folks. see my prior posts for my phone details.
[Magisk] mistermojorizin:
Thanks so much.

Yea it only goes in the magisk folder if you download from Magisk. I got it somewhere else because the Magisk repo didn't have it anymore (it was on version 1.6.1 or so at the time). So I had it in my download folder, but I guess I erased it and couldn't figure out where I downloaded it from.

Edit: I looked in the module.prop of that file you posted (the test one) as well as the readme, and it says it's version 1.6.3
[Magisk] peterlee928:
yep, its 1.6.3. its the beta version of the one thats up on magisk.
[Magisk] desu1337:
Nope,just the original Dolby, i tried Ainur sauron and James DSP once, but I didn't get it to work here. Also tried every install order there + v4a/acm/acp activated/deactivated/uninstalled,but couldn't manage to get it to run. How bout you?

-also forgot to mention before that I'm (stuck) on magisk 15.3(manager 5.5.5.),higher versions would give me problems passing safety net ,stupid ZTE firmware ~.~
[Magisk] Badger50:
How do you define the "Original Dolby"??? Not trying to be sarcastic, just curious is all :cool:
[Magisk] agplugged:
I'm using Sauron with AML, on OP3T 8.0. I think it's either a Bluetooth or app-driven issue, though it also happens to me when using Blackplayer. I've asked around both threads but no one answered me.

Edit: [MENTION=6037748]Zackptg5[/MENTION]

Latest update (1.6.3), now it seems I can't toggle the convolver on/off without switching to another IRS file first. Anyone else experiencing that?
[Magisk] desu1337:
Maybe i shouldve better called it the stock Dolby for the axon7,but it's always a bit hard translating if u don't speak English all the time :D I meant the one that comes pre-installed/baked-in with the axon 7 stock rom(in my case for the European a2017G it's 7.1.1. b10 to be specific),so no zip or magisk module is installed.

As far as I know/tried the one Dolby module in Magisk that says axon 7 basically shows what it looks/sounds like, but it may not work exactly like the original one because it's a port to work on multiple devices.But I could be wrong on that too, so just feel free to correct me if I'm wrong :D
[Magisk] shindiggity:
Are you asking for the 1 5.8 zip?
[Magisk] mistermojorizin:
Yep. It works well on my phone, I have it installed, but I'd like to have the install zip for backup purposes.
[Magisk] Zackptg5:
That's a known bug with new material apk. It's being worked on
[Magisk] shindiggity:
Here you go

https://www.dropbox.com/s/tpl8l10mq9j128m/ViPER4Android_FX-v1.5.8.zip?dl=0
[Magisk] sam2c:
Hi,

There's a very strange bug on the Essential Phone. This has been around since 8.0 beta. I posted this in the Essential forums, and at least one other user is having the same problem. In fact, it occurs with any EQ app it seems, including AudioFX! Viper4Android installs fine and works great, until you receive a phone call. If you're playing music and receive/place a call, after you answer the call and hangup Viper4Android no longer processes. Before the few latest updates, you would have to reboot the phone for Viper4Android to start processing again. Now with 1.6.3 you can at least Force Stop is and restart it for it to start processing.

Any help from the Devs in solving this issue would be appreciated. Please let me know if there's any way I can help with this, donations included
[Magisk] whitewallman:
After comparing old vs new driver on Bluetooth earphones, I really couldn't notice a distinguishable difference. However, like I said, the front facing speakers on the Pixel 2 XL sound noticably better with the new driver. Especially lock/unlock and navigation sounds, for example.
[Magisk] st4ik:
sometimes the viper stops processing the sound.

does anyone have such a problem?
[Magisk] Zackptg5:
Are you on new material? If so, redirect all app related issues to the app thread (link in op of this thread). In the app thread, there's a list of stuff the devs need in order to properly troubleshoot the problem in the OP of that thread
[Magisk] sjamie:
That means the Pixel 2 is definitely implementing some of it's own special magic. :cool:
[Magisk] kzhkr:
Updates from my end.

Updated from 1.6.2 to 1.6.3, having random no processing issues after reboot. Have to force close it then reopen to allow processing to occur. Didnt have such issue with 1.6.2. :)

OP5, OOS Oreo 8.0 (New Material, Old Driver)
[Magisk] VK'ed:
Play protect warning is back.

Using new material+old driver
[Magisk] shadowstep:
Just ran a Play Protect scan and I got no warning. Using the latest new material apk + old driver.
[Magisk] VK'ed:
Upon installing even i had run a scan and didnt get any warnings but today morning i gt it
[Magisk] groshnack:
[MENTION=6037748]Zackptg5[/MENTION] : I have a question for you concerning V4A and LDAC. When connected to my LDAC headphones, V4A does not process except if I change Bluetooth sample rate in dev options from 96khz to 48khz. JDSP works fine whatever the sample rate is. I was trying to automatically set this rate to 48 but the setting does not stick. I have read elsewhere that this is due to the viper processing chain. Do you know if this can be fixed or if there is another workaround than modifying manually this setting at each BT connection?
[Magisk] Zackptg5:
I don't have any LDAC devices myself and this issue in particular sounds like an app/driver issue so there's nothing I can do to fix this unfortunately. JDSP may be best choice for this situation
[Magisk] flitzz:
After flashing Sauron my Viper4Android and Dolby Atmos not processing. I've made logs. The strangeness is that during playing I hit "Master Power" Off and then "Exit" V4A. When I start the application again and "Master Power" On, V4A is processing again, but only temporary. It shuts off next after system reboot or when "Master Power" is switched Off and On. The situation with DA is the same only it can't be restarted from the service. [Samsung Note 8 N950F, Custom ROM I N F I N I T Y]
[Magisk] papoy1019:
Did you install AML? As for me, what I did is flashed Sauron first, then Viper4, next Dolby and lastly AML.
[Magisk] flitzz:
Yes It has been flashed. I do it every time to make them work both. But in my opinion the problem is with Sauron. Without it V4A and DA can not process. They are processing with the previous version of Sauron from 24.03.2018 not with the new one from 15.04.
[Magisk] tbqstp:
Hi, V4A processes hitchleslly with my LDAC headphones (Sony WI-1000X).

I'm only running V4A with no other audio mods (running OOS5.04 on OP5).
[Magisk] groshnack:
Can you check in developper settings, when connected, what are the bluetooth settings? (codec, sample rate, number of bits, ldac quality)
[Magisk] papoy1019:
Mine, I updated but no prob. Asus Selfie. LOS 14.1.
[Magisk] DarkSilentSC:
V4A says not processing in youtube for speaker. Bluetooth seems to be working well.
[Magisk] tbqstp:
Sure. Let me know if you require anything else.
[Magisk] Shriac:
Can anyone confirm if new material version is tripping play protect. Someone reported it few posts back. I was about to upgrade but stopped because of the play protect issue
[Magisk] Zackptg5:
Never tripped for me
[Magisk] desu1337:
Got the new material With 2.3.4 driver on my htc m8 for ~3days and nothing,just did a scan again,nothing,so seems safe for me.When I got it on my axon 7 I had no reports/issues with play protect either, but I downgraded around a day to complete old 2.3.4 on that device because the new didn't work properly,so can't give a 100% on that.

Edit-also never had it tripping with original 2.3.4,any device.
[Magisk] VK'ed:
I was the one who reported about the triping. After installing the latest version i even ran a manual scan of play protect and it didnt trigger any errors. Today morning, out of the blue, the warning was back.

I hope someone can help me out here
[Magisk] kopitalk:
Never tripped for me too, running new material with old super quality driver.
[Magisk] groshnack:
Ok your sample rate is 44.1 khz, that's why v4a process. I have 96khz. I don't know if this is a limitation of OOS or something else. I am on OP3 but on custom roms, i haven't used OOS for a while. Thank you!
[Magisk] NE0HP:
For me, even old material version with new drivers gave me a play protect warnings (not suddenly though since I never checked it on Play Store), in fact it started tripping just after I manually turned on play protect scan to check to see whether it scan it without giving any warning for v4A. But unfortunately Play Protect does detected V4A (old material) as malware. I re-flashed the v 1.6.3 again and uninstalled the old material v4A. Flashed v 1.6.3 again and this time I choose the old v4A with new drivers and I did not faced any play protect warnings till this time. (I think best way is to avoid scanning play protect manually unnecessary - lesson learned):laugh:
[Magisk] xlollomanx:
On my opo latest v1.6.3 works only on YouTube and spotify. If I open any audio file from local audio player I cannot hear anything. BTW on 1.5.5 it works. Any log or file can be helpful?
[Magisk] erak606:
Hi, if I were to connect my phone to a DAC through a USB OTG cable should it show up in Viper as speaker or USB/Dock? I would expect it to use the USB/Dock but it's being controlled by the speaker menu instead.
[Magisk] Zackptg5:
Updated V4A to v1.6.4! Changelog: Unity 1.5.2 update, add AML detection/notification for noobs, update old material to latest repo version (no longer trips play protect, uses switches like original 2.5 v4a, lots of other improvements)
[Magisk] Shriac:
version 1.6.4 with new material version and old driver working well. No play protect problem as of now.
[Magisk] peterlee928:
fyi 1.6.4 is giving me the same issues as before (ie driver issues). see attached files.
[Magisk] peterlee928:
update - uninstalling the old version and reinstalling the new version fixed the issue. see atrached files.
[Magisk] VK'ed:
Is it possible that the play protect is triggered on phones with updated Google play services/playstore?

My G play services version is 12.5.29

Play store: 9.6.11
[Magisk] flitzz:
With this version everything is ok, it is processing correctly the problem was with PowerAmp and one of its option of Direct Sound Control.
[Magisk] TENN3R:
Just want to point out: new material version when listening spotify (for me), disables and re-enables itself on every song, so I can hear the equalizer start and stop everytime. Also doesn't process audio for offline songs.

May be related to the new material apk itself, I don't know, old material works good.
[Magisk] Zackptg5:
Considering that you're the only one, unlikely. It's probably another mod you have installed triggering it. What all do you have installed?
[Magisk] VK'ed:
No other mods.

Just clarity 3.1 on RR N.

P.s. someone else also mentioned above of the same issue.
[Magisk] Zackptg5:
Hmm, I suggest following this guide to fix safetynet. I'd also uninstall and reinstall latest magisk just to see if that fixes it too

https://xdaforums.com/apps/magisk/guide-magisk-troubleshooting-t3641417
[Magisk] whalesplaho:
Is the new v4a materialised safe to install?

Reading so many issues about it... Thanks!
[Magisk] Zackptg5:
It's perfectly safe to install, ot just has some minor issues that are still being worked out (you can check the app thread linked in the OP for a bug list. If you don't feel comfortable with it, you can always use the older material (it's not really old anymore, just updated it)
[Magisk] whalesplaho:
Thanks a ton... Will flash latest version n stick with 2.5 version and it just got updated so plus1!!!
[Magisk] xlollomanx:
My phone is Oneplus One. I'm currently on dirty unicorn Oreo on 1.6.4 magisk module. Installed 2.5 app and drivers. V4a works perfectly on Spotify and YouTube vanced, but if I play music from my music player (shuttle+) or mixplorer audio player v4a say not processing. Attach all log, magisk log and screenshot.

Sent from my Oneplus One
[Magisk] matt1313:
Pixel 2 XL tried 1.6.4. Unistall all mods prior.

Installed fine. Driver was there when I play music it processed but the driver status said it wasn't.

Tried Dolby also with aml and stuck at boot up.

Back to 1.5.5
[Magisk] Zackptg5:
That's a known issue with new material, it's being worked on (or may be fixed already, I'll have to check). Dolby oreo doesn't play nicely with v4a (or anything else for that matter). Also a known issue but nothing we can do about it, it's the nature of the dolby port. So that has nothing to do with aml. Can you post your aml folder with v1.5.5 and v1.5.6 installed? Just want to check that it's working as it should be
[Magisk] matt1313:
I'll have to do it later. If it helps gh made this Dolby when i let him use my pixel and has been working with 1.5.5. Has to be flashed in twrp after v4a is installed and working.

https://drive.google.com/file/d/1vNFZwOhrCUuk74_zByV3cKBavmO7SMT2/view?usp=drivesdk
[Magisk] Zackptg5:
Oh, you're using a dolby digital plus, I assumed you were using dolby atmos. Yeah, that should work with v4a
[Magisk] matt1313:
No atoms
[Magisk] manpildo:
Where did you get DD+?
[Magisk] Darkside1984:
I've installed last VFX version (Material & old driver) and it seems to work properly. Sadly I can't see the profiles. Load profile menu appears without any option. In older versions I had a lot of different profiles. Any solution?
[Magisk] GBPackerFanForLife:
I swear between Viper an Dolby its like a Marry Go Round with it working..
[Magisk] whalesplaho:
Internal memory/ViPER4Android/Profile/

Make sure v4a has been granted storage permission in phone settings_app_Viper4Android_permission!!!!
[Magisk] beeshyams:
Folks, can someone kindly help me with v1. 6.3(2.6.0.3) zip. Can't locate in download section. Would like to flash this (working fine now) in case the update has any problems and I can roll back

Thanks in advance
[Magisk] Lughnasadh:
Its in the "Old Builds" section of the download section.
[Magisk] beeshyams:
Thanks. That's where I checked before requesting. Couldn't find it or maybe I am turning blind :) out is it because I am searching using the XDA app?

Will search again later. If I can make (unreasonable) request, will you be kind enough to post ¿ No issues if you work not to :)
[Magisk] Lughnasadh:
Maybe try with your browser. It shows up at the bottom of the list for me using Chrome on my computer.

https://androidfilehost.com/?fid=746010030569968770
[Magisk] beeshyams:
Indeed, browser worked :)

Thanks for your help :)
[Magisk] kima09:
I have the exact same issue on Android 8.1 . This happen only when I play games. The issue persist on all sound outputs, phone's speaker, headphone, Bluetooth speaker/headphone.

The inbuilt eq (Snapdragon eq+) for GPM, but the problem is this eq doesn't work with YouTube.
[Magisk] VK'ed:
I uninstalled and installed the module 12 hrs back. No play protect errors yet. Fingers crossed [emoji28]
[Magisk] Dreamer(3MF):
Deleted
[Magisk] Darkside1984:
How can I be sure that these permissions are enabled? Otherwise, where can I download profiles?
[Magisk] xxxreyxxx:
on latest version, it seems viper can't collaborate with dolby on nougat
[Magisk] Badger50:
For permissions go to..settings/apps & notifications/all apps/V4AFx app/permissions.

Here's a bunch of profiles :cool:

https://drive.google.com/file/d/1isYWI05DAmZg4hAk-JmF9tWGtOVbZtH4/view?usp=drivesdk
[Magisk] deebray36:
everything working smooth in 1.6.4 for me
[Magisk] mxn2000:
Still not working on Huawei P10 VTR-L29 with EMUI8 on Oreo 8.0.

I am willing to help an developer with informations/loggs for solving this issue.

Just contact me.
[Magisk] whalesplaho:
https://xdaforums.com/android/apps-games/app-viper4android-fx-2-6-0-0-t3774651

Dats tha thread buddy.....
[Magisk] tbqstp:
I think it's a limitation of V4A. I have now upgraded to latest OOS which is 8.1 based and my LDAC headphones are set to connect at 96khz by default and V4A won't process.
[Magisk] moscic:
Unfortunately Viper does not work on my OP3T with LOS 15.1. Can anyone help? SELinux permissive does not change anything, still need to install driver.
[Magisk] Zackptg5:
Did you run through the troubleshooting guide?
[Magisk] moscic:
Yea. On OOS was working with permissive on LOS nothing helps.
[Magisk] Zackptg5:
It should work on enforcing. Can you post your v4a folder, magisk log, and a full logcat?
[Magisk] moscic:
I install los, gaaps, magisk, boeffla kernel, remove audio FX app, in magisk AML module, v4a module, I choose original 2.5.0.5. I have few others magisk modules installed.
[Magisk] Zackptg5:
If you're only using v4a (not other audio mods), the you can uninstall aml. But the log is saying that v4a driver "isn't usable". Can you post your /sbin/.core/img/ViPER4AndroidFX folder after uninstalling aml? (flash the aml zip again to uninstall it)
[Magisk] moscic:
Zip is too big for sending. Can I remove app and libs?
[Magisk] Zackptg5:
I should only be a few mb. Not the whole magisk img, just the v4a folder
[Magisk] moscic:
XDALabs have limitations.
[Magisk] ADDICTED777:
Hey everyone, i have never faced any problem with viper but after upgrading to oos 8.1.0 it just stops after few hours. So i had to Manually exit the app & launch it again..... Any suggestions????
[Magisk] Zackptg5:
If you're using new material, that's a bug with the app. Try one of the other v4as in the zip (just reflash it). You can also try audio compatibility patch

---------- Post added at 09:01 PM ---------- Previous post was at 08:57 PM ----------

Can you dirty flash your rom, uninstall and reinstall magisk, and then try flashing this again without arise? Other than that, everything looks fine so I'm not sure what the issue is
[Magisk] moscic:
It started working. I do not know how or why. ? Thx for your help.
[Magisk] joedajoester:
To reaffirm in case anyone is still wondering but on the pixel 2 the only thing working as of now is material app with old driver. Inside of the viper app it says the driver version is 2.5.0.4
[Magisk] Shriac:
New material version with old driver was processing audio but was showing no in the driver status. After trying again with different app didn't process at all. Turning on and off few effects started processing again. Is this normal?
[Magisk] D-m-x:
Thanks for letting us know. I'm still on 1.5.5 as this works just flawless. Besides I don't need another new Material designed app for now, if my settings are set i mostly likely won't open Viper again.

Gesendet von meinem Pixel 2 XL mit Tapatalk
[Magisk] peterlee928:
hi all, quick (noob) question. when i click on driver status in my app, it is not enabled... but "neon enabled" is a yes. so does that mean v4a is, indeed, working? much thanks in advance :)
[Magisk] Tylog:
Yes but you must start it in the settings Master power. You screen mean drivers are ok but viper not started.
[Magisk] MrBrady:
You have to pick the enable button for it to show enabled. There's an enable button for each audio output (Phone, Bluetooth, etc).
[Magisk] Zackptg5:
It means that its installed properly but that its not enabled (which it isn't). You want to read up on the main v4a thread abd learn how to use it
[Magisk] DrNinjaa:
Delete as already answered.
[Magisk] beejkitsune:
I've been looking in to this for some time and wondered if there has been any update to V4A running on Mate 9 Oreo.

Model: MHA-L29

Build: 8.0.0.321(C432log)

Magisk: 16.0

I installed V4A FX from the repo (v1.6.4 (2.6.0.3)) which installs fine, reboot, launch app and I am prompted to install the driver. I select OK and choose 2.5.0.4 (I have also tried 2.3.4.0 and experience the same issue) and the prompt disappears and nothing further.

When checking the Driver Status the version is 0.0.00, nothing is enable, status is "Abnormal" and audio format is "Unsupported".

I understand that some while ago I stumble across something (perhaps GitHub) that said that there was an issue with the Mate 9 and Oreo but since cannot find again to check for updates. Is there a possibility to download and install the driver manually?

I am quite anxious to get V4A working because I loved it on my 6P (R.I.P.) which I had replaced with the Mate 9 under warranty but I also use Android Auto which has issues with audio playback from Google Play Music and can be worked around with an equalizer. I have used other options in the interim but none are of the same quality and reliability as V4A.

Thanks in advance!
[Magisk] JBolho:
A quick read of the OP will show you that no sound mod works on EMUI 8. On any device.
[Magisk] beejkitsune:
Apologies, I must have somehow over looked that or just assumed it applied for the P10 alone; thank you.
[Magisk] JBolho:
We have to hope that someday, somehow, someone can make a 64bit driver of Viper... (Because that's all EMUI 8 uses, 64bit audio drivers)
[Magisk] Zackptg5:
Updated v4a to v1.6.5! Changelog: updated new material apk to v2.6.0.4. See the app thread for details (link in OP)
[Magisk] Redhawk2000:
I messed something up. I updated the material app manually prior to flashing this via xda labs and now I can't boot system since I have subsequently flashed the zip via magisk manager. If I uninstall viper completely through twrp (by flashing the zip) I can boot but if I then try to flash 1.6.4 or 1.6.5 via twrp I again can't boot to system until I uninstall viper again by flashing the zip in recovery. Any ideas?
[Magisk] Zackptg5:
That's a weird one. In the future, I recommend just replacing the viper apk in the magisk img when you update manually but the zip should remove any traces of v4a during the uninstall/upgrade including uninstalling any data apps.

Full list of what I'd try: wipe dalvik cache/cache, install and uninstall v4a as a regular data app, uninstall and reinstall magisk. Then flash v1.6.5
[Magisk] Redhawk2000:
Thanks. I just restored a backup from 3 days ago. Figured that would be the easiest. :p:eek:
[Magisk] flitzz:
What should I do to have other options in V4A Material like in the original one?
[Magisk] Kids in Love:
I install v4a for my Samsung galaxy core 2 before and I used it with no flaws, but when I download custom ROM and install v4a, it seems that it v4a is not actually working.. the sounds is still the same and I checked the driver and it says "process: NO".

Can anyone know how to fix the problem..