yashsingh1/xdaforums huggingface dataset:
[Magisk] soulremover:
i cannt make it to work with iytbp youtube vanced.. was working perfectly on the previous versions. it's working with all other music apps, Netflix etc. Don't know why is not working with youtube. Anyone ? Any thoughts ?
[Magisk] Watanabe_You:
I tried flashing v2.3 and it says

/data/magisk isn't setup properly
please install magisk

Isn't it supposed to install in /system if Magisk is not flashed?
[Magisk] Zackptg5:
Correct. That means it detected a magisk install. Do you have /data/magisk?
[Magisk] mamama07:
Just tell me how can I do this and give me few minutes.
[Magisk] Zackptg5:
Well first, completely uninstall old v4a/audmodlib (make sure the folders are not present in /magisk - you can just delete them if you want along with all other aml mod folders) since there's issues. Then flash v4a 2.3. The magisk img is: /data/magisk.img
[Magisk] mamama07:
So:

http://www78.zippyshare.com/v/NA6ve4Hb/file.html
[Magisk] Zackptg5:
v2.4 released! Fixed error with magisk 14.0 installs
[Magisk] SSJMatt:
I installed the zip but Viper4Android doesn't seem to be installed. Help?
[Magisk] M4TT3X:
Same... I'm with OOS 5.0 (oreo) OP3 Magisk 14.5... Tried flashing with TWRP blue sparks and magisk ---> result : Magisk manager shows the modules installed but i can't see the app in the drawer. :confused: :confused:
[Magisk] Frenzi2012:
Works great v2.3 Nitrogen Os oreo for redmi note 3. Note: i flash from magisk manager , v14.3.

I need to go developer option in v4a and disabled selinux, grant root access and restart app

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

Try flashing with magisk manager
[Magisk] yung40oz84:
Yes, the old viper!!!! Thanks so much for ur work! Love the compatibility with Ainur audio mod, which is beast in itself.
[Magisk] mamama07:
Nice to hear you fix problem with magisk 14.0 ?

But 14.5 plus mod 2.4 give same results as previously. No app into drawer.
[Magisk] Zackptg5:
Selinux is set at boot via a bootscript. You shouldn't have to mess with selinux and if you have to do anything, set it to permissive, don't just disable the whole thing (really not sure why that's even a part of the app)

---------- Post added at 18:24 ---------- Previous post was at 18:22 ----------

Ah, I see you have arise installed. Arise adds a whole bunch of stuff such as custom audio effect files so there's no telling what kind of behavior may occur. See if it works without arise and let me know
[Magisk] mamama07:
I try arise like workaround for problem with 2.3. now just let me flash stock ROM and I'll write results asap.

____________

So: reflash stock rom, magisk 14.5, mod 2.4 and still nothing.

Logs and .img file included.

http://www114.zippyshare.com/v/g7PdcUKc/file.html
[Magisk] Frenzi2012:
Its not arise, its only viper4android taked from this post, and selinux is not disabled, its a trick to force magisksu give permission to viper4android (popup). In next reboot is permissive again
[Magisk] Watanabe_You:
Yeah, just found it. Not sure why the uninstaller doesn't work, everything is fine and dandy now.
[Magisk] rahulrajmishra36:
Is it compatible with android 8.0 roms?
[Magisk] M4TT3X:
I tried but doesn't work for me... maybe it's Magisk Manager 14.5 ...
[Magisk] anware:
The app icon not showing up in the drawer stilll persists. I'm on OP3T running Open Beta 18 (Oreo) with Magisk 14.5 (beta) and the updated V4A 2.4. Confirmed Busybox and Init.d support exists. Flashed through Magisk Manager. Magisk installation seems normal. The V4A modules show as installed but no app icon in the drawer.

It'll really mean a lot of you could take a look at the attached log file and advise if there's something amiss. I'll provide anything else you'd need to check.

Appreciate the awesome work you put into this.
[Magisk] Zackptg5:
Does the v4a app exist in /magisk/viper4androidfx/system/priv-app/viper4androidfx?
[Magisk] anware:
Yes, it exists in this folder.
[Magisk] Zackptg5:
Hmm, can you attach you magisk log?
[Magisk] redpoint73:
Oneplus 3/3T on Oreo (OOS 5.0) in particular seems to be causing problems for a lot of folks. Me included: no V4A app in app tray after installing the module.

I tried doing as suggested by Zackptg5, delete all AML files and Viper files (I had none, just AML files) from magisk folder. Then installed v2.5 in TWRP. Still no V4A in app tray.

TWRP recovery log is attached.

Note that I am on Magisk 14.3. I know beta 14.5 is out, and many are on that. But it seems to have a lot of bugs. I don't know if there are actually any more or less issues than with 14.3. But 14.3 is working fine for me, so I decided to stick with it for now.

Going back to v2.0 works fine. V4A app appears, and works/processes correctly.
[Magisk] Didgeridoohan:
I took the plunge today and updated my OnePlus 3T to Oreo, to see what's up with this issue. Love this module!

It seems like it's preventing Magisk from mounting any Magisk modules at all. That's why no app appears...

Other modules mounting things to system work fine. Among others, I tested busybox and your Unified Hosts.

I've saved some logs (Magisk log and debug log and module installation log), with and without the V4A FX module. Hope they show something...

Let me know if you need more details or to test anything.

Edit: Oops... Just realised I tested this on a test build of Magisk, but it should not be much different from official beta v14.5.
[Magisk] Frenzi2012:
it works very well in AOSP oreo [MENTION=5357345]ahrion[/MENTION] , the only problem I have is whenever I need to play music, I need to enter the viper, press the three points to exit, re-enter and then it works.
[Magisk] Zackptg5:
That's been a viper issue for a while now. Have you tried universal deep buffer remover?

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

Thanks! I'll take a look at it
[Magisk] Frenzi2012:
i havent tried, what suppouse do that?
[Magisk] Zackptg5:
https://xdaforums.com/apps/magisk/module-universal-deepbuffer-remover-t3577067

It can sometimes help with the issue your having (as well as others like v4a not processing for streaming apps)
[Magisk] Hellsblade:
My config is Galaxy S6 with the famous Global Elite ROM, Android 7.0 and Magisk 14.5 .
[Magisk] anware:
[MENTION=660462]redpoint73[/MENTION] already beat to it, but attached are my logs.
[Magisk] anware:
Would you be able to share the v2.0 zip file. I can't seem to find that version anywhere.
[Magisk] Didgeridoohan:
I think you quoted the wrong post... :p

[MENTION=660462]redpoint73[/MENTION] was the one talking about v2.0.
[Magisk] anware:
Oops! You're right. Thanks for pointing that out!

[MENTION=660462]redpoint73[/MENTION], could you be able to share the v2.0 file you refer to? I can't seem to find it anywhere.
[Magisk] Darkside1984:
Is this mod compatible with any Dolby module? I'm on Oreo.

Enviado desde mi ONE E1003 mediante Tapatalk
[Magisk] channeledbymodem:
OMG, so true. I just got a 3T, and I'm sticking with Nougat for xposed compatibility. I have struggled with Viper4Android for *years* and it never gets easier. For a while I could flash lolliviper.zip and then with Viper 2.5 I managed with various selinux hacks.

But the Oxygen install was the hardest yet. The official Nougat apk would not install drivers. The ViPER4Android_2.5.0.5_guitardedhero.zip completed the driver install but I couldn't enable it. But at least with both of these the Viper icon was visible in the app drawer.

As a last resort I tried both FreedomOs and Arise, although I am constitutionally opposed to aroma installers (too many options that might be buggy). But my experience has been that using Aroma to install Viper makes the required changes on the system level I don't understand or want to do myself. And I come to find THERE IS NO VIPER ICON IN THE APP DRAWER. WTF.

Finally, in desperation I reinstalled stock Oxygen nougat and re-rooted with Magisk in hopes this version of Viper would work. Never considered Magisk before because I don't care about Safetynet, Android Pay, etc. I rooted with Magisk *soley* to get Viper to work.

Which it now does. Why you experienced the same issues with the Magisk install that I had with Arise, g*d only knows.

What a PITA.

(If I had seen a donation button I would buy the developer a beer but I don't see one.)
[Magisk] Danilo-Sanchez:
I don't know if it is hapenning just with me, but as soon as I flashed this it broke my offline charging.
[Magisk] coolfire92:
Oneplus 3t

Tried installing on my op3t on oreo. Installation is successful and the app appears in app drawer. However the driver isn't installed. When trying to install the drivers an io error msg pops up. Attaching log
[Magisk] Wilguens Joachin:
What you said
[Magisk] appman1234:
I just want to report the v2.4 module installed and executed successfully in Redmi Note 4X (mido) MIUI 9.1 v7.11.30 with Magisk 14.5.

Can chose old and new v4a during installation via Magisk.
[Magisk] Frenzi2012:
I installed latest 3 modules , include deep buffer, but still i need to exit and enter again
[Magisk] mamama07:
Ok, I personally think problem exist in a magisk or oreo, not in module. I downgrade to 7.0 android with magisk v14.0 and working PERFECT. So just w8 for next magisk or next oreo update.
[Magisk] channeledbymodem:
I was also able to install on a 3T running 7.1.1 with 14.0. However using any version of Arise with supersu failed (no icon in drawer) so I don't agree that this is caused by magisk or oreo. It's a viper problem. Viper has always been a pain to install correctly.
[Magisk] Skittles9823:
The arise problem was most likely due to the lack of system space as it isn't systemless, where as these modules install into the /data partition which counts as internal storage.
[Magisk] channeledbymodem:
I think that was very likely true. While I was struggling to set the 3T up with Oxygen 7.1.1 intially I sometimes got a no space error (e.g., Adaway could not save a modified host file). I have never encountered this on any device except the LG G Pad X. I wonder why they make the os so large or the system partition so small. It isn't practical.
[Magisk] SilvrDrgn:
[MENTION=6037748]Zackptg5[/MENTION],

Device = Google Pixel 2 (non-XL) with November update. Patched stock boot.img via Magisk Manager.

Magisk v14.5.2, Magisk Manager v5.4.3.

Flashed V4A v2.4 from OP, over the top of v2.2, via TWRP 3.2.0 for Walleye. FX Compatible Mode = Normal. Driver status Abnormal. It only appears to be operable when setting SELinux to permissive. Will put links to TWRP recovery.log and post-fs-data.sh script at bottom of this post.

These links are to my Box.com account. If they don't display, just click the "Download" link in the middle of the page for each one.

recovery.log

post-fs-data.sh
[Magisk] channeledbymodem:
Viper has only worked with selinux permissive for some time now. There is a zip file somewhere on xda that changes selinux to permissive permanently. Otherwise you need an app.
[Magisk] Zackptg5:
The upgrade process only works if coming from v2.3 or newer. You need to completely uninstall all AML modules before flashing v2.4

---------- Post added at 03:55 PM ---------- Previous post was at 03:54 PM ----------

This isn't true. The AML boot script has sepolicy patches allowing v4a to work in enforcing mode. For some reason though, some roms don't seem to like it (oos Oreo)
[Magisk] SilvrDrgn:
What's the recommended procedure for complete uninstall and reinstall?
[Magisk] Zackptg5:
To completely uninstall, just flash every AML mod zip you have installed. They'll detect the mod and uninstall instead of install. Then after that, flash the zips once more to install
[Magisk] SilvrDrgn:
So, I basically have to flash v2.4 to uninstall that, and v2.2 to uninstall that. Then v2.4 again to reinstall. Hopefully, I've got that right. I'll give it a go.
[Magisk] xflowy:
pixel 2 xl, oreo 8.0 nov and viper not working. anyone any ideas?
[Magisk] Badger50:
Is selinux set to enforcing or permissive? Which version are you using, and how did you install it??
[Magisk] xflowy:
does it need to be on permissive? didnt read about that in the instructions.

i used the magisk installer from here. latest one ?
[Magisk] Badger50:
Yes it needs to be permissive. You can set it by enabling it in the V4A app under settings.

Also enable developer mode.
[Magisk] SilvrDrgn:
Took me a couple of tries, but I think I got a complete uninstall/reinstall done. It presented me with a changelog popup when I opened V4A v2.4 on my last attempt, and my previous settings were reset to defaults. It still does not work in enforcing mode for me, but that's probably because I am using the stock Oreo 8.0 ROM boot.img (patched via Magisk Manager), per the "(oos Oreo)" text in your message?
[Magisk] danmaman:
I'm on nitrogen os 3T

Kernel is permissive stock

I've just flashed the attached file via magisk manager

And it works

I've tried also v2.4 here, but no app in appdrawer
[Magisk] Rebel_00XCV:
It doesn't work on OOS 5.0
[Magisk] Zackptg5:
This is a known issue. There's something wonky with the ROM and we're currently looking into it
[Magisk] danmaman:
As I wrote mate... I'm on a permissive kernel

Your kennel is enforcing I guess
[Magisk] Zackptg5:
Open the post-fs-data script in /magisk/audmodlib and delete the set_sepolicy lines. Since you're on permissive kernel, you don't need them and something about that ROM doesn't seem to like it for some reason
[Magisk] danmaman:
I don't have this audmodlib folder in magisk
[Magisk] Zackptg5:
I see, you're using a different v4a mod, nevermind then :)
[Magisk] danmaman:
Yeah no problem mate...

The one who I've attached.. Works for me
[Magisk] mamama07:
Look at post from thread owner. He said as well is a ROM problem, not magisk and not module. ;)
[Magisk] Danilo-Sanchez:
Just an update to this issue: I uninstalled the version 2.4 and offline charging worked again. Then I tried to install older versions. The only version that doesn't break offline charging for me is 2.1 (I'm using Lineage 14.1 and Magisk 14.0 on Moto G 2014)
[Magisk] Zackptg5:
Okay, so I've been doing some testing with [MENTION=4667597]Didgeridoohan[/MENTION] and for reasons still unknown, OOS 5 doesn't like sepolicy setting. Magisk users noticed that V4A didn't show up in their app drawer. Reason for this is that Magisk would hang on the audmodlib boot script at the sepolicy setting part and magisk would kill the script after a certain amount of time. Supersu users noticed that boot hung up altogether because supersu doesn't have this script killing functionality.

Long story short, we tried different ways of setting the sepolicy patches including patching the boot img itself and nothing worked. Only solution at this point is to set selinux to permissive.

So this zip will patch the aml bootscript by replacing all of the sepolicy setting lines with "setenforce 0" and therefore set selinux to permissive at boot.

So just flash latest aml v4a from the OP, then this zip, and you should be good to go (I'll put this on the OP too for time being). Note that this hotfix MUST BE FLASHED IN TWRP. It won't work in magisk manager, don't waste your time trying. Hopefully we'll get this thing figured out.

PSA: oreo breaks a log of audio mods (but oos has been the first to break v4a as far as I've seen)
[Magisk] shaqib.khan:
Why is the app using so much data??
[Magisk] Rebel_00XCV:
With your fix v4a appears to the app drawer but still v4a ask every time to install drivers... I'm on OOS 5.0 and magisk 14.5.

Any solution for this?
[Magisk] Zackptg5:
Ugh. That v4a zip that was working for some oos users is basically the same as this one wih the hotfix so I don't know what's up then. There's something about this rom that's breaking stuff. Since it's still a beta, I'd make a bug report about it to oneplus

So although the permissive thing seemed to work for a few people, it doesn't seem to be a true solution as it's still not working for many users. Until we figure out exactly the problem, make logcats and report the issue to oneplus as oos 5 is beta and this issue is likely something with the rom itself since it works on other oreo roms

Update: oneplus just released an official version of oos 5. Completely remove v4a and all other aml mods and then try it again if you want to see if it works now
[Magisk] mamama07:
But I always try it at official rom oos5, not in beta one, so I can confirm is still don't work. BUT - OP give us next beta of oreo, which is younger than official oos5, so maybe I'll try do it on that rom.
[Magisk] jay-em-ass:
On the latest beta of Oreo the driver cannot be installed. It always says "I/O error."
[Magisk] M4TT3X:
I tried flashing the zip file after v4a but now I have 3 problems... 1: I see the v4a app but it says "app doesn't respond" 2: my home button and background app killer button doesn't work (they make the vibration but I can't see how to configure back again those buttons even on settings) 3: settings app is kinda messed up now, the smartphone doesn't recognise me as developer and when I try to click on "choose account" on settings the app crash. How can I uninstall the zip file? Thanks
[Magisk] beren:
i installed the module from the OP...

but when try to install driver from v4andoroid fx it says installed and reboot...but actually it did not install.

magisk is the newer released.
[Magisk] IagoJevaux:
I had this issue once. When property installed, it does not ask to install driver as the drivers are installed when flashing. Try to redownload and reinstall.
[Magisk] HampTheToker:
I installed your AudModLib and Viper and still get BusyBox error.
[Magisk] davall:
Had the same on Magisk 11.6. Installed Magisk 12 and voila everything was fine and operating :)
[Magisk] ahrion:
Did you have another v4a installed when you installed this?
[Magisk] justjr:
It gives me bootloops
[Magisk] Didgeridoohan:
Are you expecting help or is that just a general statement? There are no mind readers here...

