yashsingh1/xdaforums huggingface dataset:
[Android Software Development] PedroTakeshi:
Ok, i checked the log and even though i have 700MB free on /system, it says:

(...)

inflating: META-INF/com/google/android/modules/dirac/system/lib/libDiracAPI_SHARED.so

unzip: write: No space left on device

unzip: inflate error 2

This session is now complete.

Maybe it's because the installer unzips the files to the tmp/cache partition before moving to /system, right? And mine is only 200MB, "adb shell df" shows 100% usage during the install. If anyone want to help me with this, i'm free later today or tomorrow.
[Android Software Development] BerkeKan:
Hello. Could somebody explain which effects can be used on a x86 based phone?
[Android Software Development] dhrjbhtt0:
Thanks a ton, I used ur customize.prop file and Sony effects working now.(though dsee hx setting doesn't seem to affect sound even in lossy files)

Anyways, cud u help me with icesound in non aroma installer. Whenever I try to flash the non aroma zip(3.31), it replies "Icesound module must be installed in order to select Iceconfig".What does this mean? Is there some way to sort this out?

Thanks again..
[Android Software Development] BloodEdge:
device: Xperia V

ROM: CM13 Snapshot

SS 3.31 conflict with Adrian's Kernel Permissive Patch, system cant boot up, stuck at bootanimation

https://github.com/AdrianDC/kernel_permissive_patcher
[Android Software Development] JaylanPHNX:
Have you put true after either Deluxe ICE or Ultra ICE? They should be just above the config options. Check those.

---------- Post added at 06:15 PM ---------- Previous post was at 06:14 PM ----------

That's a ROM thing.
[Android Software Development] Ashtrix:
Well, I was away from ARISE since v2.79-1 by Guitaredhero (I ran this version until now), Now I'm back with v3.31 AROMA and BOOM goes the weasel !! Everything works as it should same as my old profile except that this Dolby Atmos is somewhat different to the older one, older one was too loud this seems to be balanced could be placebo,

One more thing, Whenever I changed the volume the ICEsound would showup in log iirc, now it doesn't..

Just a few doubts, please excuse me..

Is the SElinux premissive script included, didn't get the AROMA option to select ? I remember it was needed for SuperSU users for V4A and etc mods else Magisk module for MagiskSU. Oops, Enforcing is fully supported !

Next up the ICEsound Ultra vs Default - I went with Ultra +PureSh*t, Also QCom sound profile what's this for (used stock) ? Increase compatibility with the various OEM mods (ASUS, Sony, Huawei etc) ?

Finally I made the jump to 2.5.0.5 and It's Beautiful ;)

Thanks a lot guys for this amazing masterpiece, made my OP3+Dunu's sound like Subwoofers just like my ultra modded F2K Dolby'd Windows PC setup, perhaps more :good: :cool:
[Android Software Development] KUSOsan:
Yeah before you check the config and she style: (pure, wide clarity etc) I had to install the main ICE module first similar to the core arise module. Then I had to go back in and install the config and style
[Android Software Development] gibbsnich:
No, it goes: Pop! :)
[Android Software Development] oneszero:
I am using RR Sultanized 6.0.1, the first few times I installed 3.31, either Aroma or Modular, it worked each time. I cleaned flashed ROM this last time and now it is not working. Any ideas?
[Android Software Development] churapa:
Thanks [MENTION=4445176]guitardedhero[/MENTION] , as always, you breaking it up to us in clear words!
[Android Software Development] Lownita:
I could need some advice on what setup should work best for Bluetooth speakers. Maybe someone has made experiences in that field, would be great! I'm not listening over headphones at all.
[Android Software Development] Magz Heaven:
I am using AICP, but then when using the magisk compatibility module, both Dolby and DTS crash repeatedly, I need to set my SELinux to permissive, but then I will break safetynet if that's the case. So I searched for the magisk multiple audio mod module by@ahrion, and used them both side by side with the magisk ARISE module, sadly, my baseband broke, didnt get any signal, and by uninstalling one of em will make things right. Anyone also having this issue?

I just wanna ask if my modules on ARISE will still work. I dont know how to look on this, so here is my audio.effects_confhttp://cloud.tapatalk.com/s/58f94fa13c547/audio_effects.conf

Can someone please take a look at this. Thanks. :)

Here is the screenshot of my magisk module

El Psy Congroo
[Android Software Development] gehess:
Don't know if this will help, but here's something I posted previously:
[Android Software Development] kyzn:
Have you tried 1.3? I'm using that and it works. Although it also had a few issues before it suddenly started working.
[Android Software Development] Fdraco10:
Installed ARISE 3.31 on Nougat 7.1.2 Xenon HD.

And everything work fine! ****!! So ****ing perfect!!

Install Core

Viper 2.5.0

Dirac module

Toolbox

Android_O custom

Remove deep buffer

Ice Sound ultra

Ice Sound Config 2

Too modify a little bit the Mixer_path and add other profiles for ViperArise.
[Android Software Development] atulclassic:
how to check everything's working?
[Android Software Development] mrrocketdog:
through terminal emulator.

su

dumpsys media.audio_flinger > /sdcard/dumpsys.txt

and through matlog.:good:

"err on the side of kindness"
[Android Software Development] Magz Heaven:
Everything that is present on the terminal emulator is working? Is that it?

El Psy Congroo
[Android Software Development] Fdraco10:
Yeah!
[Android Software Development] IagoJevaux:
Sorry if I'm dumb but, where are the download links for aroma 3.31? I just can't find them ://

Any help? :P
[Android Software Development] Roi007leaf:
You'll find out why soon enough
[Android Software Development] jandia7381:
ARISE UP!!!!!! Respects all ARISE family. Salutes..... :good:
[Android Software Development] IagoJevaux:
Oh, I see now HAHAHAHA
[Android Software Development] DEVILOPS 007:
Massive respect to you and the whole arise team. It wasn't 100% us. If you hadn't made this sound system then we wouldn't be here. Call it 50/50?
[Android Software Development] rock'n'rolla85:
Waitning for AROMA version :)
[Android Software Development] Mayank7795:
Can we flash this on top of 3.31 or clean flash recommended??
[Android Software Development] rolarocka:
Installed Magnum version and all works great with USB audio player pro. Atmos and viper process the sound. Problem I have is with Spotify, it kills processing of Atmos and viper after an half second... Anyone can help me on this? Maybe a wrong prop setting or workaround? Ty.

OnePlus One - Tapatalk
[Android Software Development] brockn1985:
Magnum Opus.

Seems like this SoundSystem got the name it deserves, from now on.

There is nothing to say, further, for this, more than excellent​​ combination of knowledge in soundimprovement. I think, there is some dust in my eyes, cause their a little wet...;-(

P.s.: I Said in this post above, that the soundsys reached max improvement for my device. U guys teached me sth better.
[Android Software Development] ala_mo:
XDDD
[Android Software Development] kyzn:
DTS FC seems to have made a return...

https://hastebin.com/arajofukic.sql
[Android Software Development] docnok63:
There won't be one for Magnum Opus. Please read the announcement post again as to why.

As with every major ARISE version change, clean/dirty flash of your ROM is required

If you're using ICEsound, make sure you're using ICEconfig 2. If you're not using ICE, then use the deep buffer remover.
[Android Software Development] DEVILOPS 007:
How do you upload to hastebin?
[Android Software Development] kyzn:
Just paste and save. The URL will change to a unique link.

There is a limited number of lines though. So I usually just find relevant lines and/or attach a txt file of the logcat.
[Android Software Development] rolarocka:
Wow thanks for the fast response, iceconfig 2 and deep buffer remover did the trick, was using iceconfig 3 before .. Have a nice weekend. :D

OnePlus One - Tapatalk
[Android Software Development] hyewiz:
Will there be a brief step-by-step written tutorial, on how to install "

Magnum Opus

", and "

Arise Compatibility Module For Magisk

" for Not so tech savvy people like myself?

I read the "getting_started.prop" but there are so many folders and too many "arise_customize.prop" which one to be edited before flashing, and copy it to "/sdcard/".

Please...

Thank you
[Android Software Development] JaylanPHNX:
Strangely, though the installer finds the customize.prop and begins installing the core system, it then fails with error 1. I'm going to redownload and try again, but if anyone knows why this might be happening, I'd appreciate the help.

Edit: redownload worked. Not sure what that was about, but all's well that ends well. Sorry for cluttering the thread.
[Android Software Development] docnok63:
Video inbound shortly...

You didn't set install.core= to true
[Android Software Development] Mayank7795:
It's actually very simple.

First I would recommend you to go through OP (first post) to know about each module and ARISE mod as a whole.

Then we come to installation:

1) inside the zip -> getting_started

2) 2 folders present to work upon - "our_systems" (contains ARISE team members configurations) and "your_system" (for your own customisation)

3) The file you need to work with is - "arise_customize.prop"

4) Edit the file with a text editor and whichever module you wish to install, just write "true" after the 'module_name'. Be sure to set 'install.core' to true during first time installation of ARISE Sound Mod.

5) Save the changes and make sure to place this edited file under 'sdcard', so it should look like -> sdcard/arise_customise.prop

6) Flash the ARISE Sound Mod Zip.

7) If you're using combo of SuperSU + Magisk, Magisk compatibility module is not needed, else if just using Magisk for Root solution, now flash the compatibility module zip (remember to flash this after flashing the ARISE Mod Zip)

8) Done.

PS - Many combinations possible through the use of 'arise_customise.prop' file so try changing values inside it until you're satisfied and flash the ARISE Sound Mod Zip again.

VERY IMPORTANT - If you're trying to customise previous ARISE installation, then be sure to keep the 'install.core' line to empty (blank) or a false value after first time installation of ARISE Mod.
[Android Software Development] hyewiz:
Wow! Thanks for this great Info, I will try it today and let you know if it was success :) thank one more time.
[Android Software Development] btb55:
Magnum Opus

OMG (I haven't ever wrote that before), Awesome (nor that). This just works for me on OP3T. Installed core, v4a_2.5.0.5, v4a_profiles, ddplus, atmos, ToolBox, dirac, dts-client, ANDROID_O, ICEsound, ICEconfig=2, SHAT Then flashed the Magisk compatibility module 2.3

Amazing work, thank you. One observation, booting takes longer on my encrypted f2fs Magisk rooted phone., and I now have to enter my pin twice in the boot process, once early on, then Android loads and I now need to enter pin again to unlock phone, previously just the once was enough and it booted to unlocked home screen.
[Android Software Development] Mayank7795:
Sure bro.. ✌️

---------- Post added at 01:16 PM ---------- Previous post was at 01:14 PM ----------

Am just glad that the MOD is working for us 3T users again. With 2.94 and 3.31 AROMA versions, my device would become unstable..
[Android Software Development] Roi007leaf:
https://www.youtube.com/watch?v=KTugNE7ML-4

this will be in the OP soon
[Android Software Development] btb55:
Indeed, I should add I'm on OOS 4.1.3 with Boeffla kernal
[Android Software Development] tathagatab:
A custom kernel is usually flashed after SuperSU, else SuperSU will replace it with the stock kernel. Don't know if this is related to your problem.
[Android Software Development] Shadowghoster:
[MENTION=6290416]tathagatab[/MENTION] SuperSU patches the boot-image present when you flash it. So you need to flash it after you flashed the custom kernel otherwise you won't have any root after you boot your phone.
[Android Software Development] kyzn:
That isn't true. I always flash super user last, SuperSU or Magisk, never had any issues - anyway, it's​ fine either way.
[Android Software Development] DEVILOPS 007:
Happy birthday [MENTION=4967345]docnok63[/MENTION]!

---------- Post added at 02:32 PM ---------- Previous post was at 02:31 PM ----------

Quick question, as Dolby Atmos and dolby digital have the same options does that mean we only need one?
[Android Software Development] Magz Heaven:
I used the Magisk Compatibilty module, but DTS and Dolby crash all the time. Is it okay to just use the magisk multiple audio mod module for that? Everything seems working when using that zip. Using both magisk Compatibilty module and the magisk multiple audio mod module break my baseband, got an unknown baseband.

El Psy Congroo

---------- Post added at 09:42 PM ---------- Previous post was at 09:41 PM ----------

I guess so.

El Psy Congroo
[Android Software Development] Iloveweed1864:
Could someone help me to get Dirac to work. I've tried installing with modular and aroma, both have same result it installs but always says dirac has stopped. Constantly. I tried the fixes mentioned by hammer smashed face and same result. Nothing I do allows it to work. Even if I install it alone, same result on all Qualcomm effects.

I checked dumpsys, and its not in the chain of effects.

I use a sprint s5 (smg900p) on resurrection remix 7.1.1 nougat everything else works, just not Dirac.
[Android Software Development] Eyalkn:
I read all the guides on the thread and the guides inside the file and followed all the directions using only SuperSU, Selinux set to permissive and trying couple of moudle installation props from other members here, changing the truef to true in the script and clearing the data of the Dirac apps but I'm still getting non stop Dirac fc after booting up. I'm using stock 7.1.2 pixel XL with custom kernel. Any ideas how to get Dirac to work?
[Android Software Development] Roi007leaf:
dirac seems to be incompatible with samsung devices for some reason
[Android Software Development] secone00:
I would only recommend using one Dolby yes, you're not going to get much benefit from using them both at the same time. It would get quite confusing too, I would think, see what works better for you :good:
[Android Software Development] Magz Heaven:
What will I do to make the MOD works(dolby and DTS crashes) without changing my SELinux to permissive? I already flashed the 2.3 magisk compatibilty module, but still the same. It crashes.

El Psy Congroo
[Android Software Development] docnok63:
Thank you so much!!!! They have the same options, but different technologies. Dolby Atmos is all about making a theater surround setting while Digital Plus is "sound compression" that focuses on vocal/music. In fact, many Dolby Atmos videos use Digital Plus technology at the same time. In tune with its vocal focus, Digital Plus is the only one that allow you turn turn on Surround Virtualizer over Bluetooth.

You can certainly install both and although it's not recommended to use both at the same time, some still do. As always, do what your ears tell ya to do!

http://www.vizzva.com/2015/07/what-is-dolby-atmos-dolby-digital-dts.html
[Android Software Development] Iloveweed1864:
I was starting to come to the same conclusion, thank you.

Is there a section that explains the qualcom effects and arkamys
[Android Software Development] DEVILOPS 007:
Okay thanks a lot. I'll definitely have a look. Have a good day:)
[Android Software Development] Hecke92:
Icesound Module must be installed in order to select iceconfig!

But these are the extracts of the arise_customize.prop:

## Qualcomm™ Audio Effects Configuration START ##

# Qualcomm™ devices have the ability to select from four audio effects configurations using Asus, Huawei, Sony, or Stock /soundfx libraries.

# As a reminder, any preferred or custom audio effects configuration can always be automatically installed during the Core System module installation by placing it directly in /sdcard named arise_effects.conf to result with /sdcard/arise_effects.conf.

ASUS
HUAWEI
SONY
STOCK

Example: install.qc.ef**cts=ASUS

install.qc.effects=STOCK

## Qualcomm™ Audio Effects Configuration END ##

#

## ICEsound™ START ##

# Two ICEsound™ ICEpower™ audio systems from the top two device firmwares of Asus™:

Asus™ Zenfone 3 Deluxe

Asus™ Zenfone 3 Ultra

# Add a value of "true" to install one (1) of the two ICEsound™ modules below.

install.deluxe.ICEsound=

(750KB)

install.ultra.ICEsound=true

(5.6MB)

# Add a value of "0", "1", "2", "3", "4", "5", or "6" for the desired ICEsound™ configuration below. A value of "0" will delete /system/etc/icesoundconfig.def. Example:

use.ICEco**ig=0

use.ICEconfig=4

# The following ICEsound™ presets are available below. A value of "None" will remove an existing preset to use no ICEsound™ preset. Enter a value of the preset name exactly as shown below. Example:

use.ICEsound.pr**et=01

BATHSALTS =01
DEEPBASS =02
HOLYSH*T =03
KRAZY =04
MOVIE =05
MUSIC2 =06
OUTDOORS =07
PURE =08
PURESH*T =09
WIDECLARITY =10
Default =11
None =NO

use.ICEsound.preset=03

## ICEsound™ END ##

So it should work, shouldn't it?
[Android Software Development] hokiealumnus:
Bug report:

Device - Pixel XL

ROM - crDroid 3.0 (LOS based)

Root - Magisk

Arise Magnum Opus (love that!) + Magisk compatibility plugin

I installed using [MENTION=4445176]guitardedhero[/MENTION] 's arise .prop file as soon as it finished booting, Dirac and DTS started going ape and crashing every few milliseconds.

This was easily remedied by editing the .prop file (well, a little complicated with the apps continually crashing ;) ) to uninstall both of them, re-flashed and everything is great.

I didn't grab logs, and was in a minor panic (OMG make the crashes stop!) frame of mind. If you need logs and this isn't a known issue or something I'm doing wrong, I'm happy to reproduce the process and grab logs for you.

Finally, thank you for this. My main gripe about the Pixel has been not having an easy to use Viper installation with enforcing. You have made me one heck of a happy camper. The sound I get even without Dirac and DTS is a whole lot better. Thank you ARISE team!!!!
[Android Software Development] DEVILOPS 007:
Try mine to see if this works. You could try it as a test to see if it is your device or how you set it up. Make sure it is placed in internal storage (storage/emulated/0). Don't change anything, just paste it then flash arise and see if it works, then you can always dirty flash and try your personal setup.
[Android Software Development] guitardedhero:
It's appearing that the Magisk module might be what is keeping The DTS Client Service and Dirac from being satisfied in their environment. Both modules require a Permissive Mode SELinux environment without our current /system/etc/init.d/arisesoundserver which eliminates that requirement, so ensure that arisesoundserver exists with 0755 permissions if on Lollipop and above as well as ensuring SELinux is set to Enforcing Mode if on Lollipop and above. One of these two aspects, likely SELinux Mode, is creating this issue, I believe. DTS Client Service does not rely on sound effects libraries, so this leads me to believe a Permissive SELinux Mode is the cause as this would affect both whereas unmet library dependency would only affect the Dirac module of those two. It seems that arisesoundserver (the source for Enforcing Mode support) and Permissive Mode are not able to coexist and sustain a full and harmonious experience. :good:
[Android Software Development] DEVILOPS 007:
Cool, is there supposed to be an individual app in the app drawer for dts and dirac? I feel like this got answered before but I don't see it anywhere. Thanks:)
[Android Software Development] guitardedhero:
A less than perfect ICEsound result is guaranteed with Opus as Opus uses parameters found in the included and latest arise_customize.prop. The Ultra ICEsound module is no longer included or supported and the arise_customize.prop content that you provided will only work with a Modular installation supporting the recently supported Ultra ICEsound module. :good:

---------- Post added at 09:21 AM ---------- Previous post was at 09:16 AM ----------

No, there is not. Both apk's behave as they would in their native firmware environment. The DTS Client Service operates as a background service and Dirac is an apk that is launchable through the equalization setting/option of many media players and possibly launches from the Settings apk in its native environment. :good:
[Android Software Development] shindiggity:
Error while trying to flash latest, running Pixel RR.
[Android Software Development] oakley470:
So just for understanding does this mean hold off for a magisk compatibility zip update?
[Android Software Development] JohnHorus:
I tried deleting the permissive script installed by 2.94, but my device keeps booting in permissive even if I instead modify the script to setenforce 1 instead of 0. Could it be my rom/kernel doing it? Phoenix AEX/Render R3 for OP3 if anyone knows off-hand.
[Android Software Development] secone00:
Gonna need some actual info here, what kind of error? Have a log? You edited arise_customize.prop from the zip and placed in its appropriate place? (Either /sdcard or /sdcard/0, the path your download/documents/music folders are in)
[Android Software Development] shindiggity:
I did copy paste arise.customize.prop to SD card, not sure how to edit it though.
[Android Software Development] Mayank7795:
You can withdraw from using Magisk and rely solely on SuperSU for ARISE to work properly as currently it is most compatible with SuperSU.

But if you need to pass SafetyNet, then considering your situation you'll need to let go of DTS and Dolby.
[Android Software Development] Roi007leaf:
A lot of information dude..

---------- Post added at 17:47 ---------- Previous post was at 17:45 ----------

https://www.youtube.com/watch?v=KTugNE7ML-4
[Android Software Development] Magz Heaven:
Well, I did use the magisk multiple audio mods module for that, and it seems working. I will try to experiment later

El Psy Congroo
[Android Software Development] smohanv:
I am totally gobsmacked with the new version (Magnum Opus).. Sound is so clearer and has become more enjoyable. I was using 3.31 for a while. I dirty flashed my ROM and flashed Magnum... Well done team... music is taking it's new heights with this mod.

---------- Post added at 03:57 PM ---------- Previous post was at 03:54 PM ----------

As suggested by [MENTION=4877463]Mayank7795[/MENTION] use DTS client. I am using Magisk root as I need safetynet for Android Pay. DTS client works good.
[Android Software Development] shindiggity:
Yeah sorry about that, been using aroma forever. I'll check out the youtube thanks ?
[Android Software Development] guitardedhero:
Yes. Admittedly, I am not well versed in the Magisk side of installation and support but am aware of consistent reports of full success without it. My best advice for many different aspects of the sound system is to not do anything to the installed system unless already found to be necessary. So, test for full functionality in a Magisk environment before adding the Magisk module to fix whatever was found to be subpar. :good:
[Android Software Development] kyzn:
Lucky. Mine crashes on boot.
[Android Software Development] tathagatab:
On my OnePlus 3, I always flash SuperSU first, and then the ElementalX kernel. Works every time, root and all. The couple of times I did the reverse, ElementalX was replaced with stock.

My tuppence. You do whatever works for you.
[Android Software Development] _velocity_:
Just stopped by to search through this beast of a thread for a possible solution to 'Dirac Control Service has stopped' - only to find that there is a new release D=

Perusing the arise_customize.prop file of Magnum Opus - it appears that Ice Sound no longer has the option to choose between deluxe and ultra? Based on the file size mentioned, 'Ice Sound' is now only available as the deluxe version?

Will this conflict with a previously installed ultra module?