[Android Software Development] guitardedhero:
Flashing the installation archive is required as that file is merely a set of instructions the installation script uses to manifest the outcome.

Bass is far from a luxury and in ample supply througout the modules. It's almost difficult to suggest where to begin not having any details of what you're working with. Besides the unanimous popular sources like the Dirac and AM3D modules, audio effects configuration can provide surprising changes. If using a Qualcomm device, I find that the AOSP libraries provide a much more impactful and desirable bass response than Qualcomm's libraries, libqcbassboost.so and libqcvirt.so, specifically.

Another one of those unanticipated surprises we've found. I mean, who would genuinely predict the dedicated vendor Qualcomm libraries of paling in comparison to the almost seemingly generic AOSP libraries? libbundlewrapper.so is just such a fantastic effects library, responsible alone for bass, virtualization, equalization, and volume.

The default audio effects configuration currently is still Android O for qualcomm devices, but the available Android O Preview does not utilize vendor Qualcomm effects libraries for bass, virtualization, and reverb, letting AOSP handle everything outside effect offloading and voice pre-processing handled by Qualcomm libraries.

If having installed the ICEsound module, testing alternate configurations and presets will make many significant changes to the sound profile. It just takes the time necessary to see your device reacts to these options, including using neither by deleting both.

I mean, the resources we've made availble at your disposal are almost overwhelming when losing focus on individual components. Focus on one at a time using a minimal installation if wanting to know Magnum Opus inside and out. :good:

Honestly, I do not remember such a statement, but I've been focusing on this specific report this afternoon and have an idea I'd love to be tested on a Pixel device. Interested? :good:

That's the behavior that should be expected, fortunately. I still recommend an environment free of SELinux meddling and SuperSU. :good:

By design, the contents of arise_customize.prop are not open to any interpretation whatsoever and are explicit instructions for the numerous operations of the installation script to provide repeatable and anticipated results, which by way of residing in the root of internal storage, are able to survive fully intact when flashing/updating roms as well as factory resets in TWRP. The format data option in TWRP is the only way to indirectly this file and its contents. :good:

Whoa! Who's this guy lol?!

Missed you, brother. Hope you've been having a great year so far. Still have that Nexus 6? :good:

Thank you for such an informative and descriptive post! :highfive:

This is a great example of what a sneak peak of Round 2 of Family Feud would appear like. :good:

Normally a characteristic attributed to the Arkamys Audio module, I'd suspect Dolby Digital Plus among your installed modules causing this undesirable occurrance. :good:

Quite rare for ViPER4Arise, I'd suspect any Force Closes to be from /data/data, or possibly /data/app which can include a rare scenario of having two different versions of ViPER4Arise installed: one in /system/priv-app/ViPER4Arise and one in /data/app/com.one-of-two-possible.viper user installations.

If there is no /data/app user installation of ViPER4Arise, delete its /data/data ...data instead followed by a device reboot to test for corrected results. :good: