yashsingh1/xdaforums huggingface dataset:
[Magisk] Zackptg5:
[MENTION=6912702]mshinni80[/MENTION] everything looks fine in your v4a folder and since it works for a while, that means that something is killing off the process. Couldn't tell you what that would be though. You could try force closing v4a and reopening it rather than restarting your phone

[MENTION=6530865]Lughnasadh[/MENTION], for issues with the new material apk, gather a full logcat and magisk log and post it on the thread for it so the devs can see what's up with it

Okay pixel 2 users [MENTION=2544666]whitewallman[/MENTION], [MENTION=2885225]cmo220[/MENTION], [MENTION=7424654]Blooddrunked[/MENTION], [MENTION=6089972]peterlee928[/MENTION], got a test build. The 1.5.7 vs 1.6.2 comparison by cmo220 showed one problem: no libstdc++ lib. Found a nice typo in the installer with that so here's a test build that fixes that. Can you try it out, and post the v4a folder again along with a full logcat if it doesn't work (or let me know if it does - fingers crossed)? Thanks guys

Edit: removed test build
[Magisk] sjamie:
Your persistence amazes me, my friend. Nice! ?
[Magisk] cmo220:
This one works on Pixel 2 XL! Good job. I was going to feel bad when I said I didn't have time to get logs right now.
[Magisk] Zackptg5:
Finally!! :D

Dont need logs since it works. Thanks for the report!
[Magisk] Zackptg5:
Okay, released v1.6.3! Pixel 2 users, let me know if it works for you. In the beta build, I forgot that I added an extra sepolicy from a long time ago but I'm pretty sure it isn't needed so got rid of it in the official build
[Magisk] chikimonke:
So far so good here. I know you mentioned that there was a typo in AML earlier too, will there need to be another update to AML now, or did this latest typo not affect AML?
[Magisk] Zackptg5:
Nope, this is v4a only. I fixed the typo in the last release onslought yesterday :)
[Magisk] Zackptg5:
Can you try removing all audio related magisk modules and then reinstalling them?
[Magisk] whitewallman:
I didn't get a chance to grab the file. It's since been removed.
[Magisk] DarkSilentSC:
Try uninstalling AML and re-installing AML and have the module patch V4A again.
[Magisk] peterlee928:
i think its good! see attached files.
[Magisk] whitewallman:
1.6.3 does not work here.

Same thing. Status shows version 0000, abnormal, etc..
[Magisk] Zackptg5:
Can you uninstall and reinstall magisk, then flash v1.6.3? I want to make sure nothing got messed up/is interfering with it
[Magisk] DarkSilentSC:
Remove AML, V4A, ACP, and Reboot.

Install V4A, then AML., and Reboot.

Done!
[Magisk] whitewallman:
Update: Good news!

When I first installed, it upgraded from 1.5.5, and didn't work. Same Pixel 2 XL issues.. uninstalled module via magisk, rebooted, and said what the heck and installed 1.6.3 clean from magisk manager. Works great so far! Even survives reboot! Nice work! Thank you!

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

Since v4a is working now, did you still want me to uninstall/reinstall magisk? It looks like something just went haywire when it upgraded from 1.5.5. I did notice the install log said "upgrading".. Clean install worked fine.
[Magisk] xflowy:
pixel 2 xl, stock, magisk and latest build: every time i skip within a track on Spotify the sound engine goes of and then on again.

also it shows "processing no" while its clearly working (other players too).
[Magisk] peterlee928:
i know i gave the thumbs up, but wanted to say thanks again. really awesome work. ???
[Magisk] Zackptg5:
Try installing audio compatibility patch
[Magisk] whitewallman:
Agreed! Thanks for the hard work devs! Thanks for pushing through to a resolution!:good::good:
[Magisk] D-m-x:
Yeah thanks, the last Days can't have been easy with those Problems.
[Magisk] MrBrady:
Completely uninstalled 1.5.5, rebooted, then installed 1.6.3. Works great on Pixel 2 XL
[Magisk] xflowy:
how is Spotify for you? did you need to apply the audio compatibility patch?
[Magisk] MrBrady:
I don't use Spotify. Only Google Play Music and Amazon Music. They're both streaming, I'm guessing it would have similar issues with Spotify if there are any. Do not need the Audio Compatibility Patch for either GPM or AM to work.
[Magisk] xflowy:
thanks, but

1. didnt have to install it on previous version to get Spotify to work without hiccups

2. just installed the thing and it still happens
[Magisk] Zackptg5:
Are you using the new material? If so, post the issue on the thread for it (link in the OP). In the OP of the material v4a thread, they have a list of what logs and stuff they'd need.

If you're not, then I'm not sure what the problem is other than some other audio app messing with it
[Magisk] sjamie:
New material + Old driver = Eargasm?
[Magisk] psychoela:
problem solved. using new material v4a.yeah!:D
[Magisk] sjamie:
Congrats! You like the bassless sound of the new driver?
[Magisk] MrBrady:
Any suggested profiles for Jaybird BT earbuds? I'm on the new material app with old driver.

All my previous profiles seem to have bass clipping with the new app.
[Magisk] psychoela:
of course not,I bass lover. for me this enough. this my profile maybe can give u same ideas, cause different earphones will give different result,I think:D

edit:sorry, also need dolby Atmos for more bass:silly:
[Magisk] sjamie:
Are you using Dolby Atmos from guitardedhero?
[Magisk] psychoela:
yes version unity 2.20.18
[Magisk] VK'ed:
The only reason i installed d new version is bcoz i needed my banking apps to run
[Magisk] Zackptg5:
The new material uses the same drivers as the regular v4a. The drivers are closed source so there's no way to modify them. That being said, the new material is capable of using either the 2.5.0.4 driver or the 2.3.4.0 driver and during the install, you can choose which you want :)

Both drivers are SQ (super quality) btw. 2.4 driver sucked so no one cares about it
[Magisk] sjamie:
When using the older 1.5.5 version and all previous versions, I couldn't hear that much of a difference between the 2.5.0.5 driver and the 2.3.4.0 driver. Using the new material version, the difference is night and day. No matter what I do, I can't seem to add enough bass with 2.5.0.5 whereas I can with 2.3.4.0. Weird but TRUE!

Is there also a 2.5.0.4 driver in existence or is that a typo for 2.5.0.5?
[Magisk] Zackptg5:
Hmm, interesting. I'd bring it up with the app devs and see what they think.

It's not a typo, the driver just 2.5.0.4. The new original v4a app was 2.5.0.4, then a quick emergency fix was pushed making it 2.5.0.5 but they forgot to update the driver number so it's still .4
[Magisk] sjamie:
Understood. I was unsure because 2.5.0.4 is displayed during the install but Magisk and Viper shows 2.5.0.5.
[Magisk] sjamie:
You can use the new mat version with the old driver for superior sound.

Did you have to do anything special to get Dolby Atmos working? After flashing 2.20.18, device is stuck at boot animation. :confused:
[Magisk] psychoela:
For me 2.20.18 is perfect,flash normaly,working fine,only i think before flash dolby u need uninstall aml then flash back after flash dolby to make patch together with v4a:D
[Magisk] sjamie:
I've never used AML so maybe that's the problem. :D

Do you also use SAURON?
[Magisk] kalpik:
Does the new material version still trigger play protect?
[Magisk] VK'ed:
No it doesn't
[Magisk] psychoela:
Yes, already forgot about it:p
[Magisk] sushuguru:
Same thing happened to me, try installing the old material version, the new one always causes "hiccups" with spotigy for me.
[Magisk] sjamie:
I did all of the above in addition to installing Sauron and my device still gets stuck at the boot animation. :confused:

If I uninstall Dolby, device boots as normal.

OnePlus 5, xXx NoLimits OOS ROM, V4A 1.62
[Magisk] VK'ed:
Tried that. New material+old driver. Sound is back to its former glory[emoji7]

Never updating again!
[Magisk] kalpik:
How do you get new material with old driver?
[Magisk] sjamie:
Welcome to the Eargasm Club! :laugh:

Select them with the volume keys during installation. Flash the newest version 1.6.3.
[Magisk] kalpik:
I tried that, but I still got the new driver version when I checked in settings.

---------- Post added at 10:55 AM ---------- Previous post was at 10:51 AM ----------

Sorry, I was chosing the wrong options. I have it now. Thanks!
[Magisk] sjamie:
Flash it again and watch the prompts closely. It is easy to select the wrong thing. The first prompt should have you press vol+ for material (not original version). 2nd prompt should have you press vol+ for new material (not old material). Final prompt should have you press VOL DOWN for old driver.
[Magisk] TahirZX:
So from my understanding u r saying that somehow

(material or original?) v4afx with 2.3.4.0 driver is better than original v4afx with 2.5.0.5 drivers?
[Magisk] shadowstep:
[MENTION=6037748]Zackptg5[/MENTION] Thanks for your work, as always. I've been planning to remove the old A.R.IS.E Sound System mod that I've been using for ages now and moving onto this. I have a few questions before I try this out today.

Firstly, I just want to confirm if the below is correct, when it comes to adding these specific terms in the flashable file's name:

"old" = installs V4A 2.3.4.0 (non-material) with the 2.3.4.0 driver
"new" = installs V4A 2.5.0.5 (non-material) with the 2.5.0.5 driver
"omat" = installs V4A 2.5.0.5 (material) with the 2.5.0.5 driver
"odrv" = installs V4A 2.6.3.0 (new material) with 2.3.4.0 driver
"ndrv" = installs V4A 2.6.3.0 (new material) with 2.5.0.5 driver

Secondly, I just downloaded the latest V4A 2.6.3.0 (new material) from it's thread and compared it with the same version that is present in your zip. However, the MD5 hash didn't match. Do you do any kind of modification to that apk before shipping it with your zip?

Thirdly, I see that your zip is using the unity template. Which means it'll install the app as a Magisk module if Magisk is detected and if it is not, then it'll install the app like a normal flashable zip would've. Is there a way I can force the zip to override/ignore Magisk detection so that it flashes the app like a normal flashable zip even if I have Magisk installed?

And finally, uninstalling a zip that uses the unity template can be done by simply re-flashing the zip in recovery. I assume this is also true for this zip? Additionally, if the zip installed the app as a Magisk module, would removing the Magisk module from Magisk Manager be equivalent to re-flashing the zip for uninstallation?

Thanks for your time! :)
[Magisk] Lycox:
When switching from e.g. Shuttle(+) to TuneInRadio, V4A stops the audio processing. The driver is disabled. Have to force stop the app to get it work again. Switching from TuneIn to Shuttle there isn't this issue. Anyone else facing that?
[Magisk] beeshyams:
Thanks for the latest update. Works like a charm with excellent quality. Selected new driver. Running Oreo 8.1 custom ROM (DotOS)
[Magisk] Jamoeda:
Where you found profiles for material fx?
[Magisk] Badger50:
Here's a little assortment of profiles and convolvers you can try out if you'd like :good:

https://drive.google.com/file/d/1QCVeZzFhDKc-QiVYqineFKHWtmh1HaFB/view?usp=drivesdk
[Magisk] DrNinjaa:
I have been using tune in radio from years and have been using various sound mods but never was ever able to use any sound mod to work with tune in ever, same problem with SoundCloud but one of the developer from xda was able to mod a apk to work with soundmods.
[Magisk] Jamoeda:
Thanks, I will try :)
[Magisk] whitewallman:
I'm getting better sound with new driver. At least the Pixel 2 XL front facing speakers sound better with new driver. Haven't tried Bluetooth headphones yet. Where do you see (or hear) the improvements with old driver?
[Magisk] sjamie:
New material + old 2.3.4.0 driver = best combination

2.3.4.0 driver provides the best sound quality (especially if you like bass).

New material app fixes many bugs from original app (e.g. profiles not sticking, profile sorting, etc.).

