ARISE Sound Systems™ - Auditory Research in Sound Enhancement

[WILMANS2M]

I had the same problem, the latest versions of Arise were heavily dependent on Magisk, Google search Arise version 05062017, tried to upload it for u but got an error, that's the one you use and is heavily dependent on Supersu.

Ok thanks. Will try using Swansong or deuteronomy.

Envoyé de mon SM-T800 en utilisant Tapatalk

 

[debsankar]

i am new here...i have xiaomi mi a1...i want arise with dirac...how to flash it properly...(rooted but permissive).and will it be working on mi a1..please suggest anyone who tried it on mi a1

 

[WILMANS2M]

I had the same problem, the latest versions of Arise were heavily dependent on Magisk, Google search Arise version 05062017, tried to upload it for u but got an error, that's the one you use and is heavily dependent on Supersu.

I tried. Unfortunately, i am still stuck at bootlogo once flashed. Dunno why.

Envoyé de mon LG-H850 en utilisant Tapatalk

 

[Pshemo__]

Guys what about the old Dolby Digital+ ? Is it possible to install it on the xXx's OxygenOS 8.1? I tried the Arise installer but then I don't see Dolby app and it's not a storage problem

Sent from my OnePlus 5 using XDA Labs

---------- Post added at 07:11 PM ---------- Previous post was at 06:24 PM ----------

BTW Guys if you haven't done it already I recommend you to get and try the SRS 2.2 Convolver in ViperFX. It's a great thing

Sent from my OnePlus 5 using XDA Labs

 

[slimcyril]

I tried. Unfortunately, i am still stuck at bootlogo once flashed. Dunno why.

Envoyé de mon LG-H850 en utilisant Tapatalk

What version u tried?
Old Arise or Deuteronomy or swansong?

 

[WILMANS2M]

What version u tried?
Old Arise or Deuteronomy or swansong?

The one you adviced me.

Envoyé de mon LG-H850 en utilisant Tapatalk

 

[PePeMoke]

I almost answered, but then saw you have the Charge 3 not the Flip 3 that I have. Sorry.

Would you share your profile for the flip 3 with me please so I can test if it works out with my charge 3?
Would be great!

 

[Treasarion]

Hey everyone,

i have a question about the installation procedure with ''ARISE+Deuteronomy+2.94+Modular+AROMA+Installer'' from AFH. I installed Viper since a long time on my Samsung devices. So my Note 8 (Sm-n900f) get the same. But since Oreo, i cant mange it to work. Everytime i install it, it asks me for driver installation after reboot. If i reboot after installation progress, i get the same message again and again. No matter how often i try it. And the other thing is, taht since oreo, the font in the viper app is pink colored. Strange thing btw, dont see that before.

The installation way is the same since i started to use Viper4Arise.

Format System > Reboot TWRP & grant permissions > install Rom( [ROM][N950F/DS/N][ALEXNDR] * U3CRD7 * DevBase v5.6 * Encryption support [Apr-19]) > install TWRP Data mount fix for Supersu/Magisk how i prefer> install Viper > Reboot System > Rom Setup etc.

If this steps dont work (in some cases in the past, there was problems with this way..however)

Installation Method 2:

Format System > Reboot TWRP & grant Permissions etc how above. > Install my Rom + data mount fix> Reboot system> setup rom > Reboot twrp > install arise with the options in aroma for se linux and sd card permissions. > clean cache/dalvik > reboot.


This was my steps. But it seems like, since Oreo..no of this 2 steps work for me anymore. I installed so many diffrent Viper Builds with the same result of not working. And i also tryed it with Magisk. Yes with the Magisk plugin Viper seems to start and the driver message dont show up. But however if i put effects on.. the sound is very..let me say..silence and loud..then one time very crapy and unnatural. I think something gos wrong with this.

Maybe someone have an idea or whatever for me, what i can do to bring it to work. In the best case, with Supersu, cause this is my favourite root soulution.

 

[marcdw]

@Treasarion, I use that Deuteronomy package on most of my ROMs (Nougat) but on Oreo I get similar behavior as you.
In the case of that package the Viper app kept crashing.
Later when I redid the ROM from scratch I didn't use the package but just installed Viper 2.5.0.5 standalone.
Same same. It says it successfully installed the drivers but after reboot it wants to install them again and again.
At the moment I haven't researched why that is.
I've got Dolby Atmos working perfectly and hoped I could get Viper up and running.

SuperSU and busybox installed.


ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HELLSGATE Kernel, Multiboot, Tapatalk 4.9.5

 

[Treasarion]

@Treasarion, I use that Deuteronomy package on most of my ROMs (Nougat) but on Oreo I get similar behavior as you.
In the case of that package the Viper app kept crashing.
Later when I redid the ROM from scratch I didn't use the package but just installed Viper 2.5.0.5 standalone.
Same same. It says it successfully installed the drivers but after reboot it wants to install them again and again.
At the moment I haven't researched why that is.
I've got Dolby Atmos working perfectly and hoped I could get Viper up and running.

SuperSU and busybox installed.


ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HELLSGATE Kernel, Multiboot, Tapatalk 4.9.5

Yep that sounds like the exact same problem as on my phone. I know sammy do everything to blame us root userers, but that this do also not work on your Axon sounds strange to me too.

I also tried it to install the 2.5.05 als standalone apk, with the same result as you. I think this must be a oreo related problem somehow. I mean my rom is a DevBase, so no big Mods or other beta experiment builds from other custom roms where known to be buggy with other apps in cowork or let me say coexistence. And i think my installation method is not wrong, same as your methods you try and explained. So maybe in future there is an Fix maybe for that.

Anyway i think a time that the ''new'' data mount fix for oreo roms can maybe be the problem causing with viper. But i had feedback from the Note 8 forums that this fix cant be the reason to not work for viper. So i think this is solved and when i read your steps, you dont need that fix for oreo. So now im sure this cant be the big problem at all.

Oh and i forget in my op posting, that i have installed bussybox too.

So i hope some can figure something out, maybe a small fix or similar in future.

Anayway thank you for your answer @marcdw. Im hoping you get this fixed too on your device soon...

 

[therebel88]

Anyone having an issue where Viper stops processing if you change tracks? You have to go into the Viper app, click close, and then reopen and it'll start processing again.

 

[JaylanPHNX]

Anyone having an issue where Viper stops processing if you change tracks? You have to go into the Viper app, click close, and then reopen and it'll start processing again.

I had this problem a long time ago and if I remember right it was ICE sound causing it. I stopped using any ICE config and it went away.

 

[therebel88]

I had this problem a long time ago and if I remember right it was ICE sound causing it. I stopped using any ICE config and it went away.

Thanks for the suggestion. But I'm not running ICE. Its just weird I've never had any issues getting Viper to work in my android history. This is a first.

 

[marcdw]

@Treasarion, the Deuteronomy ARISE package (and Viper4Android) from the post below is working for me.
However, it has the annoyance of stopping processing with each track change of the music player.
I've seen that mentioned before somewhere but can't remember at the moment. I have no AudioFX/MusicFX installed so that's ruled out.
I do have Dolby Atmos(*) installed but as far as I know the two are supposed to coexist well.
Phone battery was almost drained so I couldn't​ investigate further.

(*) Flashing ARISE killed my existing Dolby. The apps would FC. Reflashing it (UNITY package) twice (once to uninstall, again to reinstall) fixed that up.

http://forum.xda-developers.com/showthread.php?p=76309119


LG G3 D851, CyanogenMod CM12.1 ROM, Fechda R7 Kernel, MultiROM, Tapatalk 4.9.5

 

[Treasarion]

@Treasarion, the Deuteronomy ARISE package (and Viper4Android) from the post below is working for me.
However, it has the annoyance of stopping processing with each track change of the music player.
I've seen that mentioned before somewhere but can't remember at the moment. I have no AudioFX/MusicFX installed so that's ruled out.
I do have Dolby Atmos(*) installed but as far as I know the two are supposed to coexist well.
Phone battery was almost drained so I couldn't​ investigate further.

(*) Flashing ARISE killed my existing Dolby. The apps would FC. Reflashing it (UNITY package) twice (once to uninstall, again to reinstall) fixed that up.

http://forum.xda-developers.com/showthread.php?p=76309119


LG G3 D851, CyanogenMod CM12.1 ROM, Fechda R7 Kernel, MultiROM, Tapatalk 4.9.5

Thank you very very much for that info ! I will try it as soon as possible. I dont have AudioFX/MusicFX too. Just pure Arise Viper. Before in combination with Atmos, but the longer i hear, i think atmos kills some background sounds in some music, but thats a personal experience and a thing of what music you hear. But i thinked about Atmos since Viper dont work, means that i install only Atmos and hopefully in future back on arise. But before i will test that Build in the Thread you suggested. But i can confirm anyway that atmos & Viper works great together in coexistence since.. since a long time for sure

About the Accu drain, maybe a stupid question to you, but do you have installed 2.34 with super high quality driver ? That can (not must) cause draining. Never had that experience for me in personal, but i heard from some other guys some things about that. So maybe you can test the 2.5.0 if you want, or dont have back in thepast.

''Flashing ARISE killed my existing Dolby. The apps would FC. Reflashing it..'' Yep, had the exact same problem as you in the past. Can fix it by reinstall viper a second time after the dolby.

 

[marcdw]

About the Accu drain, maybe a stupid question to you, but do you have installed 2.34 with super high quality driver ? That can (not must) cause draining. Never had that experience for me in personal, but i heard from some other guys some things about that. So maybe you can test the 2.5.0 if you want, or dont have back in thepast.

Oh nah, I wasn't getting any drain. I meant my battery was running out normally.

When installing Viper I actually don't remember getting the quality choices. Just a prompt to install drivers and that's it. In the past though, I always picked High.

But anyway, the same user who linked that Deuteronomy build told me try Vioer4Android FX 2.6.0.4. Got it and tested. It works much better.

Wiped out and restored the ROM. Installed the apk. It told me something about a fingerprint id problem. It also prompted for root (the others did not).
Rebooted phone. Had a temporary SuperSU hiccup where it wanted to update the binary. Failed at first but luckily I keep the apk on hand. Reinstalled it and it successfully updated the binary.
After reboot I ran Viper again. Driver installation has only one prompt with two choices, 2.5.0.4 (recommended) or 2.3.something (sorry, forgot).
Reboot once again.

Using Retro Music player on AEX, Viper was processing. Skipped from track to track with processing still good throughout. Stopping playback for a bit and then resuming, still good.
Stopped and exited player. Restart and play, processing did not resume. Had to close and restart Viper.

Short test but still much better than previous attempts.

https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx

ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HELLSGATE Kernel, Multiboot, Tapatalk 4.9.3

 

[Treasarion]

Oh nah, I wasn't getting any drain. I meant my battery was running out normally.

When installing Viper I actually don't remember getting the quality choices. Just a prompt to install drivers and that's it. In the past though, I always picked High.

But anyway, the same user who linked that Deuteronomy build told me try Vioer4Android FX 2.6.0.4. Got it and tested. It works much better.

Wiped out and restored the ROM. Installed the apk. It told me something about a fingerprint id problem. It also prompted for root (the others did not).
Rebooted phone. Had a temporary SuperSU hiccup where it wanted to update the binary. Failed at first but luckily I keep the apk on hand. Reinstalled it and it successfully updated the binary.
After reboot I ran Viper again. Driver installation has only one prompt with two choices, 2.5.0.4 (recommended) or 2.3.something (sorry, forgot).
Reboot once again.

Using Retro Music player on AEX, Viper was processing. Skipped from track to track with processing still good throughout. Stopping playback for a bit and then resuming, still good.
Stopped and exited player. Restart and play, processing did not resume. Had to close and restart Viper.

Short test but still much better than previous attempts.

https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx

ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HELLSGATE Kernel, Multiboot, Tapatalk 4.9.3

Oh, then i must understand you a bit wrong with that battery Lol. My English is not the best i guess, i try it to write in a half perfect way that smeone can understand me, but the truth is, that i must translate every second word So im sorry for that, i give my best.

I heard from 2.6 Viper and im nearly sure, that this is exact the magisk version. Or the Buildlevel is similar to the Mgaisk Version. However i dont try that bevore , only with magisk i had a version that comes on 2.6 too. Then i will see how that works for me..again im very thankfull to you for your help. You cant except how happy i would be, when it would work again


And i think the best thing is anyway, to start from scratch with my Rom. I had to do too much experiments with diffrent Viper Builds or ''Sound Packs/Suites'' with viper inside i tested back in the past few days. And today is not a working Day in Germany, so i think i will do this all today evening. Its a good day for that kind of things, hoepfully all will work fine.. i will write if i have luck or not with it. :fingers-crossed:

 

[Treasarion]

@marcdw All working fine as before.. thank you !!! :fingers-crossed:

 

[topbasework]

Hai all.what is best combination sound mod for Samsung note 5 nougat ?

Sent from my SM-G955F using Tapatalk

 

[slimcyril]

Hai all.what is best combination sound mod for Samsung note 5 nougat ?

I installed core and all the modules excluded icesound and audio sounds incredibly