Related
Hello. I currently have a OP2 (or is it OPT? ) with Official RR + Boeffla for CM (alpha 10). I know, I need to update my signature.
Today I decided to try Viper (making a nand backup first, of course) and it installed without problems, but it only works on Play Music. Same for AudioFX, the default EQ that came with the system that I have now disabled (to avoid Viper issues).
No effects on YouTube or BSPlayer for example (with eighter A-FX or Viper), in short, the EQs don't affect the system, but only some apps, or one in my case.
Is this normal behaviour? Back on KK 4.4.4 I could use Viper or whatever EQ app and it would apply to all the system and apps!
Thanks in advance.
Do you have force enable v4a on?
I tried but nothing. Do I have to reboot when I enable that?
Tried rebooting, nothing. It's just not applying to the whole system, only to the apps tha use equalizers.
Is this normal?
For me, it didn't even work on Spotify using the latest 2.4.0.1 of V4A in permissive mode and using the correct busybox. So I uninstalled it, maybe in a couple of months it will work again.
It's like not all system uses the default EQ. And I don't know if that's normal behaviour on MM or is it just me.
Fixed thanks to this post:
http://forum.xda-developers.com/showpost.php?p=66617379&postcount=22262
Hope it helps others.
eXtremeDevil said:
Fixed thanks to this post:
http://forum.xda-developers.com/showpost.php?p=66617379&postcount=22262
Hope it helps others.
Click to expand...
Click to collapse
Does the zip still work. Am on RR 5.7.1 and facing the same issue. Viper works for Music Player and Googel Music but nothing else. Need it for MX desperatley. Would really appreciate your help
Yes, actually, it was easier than flashing all those. Just install Viper the normal way, the apk and then the driver. You need to have Selinux set to permissive all the time, AFAIK. After the driver installation and reboot, follow these instructions:
http://forum.xda-developers.com/showpost.php?p=66717263&postcount=22331
For me, I had to set that file to read only because after reboots it would roll back to normal. But as long as those line are commented, Viper will work system-wide.
Hope that helps. Please tell me how it goes.
Cheers.
eXtremeDevil said:
Yes, actually, it was easier than flashing all those. Just install Viper the normal way, the apk and then the driver. You need to have Selinux set to permissive all the time, AFAIK. After the driver installation and reboot, follow these instructions:
http://forum.xda-developers.com/showpost.php?p=66717263&postcount=22331
For me, I had to set that file to read only because after reboots it would roll back to normal. But as long as those line are commented, Viper will work system-wide.
Hope that helps. Please tell me how it goes.
Cheers.
Click to expand...
Click to collapse
Yup that did it :victory::victory: thanks so much man.
Cheers!!
Glad I could help
eXtremeDevil said:
Yes, actually, it was easier than flashing all those. Just install Viper the normal way, the apk and then the driver. You need to have Selinux set to permissive all the time, AFAIK. After the driver installation and reboot, follow these instructions:
http://forum.xda-developers.com/showpost.php?p=66717263&postcount=22331
For me, I had to set that file to read only because after reboots it would roll back to normal. But as long as those line are commented, Viper will work system-wide.
Hope that helps. Please tell me how it goes.
Cheers.
Click to expand...
Click to collapse
What do you mean by commenting? Do I have to really delete those lines or just put quote marks before and after the lines?
And I'm on stock 3.02, rooted and xposed installed. Van this work form me?
If Viper is not working for you, you can try that solution. You can delete the lines or add "#" before them, eighter would work. I recommend commenting them because that way you can uncomment them anytime you want.
Hi,
is anybody using Viper4Android on this phone? Can it even work?
Viper4Android is not device-dependent so it should work just fine.
You'd need to follow the same steps as on any other device
Amplificator said:
Viper4Android is not device-dependent so it should work just fine.
You'd need to follow the same steps as on any other device
Click to expand...
Click to collapse
Yes, but on some phones it just does not work properly, and SELinux must be permissive. So if anybody is actually using it...
Viper works with any issues. Installing you have to remember to:
-root your yota
- set selinux to premissve
-install busybox
- to get it working ( viper4 driver status - processing -yes) set viper as default music equalizer in your player for e.g
in poweramp audio settings you have to disable Direct Volume Control and enable Music FX!
In general I recommend installing A.R.I.S.E. Sound Systems - Auditory Research in Sound Enhancement - Deuteronomy 1.86 which is in my opinion better than standalone viper4android. Before doing it you have to remember to do twrp backup , just in case . In my case everything works with any issues.
Managed to install A.R.I.S.E following your instructions. Sound before was a bit 'meh' but after tweaking the parameters my yotophone 2 sounds awesome! Well worth installing.
bobblesop said:
Managed to install A.R.I.S.E following your instructions. Sound before was a bit 'meh' but after tweaking the parameters my yotophone 2 sounds awesome! Well worth installing.
Click to expand...
Click to collapse
Viper4Android is the best thing ever somebody made in this universe Too bad author didn't / can't put it on Play
I've been using it since the beginning, audio books sound awesome, music is like injecting sound directly in your brain even with some 5$ headphones.
I've tested ARISE on my HTC M7, but it's a bit too much. I prefer clean V4A.
bobblesop said:
Managed to install A.R.I.S.E following your instructions. Sound before was a bit 'meh' but after tweaking the parameters my yotophone 2 sounds awesome! Well worth installing.
Click to expand...
Click to collapse
Which version did you install? TWRP reboots if I try to install ARISE, normal Viper can't install driver
I have SuperSU, Busy box and SelinuxModeChanger.
kbal said:
Which version did you install? TWRP reboots if I try to install ARISE, normal Viper can't install driver
I have SuperSU, Busy box and SelinuxModeChanger.
Click to expand...
Click to collapse
Deuteronomy 1.86
I wiped dalvic and cache before I installed and didn't need to change selinux
I managed to install ARISE 2.05.
Mounted System in TWRP, during install TWRP freezes, then reboots, but Viper works.
I decided to start this thread for a couple of reasons 1 so I can remember what order I did things in to get back after a wipe and 2 so maybe it can help others to setup certain apps how they want and not have to spend the time I did searching and googling.
To start we are going to assume you already have an unlocked bootloader and TWRP installed.
After a fresh wipe I flashed OOS 4.0.2 Full from this thread in TWRP
https://forum.xda-developers.com/oneplus-3t/how-to/rom-oos4-0-nougat-op3t-leaked-t3523482
I recommend a fresh wipe because every time I did a dirty flash or restored a backup my Android System started draining battery like crazy and phone would get warm while charging
Without rebooting I then flashed Magisk V10.2 in TWRP
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Still without rebooting I flashed Franco Kernel in TWRP
https://forum.xda-developers.com/on...ernel-franco-kernel-r1-28th-november-t3508904
I then wiped dalvik and cache and rebooted phone.
edit - THIS STEP WILL NOT WORK ON 4.0.3. It has been patched out.
Somewhere in the process my DM-Verity was tripped and although annoying it does not seem to matter and it can be fixed later by following this
https://forum.xda-developers.com/oneplus-3/how-to/fix-easy-method-removing-dm-verity-t3544339
After phone booted and I setup account and wifi and I go the play store and install PHH superuser
https://play.google.com/store/apps/details?id=me.phh.superuser&hl=en
Once installed I open it and click the 3 dots and go to settings
Where it says Superuser access I toggle between Apps only and Apps and ADB till I get the message Superuser granted to Superuser
I then go back into play store and install Magisk manager
https://play.google.com/store/apps/details?id=com.topjohnwu.magisk&hl=en
I go into Magisk Settings and click the checkbox to Enable Magisk Hide.
I then reboot phone
Once phone reboots I open Magisk manager again and check safetynet. It now passes.
I hate ads, I had been using Adaway from F-Droid with MM but I couldn't get it to work on N
I found this https://github.com/AdAway/AdAway/issues/770 after many searches. About halfway down a user named KreAch3R has comiled Sanjay900's changes into an apk so I figured I would give it a try.
At first I could not get it to activate and block ads
I installed this busybox and then it activates no problems and now most ads (not youtube) are blocked
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
Now what I really wanted was Viper4arise. I tried flashing some in TWRP and I couldn't get them to work and this led to a couple more wipes. But I really wanted this so I kept searching.
I found this https://forum.xda-developers.com/apps/magisk/viperfx-mkm-magisk-t3535401
I downloaded it and enabled it in Magisk manager
Still no luck and I couldn't get it to work.
After more googling and reading through the other threads for viper I figured it was deep buffering
I used ES file explorer as I was not at home and went into system/etc and found audio_policy.conf
I commented out the first line I saw that said deep_buffer.
After saving I rebooted and now Viper-fx works
To get it to work with Poweramp I had to set FX compatibility mode in Viper to compatible and in Poweramp audio/advanced tweaks I had to disable Direct Volume Control and Enable MusicFX.
Thanks for sharing
Did you have any special trick to get viper to work ? Tried commenting out the line deep_buffer and still unable to get viper to work.
ghofer said:
Did you have any special trick to get viper to work ? Tried commenting out the line deep_buffer and still unable to get viper to work.
Click to expand...
Click to collapse
The only steps I did are what was listed.
I was able to replicate it twice after wipes with same steps.
This is the line I commented out in attached
Sykojoe said:
The only steps I did are what was listed.
I was able to replicate it twice after wipes with same steps.
This is the line I commented out in attached
Click to expand...
Click to collapse
Edited: Didn't see the attachment earlier. Answered my question. Thank you btw for sharing this the rest of the steps worked great for me. I am passing safety net.
Ya I realized a SS might help more so I edited it in.
Sykojoe said:
The only steps I did are what was listed.
I was able to replicate it twice after wipes with same steps.
This is the line I commented out in attached
Click to expand...
Click to collapse
Sykojoe said:
Ya I realized a SS might help more so I edited it in.
Click to expand...
Click to collapse
Would you be able to send me that file ? I am just curious what is wrong with my setup.
Just want to say thank you again. Didn't see the PM until now. I was able to use another guide on XDA to get Viper working.
Viper will not work on all apps at any time on OOS 4.0.2. Enable Compatibility mode in settings to get it to work. IMO this produces lower quality audio, but it works.
Still cant get viper working. Nothing of deep_buffer is commanded. Please can you share your audio_policy.conf?
NielsvdS said:
Still cant get viper working. Nothing of deep_buffer is commanded. Please can you share your audio_policy.conf?
Click to expand...
Click to collapse
You need to edit in a # on the deep_buffer line.
I sent you a pm with my file
NielsvdS said:
Still cant get viper working. Nothing of deep_buffer is commanded. Please can you share your audio_policy.conf?
Click to expand...
Click to collapse
1) With what app?
2) Did you enable Viper's Compatibility mode?
3) I've also modified audio_policy_configuration.xml to remove deep buffer. Messing with this file too much will break your audio though.
damiensturdy said:
1) With what app?
2) Did you enable Viper's Compatibility mode?
3) I've also modified audio_policy_configuration.xml to remove deep buffer. Messing with this file too much will break your audio though.
Click to expand...
Click to collapse
With what app?: I've editted with ES File Explorer.
Did you enable Viper's Compatibility mode? Not tried yet
I don't have changed anything inside audio_policy_configuration.xml
NielsvdS said:
With what app?: I've editted with ES File Explorer.
Did you enable Viper's Compatibility mode? Not tried yet
I don't have changed anything inside audio_policy_configuration.xml
Click to expand...
Click to collapse
WHat app isn't Viper working with? Viper processes audio on a per-app basis, based on the audio buffer the app uses. Google Play Music, on Nougat, does not pipe through Viper even with modifications to the audio config.
Enable compatibility mode. At the moment this is the only way to get the highest compatibility with apps- like Google Play Music.
damiensturdy said:
WHat app isn't Viper working with? Viper processes audio on a per-app basis, based on the audio buffer the app uses. Google Play Music, on Nougat, does not pipe through Viper even with modifications to the audio config.
Enable compatibility mode. At the moment this is the only way to get the highest compatibility with apps- like Google Play Music.
Click to expand...
Click to collapse
It's now working after disabling audio buffer. I use most of the times Spotify to listen to music
I followed same steps earlier. But my selinux is enforcing. I have to set it to permissive everytime on reboot. Permissive fix that comes with arise didnt work for me. Any idea..?
Do you think the Elemental X Kernel would be ok instead of franco kernel? Not sure if I'd get compatibility issues with any of this stuff. Btw not going to try to get adblock or viper fx. Also, do you wipe the system or just what TWRP has already checked?
x12prem said:
I followed same steps earlier. But my selinux is enforcing. I have to set it to permissive everytime on reboot. Permissive fix that comes with arise didnt work for me. Any idea..?
Click to expand...
Click to collapse
Mine is set to enforcing with all this working fine
Ra3zor0 said:
Do you think the Elemental X Kernel would be ok instead of franco kernel? Not sure if I'd get compatibility issues with any of this stuff. Btw not going to try to get adblock or viper fx. Also, do you wipe the system or just what TWRP has already checked?
Click to expand...
Click to collapse
Not sure. I know it all worked the same with stock kernel.
Normally when I need to wipe my phone it is because I have really messed it up so I wipe system and data.
Sykojoe said:
Mine is set to enforcing with all this working fine
Click to expand...
Click to collapse
But viper4rarise needs selinux as permissive. Isnt it....?
Comprehensive audio guide for android 8.1 and P DP1 (saves battery)
Cyan means 8.1 ONLYFor android P only, flash the magisk modules in TWRP, manager is broken with module flashing, just a temp patch from @topjohnwu
I am not responsible if you break, blow up, or destroy your device in any way
Hi XDA, this is the comprehensive guide to making the google pixel and XL have the ultimate audio mods installed while saving battery (if xposed is what you're looking for, it's under amplify)
Prerequisites
TWRP 3.2.1-x
Magisk v15.x REQUIRED
busybox (osm0sis) installed (for some mods)
Link to homeboy76's guide, look at step 9 or 10
Magisk permissive module Download
Dual stereo speakers Magisk module by kingbri(me) (AML bug fixed)
I ported Chdloc's mod into a magisk module, need to add it to the official repo, but it works very well right now
Download the zip file from this thread https://forum.xda-developers.com/pixel-xl/development/magisk-module-pixel-stereo-speakers-t3753190
Make sure you have permissive installed (check prereqs)
Flash it in Magisk
Reboot
Profit
Atmos
Download dolby unity port by @Zackptg5
Install (Universal)
Flash the permissive script in magisk
Flash the dolby zip in Magisk, It's a module
Reboot
App should be installed
IF installing with V4A, install Atmos, reboot, then V4A, then audio modification library, reboot. Everything should work
V4A steps
Install Ahiron and zackptg 5's v4a module (follow the prompts during installation)
You're done!
Ainur Sauron mod- fixes audio quality by importing qualcomm drivers as opposed to the stock android ones
Open magisk manager and navigate to downloads
search for ainur and download mark II.II
AML(audio mod lib) is installed (updated if you have v4a) by default
Reboot
If mod does not install properly, reflash the installation zip and should uninstall the mod
Battery saving
Greenify
Install the magisk module for greenify
open greenify and select NOT rooted
follow the prompts
go into settings after wizard
change mode to rooted
grant SU access
L speed (very important, this is the best battery saver app)
Install the beta from play store
Open the app and choose the AMOLED theme
choose the battery profile
turn on fstrim every boot
turn on aggressive doze (not recommended while driving, use greenify aggressive doze instead if you drive a lot)
After booting, launch L-speed and allow it to execute scripts
Hibernate Google Play services
Go into magisk manager and find the downloads section
Download sysconfig patcher, patches Google play store and other battery draining system processes so they don't drain battery
ElementalX kernel
Configure as elementalx governor with wq_powersaving enabled in the cpu menu
Amplify!
Installing Xposed framework and amplify
download xposed framework systemless here(make sure it is beta 2)
download xposed installer here
Install the xposed zip directly in magisk like a magisk module
Install xposedinstaller apk
reboot(takes a long time to boot firstrun)
open xposed installer
check to see if xposed is installed
install amplify from the PLAY STORE (not sure why it isn't installing in xposed)
activate xposed module and reboot
relaunch amplify and let it run on the default settings!
amplify configurations (updating specifics, requests avaliable in comments)...
Feel free to comment with updates to this guide, I will consider them and put them into the op!
Hi, i don´t understand the step for dual stereo speakers can you explain better? because is a confuse, thanks
TotoBerto02 said:
Hi, i don´t understand the step for dual stereo speakers can you explain better? because is a confuse, thanks
Click to expand...
Click to collapse
you download the zip file, and you copy and paste the commands while your phone is connected to the computer, "file name" is the file path where the zip is stored on your computer
UPDATE:
added ainur sauron mark II mod in OP
rewrote chdloc dual stereo speakers mod
kingbri said:
UPDATE:
added ainur sauron mark II mod in OP
rewrote chdloc dual stereo speakers mod
Click to expand...
Click to collapse
What does the rewrite of chdloc stero speakers do?
does the new version of arise work with 8.1?
willyumlu said:
does the new version of arise work with 8.1?
Click to expand...
Click to collapse
As far as I believe Arise doesn't work with 8.1 (could be wrong) But I use a magisk Module Viper4Magisk or whatever it's called will install V4A works fine I tried a Dolby Oreo zip on the Arise thread but it didn't show in app drawer so not sure if that installed correctly hope that helps :good:
Fwiw, I used this with Magisk 15.2 in a clean install of 8.1. Working without issue
https://forum.xda-developers.com/showthread.php?t=3577058
Sent from my Pixel XL using Tapatalk
liam_davenport said:
As far as I believe Arise doesn't work with 8.1 (could be wrong) But I use a magisk Module Viper4Magisk or whatever it's called will install V4A works fine I tried a Dolby Oreo zip on the Arise thread but it didn't show in app drawer so not sure if that installed correctly hope that helps :good:
Click to expand...
Click to collapse
ARISE itself works with 8.1, some of the modules are incompatible though, waiting (hunting) for a fix
Homeboy76 said:
What does the rewrite of chdloc stero speakers do?
Click to expand...
Click to collapse
It just means that I edited the guide to include a few commands I missed
It doesn't actually give you dual speakers though? My understanding is that one side is a speaker and the other is a microphone.
Sent from my Pixel XL using Tapatalk
MeetFace said:
It doesn't actually give you dual speakers though? My understanding is that one side is a speaker and the other is a microphone.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
It uses the speaker and the earpiece for audio, similar to the iphones
UPDATE 1/08/18- added dolby atmos guide, make sure to install this before any magisk audio mod
kingbri said:
UPDATE 1/08/18- added dolby atmos guide, make sure to install this before any magisk audio mod
Click to expand...
Click to collapse
Link please!
fixed
How do you get Viper to work? Which prompts are the correct ones? After installing 2.5 with everything else it gives me an I/O error on installing the driver. I'm on LineageOS 15.2 btw.
buzzywuzzy said:
How do you get Viper to work? Which prompts are the correct ones? After installing 2.5 with everything else it gives me an I/O error on installing the driver. I'm on LineageOS 15.2 btw.
Click to expand...
Click to collapse
First of all are you on aml viper? ARISE doesn't work with 8.1 and i'm talking to some of the devs about fixing this issue. I've had some experience with LOS, it may be throwing an error because of the rom or because there are some other things LOS has by default that is interfering with viper. The builds are unstable, my advice would be to switch to crDroid because it is LOS based, but is made for audio. I'm not sure what you mean by prompts but I have been hitting the vol up key both times and it works for me on the Pixel Dust rom
kingbri said:
First of all are you on aml viper? ARISE doesn't work with 8.1 and i'm talking to some of the devs about fixing this issue. I've had some experience with LOS, it may be throwing an error because of the rom or because there are some other things LOS has by default that is interfering with viper. The builds are unstable, my advice would be to switch to crDroid because it is LOS based, but is made for audio. I'm not sure what you mean by prompts but I have been hitting the vol up key both times and it works for me on the Pixel Dust rom
Click to expand...
Click to collapse
Oh okay, well I might check that out then. I just followed all the steps in the guide step by step and thats the only one i couldnt get to work. I didn't attempt ARISE at all.
buzzywuzzy said:
Oh okay, well I might check that out then. I just followed all the steps in the guide step by step and thats the only one i couldnt get to work. I didn't attempt ARISE at all.
Click to expand...
Click to collapse
I changed the v4a guide, you don't need the permissive module, maybe that's what's crashing it?
kingbri said:
I changed the v4a guide, you don't need the permissive module, maybe that's what's crashing it?
Click to expand...
Click to collapse
It didn't "crash" per se, it just wouldn't install the necessary driver after the package was installed. I'll try it with the module disabled and see if it works. Do I still need the permissive module for the other mods? Or just when they're being installed?
Updated: OP contains instructions for Android Pie and below, post #5 has current instructions for Android Q.
Saw a couple Viper4Android threads, did not see much in terms of profiles for the 2 XL specifically. Just got the 2 XL coming from a 6P and there was a great profile to optimize it's internal speakers so decided to try out the mod for the 2 XL's speakers. Working very nicely.
Not sure if this will work with every ROM but works nice on Bootleggers (should work on any Pie ROM including stock) and thought I would share so more people could enjoy much improved sound quality. Makes rooting the phone well worth it.
Instructions:
After installing Magisk 18.1
Install BusyBox and run the set-up
Download the Viper4Android V4.1 (used Material theme) via Magisk manager
run the install process, select 2.5.0.4 material theme, install as system app, grand root access then reboot
Load the DorianX profile taken from the 6P. Just unzip then look over the extracted files.
Edited to explain further: You will probably need to individually place the "SRS Audio HD" IRS file in the Viper4Android Kernel folder and put the Profile folder in the Viper4Android Profile folder (using a file explorer to copy/paste the files). Once that's done, in the Viper4Android app under "Convolver", tap it and choose "impulse response file", You should see the "SRS Audio HD" IRS file that you placed in the Kernel folder, select it, tick the box next to Convolver to enable it. Under the main app settings you should be able to select and load the profile. If you did it correctly the DorianX profile folder should be visible to select it. It depends which version of Viper4Android you install. If you do materialized (2.5.0.4) the above should work. Let me know if any problems
Play some music. Toggle Viper4Android master power on and off under the phone speaker tab within the app then back to on once to enable it. Usually you have to do this to "officially" enable Viper4Android. If it's working you will hear the difference. Under the app settings you can verify that the app is processing as well under "driver status". Working with the latest Poweramp, Youtube, etc.
Credit to DorianX who made the profile. There are 4 profiles included to optimize specific bluetooth devices, headphones,etc but just using the internal speaker one (for now). Unable to locate the past post in the 6P forum containing the profile and which other devices were optimized to link to it.
Works very well and thought it was worth posting and making a small contribution so for now enjoy! Profile attached.
Have Viper4Android working nicely on Android Q Beta 4.
Those that downloaded this profile if you don't mind posting the Dorian profile speaker settings (all of them for each tab and whether enabled or disabled) would appreciate it. Profiles no longer can be loaded in this version of Viper.
Looking at the speaker xml file can see some of the settings but probably not all.
Magisk 19.3, Adaway works, viper now works all on today's beta 4. Tried all versions and combos. Getting the driver to install and stick was a big pain.Can post some instructions if anyone is interested. I'm sure plenty of people would like to get viper working.
Now if only Google apps like Gmail and Google play would be themed. Can see the force dark toggle is broken in this beta. Not sure if the Google apps were theming in Beta 3 or not.
powerserge1 said:
Have Viper4Android working nicely on Android Q Beta 4.
Those that downloaded this profile if you don't mind posting the Dorian profile speaker settings (all of them for each tab and whether enabled or disabled) would appreciate it. Profiles no longer can be loaded in this version of Viper.
Looking at the speaker xml file can see some of the settings but probably not all.
Magisk 19.3, Adaway works, viper now works all on today's beta 4. Tried all versions and combos. Getting the driver to install and stick was a big pain.Can post some instructions if anyone is interested. I'm sure plenty of people would like to get viper working.
Now if only Google apps like Gmail and Google play would be themed. Can see the force dark toggle is broken in this beta. Not sure if the Google apps were theming in Beta 3 or not.
Click to expand...
Click to collapse
a lot interesting of this, this is a reason why I am rollback to custom on pie while like q beta
libracez said:
a lot interesting of this, this is a reason why I am rollback to custom on pie while like q beta
Click to expand...
Click to collapse
See below
Ok I got it. No need to PM me the profile. Took most of the night but done now.
Would be unable to stay on Q without Viper4Android as well...
Make sure to uninstall all previous versions of Magisk and modules to start fresh.
Install Magisk 19.3 via twrp, install latest Magisk manager and then Busybox (make sure to set up busybox). Some are having problems with this Beta and Magisk so YMMV. Working well for me and no app lag.
On Pie in Magisk you should see Viper4Android 2.7.1 module as available
On Q it's not listed (for me at least) so get it from XDA labs.
Install Viper4Android:
https://labs.xda-developers.com/store/app/download/com.pittvandewitt.viperfx (link to direct download, must be signed in)
Or use this link: https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
The installer will install it as a magisk module. Grant supersu permissions, install driver, phone will reboot.
Install the magisk audio modifications library module. Reboot. After rebooting disable this module (do not uninstall). Reboot again.
Open up Viper4Android. If it asks you to install driver again do so and phone will automatically reboot. Repeat if needed. If driver install remains unsuccessful try enabling and disabling the audio modifications module then try again. What worked for some worked the opposite for others in past threads on previous Android versions and various devices. Here is the thread for reference: https://forum.xda-developers.com/pixel-2/help/viper4android-driver-installation-fails-t3766362
Once driver is installed the app will load properly and under driver status it will probably say "unsupported" and "abnormal". Close the app
Go back into Magisk manager. Now toggle to re enable the audio modifications module. Reboot. (This is the module that allows Viper4Android to process and can help to install the driver)
Upon reboot, Viper4Android should work. Play some music, check the driver status to verify, you may need to toggle off/on master limiter to finally enable it.
For this profile, put the SRS file in OP above in the Viper4Android Kernel folder. Under the apps speaker tab manually input these settings:
Master limiter: On
Playback gain: moderate or 2, max gain 4x, output threshold -1.9db
FIR Equalizer: On. EQ is flat
Convolver: On. Tap convolver then select the SRS inpulse file you placed in the Kernel folder. Cross channel set to 0
Profit.
You can set or disable the viper4android notification icon in the statusbar within the app's settings.
Let me know how the 2 XL's speakers sound Post updated, instructions should be clear enough. Some having problems will need to wait for the updated Magisk. Moving forward, we do have viper4android working on Q. Fully tested on my 2xl and stable with beta 4.
Thanks to @Team_DeWitt
And Dorianx for his profile originally created for the 6p
powerserge1 said:
Ok I got it. No need to PM me the profile. Took most of the night but done now.
Would be unable to stay on Q without Viper4Android as well...
Make sure to uninstall all previous versions of Magisk and modules to start fresh.
Install Magisk 19.3 via twrp, install latest Magisk manager and then Busybox (make sure to set up busybox). Some are having problems with this Beta and Magisk so YMMV. Working well for me and no app lag.
On Pie in Magisk you should see Viper4Android 2.7.1 module as available
On Q it's not listed (for me at least) so get it from XDA labs.
Install Viper4Android:
https://labs.xda-developers.com/store/app/download/com.pittvandewitt.viperfx (link to direct download, must be signed in)
Or use this link: https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
The installer will install it as a magisk module. Grant supersu permissions, install driver, phone will reboot.
Install the magisk audio modifications library module. Reboot. After rebooting disable this module (do not uninstall). Reboot again.
Open up Viper4Android. If it asks you to install driver again do so and phone will automatically reboot. Repeat if needed. If driver install remains unsuccessful try enabling and disabling the audio modifications module then try again. What worked for some worked the opposite for others in past threads on previous Android versions and various devices. Here is the thread for reference: https://forum.xda-developers.com/pixel-2/help/viper4android-driver-installation-fails-t3766362
Once driver is installed the app will load properly and under driver status it will probably say "unsupported" and "abnormal". Close the app
Go back into Magisk manager. Now toggle to re enable the audio modifications module. Reboot. (This is the module that allows Viper4Android to process and can help to install the driver)
Upon reboot, Viper4Android should work. Play some music, check the driver status to verify, you may need to toggle off/on master limiter to finally enable it.
For this profile, put the SRS file in OP above in the Viper4Android Kernel folder. Under the apps speaker tab manually input these settings:
Master limiter: On
Playback gain: moderate or 2, max gain 4x, output threshold -1.9db
FIR Equalizer: On. EQ is flat
Convolver: On. Tap convolver then select the SRS inpulse file you placed in the Kernel folder. Cross channel set to 0
Profit.
You can set or disable the viper4android notification icon in the statusbar within the app's settings.
Let me know how the 2 XL's speakers sound Post updated, instructions should be clear enough. Some having problems will need to wait for the updated Magisk. Moving forward, we do have viper4android working on Q. Fully tested on my 2xl and stable with beta 4.
Thanks to @Team_DeWitt
And Dorianx for his profile originally created for the 6p
Click to expand...
Click to collapse
succesfuly, ty
for my 2xl It was
1. installation from xda lab - reboot
2. install audio modification library - reboot
3. open viper (still asking to install driver - just close app, don't choose nothing)
4. go to Magisk switch off audio modification library - reboot
5. viper successfully load, status normal and working (media) with just my favorite profile no custom settings
libracez said:
succesfuly, ty
for my 2xl It was
1. installation from xda lab - reboot
2. install audio modification library - reboot
3. open viper (still asking to install driver - just close app, don't choose nothing)
4. go to Magisk switch off audio modification library - reboot
5. viper successfully load, status normal and working (media) with just my favorite profile no custom settings
Click to expand...
Click to collapse
Our 2 XL's can be temperamental, lol.
Glad you got it working. Not sure how the driver installed and the viper app fixed itself with the audio modifications module switched off. It's like you didn't need that module at all. Whatever works.
Just happy we have viper for Q. Played games, music, youtube and running stable here.
powerserge1 said:
Ok I got it. No need to PM me the profile. Took most of the night but done now.
Would be unable to stay on Q without Viper4Android as well...
Make sure to uninstall all previous versions of Magisk and modules to start fresh.
Install Magisk 19.3 via twrp, install latest Magisk manager and then Busybox (make sure to set up busybox). Some are having problems with this Beta and Magisk so YMMV. Working well for me and no app lag.
On Pie in Magisk you should see Viper4Android 2.7.1 module as available
On Q it's not listed (for me at least) so get it from XDA labs.
Install Viper4Android:
https://labs.xda-developers.com/store/app/download/com.pittvandewitt.viperfx (link to direct download, must be signed in)
Or use this link: https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
The installer will install it as a magisk module. Grant supersu permissions, install driver, phone will reboot.
Install the magisk audio modifications library module. Reboot. After rebooting disable this module (do not uninstall). Reboot again.
Open up Viper4Android. If it asks you to install driver again do so and phone will automatically reboot. Repeat if needed. If driver install remains unsuccessful try enabling and disabling the audio modifications module then try again. What worked for some worked the opposite for others in past threads on previous Android versions and various devices. Here is the thread for reference: https://forum.xda-developers.com/pixel-2/help/viper4android-driver-installation-fails-t3766362
Once driver is installed the app will load properly and under driver status it will probably say "unsupported" and "abnormal". Close the app
Go back into Magisk manager. Now toggle to re enable the audio modifications module. Reboot. (This is the module that allows Viper4Android to process and can help to install the driver)
Upon reboot, Viper4Android should work. Play some music, check the driver status to verify, you may need to toggle off/on master limiter to finally enable it.
For this profile, put the SRS file in OP above in the Viper4Android Kernel folder. Under the apps speaker tab manually input these settings:
Master limiter: On
Playback gain: moderate or 2, max gain 4x, output threshold -1.9db
FIR Equalizer: On. EQ is flat
Convolver: On. Tap convolver then select the SRS inpulse file you placed in the Kernel folder. Cross channel set to 0
Profit.
You can set or disable the viper4android notification icon in the statusbar within the app's settings.
Let me know how the 2 XL's speakers sound Post updated, instructions should be clear enough. Some having problems will need to wait for the updated Magisk. Moving forward, we do have viper4android working on Q. Fully tested on my 2xl and stable with beta 4.
Thanks to @Team_DeWitt
And Dorianx for his profile originally created for the 6p
Click to expand...
Click to collapse
Please forgive me for sounding like a complete tool ..lol but i cant seem to find viper4android app on my phone in the file explore to be able to put the srs file from the dorian zip to the folder in my phone , any help would be greatly appreciated
Mr. Blanco said:
Please forgive me for sounding like a complete tool ..lol but i cant seem to find viper4android app on my phone in the file explore to be able to put the srs file from the dorian zip to the folder in my phone , any help would be greatly appreciated
Click to expand...
Click to collapse
No problem. You are looking for the viper4android folder not the app. See attached screen
powerserge1 said:
No problem. You are looking for the viper4android folder not the app. See attached screen
Click to expand...
Click to collapse
I figured that and searched and searched through internal storage and root directory and i cannot find that app anywhere in my file explorer ..lol this is crazy im using Mixplorer and have attached pics , not sure if i should erase everything and start from scratch again ..lol
Edit: Okay after multiple reboots it magically showed up and was able to put file in correct place but now Driver Status Enabled = no (message) strange ....gonna start over and see if i can get everything working ..lol Thank you for your help @ powerserge1
Edit: Everything up and running and working ... Profit
Mr. Blanco said:
Edit: Everything up and running and working ... Profit
Click to expand...
Click to collapse
Good stuff. To anyone else installing viper just to note if you click on driver and see it as processing = no this does not mean you did anything or the install went wrong. Play a video or music, driver should show as processing yes. When nothing is playing then processing will be no.
Does this enable dual speaker for calls/message alerts?
How did you guys get magisk working on Q beta 4? For me it makes systemui not start on boot and it skips the lock screen entirely. And if it does boot normally, apps take over 10 seconds to launch. I have tried to wipe system data cache and then ran the flash-all bat and still have the issue. A lot of others have the issue on the magisk canary thread. Some don't have it. Someone suggested after a full wipe with -w it fixed it.
joedajoester said:
How did you guys get magisk working on Q beta 4? For me it makes systemui not start on boot and it skips the lock screen entirely. And if it does boot normally, apps take over 10 seconds to launch. I have tried to wipe system data cache and then ran the flash-all bat and still have the issue. A lot of others have the issue on the magisk canary thread. Some don't have it. Someone suggested after a full wipe with -w it fixed it.
Click to expand...
Click to collapse
Looks like I found a solution that is working for several members (and it was purely by accident because installing Magisk threw an error). Uninstall Magisk in TWRP first then:
https://forum.xda-developers.com/showpost.php?p=79682444&postcount=477
powerserge1 said:
Looks like I found a solution that is working for several members (and it was purely by accident because installing Magisk threw an error). Uninstall Magisk in TWRP first then:
https://forum.xda-developers.com/showpost.php?p=79682444&postcount=477
Click to expand...
Click to collapse
It's not working for me. I had to reboot about 4 times because systemui wasn't starting up and I was getting a black wallpaper with no status or nav bar. Finally rebooted normally and at times apps refuse to open but it's slightly better than it was. This is just so weird. Do I really need to wipe my phone or is it magisks fault?
joedajoester said:
It's not working for me. I had to reboot about 4 times because systemui wasn't starting up and I was getting a black wallpaper with no status or nav bar. Finally rebooted normally and at times apps refuse to open but it's slightly better than it was. This is just so weird. Do I really need to wipe my phone or is it magisks fault?
Click to expand...
Click to collapse
Someone in the Android Q discussion thread might be able to help better. Google pulled the beta so it's tough to say whether in your case it's a magisk or android issue. Or both.
I love this post for real, I have a Pixel 3 with Android P, viper v2.7.1.
I had to port the userprofile to the new version, if someone want it, PM me
zxspectrun said:
I love this post for real, I have a Pixel 3 with Android P, viper v2.7.1.
I had to port the userprofile to the new version, if someone want it, PM me
Click to expand...
Click to collapse
Feel free to post it as well. Curious how you were able to port the profile. Looked everywhere but couldn't find any info to convert the old profile to the new preset format.
powerserge1 said:
Feel free to post it as well. Curious how you were able to port the profile. Looked everywhere but couldn't find any info to convert the old profile to the new preset format.
Click to expand...
Click to collapse
I just installed the viper4android mod showed on the screenshot and it ported all my old profiles
attached dorian ported to v2.7.1.0
zxspectrun said:
I just installed the viper4android mod showed on the screenshot and it ported all my old profiles
attached dorian ported to v2.7.1.0
Click to expand...
Click to collapse
Yes it did the same for me. The first time, almost forgot. I did not find the sound to be the same, not even close. Ultimately I still had my Nexus 6p and was able to retrieve the settings and input them manually. Then the sound was as it should be.
Do you find the sound identical with the ported profiles? It might be hit and miss.