Bass and overall fullness of sound
[Magisk] whitewallman:
Through your device speaker(s), or earphones or Bluetooth device? It's odd that the new driver sounds noticeably better on my Pixel 2 XL. I'm referring to the device speakers.
[Magisk] sjamie:
My sound comparisons are for Bluetooth. It is hard to hear much difference in anything just using the device's speaker.
[Magisk] Zackptg5:
You got the options correct, this doesn't have the newest new material apk in it (it's frequently updated), as it turns out, I actually just added a system override feature back to unity - just add "sysover" to the zipname (note that boot scripts and props are still installed to magisk in this case), reflashing the zip will uninstal like any other unity mod and just deleting the magisk mod would have the same effect assuming you didn't do system override

:)
[Magisk] whitewallman:
It's a night and day difference here. I need to test Bluetooth performance now..
[Magisk] sjamie:
I'm interested in what you discover...
[Magisk] shadowstep:
Awesome! This answers all my questions. I'm gonna go ahead and make the move now. Thanks a lot, bud! :highfive:
[Magisk] sjamie:
Just out of curiosity, why overriding Magisk detection important to you if you are indeed using Magisk?
[Magisk] shadowstep:
It is not, I was just curious. :p It's great to see that Unity supports overriding again but, in case I ever run into Magisk issues... :)
[Magisk] e-cl:
Yes, absolutely. Audiomodlib, dolby and v4a. Yet it does not help.

However it is strange that script gives such errors
[Magisk] Nye-uhls:
Got any more ideas for trouble shooting? Installed the module from op (well, v1.4, which wasnt mentioned in OP, but is in most recent uploads from OP at AFH) did those two edits to the scripts you mentioned. And v4a says:

Driver version: 2.5.0.4 (weird?)

Status: abnormal

Processesing: no

Galaxy s6, i know i always see people say not to install v4a as system app on samsung devices, could that be related since this auto-intalls viper as a system app

Would installing the regular audiomodlib + v4a port of from topjohnwu be better?
[Magisk] Didgeridoohan:
Not really... I have it working great on my device with Magisk v13.0 beta (c4377ed) and enforcing SELinux.

Maybe upload your Magisk log to see if it shows anything.

No. You'll need a module that's adapted for audmodlib. That one isn't.

Of course, you could try that module by itself to see if it works better.
[Magisk] Nye-uhls:
Thanks for the response, I'm not quite sure what actions would trigger relevant logging here, rebooting?

I disabled magiskhide and re-enabled, heres the magisk log starting on being enabled:

I( 3070:17141) * Starting MagiskHide
D( 3070:17141) resetprop: setprop [persist.magisk.hide]: [1] by property_service
I( 3070:17141) hide_pre_proc: Hiding sensitive props
D( 3070:17141) resetprop: prop [ro.boot.verifiedbootstate] does not exist
D( 3070:17141) resetprop: prop [ro.boot.flash.locked] does not exist
D( 3070:17141) resetprop: prop [ro.boot.veritymode] does not exist
D( 3070:17141) resetprop: getprop [ro.boot.warranty_bit]: [0]
D( 3070:17141) resetprop: getprop [ro.warranty_bit]: [0]
D( 3070:17141) resetprop: getprop [ro.debuggable]: [0]
D( 3070:17141) resetprop: getprop [ro.secure]: [1]
D( 3070:17141) resetprop: getprop [ro.build.type]: [user]
D( 3070:17141) resetprop: getprop [ro.build.tags]: [release-keys]
D( 3070:17141) resetprop: getprop [ro.build.selinux]: [0]
D( 3070:17141) hide_list: initialize...
I( 3070:17141) hide_list: [com.google.android.gms.unstable]
I( 3070:17141) proc_monitor: init ns=mnt:[4026531840]
I( 3070:17141) proc_monitor: zygote (32-bit) ns=mnt:[4026543201] (64-bit) ns=mnt:[4026543281]

P.s. I'm also on latest official magisk beta.

I'm not afraid to get my hands dirty with adb and all that jazz, i just don't really know where to look :/
[Magisk] Didgeridoohan:
The relevant log would be from boot. It's got nothing to do with Hide.
[Magisk] Nye-uhls:
I only thought it might be relevant because it seems like whenever i have magisk problems, its related to magiskhide/resetprop.

Here's a log from a full boot, i wish I knew where to look myself lol. Btw, there's a line that says "beginning of crash" that i see pretty often, haven't been able to make sense of it, because as far as i can tell, my osm0sis busybox is still working.
[Magisk] Didgeridoohan:
Of course! I forgot about the boot script bug... None of them are running. Have you set the proper permissions for the scripts in post-fs-data.d and service.d? They need to be 755 but are probably currently at 644...
[Magisk] Nye-uhls:
I just checked and they are indeed 644!

I saw that mentioned in this thread, but i think somebody said that wasn't necessary!

I'll go change those and report back!

And to clarify, set 755 for all the scripts? Or just just the audmoblib ones?
[Magisk] Didgeridoohan:
All scripts in post-fs-data.d and service.d have to be 755 or the will not execute and are just wasting space.

You might have seen me saying that adding a script posted earlier in the thread isn't necessary if you use the SEINJECT edits.

Edit: Magisk is supposed to set 755 automatically, but there's a bug in the beta.
[Magisk] Nye-uhls:
Set them all to 755, it definitely helped. Now the driver status says normal atleast!

Unfortunately, its still not processing:/

I still get this in my magisk log:

I( 3191: 3191) hide_daemon: Unmounted (/magisk)
I( 3191: 3191) hide_daemon: Unmount Failed (/system/vendor/etc/audio_effects.conf)
I( 3191: 3191) hide_daemon: Unmount Failed (/system/vendor/etc/audio_effects.conf.bak)
I( 3191: 3191) hide_daemon: Unmount Failed (/system/xbin/busybox)
I( 3191: 3191) hide_daemon: Unmount Failed (/system/etc/mixer_paths.xml)
I( 3191: 3191) hide_daemon: Unmount Failed (/system/etc/audio_policy.conf)
I( 3191: 3191) hide_daemon: Unmount Failed (/system/etc/audio_effects.conf)
I( 3191: 3191) hide_daemon: Unmount Failed (/system/etc/mixer_paths.xml.bak)
I( 3191: 3191) hide_daemon: Unmount Failed (/system/etc/audio_policy.conf.bak)
I( 3191: 3191) hide_daemon: Unmount Failed (/system/etc/audio_effects.conf.bak)
I( 3191: 3191) hide_daemon: Unmounted (/system/lib/soundfx/libv4a_fx_ics.so)
I( 3191: 3191) hide_daemon: Unmount Failed (/system/priv-app/ViPER4AndroidFX)
[Magisk] Nye-uhls:
I jist realized that was probably just a magisk hide thing, heres the new boot log

Edit: I'm still confused that the driver status says v2.5.0.4 shouldn't it say 2.5.0.5?
[Magisk] Didgeridoohan:
Yes, that's a Magisk Hide thing. It's possible that it does have some kind of impact since it looks like proc_monitor start to crash around the time service.d is loading.

Not sure how to continue... You could try disabling Magisk Hide and reboot to see if there's any difference.

---------- Post added at 20:52 ---------- Previous post was at 20:51 ----------

That's normal.
[Magisk] Nye-uhls:
Thank you tremendously for your help!

I think I'm about to chalk this up as magisk vs. samsung thing. At this point it seems like its not anything to with this mod itself, so I'll do some digging into magisk errors and maybe try topjohnwu's v4a and see if thats any different with proper permissions.

Also, i just realized when i uninstalled xtrememusic mod (because that was also not processing), that it didn't fully uninstall, so that cant be helping lol.

Last samsung phone i ever buy -_-
[Magisk] Didgeridoohan:
Best. Advice. Ever. :p
[Magisk] e-cl:
If i manually execute following commands in adb shell (got tired typing on little phone keyboard):

su

sepolicy-inject --live "allow mediaserver mediaserver_tmpfs file { read write execute }"

i'm getting following result:

(Android M policy compatibility mode)

Can't open '/sys/fs/selinux/load': Permission denied

That's the reason i guess it doesn't work. How to deal with it?
[Magisk] marbertshere:
I got Viper to process over Bluetooth but it won't process whenever my headphones are plugged in. Otherwise everything is normal. I did edit those files in the Magisk directory.
[Magisk] Didgeridoohan:
Not quite sure how to deal with it, but what are the permissions on that file?
[Magisk] Nye-uhls:
Update on my situation in case this helps anyone (these steps may be fairly samsung specific):

1. Followed [MENTION=4667597]Didgeridoohan[/MENTION] 's instructions to set permissions for those 2 scripts AND edit seinject

2. Flashed an old galaxy s6 specific v4a flashable.

Now it works completely...

I think the main thing that the flashable v4a did was add the following lines to build.prop:

lpa.decode=false
lpa.releaselock=false
lpa.use-stagefright=false
tunnel.decode=false

I would attach the flashable v4a, but I'm out at the lake today with weak cell service and no WiFi
[Magisk] whalesplaho:
Sound wasnt processing here too... Installed Selinux changer n changed to enforcing and now its processing sound...... Tho i followed [MENTION=4667597]Didgeridoohan[/MENTION] 's instructions and edit seinject
[Magisk] whalesplaho:
After reboots processing shows NO.:crying:
[Magisk] sjamie:
Thanks. I wish all zips were as easy to uninstall as Unity zips are! :) #brilliant
[Magisk] quinejh:
1.5.5 works great on my pixel 2xl but the most 1.6.3 wouldn't process I had to revert back.
[Magisk] matt1313:
Back on 1.5.5. Got it to work but when I add Dolby everything goes bad. No processing and Dolby fc

Pixel 2xl
[Magisk] Zackptg5:
You need to completely removed all audio mods, them flash v1.6.3. Dolby Oreo doesn't play nicely with v4a and you need aml if using multiple audio mods with magisk
[Magisk] matt1313:
Ok I'll try later when I have more time. Which Dolby for pixel 2 xl
[Magisk] GBPackerFanForLife:
On a Pixel 2 xl running DU ROM Nathans kernel with Magisk 16.3 tried everything from all these post still Viper a No go..I gotta say Z you are very committed to gwtti g this to work for Pixel 2 users Much Appreciated.. I will just keep messing with it..
[Magisk] MrBrady:
I love the new Material app but find it buggy compared to other versions. Maybe it's because my profiles were all built for previous versions.

But I noticed when I load a profile (after it converts the profile), it appends the profile settings to whatever is loaded instead of null'ing the settings and applying the new ones.

The work around I found is to disable each setting between profile switches. Then it seems to only apply the settings in the profile I'm loading.
[Magisk] JFK1975:
Sometimes came a pop up with the new versions to update/install the driver, what never succeeded. With 1.6.3 there comes a message on my device for the first time that installation wasn't possible and viper asks for a restart of the device.

Just Wanted to give that information.

Thanks [MENTION=6037748]Zackptg5[/MENTION] :cool:
[Magisk] youtuber123:
Guys got an issue. I have the honor view 10, emui 8.0 android 8.0 and I can't install the driver. When I reboot the driver don't stick to my phone. So V4A isn't working... Any idea?
[Magisk] tagari:
Great work on the app, thanks for all the hard work! I decided to change from the old UI and 2.3.4.0 driver to the new material UI but stick with the old driver. As others have mentioned, I also have issues with Spotify with the latest version (1.6.3) when skipping ahead on the same track or changing to next song.I am on Stock, Rooted Nexus 6P with 8.1 Oreo, April Security Patch. I have noticed that,in addition to the effects stopping and starting when i do any of the actions i mentioned, convolver also stops functioning and you need to choose a new one. I have tried ACP and AML, but it all results to the same issue. I also tried with 2.5.0.4 driver but the same problems occur.Apart from this mod, i only have busybox and unified hosts adblock in magisk.