Hi,
some information for everyone who's interested: I tried to install Xposed Framework and Viper4Android on my rooted H960A and that worked very well.
1. Xposed Framework:
I just installed the latest framework V85 for arm64 and the second screen fix for MM, which you can find here.
Both zip files were flashed via TWRP after I flashed the SuperSu.zip to root my phone. Afterwards I installed the XposedInstaller_3.0-alpha4.apk.
You can find the latest xposed framework here and the Xposed Installer here.
To test the Xposed frameword I installed some modules (RootCloak and Flat Style Bar Indicators). Both modules work perfectly on the V10.
2. Viper4Android:
Why would you want to install Viper4Android if you have a very good Hifi DAC onboard? Simple answers at least for me: Viper4Android supports sound settings for Bluetooth devices. I have a nice Bluetooth headset I wanted to use with my V10 and after the installation I must say it was totally worth it.
You need:
* rooted H960A
* Viper4Android (I used version 2.4.0.1)
* install Busybox and run it at least once to obtain root rights
* set Selinux to permissive
* After the phone is rooted install Busybox and run the installation procedure to have busybox installed (current version 1.24.2).
* Then Viper4Android can be installed and started to install the drivers. The phone needs to be restarted afterwards.
* Then I tried to change Selinux setting to permissive with the app SelinuxModeChanger. But that did not work for me as after starting the app and granting root rights I just received the message that the superuser manager did not allow the application to access root or that my device is not rooted at all.
I tried a manual way by installing a terminal emulator and entering the commands
Code:
su
setenforce 0
Opening Viper4Android and showing the driver status revealed that the driver was now active.
The downside of this manual method is that after a reboot Selinux is set to enforced again and you would have to enter above commands in the terminal emulator again.
To set Selinux to permissive at boot time you can do the following:
* install the "Universal inid.d Tool" from the play store. Start the application and switch the slider at the top of the page to "on" to activate inid.d support. Reboot your phone.
* after the reboot is done start the universal init.d tool again and tap on the entry "scripts" under "Manage your inid.d scripts". Then tap on the pen symbol at the top right of the app screen to edit this script.
* a popup window opens showing "no scripts found". If you tap on this line you can change it. Remove everything and enter the following code instead:
Code:
#!/system/sh
setenforce 0
* tap on "save"
That should be it. Now every reboot Selinux is set to permissive again.
Have fun.
If you have questions I will try to answer them.
thank you very much for this tutorial
did you notice any battery drain ?
vip57 said:
thank you very much for this tutorial
did you notice any battery drain ?
Click to expand...
Click to collapse
No, so far no noticeable battery drain. But I have this running only since yesterday afternoon. I will observe the battery consumption an let you now should I notice any drain.
This Guide helps on configuring the A.R.I.S.E. (Auditory Research in Sound Enhancement) Sound System, including Viper4ARISE, in your Axon 7. This fixes the low volume problem for the EU version of AXON 7 2017G and increases the quality in all the models. Among other features it reconstruct the signal for streaming audio, increasing the spectrum and bringing more detail to the sound. It is also compatible with Dolby ATMOS. The official thread is complicated since it offers a lot of different options. Here I try to provide an easy and straightforward guide for beginners. After a while you will be able to get into the universe of profiles, settings and extras explained in the official thread.
REQUIREMENTS:
- Since this package modifies your system partition, it requires unlocked bootloader and root.
- Another requirement is to have the Busybox patch. If your root method is not including it, just grab one of the many free Busybox Apps from Play Store.
WARNINGS:
- Since this module is not systemless, in case of an OTA upgrade you will need to reflash the stock system before performing an OTA upgrade, apply the upgrade and then reinstall the Sound System.
- Unfortunately there is no uninstaller so keep a backup of your system partition before proceeding with the installation.
DOWNLOADS:
For a safe installation begin using ARISE Deuteronomy 2.2.3 Patched. Some people likes better the sound athmosphere provide by this version. The latest stable release ARISE Deuteronomy 2.3.3 and other versions can be found in the official thread. However 2.2.3 patched has proven to be very stable and fully compatible with our device. Later on you can test upgrading to the current or another release.
Since ARISE Sound Systems rewrites the audio configuration depending on your settings, you may need the Dolby ATMOS add-on too to recover this feature.
You'll have to flash it using TWRP recovery 3.0.3 or Flashfire app.
INSTALLATION:
STEP 0: Ensure you have a backup of your system partition and you have downloaded the ARISE Sound System to the internal or external storage of your phone.
STEP 1: Disable Dolby ATMOS.
STEP 2: Flash ARISE Sound System version 2.2.3 patched either using TWRP or Flashfire.
STEP 3: Reboot, play some music, open Viper4ARISE, activate the master switch for your headset and enjoy. Save your current configuration in the hamburger menu before testing new settings. You can also tune the phone speakers, bluetooth and external USB DAC settings.
STEP 4 (Optional): If Dolby ATMOS is not working after applying the patch, Flash the Dolby ATMOS add-on.
TROUBLESHOOTING:
- If ask for driver installation then Open your favorite file explorer and go to: /vendor/etc and rename audio_effects.conf to audio_effects.conf.bak, reboot and follow step 3 again.
- Ensure you have unlocked the system partition by typing reboot disemmcwp in the system or TWRP terminal or ADB shell. and repeat from step 1.
MY SETTINGS:
My recommendation is to leave Dolby ATMOS disabled unless you are watching a movie or concert. You do not have to disable Viper4ARISE when using Dolby ATMOS, however do never mix surround or spatial processing in both, it will be a mess. I share my general settings as an starting point, however you can experiment with all the parameters to find the sweet spot for your gear. Do not forget to save your current configuration in the hamburger menu before testing new settings, it is hard to remember the detailed configuration afterwards:
Check that the Headset HiFi setting in your Phone settings is set to Super. and for Viper4Arise set:
Master Power ON
Spectrum Extension ON (only for low quality streaming)
- Strength: 0.2
Dynamic System ON (Headset Only)
- Listening Device: Common Earphone v2
- Dynamic Bass: 18% for acoustic music and high dynamic range sources, up to 29% when listening dance/electronic
ViPER Bass OFF (only activate it if your headphones require extra Bass. In my case I have it disabled).
- Bass Mode: Natural
- Bass Frequency: 40hz
- Bass Boost: 13dB
VIPER Clarity ON (It can bring up pretty good detail to the sound).
- Clarity Mode: Natural
- Clarity: 6dB
Master Gate (Limiter)
- Channel Pan:0%
- Output Gain: 2.3dB (set more if you want more output volume without making quantization noise audible)
- Limit Threshold: 0dB
After setting it, just toggle the master switch several times to hear the difference. You will realize how much quality can be extracted from this excellent Axon 7 hardware.
How was your experience?
I love this mod, but every once in a while (like at least once or twice a day) I have to disable/ re-enable V4a or restart my phone because something goes wrong with it and it turns off (but shows it's on), like the driver unloads? So, I came back to the stock Dolby Atmos.
Hello, I'm having issues having viper to download drivers, for some reason, I am unable to rename audio_effects.conf with either es file explorer or root explorer despite es file explorer saying renamed successfully but it wouldn't change or show after reboot. I made sure they both have root permission. I have also checked if I have busybox installed but it came with systemless root. Root Switch shows selinux is set to permissive. So i'm scratching my head trying to figure out what the issue is.
PS. forgot to mention my bootloader is also unlocked.
vyurdin said:
Hello, I'm having issues having viper to download drivers, for some reason, I am unable to rename audio_effects.conf with either es file explorer or root explorer despite es file explorer saying renamed successfully but it wouldn't change or show after reboot. I made sure they both have root permission. I have also checked if I have busybox installed but it came with systemless root. Root Switch shows selinux is set to permissive. So i'm scratching my head trying to figure out what the issue is.
PS. forgot to mention my bootloader is also unlocked.
Click to expand...
Click to collapse
Did you ever do a "reboot disemmcwp"?
If not, turn on usb debugging, connect the phone to your computer and do a "adb reboot disemmcwp".
This disables the write protection on /system.
Loader009 said:
Did you ever do a "reboot disemmcwp"?
If not, turn on usb debugging, connect the phone to your computer and do a "adb reboot disemmcwp".
This disables the write protection on /system.
Click to expand...
Click to collapse
It works now, thanks! luckily I didn't have to edit that file.
Did anyone get it to work on Cm13? For me the driver fails to load with status abnormal, both with stable and alpha of Deuteronomy
nupi said:
Did anyone get it to work on Cm13? For me the driver fails to load with status abnormal, both with stable and alpha of Deuteronomy
Click to expand...
Click to collapse
Change the Selinux to Permissive on boot.
reV17 said:
Change the Selinux to Permissive on boot.
Click to expand...
Click to collapse
I shall try that. Can I put it back to enforcing after boot? I really dislike running devices on permissive...
nupi said:
I shall try that. Can I put it back to enforcing after boot? I really dislike running devices on permissive...
Click to expand...
Click to collapse
Unfortunately I don't believe it'll work if you put it back to enforcing.
tele_jas said:
I love this mod, but every once in a while (like at least once or twice a day) I have to disable/ re-enable V4a or restart my phone because something goes wrong with it and it turns off (but shows it's on), like the driver unloads? So, I came back to the stock Dolby Atmos.
Click to expand...
Click to collapse
Dolby ATMOS is meant for movies or concerts. Music sounds horrible with Dolby ATMOS.
I have been using this mod for about a week now in this device without any issue. I have tested the three proposed versions, and I have: the bootloader unlocked, F2FS filesystem, root, Xposed (all 9 modules working) and SafetyNet below this sound system.
What ROM are you using? Have you unlocked your system partition by doing a reboot disemmcwp in the terminal or adb shell? What version of ARISE Sound Systems are you using? How did you root your phone? Perhaps we could help you on this.
nupi said:
I shall try that. Can I put it back to enforcing after boot? I really dislike running devices on permissive...
Click to expand...
Click to collapse
You can try setting up V4A in enforcing mode using this guide.
for me it doesn't work, it ask for install drivers every time i reboot, and for no reason selinux don't stay to permissive after reboot (with selinuxmodechangerv3.2).
so i have abnormal statuts in viper4arise.
i try with stock b06, stock b08 and stock b09, it never work for me (maybe is because of b09 bootstack).
i also cannot use xposed framework anymore with b09, i can install it but if i activate any mod and reboot my phone bootloop.
Killerdog said:
i also cannot use xposed framework anymore with b09, i can install it but if i activate any mod and reboot my phone bootloop.
Click to expand...
Click to collapse
Did you try xposed 87? November security patches broke the earlier versions
nupi said:
Did you try xposed 87? November security patches broke the earlier versions
Click to expand...
Click to collapse
i try updating xposed inside the app. update is ok, but if i activate any module it bootloop at next reboot.
Oki said:
Dolby ATMOS is meant for movies or concerts. Music sounds horrible with Dolby ATMOS.
I have been using this mod for about a week now in this device without any issue. I have tested the three proposed versions, and I have, the bootloader unlocked, F2FS filesystem, root, Xposed and SafetyNet below this sound system.
What ROM are you using? Have you unlocked your system partition by doing a reboot disemmcwp in the terminal or adb shell? What version of ARISE Sound Systems are you using? How did you root your phone? Perhaps we could help you on this.
Click to expand...
Click to collapse
> I used the latest 2.3.3, flashed it twice in the past month (also tried an older one, but not sure which one)? Also flashed just V4a, with the same issue
> I'm running Z.A.D. Mix7 (V.3) ROM
> Xposed is installed for status bar changes only, and re-orientated volume
> I did do the disemmcwp (had to do this for my font and emoji changes to stick)
> I was one of the few that have the actual ZTE unlocked bootloader, then I followed DrakenFX thread on how to root.
But... the reason I went to ARISE, was because I wanted to use my favorite music player, n7 music player..... Which isn't compatible with Dolby Atmos. So, the issue may have been with n7? I'm currently trying to decide between XenoAmp and Double Twist Cloud Player as my player of choice. I also used PowerAmp for about 4 years, even ran the beta (build 703) up until about 3 months ago, but am tired of the same Gingerbread style UI it's had for the past 3 or 4 years.
So, that's where I'm at.... I may try it again without n7?
Killerdog said:
for me it doesn't work, it ask for install drivers every time i reboot, and for no reason selinux don't stay to permissive after reboot (with selinuxmodechangerv3.2).
so i have abnormal statuts in viper4arise.
i try with stock b06, stock b08 and stock b09, it never work for me (maybe is because of b09 bootstack).
i also cannot use xposed framework anymore with b09, i can install it but if i activate any mod and reboot my phone bootloop.
Click to expand...
Click to collapse
Try rooting your device using this method. The root includes Xposed (I have 8 modules up and running) and everything should be working. Probably using HelsAx7 as the base ROM could solve your problem.
tele_jas said:
> I used the latest 2.3.3, flashed it twice in the past month (also tried an older one, but not sure which one)? Also flashed just V4a, with the same issue
> I'm running Z.A.D. Mix7 (V.3) ROM
> Xposed is installed for status bar changes only, and re-orientated volume
> I did do the disemmcwp (had to do this for my font and emoji changes to stick)
> I was one of the few that have the actual ZTE unlocked bootloader, then I followed DrakenFX thread on how to root.
But... the reason I went to ARISE, was because I wanted to use my favorite music player, n7 music player..... Which isn't compatible with Dolby Atmos. So, the issue may have been with n7? I'm currently trying to decide between XenoAmp and Double Twist Cloud Player as my player of choice. I also used PowerAmp for about 4 years, even ran the beta (build 703) up until about 3 months ago, but am tired of the same Gingerbread style UI it's had for the past 3 or 4 years.
So, that's where I'm at.... I may try it again without n7?
Click to expand...
Click to collapse
PowerAmp and Player PRO are the best in sound quality, the second is even better. And both seem to be working fine with Viper4ARISE. What kind of source are you playing (bandwidth and bitdepth)?
This makes my music sound sweet! I don't know if anyone experienced this but my phone has 0% sleep and is always 100% awake and heats up like an oven after flashing this I restored my backup and it's okay now
Teet1 said:
This makes my music sound sweet! I don't know if anyone experienced this but my phone has 0% sleep and is always 100% awake and heats up like an oven after flashing this I restored my backup and it's okay now
Click to expand...
Click to collapse
You can use wake lock detector to check what's wrong. The package is pretty stable. Could you please provide some more info (device, ROM, root method, media player, ARISE version, Viper4A configuration...)?
Oki said:
Dolby ATMOS is meant for movies or concerts. Music sounds horrible with Dolby ATMOS.
I have been using this mod for about a week now in this device without any issue. I have tested the three proposed versions, and I have, the bootloader unlocked, F2FS filesystem, root, Xposed and SafetyNet below this sound system.
What ROM are you using? Have you unlocked your system partition by doing a reboot disemmcwp in the terminal or adb shell? What version of ARISE Sound Systems are you using? How did you root your phone? Perhaps we could help you on this.
Click to expand...
Click to collapse
I'm wondering if you can help me with another issue I'm experiencing since I last posted here. My battery started draining really fast since I flashed the audio patch, I'm aware that's normal for viper but this is abnormal since the battery drains when the phone is not in use and it tends to stay warm. I have never had this issue when I had viper on my note 4.
The steps I have done for my phone:
Root method by jcadduono’s official thread in your safety net guide with success.
Done all steps with safetynet steps from above with success.
And I did the audio upgrade from this thread with success by using your preferred one.
And that's when my phone started draining more than it usually does for viper and being slight warm when not in use. I have already done a wipe before I did all these methods.
EDIT: Someone already mentioned the issue I'm having and I did not see that on mobile. I'm running all of those on A2017U stock rom running on b29 for additional info. I used stock music player, usb audio player pro (eXtream Software Development) for external dac and Equalizer + (DJiT) which i rarely use. I'll install wakelock detecter and ill report back what I find.
in global v11.0.4.0 ,This is work.if you are in higher version then it will not work.if you are in v11.0.4.0 and install viper successfully then you update your system via ota or recovery.vyper will work great.
Yes you can hear right. You can install it in your redmi 9. But you have to root your device. Without root it will not work. Installation is separate in two parts....
Part 1:
1.First of all, make sure that Your Magisk is updated to the latest version.
Now, Install the Viper4Android FX app on your phone.
Open the App but, Don’t install drivers in the app.
Minimize the app in the background and open the Magisk Manager.
5.Go to Menu>Downloads and search Audio Modification Library.
Install the AML module but, Don’t reboot your device.
Go back to the Viper4FX app and Click on the Install driver button.
Your Device will reboot automatically.
After device reboots, Open Magisk manager and Go to Modules.
Uncheck the Audio Modification library (don’t remove).
Open the Viper4FX app again and click Ok to install the driver automatically.
Reboot your phone and Again Open Viper4FX app and Install the driver again.
Your Device will reboot and Now, Viper will not ask for driver installation..
You have to enable AML again and reboot again...
Then you successfully install it. But there is a problem. Install the driver correctly. But no sound modification will available. Because neon is not enabled. You have to enable it. After many research I found a solution. You have to to install Dolby atoms also...
Part 2:
Install 4 zip file according to serial number...
**First zip file..
After volume key test you have to press down key to choose the second option....
**For second file...
Do not need to press any thing..
**For third file..
Down,down,down,up,down,up....is the volume key sequence...
**For Fourth file..
Do not need to press anything...
Reboot your device..
Magic.....
Now you can modify your audio for a great listening experience...
Thank you.....
sorry but open youtube is broken
AstroKkngTool said:
sorry but open youtube is broken
Click to expand...
Click to collapse
This method worked on v11.0.4.0 but unfortunately does not work with upper version
Yes you hear right. You can install it in your redmi 9 MIUI 12. But you have to root your device. Without root it will not work.
First of all, make sure that Your Magisk is updated to the latest version.
Now, Install the V4fx.apk(from this post) app on your phone.
Open the App but, Don’t install drivers in the app.
Minimize the app in the background and open the Magisk Manager.
Go to Menu>Downloads and search Audio Modification Library.
Install the AML module and permissiver.zip(from this post), Don’t reboot your device.
Go back to the Viper4FX app and Click on the Install driver button.
Your Device will reboot automatically.
After device reboots, Open Magisk manager and Go to Modules.
Uncheck the Audio Modification library (don’t remove).
Open the Viper4FX app again and click Ok to install the driver.your device reboot automatically..
You successfully install it. But there is a problem. Install the driver correctly. But no sound modification will available. Because neon is not enabled. You have to enable it. After many research I found a solution. go to viper4fx and open setting then enable legacy mode...
Do not forget to thanks me if you can successfully install it...good bye
Update. (For Miui only)
when you restart your phone then you see that the YouTube is suddenly stop working. I found a solution for this. You need to install termux emulator and run this command
su
setenforce 1
setenforce 0
Problem is solved...
Remember...
In many gsi their are a audio modified app called 'Audio Fx '...you must disable it to get audio effect from viper4fx
Is this method work on miui 11?
quangkhai6912 said:
Is this method work on miui 11?
Click to expand...
Click to collapse
Try yourself..I think. It should work