Details, details, details... And logs!
[Magisk] Terkitoez:
Spotify not processing

I flashed your module with Magisk v12.0 and V4A processes for everything but Spotify. Any ideas? Processing works fine when I run V4A on any other ROM without Magisk. Any ideas?
[Magisk] Zackptg5:
Have you're tried deep buffer removal? It's another module
[Magisk] NATO66613:
Sorry for noob post

I am having issue no viper4android app shows after installing module
[Magisk] kopitalk:
del
[Magisk] Didgeridoohan:
You could also try changing compatibility mode to compatible. That's worked for me with Spotify on some devices/ROMs.

The module might not have loaded properly on boot. Try rebooting.
[Magisk] IagoJevaux:
You are probably isntallig the module straight from the modules list, which you shouldn't.

DOWNLOAD the module from this thread and install it using a custom recovery alongside​ with the audiomodlib v1.3 (this one you can use the Magisk repo).
[Magisk] kopitalk:
What I did was to download v4afx_v1.3.zip and install it in magisk, and I get both VIPER4Android and AudModLib modules loaded.
[Magisk] marbertshere:
Hi! I remember in the past that flashing viper would uninstall MusicFX. However, MusicFX​ is still present after flashing this mod. Should I touch it or leave it as is?
[Magisk] NATO66613:
Tnx sorry my mistake
[Magisk] ahrion:
Installmy module. The one on the magisk manager is NOT my module. Install the one on this thread.

Holy.
[Magisk] ahrion:
You're becoming a godsend in my threads lol. Appreciate.

Yeah I'm not gonna remove people's outside apps like that. MusicFX doesn't effect anything anyways.
[Magisk] ahrion:
So audmodlib v1.4 will have a few changes.

- I will further integrate AB device support (aka Pixel).

- I decided not to move my permissive script from post-fs-data.d to service.d like as suggested on Magisk V12 via [MENTION=4470081]topjohnwu[/MENTION] because those SELinux edits I made for SELinux Enforcing mode don't all work on service.d because somehow parts of certain apps load BEFORE late_start service.

- SELinux live patching has been edited to allow somewhat better compatibility between kernels, ROMs, and devices.

- I will make my scripts even more efficient and remove su.d (system install) folder and use audmodlib.sh as well as dax.sh and so on to be a unified shell script. This is just to eliminate the amount of files I need to edit and increase efficiency and precision, which would decrease times before updates.

- I haven't even touched addon.d; if you looked at the scripts between various mods, which will be revamped for system install only.

- The various mixer_paths paths will be added as part of AudModLib but I am not sure if I want to keep them for this version or next version.

I have not pushed any changes to GitHub as of yet.
[Magisk] androidvivek:
Thank you so much...

After trying every other systemless method(failed) for viper4android this awesome mod of your works perfectly...

Thank you so much... ☺️
[Magisk] Zackptg5:
Something goofy happened with magisk. Try uninstalling and reinstalling magisk
[Magisk] M4TT3X:
I just download magisk 14.5 and re-flash it or I have to run kinda of an "uninstaller" ?

Re-Flashed Magisk 14.5 , it didn't worked. What do I do now? Thanks.
[Magisk] Zackptg5:
There's an uninstaller you need to flash first. You may want to dirty flash at this point
[Magisk] M4TT3X:
Ok, meanwhile i was doing this i noticed that the V4A app now is on the drawer and works( the bugs of settings/buttons persists) but has another name like "com.audiomodlib...."

but I ran the Uninstaller of magisk and now I can't enter anymore in TWRP But just in OP3 stock recovery mode... Oh jesus ... It's getting worse

Edit: Solved the problem of TWRP and everything..... Btw, it's strange that i see com.audiomodlib instead v4a on the name of the app in the drawer? thanks!
[Magisk] davidisflash:
I'm seeing an issue with 2.4 that I haven't seen with previous versions. I'm on Google Pixel 2 directly from Google, unlocked and rooted. I tried this also by performing a factory data reset and still see it. I can install the 2.4 zip in TWRP just fine after having installed Magisk. Magisk will then show AML as a module along with Viper. Viper shows up as an app, great. I didn't have to flash the fix on the previous page.

My issue is that with this version, I can't get viper to process at all, whereas I can with previous versions. This is either having it install viper 2.5.0.5 or the old one. Viper just says driver isn't enable and isn't processing.

Any idea? Rebooting doesn't fix this either.
[Magisk] SilvrDrgn:
Official Google Pixel 2 (non-XL) Oreo 8.1 update

I have Magisk v14.5.2, Magisk manager v5.4.3, and V4A from OP working on my Google Pixel 2 (non-XL) Oreo 8.0 with November security update, stock boot.img patched by Magisk Manager. Just now I am getting the notification on screen that Google official Oreo 8.1 update is available for download and install on my device. Reluctant to do that since I have V4A working now. What are people's experiences with getting V4A working Oreo 8.1? Good? Bad? Ugly? Recommendations?
[Magisk] dethknite:
It is the only thing I have not been able to get working. Processing so far is a no go... but I am sure someone will figure it out soon (or already has as I am typing this).
[Magisk] Badger50:
Don't know if this will work on the P2, but it does on the P2XL.

https://xdaforums.com/pixel-2-xl/help/viper4android-8-1-0-t3711474
[Magisk] TWisTeD48:
Thank you! This is working for me.

Pixel XL 8.1, Magisk v14.5, ElementalX v3.00
[Magisk] SilvrDrgn:
Well, I decided to try the Oreo 8.1 update, but that fails to install. I can only assume it's because of bootloader being unlocked, permissive mode or something else with the Magisk/V4A install interfering somehow. No idea what it would be specifically. So, when I have time, I'll probably just download it from Google site and flash it on. Will test Magisk and V4A again after that. Dunno when I'll get to it, probably not until the weekend.
[Magisk] Badger50:
Did you unlock_critical??
[Magisk] SilvrDrgn:
The Oreo 8.1 update I was trying to apply was an OTA update that my Pixel 2 automatically notified me about.

My device is Pixel 2 non-XL. My understanding is that unlock_critical is not needed for the non-XL version of the device. I just did standard unlock. Is that not correct?