Related
Hello all,
Has anyone gotten Viper4Android running on a Moto X 2014 Pure Edition? I have upgraded my Pure Edition to Lollipop 5.1 and still having issues getting it to work right.
Thanks,
Steve
it never worked reliably for me on moto x original in kk or on 2014 moto x in kk. Always caused issues between maps and pandora
To use Viper4android,(This is for CM Based ROMS)
1.install the lolliviper, the zip can be found in the v4a forum
2.Install SElinux kernal changer and change the Kernal to permissive
3.Make sure you have the latest busybox installed
4.Enable developer options and uncheck Use Nuplayer
5.Verify if it works with google play music
6.To work with poweramp, disable DVC and Audio fx
7.But with this method convolver will not work
Below instructions are for Stock
Also u can try the other method(Convolver will work, but dont flash lolliviper with this method)
1. Install v4a as a user Apk
2.Install SElinux kernal changer and change the Kernal to permissive
3.Make sure you have the latest busybox installed
4.Enable developer options and uncheck Use NuplayerFlash the two Zips
Flash Sound Lib Fix (Viper4A-_Soundfix-LibFiles_-CWM.zip)
Flash Build.prop Tweaks addition (Viper4A-_Build.Prop-Tweaks_-CWM.zip)
The the above two zips can be found the below mentioned Path
http://forum.xda-developers.com/moto...-root-t2997005
blademaster1990 said:
To use Viper4android,(This is for CM Based ROMS)
1.install the lolliviper, the zip can be found in the v4a forum
2.Install SElinux kernal changer and change the Kernal to permissive
3.Make sure you have the latest busybox installed
4.Enable developer options and uncheck Use Nuplayer
5.Verify if it works with google play music
6.To work with poweramp, disable DVC and Audio fx
7.But with this method convolver will not work
Below instructions are for Stock
Also u can try the other method(Convolver will work, but dont flash lolliviper with this method)
1. Install v4a as a user Apk
2.Install SElinux kernal changer and change the Kernal to permissive
3.Make sure you have the latest busybox installed
4.Enable developer options and uncheck Use NuplayerFlash the two Zips
Flash Sound Lib Fix (Viper4A-_Soundfix-LibFiles_-CWM.zip)
Flash Build.prop Tweaks addition (Viper4A-_Build.Prop-Tweaks_-CWM.zip)
The the above two zips can be found the below mentioned Path
http://forum.xda-developers.com/moto...-root-t2997005
Click to expand...
Click to collapse
Link gives a 404 error
adm1jtg said:
Link gives a 404 error
Click to expand...
Click to collapse
Try this link
http://forum.xda-developers.com/moto-g-2014/themes-apps/viper4android-lollipop-root-t2997005
blademaster1990 said:
Try this link
http://forum.xda-developers.com/moto-g-2014/themes-apps/viper4android-lollipop-root-t2997005
Click to expand...
Click to collapse
Finally getting around to this.... got it all loaded but couldn't for the life of me hear even a minor difference.
adm1jtg said:
Finally getting around to this.... got it all loaded but couldn't for the life of me hear even a minor difference.
Click to expand...
Click to collapse
Did you check the driver status? I don't think the driver was able to install on your phone. It's working fine on my stock rooted Moto X XT1092 running 5.1. Note that I installed the FX_A4.x.apk version. The FX_A2.3.apk version does not work.
Yes driver status was active, changing convolver files had no effect at all and cganging other settings alkso had no effect. I also loaded the build.prop changes and the additional sound file and stil no go.
I am not on cm12.1
P.S. also didn't work WITHOUT applying the build.prop and additional sound files. And yes installed the same apk as you did.
Ota with these apps installed is impossible ! Full flash stock rom before ota
This is at your own risk !
I am not responsible for dead sdcards, thermonuclear war or you getting fired because the alarm app failed
If you point the finger at me for messing up your device, I will laugh at you
I am not responsible if your phone becomes a hipster and claims to have been modified before it was cool
I am not responsible for what you do with your computer, be it a laptop or a desktop/whatever and your phone as well
What are c-apps ?
https://cyngn.com/c-apps
Click the link to learn more
Requirements :-
C-apps package
Es file explorer OR aroma file manager
1) Install es file explorer (or boot to twrp, mount system in options, disable only mount system read-only and flash aroma file manager)
2) (Es file explorer users only) enable root explorer and mount system read-write
3) now rename /system/priv-app/dialer -> /system/priv-app/dialerx
4) similarly, rename /system/app/incallui -> /system/app/incalluix
5) (es file explorer users only) you may experience app crashes. Don't worry about them and reboot to twrp
6) flash c-apps package
7) (aroma file manager users only) mount system read-write in twrp options and disable the mount system read-only checkbox, then flash aroma file manager again and rename /system/app/incalluix -> /system/app/incallui (remove the x) and do the same to /system/priv-app/dialerx -> /system/priv-app/dialer (remove the x, do not change the case of the letters ! )
8) (aroma file manager users only) exit it and reboot to system
9) (es file explorer users only) follow step 7 after booting into android
10) (es file explorer users only) reboot your phone
11) now, disable these apps after booting into android (they do not work)
(I couldn't find the time to upload screenshots, coming soon !)
Edit :- screenshots added, check attachments
Truedialer works (partially, incallui doesn't work, dualsim works) but I prefer stock that is why I disabled it
Only use 1 dialer app or they may conflict !
Working :-
Cm account
Gallery
Email
Calendar
True caller service
Cm anti-theft
Screencast screen recorder
Etc etc
Audiofx is not working but maxxaudio tuner and audiofx are the same thing
Thanks, it works.
1. I couldn't find "disable only mount system read-only" in TWRP. Anyway, I flashed Aroma File Manager,
2. renamed said files, exited Aroma,
3. flashed C-Apps package,
4. again flashed Aroma, went inside /system to rename files, they were replaced by DailerNext and InCallUiNext, exited Aroma,
5. rebooted to system.
6. Found that stock apps have been replaced(Nevermind, I'm not fan of them anyway).
I followed TWRP procedure.
krishna442 said:
Thanks, it works.
1. I couldn't find "disable only mount system read-only" in TWRP. Anyway, I flashed Aroma File Manager,
2. renamed said files, exited Aroma,
3. flashed C-Apps package,
4. again flashed Aroma, went inside /system to rename files, they were replaced by DailerNext and InCallUiNext, exited Aroma,
5. rebooted to system.
6. Found that stock apps have been replaced(Nevermind, I'm not fan of them anyway).
I followed TWRP procedure.
Click to expand...
Click to collapse
If you followed the procedure correctly, that wouldn't have happened
Anyways, I'll upload the 2 stock apps the got replaced and a file that contains permissions that need to be applied to them
[email protected] said:
If you followed the procedure correctly, that wouldn't have happened
Anyways, I'll upload the 2 stock apps the got replaced and a file that contains permissions that need to be applied to them
Click to expand...
Click to collapse
I thought so, I couldn't find "mount system read-only."
@[email protected] check attachment for screenshot
krishna442 said:
I thought so, I couldn't find "mount system read-only."
Click to expand...
Click to collapse
I'll look into this
In the meantime, try reflashing twrp
krishna442 said:
I thought so, I couldn't find "mount system read-only."
Click to expand...
Click to collapse
The option is there, just checked....in the bottom left of the mount section
[email protected] said:
I'll look into this
In the meantime, try reflashing twrp
Click to expand...
Click to collapse
[email protected] said:
The option is there, just checked....in the bottom left of the mount section
Click to expand...
Click to collapse
Thanks, I did, and there's this option .
krishna442 said:
Thanks, I did, and there's this option .
Click to expand...
Click to collapse
Strange....
I'll add this information to the op so that if anyone faces the same issue, they'll know what to do
Thanks
Get audiofx apk from teamsek or any cyanogen build of 5.1.1 install manually thats working
i m using write now with audio tunner
install the apk i have uploaded manually working fine along with audiotunner
sahil chandel said:
Get audiofx apk from teamsek or any cyanogen build of 5.1.1 install manually thats working
i m using write now with audio tunner
Click to expand...
Click to collapse
Send me a detailed guide via pm (what did you exactly use, etc) and I'll add it to the op
And, maxxaudio tuner and audiofx are the exact same thing....no difference...both are from maxxaudio....same dev
sahil chandel said:
Get audiofx apk from teamsek or any cyanogen build of 5.1.1 install manually thats working
i m using write now with audio tunner
install the apk i have uploaded manually working fine along with audiotunner
Click to expand...
Click to collapse
I just tried it out
Didn't work
Stick with audio tuner on op2 its the same thing
[email protected] said:
I just tried it out
Didn't work
Stick with audio tuner on op2 its the same thing
Click to expand...
Click to collapse
its working install manually see screenshots
sahil chandel said:
its working install manually see screenshots
Click to expand...
Click to collapse
it isn't
just tried
and that does not look like official audio tuner
[email protected] said:
it isn't
just tried
and that does not look like official audio tuner
Click to expand...
Click to collapse
bro thats audiofx.apk.....not audio tunner i have both audiotunner & audiofx.apk look 2nd screenshot i used them combinely too during headphones....gives awesome bass combination
sahil chandel said:
bro thats audiofx.apk.....not audio tunner i have both audiotunner & audiofx.apk look 2nd screenshot i used them combinely too during headphones....gives awesome bass combination
Click to expand...
Click to collapse
my bad
it doesn't look like the apk in the c-apps package
[email protected] said:
my bad
it doesn't look like the apk in the c-apps package
Click to expand...
Click to collapse
use the app that i hv uploaded
its from teamsek cm12.1
krishna442 said:
I thought so, I couldn't find "mount system read-only."
@[email protected] check attachment for screenshot
Click to expand...
Click to collapse
Thanks
But that does not look like official twrp
http://twrp.me/devices/oneplustwo.html
[email protected] said:
Thanks
But that does not look like official twrp
http://twrp.me/devices/oneplustwo.html
Click to expand...
Click to collapse
Yep, even I just noticed it. Omg. I'm really getting dumb these days. Thanks a lot.
WELCOME
Dual Boot Patcher
I am proud to present to you, Dual Boot Patcher for j510!
Code:
Disclaimer:
I am not responsible for any bricked devices lost data or national disasters. Use at your own risk
Features:
Run two or more roms on your device at the same time!
Able to patch rom zips, custom kernels, gapps, supersu zips etc
Clean Material UI
Boot UI which allows you to select ROM at boot
App Sharing between Roms
Backup and Restore roms
Note: If the app is saying that this device is not supported and you have j510, edit your build.prop to set ro.build.product and ro.product.device to "j5xnlte". Then reboot. The app should be working. Do this only if you have j510. If you set the values improperly, installing a dual boot zip will hard brick your device.
TUTORIAL:
NOTE:Make a full nandroid backup before proceeding!!
Install your first ROM normally(from TWRP). It is recommended that if you want to multiboot an AROMA ROM, you should install it first(as primary). If you want to make your current rom as primary, skip this step.
Download and install the apk provided in the attachments.
Download the second rom.
Open the Dual Boot Patcher app, in the left swipe-in menu, select ROM section
It will ask you to set the kernel for Primary Rom. press Ok
Then go to "Patch zip file" menu, and click on the red "add" button
Then select "Add flashable zip". It will ask you to select a rom zip. Browse to your downloaded ROM and long-press to select it.
It will then ask you where to install it. You can Either Install it in "Secondary" which will install the Rom in system partition(use this if you have enough space on your system partition( at least 1.1 GB for AOSP roms and 1.8 GB for Touchwiz Roms). If you dont have enough space on your system partition, install it in Data or ext sd slot.(Note that installing in Data will take up space from your internal memory. DO not select the "multi slots"! they are for other devices
Click on OK. it will ask you the location of target file, just click on select to use defaults.
if you have any additional zips(such as gapps or supersu) patch them all using the above method. Select the same setting you used for the ROM!
After you have added all your zips, Click on the tick in the upper right corner and the patching will begin!
After Patching is done, reboot to recovery. DO NOT WIPE ANYTHING. Just install the zips you just patched(they will have "Dual" or "Data slot" written in front of their names.
After installation is complete, click reboot, and it will reboot to your newly installed ROM. Set up the rom normally. After setup is complete, install the DualBootPatcher apk.
Now you can select whichever ROM you want in the app. Just select it and restart!
From now onwards patch every zip with dual boot patcher before installing!
Boot UI
If you want Boot ui, follow these steps:
Go to roms section of the app. Press the 3 dots next to your first rom then scroll down and select update ramdisk. then press ok. It will ask you to reboot. just press reboot later
Repeat the same with other roms
Then go to settings and select install Boot ui.
Download Apk
DualBootUtilities
If anything goes wrong with the DualBoot keep the utilities zip in your sdcard. You can flash it in recovery(AROMA only). It allows you to wipe any rom installed on your device or switch to any rom.
Download Utilities
UPDATES
Update1:
Performance Improvements
Now you can restore backup to primary and secondary locations too(previously gave error)
Update2:
Added j5xnltexx to supported device codenames
Performance improvements
This app is not mine. I added support for dual boot on J5 2016.
This app is licensed under GPL. As per its requirements, here is the source code:
https://github.com/RIPT1DE/DualBootPatcher
Hello. I looked at your GitHub, and you have made no changes to it.
You should do that, as currently the GitHub is a fork with absolutely no changes to the original one.
Boot ui not supported ?
Wizardlysense said:
Boot ui not supported ?
Click to expand...
Click to collapse
This not work either
Moshifan100 said:
Hello. I looked at your GitHub, and you have made no changes to it.
You should do that, as currently the GitHub is a fork with absolutely no changes to the original one.
Click to expand...
Click to collapse
No changes to the master branch as I am keeping it in sync with the original developer's master. The changes are in branch j510fn_support.
Wizardlysense said:
Boot ui not supported ?
Click to expand...
Click to collapse
Bro change ro.build.product and ro.product.device in build. Prop to j5xnlte.
Wizardlysense said:
This not work either
Click to expand...
Click to collapse
Also if the above doesn't work send me the update.log
__riptide__ said:
Also if the above doesn't work send me the update.log
Click to expand...
Click to collapse
Here
Wizardlysense said:
Here
Click to expand...
Click to collapse
Did you give storage and root permission?
__riptide__ said:
Did you give storage and root permission?
Click to expand...
Click to collapse
Yup
Wizardlysense said:
Yup
Click to expand...
Click to collapse
Ok. Then can you send me a copy of your build. Prop?
Guyz, this is perfectly working for me.
Just follow the instructions.
@Wizardlysense I have edited my post with further instructions. Try those. If it's still not working, we will and figure it out.
Work for me after edit build.prop
Boot ui auto booted to which ramdisk update last.no option for selection which one is to boot
Hello everyone !
I edit my build.prop but dont work... Help me if you can and thank you of the app
Thanks !
Incredible! Just incredible! Works fine with a5ux and lineage os!
GlitchWolf said:
Hello everyone !
I edit my build.prop but dont work... Help me if you can and thank you of the app
Thanks !
Click to expand...
Click to collapse
What is the error?
doc_elias said:
Work for me after edit build.prop
Boot ui auto booted to which ramdisk update last.no option for selection which one is to boot
Click to expand...
Click to collapse
The boot ui has a countdown timer. There are two buttons on the boot ui. Clock the left one which is "cancel". It will then give you the option to switch rom
gzdc said:
Incredible! Just incredible! Works fine with a5ux and lineage os!
Click to expand...
Click to collapse
Same here.. Great Work! Amazing!
__riptide__ said:
The boot ui has a countdown timer. There are two buttons on the boot ui. Clock the left one which is "cancel". It will then give you the option to switch rom
Click to expand...
Click to collapse
Everything working fine.
I read the OP of A.R.I.S.E. several times, and honestly, I didn't understand it properly. And plus, I have also seen a lot of Onyx users reporting that the installation freezes in recovery. Can someone please guide me through the entire process? Thanks in advance!
meraj99 said:
I read the OP of A.R.I.S.E. several times, and honestly, I didn't understand it properly. And plus, I have also seen a lot of Onyx users reporting that the installation freezes in recovery. Can someone please guide me through the entire process? Thanks in advance!
Click to expand...
Click to collapse
I hope you are aware of flashing custom recovery and rooting your phone. Once you did that it is easy to install it.
1. Download arise from official thread. (am using magnum opus version) Make sure you download non auroma version.
2. For starters inside zip there will be a folder called our modules. Copy any of the arise_customize.prop file from that and paste it in in internal storage root directory.
3. flash the ARISE zip from recovery and you are good to go.
4. Read arise_customize.prop file for further info of adding and removing modules.
micoeyes said:
I hope you are aware of flashing custom recovery and rooting your phone. Once you did that it is easy to install it.
1. Download arise from official thread. (am using magnum opus version) Make sure you download non auroma version.
2. For starters inside zip there will be a folder called our modules. Copy any of the arise_customize.prop file from that and paste it in in internal storage root directory.
3. flash the ARISE zip from recovery and you are good to go.
4. Read arise_customize.prop file for further info of adding and removing modules.
Click to expand...
Click to collapse
which effect do you prefer?
meraj99 said:
which effect do you prefer?
Click to expand...
Click to collapse
I prefer Dolby Atmos with Dirac. Viper with ground zero preset (with my customization) nothing else. For speaker mode I use Atmos with movie preset no Viper n Dirac.
Hello everyone, I have a problem on which audio enhancement to use? I tried to install Viper4Android_FX_v2505_A7.x_Nougat_IO_test_fix.apk, but it does not install the necessary drivers, my problem is that I use Spotify and the sound is very simple, I would need to strengthen the bass a little bit, I have the B&O headphones.
Thanks
the best audio package by far is A.R.I.S.E.
I use magisk, but it should work with SuperSU too.
You need to have busybox installed to /system/xbin for Viper4Arise to work properly.
When you flash the ARISE package the first time, it will drop a file "arise_customize.conf" into /sdcard
This is what you use to customize which ARISE modules you want to be installed when you flash the ARISE installer the second time.
I have attached the arise_customize.conf file that I use, and know works very well on LG-V20.
For many reasons, though, I recommend looking into switching to magisk over supersu.
After you have busybox installed properly, and after you have Viper4ARISE flashed properly with the customize file used, there is a module in the magisk app repository "universal_deep_buffer_remover".. this is the ONLY thing I have found that correctly removes the deep buffer without breaking the HIFI dac on the V20.
(you can also easily install busybox from the magisk manager app too, although I recommend flashing that module from recovery first. You may need to play with that its triicky. Install from recovery and/or from within the magisk manager app.)
it should go without saying that before you start installing this you will need to remove any other audio mods that you have installed previously, or the best bet being reflash your ROM to get a fresh start.
syndre said:
the best audio package by far is A.R.I.S.E.
I use magisk, but it should work with SuperSU too.
You need to have busybox installed to /system/xbin for Viper4Arise to work properly.
When you flash the ARISE package the first time, it will drop a file "arise_customize.conf" into /sdcard
This is what you use to customize which ARISE modules you want to be installed when you flash the ARISE installer the second time.
I have attached the arise_customize.conf file that I use, and know works very well on LG-V20.
For many reasons, though, I recommend looking into switching to magisk over supersu.
After you have busybox installed properly, and after you have Viper4ARISE flashed properly with the customize file used, there is a module in the magisk app repository "universal_deep_buffer_remover".. this is the ONLY thing I have found that correctly removes the deep buffer without breaking the HIFI dac on the V20.
(you can also easily install busybox from the magisk manager app too, although I recommend flashing that module from recovery first. You may need to play with that its triicky. Install from recovery and/or from within the magisk manager app.)
it should go without saying that before you start installing this you will need to remove any other audio mods that you have installed previously, or the best bet being reflash your ROM to get a fresh start.
Click to expand...
Click to collapse
You forgot to attach the file
Looking forward to it, I've always used Viper and never heard of this one, I'm eager to try it.
UL7RA said:
You forgot to attach the file
Looking forward to it, I've always used Viper and never heard of this one, I'm eager to try it.
Click to expand...
Click to collapse
so sorry, my fault
I did attach the file but I didn't see that it rejected the .prop extension, I edited that first post with it uploaded as a text file, same file is attached here too. Remove the .txt and put it on /sdcard
If you open the file and change the install core to =true, you will only have to flash the arise zip once (instead of letting it place that customize.prop file on SD card the first time around).
syndre said:
so sorry, my fault
I did attach the file but I didn't see that it rejected the .prop extension, I edited that first post with it uploaded as a text file, same file is attached here too. Remove the .txt and put it on /sdcard
If you open the file and change the install core to =true, you will only have to flash the arise zip once (instead of letting it place that customize.prop file on SD card the first time around).
Click to expand...
Click to collapse
Unfortunately, I believe not much of ARISE works on my H990DS, as the first time I flashed using your prop file, I got arkamys audio to continuously force close. Uninstalled it by editing the prop file, reboot. Tried opening Dolby Atmos, force close. I guess I'm left with Viper, which I've had before anyway. I'm on magisk, if that matters, but I saw that the magisk compatibility was set to true.
UL7RA said:
Unfortunately, I believe not much of ARISE works on my H990DS, as the first time I flashed using your prop file, I got arkamys audio to continuously force close. Uninstalled it by editing the prop file, reboot. Tried opening Dolby Atmos, force close. I guess I'm left with Viper, which I've had before anyway. I'm on magisk, if that matters, but I saw that the magisk compatibility was set to true.
Click to expand...
Click to collapse
If you're using SuperSU the only other thing that I could think of would be making sure BusyBox is installed
In the future if something like that is force closing you can either just freeze the application or delete the app folder in system partition using recovery.
If you haven't yet tried flashing your ROM again, letting boot up and sit for a few minutes, then flash busybox and arise again on a fresh ROM installation, that is definitely something to try.
I'm just curious, is there a reason why you prefer SuperSU over magisk?
I use the BusyBox flashable installer made by as from here. He's got lots of other neat things on that thread to!
https://forum.xda-developers.com/showthread.php?t=2239421
Sent from my LG V20 using XDA Labs
syndre said:
If you're using SuperSU the only other thing that I could think of would be making sure BusyBox is installed
In the future if something like that is force closing you can either just freeze the application or delete the app folder in system partition using recovery.
If you haven't yet tried flashing your ROM again, letting boot up and sit for a few minutes, then flash busybox and arise again on a fresh ROM installation, that is definitely something to try.
I'm just curious, is there a reason why you prefer SuperSU over magisk?
I use the BusyBox flashable installer made by as from here. He's got lots of other neat things on that thread to!
https://forum.xda-developers.com/showthread.php?t=2239421
Sent from my LG V20 using XDA Labs
Click to expand...
Click to collapse
No, I'm not using SuperSU, I'm on Magisk (14.0). You might have missed when I said that. BusyBox is installed and running fine, and I managed to fix everything by flashing the ARISE zip, but with a modified prop file.
UL7RA said:
No, I'm not using SuperSU, I'm on Magisk (14.0). You might have missed when I said that. BusyBox is installed and running fine, and I managed to fix everything by flashing the ARISE zip, but with a modified prop file.
Click to expand...
Click to collapse
ahh ok, yeah misunderstood that you got it going
great
Sent from my LG V20 using XDA Labs
Hello, thanks for replying ... I installed my system again with MagiskSU, but when I installed ARISE, I could not understand how to install it ... I downloaded the MAGNUS OPUS package and tried to flash with the TWP, and there was ERROR 1, I put both your "arise_customize.prop" in my sdcard (/sdcard/arise_customize.prop) and what is in the ARISE forum, but without success ...
let's go to the beginning ... first I install MagiskSU, then BusyBox, then I put the file on sdcard? and then try to install? that's what i did
what am I doing wrong?
Thanks for the cooperation
pkrename said:
Hello, thanks for replying ... I installed my system again with MagiskSU, but when I installed ARISE, I could not understand how to install it ... I downloaded the MAGNUS OPUS package and tried to flash with the TWP, and there was ERROR 1, I put both your "arise_customize.prop" in my sdcard (/sdcard/arise_customize.prop) and what is in the ARISE forum, but without success ...
let's go to the beginning ... first I install MagiskSU, then BusyBox, then I put the file on sdcard? and then try to install? that's what i did
what am I doing wrong?
Thanks for the cooperation
Click to expand...
Click to collapse
The order I flash those things is first the ROM (if your ROM has any audio mods included as separate zips in the main rom zip, most modded stock roms do this, remove that. Either delete any viper or dolby zips from the main rom zip, or comment out the libes that install them in the update-script FIRST).
Second I flash busybox, it should say "installng to /system/xbin".
Third I flash Magisk. The current latest version is v14.5 and I can confirm it works n my V20.
After that, I boot into the rom and let it up the stock audio configuration to and confirm that you have sound working initially. After it settles down for a few minutes, I go back into recovery and then flash the arise zip.
The first time you flash ARISE, it checks to see if the customize prop file is present on/ sdcard and if it is it will use those options. If the customize file is not present the only thing it will do is install the core part of ARISE, and it will place that customize.prop file onto /sdcard for you. If that happens you'll get a message saying so, instructing you to edit it to select which modules you want. The customize.prop file I attached is what I use, you don't necessarily have to use those exact settings, you can choose what you want and play around with it and see what works. Trial and error is a way of life doing these mods.
Flashing the same ARISE zip a second time once you edited the prop file to your liking will install what you choose instead of just the core files.
Reboot back into your ROM and open the magisk manager app. You'll notice there is a module there for ARISE compatibility. At this point your equalizer apps should be functioning, but only for local media files. To get the sound to process through the Viper equalizer using streaming music you need to remove the deep audio buffer. Magisk manager allows you to do this very easily by just downloading the universal deep audio remover module from the repository in magisk manager.
While you're at this point, it's a good idea to also download and install the BusyBox module from the magisk manager app too. You can install the magisk BusyBox module on top of what you already flashed in recovery, thats how I do it. If there's any conflicting files the magisk module takes priority. If anything, doing this gives me the peace of mind that BusyBox is for sure installed correctly.
After installing the BusyBox and deep buffer remover modules from the magisk manager app, reboot and that should be it! The only thing you need to do now to take your already amazing DAC to the next level is adjust the equalizer settings to what you like. This is a never ending quest to make whatever youre listening to sound perfect. Frustrating but fun at the same time.
Of course there are a ton of things that could go wrong, each case seems to be different, so there's no way to let you know what to do before a problem shows up.
Try that and let me know how it goes. Good Luck!
syndre said:
The order I flash those things is first the ROM (if your ROM has any audio mods included as separate zips in the main rom zip, most modded stock roms do this, remove that. Either delete any viper or dolby zips from the main rom zip, or comment out the libes that install them in the update-script FIRST).
Second I flash busybox, it should say "installng to /system/xbin".
Third I flash Magisk. The current latest version is v14.5 and I can confirm it works n my V20.
After that, I boot into the rom and let it up the stock audio configuration to and confirm that you have sound working initially. After it settles down for a few minutes, I go back into recovery and then flash the arise zip.
The first time you flash ARISE, it checks to see if the customize prop file is present on/ sdcard and if it is it will use those options. If the customize file is not present the only thing it will do is install the core part of ARISE, and it will place that customize.prop file onto /sdcard for you. If that happens you'll get a message saying so, instructing you to edit it to select which modules you want. The customize.prop file I attached is what I use, you don't necessarily have to use those exact settings, you can choose what you want and play around with it and see what works. Trial and error is a way of life doing these mods.
Flashing the same ARISE zip a second time once you edited the prop file to your liking will install what you choose instead of just the core files.
Reboot back into your ROM and open the magisk manager app. You'll notice there is a module there for ARISE compatibility. At this point your equalizer apps should be functioning, but only for local media files. To get the sound to process through the Viper equalizer using streaming music you need to remove the deep audio buffer. Magisk manager allows you to do this very easily by just downloading the universal deep audio remover module from the repository in magisk manager.
While you're at this point, it's a good idea to also download and install the BusyBox module from the magisk manager app too. You can install the magisk BusyBox module on top of what you already flashed in recovery, thats how I do it. If there's any conflicting files the magisk module takes priority. If anything, doing this gives me the peace of mind that BusyBox is for sure installed correctly.
After installing the BusyBox and deep buffer remover modules from the magisk manager app, reboot and that should be it! The only thing you need to do now to take your already amazing DAC to the next level is adjust the equalizer settings to what you like. This is a never ending quest to make whatever youre listening to sound perfect. Frustrating but fun at the same time.
Of course there are a ton of things that could go wrong, each case seems to be different, so there's no way to let you know what to do before a problem shows up.
Try that and let me know how it goes. Good Luck!
Click to expand...
Click to collapse
Great Tutorial... but... in my phone... (H990DS) with custom root by DirtySanta, the Magisk v14.5 make this device no boot... does it work with version 14.0?
I have a LS997 and also see dirty santa. I run Schwifty's kernel, if that is of any interest to you.
Yes, v14 will be fine to use.
This is for anyone doing audio mods, check out sauron ainur audio, it's a Russian team that figured out a new/better way to mod devices,, (any variant) I've tried bout everything, and it is way better than arise, guitarded hero even chimed in on the forum and credited them as the real deal and not a poser basically, the bass is much tighter and puncher and tunable, must have magisk and u can have other mods along with it e.g.--v4a, James dsp, Arkamys, Dirac, etc. Read the thread!!! And it's easier to install. It will/is change android modding imo.
I was able to do it, but I only managed to release it on my device after upgrading to version 14.5... in version 14 it did not run... I did all the steps as it happened in my tutorial and now it is running the perfect V4A !! Thank you syndre was a great help!
I used to think arise was best, all magisk users should try sauron ainur audio mod, the only one I got to activate is the mk II beta 8. Easy to install if you follow directions and can use viper and other mods with it, they found a new way to do audio mods that's changing the game for audio it just ain't well known yet, read the thread, guitarded hero chimes in and validates them as the real deal and I can say it is awesome, tighter bass, clearer w/less congestion from non working/compatible ports. Message me if you need help or have general questions. Can be tricky to learn, (me anyway since I just started using magisk). Russian team I believe, try it out, good luck.
---------- Post added at 01:40 AM ---------- Previous post was at 01:34 AM ----------
Beta 8 was only one i could get to activate quad dac, wanted to correct that, but the versions without dac activated still sound better than other mods with dac working, it's that good. Imo the bass is way more tunable and precise, and punchier which is important to me.