Related
I m not responsible for any damages in your phone Proceed with your responsibility.
I used supersu root, install titanium backup and removed every bloatware . My rom is hell fast. here are a list of stuff essential and confirmed working for our device j2.
Dolby here https://forum.xda-developers.com/note-4/themes-apps/audio-mod-dolby-digital-plus-note-4-t3075871
Amazing without selinux permissive mode it works, it force closes but proceed again the same step. it works like a charm.
Viper Audio mode here https://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
xposed installer here https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
wanam framework here https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960 ,,flash this zip via twrp.
, just download the xposed-v87.1-sdk22-arm-custom-build-by-wanam-20161125.zip from the download section,there shouldn't be any confusion, this zip is the essential FRAMEWORK to run the modules. no need to use the installer alpha version from the link . After reboot, download the wanam MODULE from the download module section , remember do not tweak much coz it gives a bootloop. so a back up in external card is essential. just restore the system from nandroid/twrp backup.
Edit: install universal init.d enabler and put 01selinux script to make permissive mode to install Dolby atmos.
thanks works like a charm.
Also, Can you make a list of all the bloatware you have safely removed and share with us. it will be very helpful to know which system apps i can get rid of
I have tried installing the apk but everytime I install the driver and reboot it asks me to do it again.
I have tried renaming audio_conf but still not luck.
How do I go about install viper to 7.1.2 without it failing
Search for VIPER4Android_2.5.0.5_guitardedhero.zip,
flash the zip with twrp, reboot your device, use a root explorer and under vendor/etc rename the audio_effects.conf to audio_effects.conf.bak for example.
Start the viper app, apply the driver install, be patient, after install reboot your device, viper works now even with selinux enforced. The viper app will be installed with the zip, no need to download it anywhere else.
Here on XDA you will find threads about viper and arise from guitardedhero.
coremania said:
Search for VIPER4Android_2.5.0.5_guitardedhero.zip,
flash the zip with twrp, reboot your device, use a root explorer and under vendor/etc rename the audio_effects.conf to audio_effects.conf.bak for example.
Start the viper app, apply the driver install, be patient, after install reboot your device, viper works now even with selinux enforced. The viper app will be installed with the zip, no need to download it anywhere else.
Here on XDA you will find threads about viper and arise from guitardedhero.
Click to expand...
Click to collapse
This solution is indeed reposted everywhere but did not work for me.
What worked was a clean install of my ROM ( lineageOS 14.1 20170619 nightly) , Kernel (Franco v52), and SuperSU (v2.79) (Magisk somehow messes everything up). Then I flashed ARISE with one of the older .zip (2.94 should work, I don't know which version I used since I renamed it back in march).
In AROMA I chose "jedi" -> viper 2.3.4.0, since only the older Version works and "remove deep buffer"
after the installation I rebooted, changed the name of
/vendor/etc/audio_effects.conf
and installed busybox to
/system/bin
so viper would find it. If you don't do that, viper will try and fail to install the driver, complaining busybox is not installed. The driver is already installed by the ARISE.zip so you can reboot.
After turning off "AudioFX" Viper worked as desired (including streaming audio, that's what "remove deep buffer" is for).
theduckking said:
This solution is indeed reposted everywhere but did not work for me.
What worked was a clean install of my ROM ( lineageOS 14.1 20170619 nightly) , Kernel (Franco v52), and SuperSU (v2.79) (Magisk somehow messes everything up). Then I flashed ARISE with one of the older .zip (2.94 should work, I don't know which version I used since I renamed it back in march).
In AROMA I chose "jedi" -> viper 2.3.4.0, since only the older Version works and "remove deep buffer"
after the installation I rebooted, changed the name of
/vendor/etc/audio_effects.conf
and installed busybox to
/system/bin
so viper would find it. If you don't do that, viper will try and fail to install the driver, complaining busybox is not installed. The driver is already installed by the ARISE.zip so you can reboot.
After turning off "AudioFX" Viper worked as desired (including streaming audio, that's what "remove deep buffer" is for).
Click to expand...
Click to collapse
Yes, that's what I usually use too (2.94), but he was only asking for viper, and the solution i posted does work. I'm actually using it this way with paranoid and have no issues. I use viper with every rom and I always delete AudioFX, musicfx and remove deep buffering, but I don't install extra busybox on los based roms.
coremania said:
Yes, that's what I usually use too (2.94), but he was only asking for viper, and the solution i posted does work. I'm actually using it this way with paranoid and have no issues. I use viper with every rom and I always delete AudioFX, musicfx and remove deep buffering, but I don't install extra busybox on los based roms.
Click to expand...
Click to collapse
The guitardedhero.zip did not work for me, as to why I don't know. Magisk also has several modules that should enable Viper4Android which seem to function for the wast majority of (angler) users. Maybe the installation of busybox is unnecessary, I did not check because I dreaded one more reboot after hours of tinkering. If there is an obvious culprit that hinders an "easy" installation of Viper4Android, I'd be quite interested. I'm struggling with that guitardedhero.zip solution since i upgraded to 7.x. (throughout stock and LineageOS and all bootloader/radio/vendor versions).
theduckking said:
The guitardedhero.zip did not work for me, as to why I don't know. Magisk also has several modules that should enable Viper4Android which seem to function for the wast majority of (angler) users. Maybe the installation of busybox is unnecessary, I did not check because I dreaded one more reboot after hours of tinkering. If there is an obvious culprit that hinders an "easy" installation of Viper4Android, I'd be quite interested. I'm struggling with that guitardedhero.zip solution since i upgraded to 7.x. (throughout stock and LineageOS and all bootloader/radio/vendor versions).
Click to expand...
Click to collapse
I will update my n7 and tryout guitardedhero.zip.
The n7 runs with los.
Usually I use arise with my tablet for enjoying dolby too.
Edit: with Los only permissive, but it's working
Hey guys, today I rooted my phone and installed newest Viper's audio for android. Everything is OK, apart the driver installation. App asks me to install drivers and when I let it do that (with root permissions enabled) it tells me to reboot phone to complete the installation. When I reboot, driver status is "abnormal" and the app asks me to install drivers again. There is no end. Please, couldn't you guys try to install Viper if it is functioning? Or if I made mistake somwhere and I have to flash fresh ROM? I tried almost everything.
Thank you.
arharos said:
Hey guys, today I rooted my phone and installed newest Viper's audio for android. Everything is OK, apart the driver installation. App asks me to install drivers and when I let it do that (with root permissions enabled) it tells me to reboot phone to complete the installation. When I reboot, driver status is "abnormal" and the app asks me to install drivers again. There is no end. Please, couldn't you guys try to install Viper if it is functioning? Or if I made mistake somwhere and I have to flash fresh ROM? I tried almost everything.
Thank you.
Click to expand...
Click to collapse
If you are using Magisk. Open Magisk Manager. Install Viper4Android module from downloads, then go to root file manager. Open Root/system/vendor/etc folder. Change audio_effects.conf to audio_effects.conf.bak Restart your device and then check the status then it should work. If you are on SuperSU then just don't forget to rename audio effects file after driver installation.
Klawzy said:
If you are using Magisk. Open Magisk Manager. Install Viper4Android module from downloads, then go to root file manager. Open Root/system/vendor/etc folder. Change audio_effects.conf to audio_effects.conf.bak Restart your device and then check the status then it should work. If you are on SuperSU then just don't forget to rename audio effects file after driver installation.
Click to expand...
Click to collapse
I will second this method. Installing via Magisk is probably the only way I've found on Nougat to install Viper without trouble. I install through Magisk and then install the newest Viper4Android app from that thread. Drivers preinstalled.
Kindly Read forum rulea before creating a thread bro.
You have Created it in wrong section.
Ask in question and answers section . ?
Could someone link to viper they are using please
Sent from my ONEPLUS A5000 using XDA-Developers Legacy app
I have 2.4.0.1 by guitarhero that works, flashed via TWRP. I have to use an SELinux toggling app (only available via APK mirror or similar sites) to set SELinux to Permissive for it to work. The OS will flag the app as dangerous, but it's fine.
Oh sorry for wrong section. Thank you guys. I tried the magisk version but didn't work. Then I tried to flash Viper by guitarhero and this works, because the driver is flashed into system along with app. I even had a newer version installed (2.3.4.0) and when I started this newer version first rather than older guitarhero, it worked. So I suppose you just need to flash viper for driver and then you can run new versions.
Hi guys, why don't you install ViPER4Arise™ 2.5.0.5 module (ARISE™ themed version of ViPER4Android's latest DSP application with pre-installed driver. All ARISE™ artwork is the work and property of @churapa) ?
https://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
chrissss91 said:
Hi guys, why don't you install ViPER4Arise™ 2.5.0.5 module (ARISE™ themed version of ViPER4Android's latest DSP application with pre-installed driver. All ARISE™ artwork is the work and property of @churapa) ?
https://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
Click to expand...
Click to collapse
You mean all the magnus opus package (130MB)? Is it working also on enforcing or should I switch to permissive?
carlese said:
You mean all the magnus opus package (130MB)? Is it working also on enforcing or should I switch to permissive?
Click to expand...
Click to collapse
If you read the linked first post is says:
Magnum Opus™ Features:
- The most advanced and comprehensive sound system ever made available.
- Jellybean through Android O developer preview support.
- ARM, Mediatek™, Qualcomm™, 32bit, 64bit, and x86 support.
- Full SELinux Enforcing support
- Magisk™ support provided by the incredibly talented Zackptg5 and his Magisk™ Resource.
- 300MB of fully customizable sonic bliss.
So at least there is a claim of enforcement support.
3DSammy said:
If you read the linked first post is says:
Magnum Opus™ Features:
- The most advanced and comprehensive sound system ever made available.
- Jellybean through Android O developer preview support.
- ARM, Mediatek™, Qualcomm™, 32bit, 64bit, and x86 support.
- Full SELinux Enforcing support
- Magisk™ support provided by the incredibly talented Zackptg5 and his Magisk™ Resource.
- 300MB of fully customizable sonic bliss.
So at least there is a claim of enforcement support.
Click to expand...
Click to collapse
I know but that's a generic statement, as far as I know it takes time to make it work on new devices.. Can anyone confirm?
carlese said:
You mean all the magnus opus package (130MB)? Is it working also on enforcing or should I switch to permissive?
Click to expand...
Click to collapse
Hi,
I've installed :
- Core System module (required once during initial installation)
- ViPER4Arise™ 2.5.0.5 module (optional)
- ViPER4Arise™ Profiles module (optional)
No need to modify anything else.
Just carrefully read installation process (search "arise_customize.prop").
Viper4ARISE + Magisk mod works for me too. SafetyNet passes.
I did have to set "delete.deep_buffer=true" to get it to work with Google Play Music.
chrissss91 said:
Hi,
I've installed :
- Core System module (required once during initial installation)
- ViPER4Arise™ 2.5.0.5 module (optional)
- ViPER4Arise™ Profiles module (optional)
No need to modify anything else.
Just carrefully read installation process (search "arise_customize.prop").
Click to expand...
Click to collapse
After fiddling witht he file I managed to install it on my op5.. But status is "abnormal".. I tried uninstalling the driver and only then V4A asked for root permission, then rebooted and still there is no option to reinstall driver.. What can I do?
carlese said:
After fiddling witht he file I managed to install it on my op5.. But status is "abnormal".. I tried uninstalling the driver and only then V4A asked for root permission, then rebooted and still there is no option to reinstall driver.. What can I do?
Click to expand...
Click to collapse
No problem for me, are you sure you have installed the core version (install.core=true) ?
chrissss91 said:
No problem for me, are you sure you have installed the core version (install.core=true) ?
Click to expand...
Click to collapse
Sure, are using supersu or magisk? Did you install V4A module?
carlese said:
Sure, are using supersu or magisk? Did you install V4A module?
Click to expand...
Click to collapse
i've installed :
- core
- v4a_2.5.0.5
- v4a_profiles
An d I use Magisk 13.0 beta
chrissss91 said:
i've installed :
- core
- v4a_2.5.0.5
- v4a_profiles
An d I use Magisk 13.0 beta
Click to expand...
Click to collapse
Ok but on magisk, did you install the V4A module?
carlese said:
Ok but on magisk, did you install the V4A module?
Click to expand...
Click to collapse
No, only busybox
chrissss91 said:
No, only busybox
Click to expand...
Click to collapse
Which one? SOrry to bother you, I'm not a newbie but there are a lot of busybox out there, just want to check if everything works and follow what you did..
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.