[Android Software Development] guitardedhero:
Indeed. :good:

Just curious, is the ICEsound module currently installed?

No prerequisites, obviously anything other than Sony devices are the target. Well, maybe not obvious but Sony devices have nothing to gain from the module except possibilities for issues somewhere.

I may be incorrect as I have no other device than my Nexus 6 to test with, a Qualcomm device. I was under the assumption from my hardcore moments of Sony firmware examination in the past that the libraries and effects you do not see in your audio effects configuration are only compatible with Qualcomm devices. I would love to be proven to have a false assumption, so someone please let me know that is able to adequately test these entries along with /system/lib/soundfx/sony libraries.

And just to clarify, the Sony module does not add or remove audio effects configuration entries. That is a Core module component when selecting the most logical audio effects configuration for your device. Again, we are proven wrong many times through various phases of development throughout this project, which is something we embrace rather than shun. We learn more from these scenarios than from scenarios where nothing occurs other than best educated judgements. :good:

Are you using the arise_customize.prop included in the installation archive you flash in TWRP? Have you enabled all requested permissions yet to be granted by the system applications installed? Also, deleting the /data/data folders of Force Closing applications and then rebooting often times can yield positive results. :good:

Possibly. ;)

You know we include you guys in every aspect of this project.

I cannot say much at all about #StayTuned, but our main desire with the launch of Magnum Opus was to kick off the Family Feud project in order to get you guys into the many, many possibilities of the sound system that we all will never have a chance to experience. I mean, it might be possible to test every single combination, but there's certainly not adequate time to properly test all.

The Modular installation using arise_customize.prop makes it incredibly easy to test numerous different installations that others have provided without any thought necessary to prepare an arise_customize.prop. In fact, you may have prepared a dozen different ones and feel that you are getting the most out of the available options, only to find that one another user provided completely changes your perspective on the personality of Magnum Opus.

Round 2 of Family Feud begins May 20, which will be most effective without the distraction of an AROMA installation that is unable to participate. Remember, Round 2 will be completely under the control of this entire community, except the ARISE team. We will have no hand in its course, it is all yours to make decisions along the way as they are needed to be addressed: rules, duration, accolades for placement when over, extension or terminate, etc...

Once at least Round 2 has concluded based upon the parameters you guys decide to apply to it, and the decision to terminate Family Feud, that would be a time to revisit AROMA. Take that as a gamble on my behalf and not a tease to make you guys work for it. I have long held the opinion that AROMA has no benefit over the Modular method, is slow and is archaic compared to the rest of the entire sound system. Modular is fast, efficient, and is easily repeated without having to remember selections made in AROMA. My gamble is that these two rounds of Family Feud will help form similar opinions of AROMA for you guys when you see the flexibility and possibilities of the Modular method. :good:

Lol, I can assure you that I use AM3D in the most unorthodox way!

I'm willing to make another gamble and say that I am the only XDA member to ever use AM3D as follows:

Open AM3D

Power Off

It sounds very different than not having the AM3D module and obviously different than when Powered On. However, my usage is exclusively Bluetooth speaker output, so other outputs may not produce similar results Powered Off versus Powered On.

Furthermore, if the AM3D application fails to successfully launch to make any changes, delete /system/priv-app/AM3DZirene and reboot if not testing different roms using the dumpsys utility in order to see if an available rom for your device supports the AM3D library. Again, quite unorthodox, my usage has shown the AM3D module to enhance sound quality with the apk deleted if settling with a rom without the necessary support for the library compared to no AM3D module installed. Deleting the apk when unable to launch is absolutely crucial to avoid the inevitable and massive battery depletion that scenario causes. :good:

I will be preparing an update focusing on several minor and not so minor aspects today, including you specifically. :good:

Thank you very much, this is specifically being addressed by me today as well. :good:

Great question as I neglected to mention that very important step. The workaround I described to you requires the Core module to be installed, which also means that any currently installed optional module will need to be reinstalled as well, in order to complete the necessary audio effects configuration as the Core module provides the base template of the configuration while optional modules add necessary entries to this file. :good: