yashsingh1/xdaforums huggingface dataset:
[Magisk] RoboJoe:
Can you confirm that this method works with Bluetooth because it didn't on my P2XL. Everything looked like it should be working but it never actually processed on Bluetooth.

I don't *think* I screwed something up, but it's possible.

Oh, I'm on the 8.1 Beta 2 since they haven't pushed the Release version to us beta testers yet. If that matters.
[Magisk] Badger50:
Nah, beta 2 or final 8.1 is having some trouble processing on the P2XL. But I'm sure it'll get sorted out :good:
[Magisk] RoboJoe:
Good to know it's not just me, thanks.
[Magisk] Danilo-Sanchez:
[MENTION=5357345]ahrion[/MENTION] is this a known issue? Is there something I can do (other than stay on v2.1)?
[Magisk] bkkzak:
Sorry I just finished exams.

So I've tried all v4a v2.1-2.4 and none install work with magisk (meaning they all install the app, but always request drivers - and installing drivers always fails). I've tried system install with each of those, and no matter what (whether I put v4afx-v2.4-system-old.zip or v4afx-v2.4-system.zip) it won't install work (installs as a magisk module, won't install directly).

Am I doing something wrong?

Since it won't work on my magisk (pixel xl) I was trying for system install.
[Magisk] SilvrDrgn:
[MENTION=6037748]Zackptg5[/MENTION]

Pixel 2 (non-XL) updated to Oreo 8.1 via similar instructions to these three posts:

[UPDATED][2017.11.6][Magisk] Root Pixel 2 (XL) by topjohnwu - Page 134

[GUIDE] Unlock/Flash/Root for the Pixel 2 XL (taimen) Post #296

Unofficial Build Thread... (Magisk, TWRP, etc.) by thedude420

Though since my Pixel is non-XL, I used the Walleye files instead of Taimen. Used Magisk-v14.5420NOdtbo.zip from the third link for the Magisk install. Root works fine, no issues. Built-in MusixFX is disabled. Tried installing both the old and new V4A versions from the OP via TWRP 3.2. They have separate issues:

Old version: Generic com.audlabs.viperfx icon in the launcher. I get "com.audlabs.viperfx has stopped" popup when I boot my Pixel 2. Same popup when I try to start it manually.

New version: When I start V4A, it asks to install/update driver. Tapping on YES, it gives me message "Driver install failed: I/O error, please reboot and try again." Driver status is Abnormal. Neither setting to Compatible mode nor setting SELinux permissive resolves the issue.

Recovery and kernel logs, and post-fs-data.sh script from both version install attempts are in ZIP files on my Box account at the links below.

install_logs_for_old_V4A.zip

install_logs_for_new_V4A.zip
[Magisk] Deadeye*:
Not processing on S8 exynos :( runing Renovate ROM

Any tips?
[Magisk] davidisflash:
I asked this a few posts back too. It seems 2.4 broke something that was working fine for me in 2.3 and before. Haven't seen any updates or comments.
[Magisk] Zackptg5:
Hold out for a few days more, v2.5 has a ton of fixes, rewrites, and Oreo support (minus OnePlus devices)
[Magisk] Cowbell_Guy:
Awesome, can't wait. You guys are the best, thanks so much for all your help and hard work!

Does this mean that the magisk module will be updated to run with 8.1?
[Magisk] Zackptg5:
It runs fine on my bullhead running stock 8.1 but some other devices/ROMs are more problematic so we'll see
[Magisk] davidisflash:
Awesome, thanks!
[Magisk] Badger50:
Oh yeah! :good:
[Magisk] Golf c:
Works great on Pixel 2xl Dec. 8.1 Oreo selinux enforcing. Have to test Bluetooth tomorrow. Phone speakers processing good with Google play music.
[Magisk] SilvrDrgn:
Awesome! Great to hear! You guys are the best!
[Magisk] theduke7:
may i ask why not OnePlus devices? 2.3.4.0 (i'm using the Magisk Module) works fine on OP3 with latest oreo, either with the device set to permissive or using a permissive module for magisk ...
[Magisk] Zackptg5:
Ya, they work with permissive but they should work on enforcing so that's the issue
[Magisk] Ser0:
Will this fix audio lag in some games?
[Magisk] SSJMatt:
"Minus OnePlus devices"

Bummer
[Magisk] Zackptg5:
It'll work with them, it'll just require permissive selinux
[Magisk] Badger50:
Release the beast! :cool:
[Magisk] Zackptg5:
If audio is lagging, it'd be because your device can't handle all of the effects applied with v4a. Not much I can do about that unfortunately
[Magisk] Deadeye*:
OP, is there a known issue with Viper and S8+ Exynos not processing?

Driver Version 2.5.0.4

NEON Enabled: Yes

Enabled: Yes

Status: Normal

Audio Format: Supported

Processing: No

Sampling Rate: 48000
[Magisk] roboprint:
Start to play music and check again status:)
[Magisk] Ser0:
Huh that's odd. The audio lags when V4A is disabled as well but is gone when I uninstall V4A. I'm using an HTC 10 with PureFusion OS Android 8.0
[Magisk] Zackptg5:
It's finally here! New aml is out and v4a has been updated to it. This includes lots of fixes and some additions for v4a oreo compatibility. Thanks to [MENTION=3730810]Badger50[/MENTION] for testing

If you're on an oneplus oreo device, the installer will remove all sepolicy patches in the aml boot script and instead just set selinux to permissive. Not what I want but a workaround for now.

Any experienced uses with a oneplus device on oreo who would like to test it on enforcing, let me know :)
[Magisk] Badger50:
Saaweeeeeeeeeeet! Thank bro :good::good:
[Magisk] triggeredbot:
V2.5 working fine on oneplus 3T with Open Beta 19 ?
[Magisk] Steffen.e:
I'm on OnePlus5 but NOT on OxygenOS . I'm on OmniRom with Oreo 8.1 ...

Can it Work on 8.1 ? ?
[Magisk] Zackptg5:
It should. What it does is detect if device is a OnePlus device and if the rom is Oreo or newer and if so, uses permissive selinux. So you should see a message about that when you flash it (let me know cause it have no way of testing that myself)
[Magisk] Ariac Konrel:
Latest UDBR and V4A via AML is working great on my Pixel 2 XL (Android 8.1).

SELinux is on enforcing too.

Thank you, devs!
[Magisk] Steffen.e:
SElinux was already permissive before cause of testing the last 2 or 3 Days ( but with absolut No Luck ^^) :P

Flashed the latest 2 minutes ago , rebooted Phone, checked V4A ... And BOOM !! It WORK !!!

Very Nice Job ! Thank You ;)
[Magisk] husseinaltaaf:
Hello, hmm Latest v2.5 is not working for me. Please Help me! i tried installing Via Magisk Manager and Also Tried via TWRP! But both not working

I mean Both Modules Are Installed But The ViperFX App Is Not Installed.

Of Course I Tried NEW version Material, Then New Version Original, Then Old Verison

But For All No ViperFX App is Installed

Help Please

---------- Post added at 03:36 AM ---------- Previous post was at 03:32 AM ----------

If You Cannot help, then at least please provide Old Version Download Link. I was Using v2.2 and then its today i checked For Update and found out about v2.5
[Magisk] Badger50:
Using your root browser, navigate to: root/magisk/Viper4AndroidFX/system/vendor/app/Viper4AndroidFX/then you'll see the apk. Install it, reboot and done :good:

Or, just extract the apk from the zip and install it.
[Magisk] Zackptg5:
That's why. Completely remove all other audio mods before flashing this one
[Magisk] Badger50:
Install this with TWRP! :good::good:
[Magisk] husseinaltaaf:
Sorry but i tried that also
[Magisk] Badger50:
What device are you using?

---------- Post added at 05:30 AM ---------- Previous post was at 05:20 AM ----------

Suggestions...

1. Uninstall all sound modules from magisk.

2. Flash the zip in twrp. It's both an installer and uninstaller. Flash once for install, again for uninstall.

3. If there's no app, extract the apk from the zip and install it.

4. You might have to disable selinux the first time to activate the driver.

5. Toggle master power if not processing.
[Magisk] davidisflash:
Looks like 2.5 is up. Thank you so much OP! Just installed it in TWRP and will try it in my car first thing in the morning to see if the processing bug is fixed :)
[Magisk] jst98:
Google play protect notified me that the material design app is harmful to the device. What i should do?
[Magisk] anujyadava:
In the v 2.5 magisk module ,it asks to install v2.3.4 or v2.5.0.5 of v4a.just wanted to know which one is better in terms is sound output ?
[Magisk] sarp41:
Greetings,

V4A FX 2.5.0.5 [12/13/17] causes bootloops on my device. I'm using Magisk v14.5 (1456), E6603 7.1.1 stock.

I've tried both old and new versions, uninstalling and installing freshly but nothing worked strangely. I was using latest old version before this one flawlessly.

Any suggestions? [MENTION=5357345]ahrion[/MENTION]

Thanks..

Sarp
[Magisk] anhnambroz:
Processing: NO

Using RR 5.8.5 with v4afx-2.5. No process when playing video on youtube. What should i do? I'm using Magisk 14.5
[Magisk] Badger50:
Ignore the warning, or disable play protect.

Go with the 2.5.0.5 version. The older version will work, however, it does not have the ability to disable selinux within the app.
[Magisk] mimo_s16:
Thank you. I haven't tried v2.5 but v 2.4 works just fine with miui 9. Installed via magisk manager. Reboot and everything works. No conflict
[Magisk] Badger50:
I have no problem with YouTube processing. Try running both at the same time, then see what you get.
[Magisk] husseinaltaaf:
Its Not Cool, the older one was better! Because i just had to flash it thats all!

Anyway i will try what you said!

But can you please give me the older versions zip IF Yoh have??
[Magisk] radz_:
Can someone please provide the zip name if you choose "new" app. Special Instructions in the OP is not clear. Its say add new or old in the zip name, where exactly?
[Magisk] Badger50:
It's up to you if you don't want to use it, however, please don't impugn the time and effort these guys put into making this work! If the older version works for you, then use that one.
[Magisk] SilvrDrgn:
Happy to report that V4A 2.5 from OP in this thread is working, in SELinux enforcing mode (YAY!), on my Google Pixel 2 (non-XL). Info:

Stock Oreo 8.1 dirty flashed (removed -w in flash-all.bat) over the top of Oreo 8.0 with November update

Kernel patched via Magisk-v14.5420NOdtbo (found here Unofficial Build Thread... (Magisk, TWRP, etc.) by thedude420)

MagiskManager-v5.4.3-171125

I do have Universal Deep Buffer remover installed.

Procedure (V4A v2.4 was already installed, but not working on my device, same config listed above):

Uninstalled V4A and AML by flashing the V4A 2.4 ZIP via TWRP v3.2 for Walleye (Link) with V4A v2.4 already installed.

Rebooted back into Android to make sure my device still worked OK.

Rebooted back to bootloader and TWRP 3.2.

Flashed the V4A 2.5 ZIP via TWRP v3.2 for Walleye - selected NEW, material design version

Rebooted back into Android, started V4A 2.5 - driver status supported and normal.

Turned on master power and set my preferred FIREqualizer settings.

Started some playback and all is well!

Thanks very much, [MENTION=6037748]Zackptg5[/MENTION], [MENTION=5357345]ahrion[/MENTION] and anyone else involved!!!
[Magisk] sarp41:
https://xdaforums.com/showpost.php?p=74842855&postcount=1236

Greetings,

I've tried everything you said above like flashing it with TWRP, cleaning all the sound modules etc. before flashing latest one but nothing worked. I hope someone can figure it out and help. Also i have done my search no one has bootloops or dead kernelish errors (red led) like me.

Thanks.
[Magisk] SilvrDrgn:
Adding "new" (without the quotes) to the filename for the V4A v2.5 zip did not work for me during install via TWRP. I had to press the Vol+ button on the side of my phone twice. Once to select NEW (v2.5.0.5) version, and second time to select material design.
[Magisk] Badger50:
Hmmmm....sorry your having trouble with this. What device are you using? Do you have the busybox module by osmosis installed? I'm using a P2XL, and tested about 5 different versions of this before they released this one. It works on all apps I've tried, YouTube, play music, bluetooth (my vehicle) iheart radio..etc..etc. Hopefully you can get it working.
[Magisk] anhnambroz:
Still NO :(
[Magisk] sarp41:
I'm using Sony Xperia Z5 E6603 as i said and ofc I have that busybox module. I was using every V4A versions before this one so problem has to be with this build for me. I can't boot the phone with V4A flashed that's the problem not the "Processing=No" thing if someone else is interested.

Greetings,

V4A FX 2.5.0.5 [12/13/17] causes bootloops on my device. I'm using Magisk v14.5 (1456), E6603 7.1.1 stock.

I've tried both old and new versions, uninstalling and installing freshly but nothing worked strangely. I was using latest old version before this one flawlessly.

Any suggestions? [MENTION=5357345]ahrion[/MENTION]

Thanks..

Sarp
[Magisk] Zackptg5:
Try flashing universal deep buffer remover (just Google it it'll show up)

Can you post a logcat? You can do that via ADB with your phone plugged into your computer so we can see what's causing the boot hang

My first suggestion would be to uninstall and reinstall magisk
[Magisk] sarp41:
Okay sir I'll do it when I'm home, I had to left home.

Regards...
[Magisk] theduke7:
Please add to changelog here and on AML thread that AML detects OOS and automaticly set selinux to permissive

That said, on peemisive it works on oos oreo , it doesnt as enforcing,

That is if the system booted in enforcing, but , if the system booted to permissive and them manually set to enforcing from terminal v4a still works and of course the following reboot selinux resets to permissive
[Magisk] Badger50:
Hmmmm, interesting. I'm running 8.1 on P2XL with ex kernel, no permissive scrip installed, yet when I reboot, it works without having to disable selinux in the V4A app. Not trying to question you, just trying to understand is all :good:
[Magisk] Zackptg5:
It's part of aml and so it was already added to the AML changelog on its thread. If device is oneplus and rom is Oreo or newer, it'll change boot script to set selinux to permissive
[Magisk] theduke7:
Yes i saw it while it was flashing , i disabled it on the script though, i like to keep it endorcing and set permissive when needed,

I checked the changelog but didn't see it , 8 must've missed it,

Not complaining here, was just suggesting it becomes more obvious , most people unlike me wont check the magisk flashing script and probably wont know it happened
[Magisk] Shished:
Google Play Protect detects V4A as harmful app.
[Magisk] Zackptg5:
Material one does that because of the disable selinux option. It's a perfectly safe app (you shouldn't have to disable selinux anyways)
[Magisk] husseinaltaaf:
I never said that! I mean The NEW Version is NOT working!!!

---------- Post added at 05:30 PM ---------- Previous post was at 05:28 PM ----------

Is There anyone who still have the OLD v2.2 .zip. please send it to me. Please please please!!
[Magisk] davidisflash:
I too would like to know if the old version has better sound quality. I feel the convolver might be worse in the new but not sure.

Installed and tested AML 2.5. Bluetooth now processes, which seems to fix the bug on my pixel 2 that was introduced with 2.4. I can't process over USB-c to my car's android auto. It shows up as speaker profile and I've tried compatibility mode / forcing each fx profile.

Any ideas? I know the USB issue is known with viper but usually compatibility mode would work. It last worked in AML 2.3
[Magisk] Badger50:
http://vipersaudio.com/blog/?page_id=48
[Magisk] davidisflash:
Great news! I'm still on 8.0. I didn't uninstall v4a 2.4 zip. Just flashed 2.5 in TWRP. Bluetooth processing now works. Does USB processing work for you
[Magisk] Badger50:
Couldn't tell ya buddy. I haven't tried the older version. One way to find out though. About the only difference, according to Zack, was the older version isn't able to disable selinux from within the app.
[Magisk] davidisflash:
Thank you. Yeah, that option is not important to me. I never could really tell with the old one as it never would process over USB whereas the new could in compatible mode
[Magisk] japoola:
Getting I/O error when trying to install the driver on OnePlus3T Oxygen OS 5.0 Magisk 14.5
[Magisk] Zackptg5:
Ya, driver should already be installed so if you're getting a message like that, then something wrong is happening. Can you remove all other audio mods, flash v2.5 from OP, and post the recovery log? Then after booting and opening v4a, post full logcat? Thanks!
[Magisk] sarp41:
Greetings,

[MENTION=3730810]Badger50[/MENTION] [MENTION=5357345]ahrion[/MENTION] [MENTION=6037748]Zackptg5[/MENTION]

Previous replies by me:

https://xdaforums.com/showpost.php?p=74844385&postcount=1245

Here is the logcat in attachments.

Fresh installing V4A via Magisk.

Especially check the last lines, logcat has been started from downloading phase in Magisk.
[Magisk] Zackptg5:
Is this the full log? Plug phone into computer and type:

adb logcat -d > log.txt

after waiting a while

There's absolutely nothing in this log about viper4android or magisk so that's why I'm thinking it's not the full log
[Magisk] japoola:
Attached my logcat
[Magisk] Zackptg5:
I actually don't see anything unusual in the log. Have you tried wiping cache and dalvik cache?
[Magisk] husseinaltaaf:
Bro whats that?? Its the official ViperFx! I need the Magisk VieprFX v2.2
[Magisk] razrlover:
Working great, thanks again!!

Updated module on Pixel 2 with no other mods necessary, streaming spotify!

You da audio mod wiz!!
[Magisk] sarp41:
This log file is the full log friend. I'm telling you the things i did step by step:

1) Opened command line in x10flasher_lib,

2) Plugged in the phone with ADB enabled,

3) Wrote the code you told me,

4) Went in Magisk/Modules and started installing the V4A and selected new one & classic design,

5) After installing is finished I pressed "Reboot",

6) Phone started restarting after SONY logo on Powered by Android screen it got stuck 4 red leds and bootloop,

7) Then I let it bootloop for some time, CTRL+C on command line and I waited again couple minutes (phone is still looping) then plugged out and again waited couple minutes just in case. And here is the log file.

I'm uninstalling V4A via TWRP then it reboots normally.
[Magisk] Zackptg5:
Do you have any other magisk modules install?

Try flashing v4a, then mount magisk IMG with this: https://xdaforums.com/attachment.php?attachmentid=4311165&d=1508717947

Then navigate to /magisk/audmodlib and move the post-fs-data.sh script to somewhere else like your sdcard and see if you can boot then
[Magisk] sarp41:
Yes I've other modules like busbox, greenify, iyoutube, sysconfig, deep buffer remover. I'll see if i can handle this mounting thing when I'm home. Am I going to loose any data with this process?

Thanks..
[Magisk] Zackptg5:
Nope. Worst case scenario, you'll have to uninstall and reinstall magisk, so you'll only loose your magisk modules. Can you try v4a without any other modules? (busybox is fine)
[Magisk] sarp41:
It didn't work. :( I'll try mounting magisk trick if it will be the same then i will go with previous version of v4a. And one more thing I have never changed stock selinux setting. I mean is it has to be stock value (permissive/enforcing idk which one is stock selection by android.)
[Magisk] SilvrDrgn:
I have not tried USB processing. I am not sure I even have anything I could connect it to here in order to test it.
[Magisk] davidisflash:
Now it started working lol.
[Magisk] stargzrr11:
No luck on a Pixel XL running Android 8.1.

I can see this in ADB after rebooting.

12-14 21:25:54.963 2327 2327 I ViPER4Android: System booted.

12-14 21:25:54.964 2327 2327 E ViPER4Android_Utils: [Fatal] Can't load libV4AJniUtils.so

12-14 21:25:54.965 2327 2327 I ViPER4Android: Jni library status = false

12-14 21:25:54.981 2327 2327 I ViPER4Android: Driver not configured correctly.

12-14 21:26:02.589 2327 2327 I ViPER4Android: Jni library status = false

12-14 21:26:02.642 2327 2327 I ViPER4Android: Starting service, reason = ViPER4Android::onCreate

12-14 21:26:02.644 2327 4367 I ViPER4Android: Init environment

12-14 21:26:02.654 2327 4367 I ViPER4Android: Now checking for external storage writable, file = /storage/emulated/0/v4a_test_file

12-14 21:26:02.654 2327 4367 I ViPER4Android: FileNotFoundException, msg = /storage/emulated/0/v4a_test_file (Permission denied)

