Yup that's what I thought too..and I'm using Viper4Android via MagiskHmm.. that's weird. If you stop play music , movies, YouTube stuff, the processing will be No which is normal.
I'm not what cause it not to processing anything. But have you tried with magisk module for viper4android?
Thnx that link works great, got V4A 2.7.1, AML and Ainur Narsil working now with working BT, BT was my biggest problem - not putting audio through.Are you talking about this when referring to the "few things you have to do to make it work"
P.S. I have a Pixel 3 XL with Android 10 October update.
Thnx that link works great, got V4A 2.7.1, AML and Ainur Narsil working now with working BT, BT was my biggest problem - not putting audio through.
OP6 OB30/OB1 Android Q
Try this if you want http://bit.ly/2P4gSH7 ,Running flawlessly on Samsung Galaxy A7 (2018) (SM-A750FN) Android 8.0 Stock with Magisk 20!
But how do I turn the Dark mode on?
So I've been living under the you know "rock" that is my bed but the app just turns to abnormal even with my phone's built in loud speaker worked for like one song but then it died. Uninstalling it worked for a bit but I'm not wanting to keep doing that Everytime it doesn't wanna work (uninstalled through magisk). Help me understand what happened!!! . ..
Just of an off question. How did you install this? With the app or magisk module?This maybe a device specific issue, but I'm using a Pixel 4 XL (on Android 10 of course) and with the installation of Audio Modification Library and Audio Compatibility Patch installed, I can get system wide equalization except for one thing, Google Maps's voice direction audio.
I guess it's a minor problem but if I'm listening to music and Google is about to alert me the next turn, viper stops processing and my music goes all flat while Google is speaking, and then for like a split second to a few seconds later, viper starts to kick in again.
I can't seem to figure it out for the life of me on how to get viper4android to still process even when Google is speaking the next turn direction via voice. Has anyone ran into this issue? Anyone managed to fix this?
I tried various settings when installing Audio Compatibility Patch with the audio_policy using both old and new logic, also enabled lib workaround too if that helps.
Any help is greatly appreciated!
Just of an off question. How did you install this? With the app or magisk module?
Sent from my OnePlus7TPro using XDA Labs
Same for me, each time the processing status is no and I have to toggle off and on the legacy mode to have it processing again.After a couple of days, it just stops working and then I have to go to settings and disable and enable legacy mode and it starts working again until the next time.
Well buddy, not everybody would agree with your opinion.What are the mods here doing???
Delete this 2.7.2.* update please! Its the source of all problems here....why do the mods watch this since months and doing nothing?
Unbelieveable in my opinion whats going on here....more than 20 pages just because noone is willing to remove a defect update...
Yep, me (and many others who used the magiskpolicy fix). Viper works with or without legacy mode, but I don't hear the difference between standard and legacy mode anyway (tried on a couple of headphones, both modes sounds the same). I assume that the difference is in how the equalizer connects to the audio session, the audio processing itself is still the same.Is there just 1 person, where the latest update work as it should? And no, legacy mode is not - as written by others in earlier postings - "working", its just a fallback for problems.
Again, selinux is switched to enforcing. Therefore, only the absolutely minimum changes to SELinux are running. It is NOT "absolutely everything".Sorry, I checked wrong script. You are right that it turns SELinux back to enforcing so shouldn't be a big security risk. But in each case "mine" script is "allow only absolutely necessary selinux", "your" is "allow everything".
Attach audio effects in your screenshot is basically Legacy mode. Why it's named differently on your and mine phone..no idea. I must keep legacy mode enabled for youtube vanced. Non legacy works only for Youtube music. But I have different phone and system - Mi 10T lite with MIUI 12.
The following are the details from running AAPT on my device, against Viper:Been watching the convo, my viper is just like yours, not sure why the other one is named differently either, I was wondering if he installed viper fx, legacy, xhfi, myself.
Well, in the screenshot above (not my install), the other version has both legacy and compatibility mode settings. But it appears I do not need legacy mode (or even compatibility mode), as my YouTube IS being processed by Viper; although I personally only really care about my music app.Looks to me like you have previous Viper version installed, like 126.96.36.199. On latest it's "Legacy mode" in my case as well