12-14 21:26:02.654 2327 4367 I ViPER4Android: Really terrible thing, external storage detection failed. V4A may malfunction

12-14 21:26:02.654 2327 4367 I ViPER4Android: Check driver

If I go to SELinux permissive mode it works, would just prefer not to do that.
[Magisk] Scottay5150:
I am having the same issue...
[Magisk] Zackptg5:
Can you both post full logcats? Sounds like you may have some new sepolicies that need allowed
[Magisk] madscribblerz:
Works great on my Pixel 2 Xl. 8.1.

Running magisk 14.4 with:

GSM doze

Busybox

Greenify

Permissive script

Just installed via magisk and came right up.

Rock on!
[Magisk] nexus_man12:
that's right. Probably the easiest viper install out there for systemless root. Running on Pixel 2 XL with latest Magisk /Elemental kernel and works flawlessly.

Thank you [MENTION=5357345]ahrion[/MENTION] for your tremendous effort, It's because of folks like you why Android > iOS :)
[Magisk] mbrian27:
Updated to V2.5 a couple days ago from 2.4 on my OP3T, works perfectly, but this morning I got a play store notification about V4A being a harmful app. Yes, I have play protect on but even when I toggled it off it still gave me a harmful app notification (not sure why). Anyway, what I'm getting at is that I had V2.4 installed since it was released and never got this notification, I guess it could be coincidental and just be Google's doing. Who knows.
[Magisk] Zackptg5:
It does that for the material v4a because it had the disable selinux option in it. Not sure why the original 2.5.0.5 doesn't do the same though. Pittvandewitt is working on finding it why. But the app is of course safe :)
[Magisk] chikimonke:
I could have misunderstood the release notes, but it was my understanding that it was only OnePlus devices that needed the permissive setting. I'm on a 2XL and I just got the warning as well about V4A, and I just checked and my 2XL running the material V4A 2.5.0.5 and selinux is enforcing. If there's a log or something I can pull, let me know.
[Magisk] Zackptg5:
Right. The app warning is unrelated to needing permissive selinux. There is a setting in the app allowing you to completely disable selinux which is likely causing Google to flag it. Long story short, don't worry about it :)
[Magisk] HACK3DANDR0ID:
What process did you use? I have the Pixel XL on Android 8....
[Magisk] TWisTeD48:
I have this working on my Pixel XL running 8.1:

-Installed ElementalX v3.0

-Installed Magisk v14.5

-Installed BusyBox Module

-Installed V4A

-Installed The SELinux Switch

-Set SELinux to permissive

-Restart
[Magisk] HACK3DANDR0ID:
Worked without issue, thanks a lot!
[Magisk] Scottay5150:
Duplicate
[Magisk] Scottay5150:
Duplicate

---------- Post added at 08:43 PM ---------- Previous post was at 08:41 PM ----------

Keeps AP on Pixel XL?
[Magisk] stargzrr11:
Full log attached. Let me know if you need anything else or someone to test.
[Magisk] ronyscomparim:
I am having error when installing via twrp and magisk, says that it was possible to unzip zip file
[Magisk] Zackptg5:
Try adding these lines next to the others like it in /magisk/audmodlib/post-fs-data.sh

set_sepolicy hal_audio_default audio_data_file dir search
set_sepolicy hal_audio_default hal_audio_default_tmpfs file execute

If it still doesn't work, then it's likely more audit policies need allowed so just send another logcat over :)
[Magisk] stargzrr11:
Thanks!

I think that fixed it. Driver status is showing as "Normal" now. I have some more testing to do to make sure everything is working good, but definitely looking promising!
[Magisk] fahric74:
Installed Magisk v14.0

-Installed BusyBox

-Installed V4A

-Set SELinux to permissive in custom kernel

In V4A Processing :no

Samsung A5 2017 :nougat

Please help!
[Magisk] SilvrDrgn:
Does it say status Normal? If yes, then you need to actually start playing some music or other audio. Then it will show Processing: Yes.
[Magisk] fahric74:
YES, status is normal, i play music but still processing:no
[Magisk] Badger50:
Is selinux set to permissive inside the V4A app under enable developer mode?
[Magisk] fahric74:
how to check it?
[Magisk] Badger50:
V4A..settings....should then look the pic :good: