[Android Software Development] guitardedhero:
Just to expound a bit on Sony's Audio Settings:

If a Sony effects-chain appears in the output of dumpsys underneath the list of available libraries, the Audio Settings application has fulfilled its purpose. I will not be dishonest and claim that it is designed to not make discernable changes to the sound output when adjusting settings within Audio Settings, but Audio Settings simply sounds quite horrible unless it is on its own and not fully active with the rest of the DSP's and effects. Even with only ViPER4Android processing, Audio Settings adds nothing desirable when adjustments in the app have an effect on the output.

Deuteronomy™, if only to be known/remembered for one thing, it is the saga of effects-chain building. This is where the "magic" happens and is the only instance of Audio Settings having an impact other than "yuck".

Also, don't forget that Sony's effects-chain is system-wide and NOT limited to the Sony™ Music application. Also, don't assume that Audio Settings adjustments making a discernable change to sound output means subpar implementation when a Sony effects-chain exists. Simply turn off or disable any feature within the Audio Settings application. Lastly, MusicFX is almost (almost as in a different scenario may appear one day) always required to be installed AND disabled for best results with Audio Settings. Although, I still recommend to ALWAYS test with MusicFX enabled first as this and AudioFX are two DSP's responsible for creating effects-chains of AOSP and Qualcomm libraries like libbundlewrapper.so and libqcbassboost.so, respectively, which is still possible when either is disabled, but usually only after an appropriate /data/data/xxx/shared_prefs configuration xml has been generated while previously enabled.

For convenience, MusicFX is automatically installed with the Sony™ module and a couple other modules that benefit most from its installation.

And while I'm thinking about it, we do not seek and destroy AudioFX anywhere in the various script operations and so should you not do so as well. Of course, scenarios vary greatly, requiring different needs, but always ENSURE AudioFX needs to be eliminated through testing before automatically doing so.

We have created the ultimate collection of sound enhancement content that is compatible with nearly all devices and operating systems going back to JellyBean (Various apk's force this minimum OS compatibility) with the only absolute incompatibility with software being DSPManager, which is why it is the only content that will ever be sought and destroyed automatically by our script.

Forget the bad habits formed over the last few years by what was normal and typical back then before we made it our mission to do something different. I realize it's difficult as so much becomes automatic when trying out all the various mods of the past. We've proven that much can be gained by utilizing existing content and unnecessary sacrifices may prevent you from experiencing the ultimate potential of your software/hardware combination.

What we provide should be forming new habits, not stifled from needless habits of the past.

I swear, I'm almost finished lol...

Every action taken outside the sound system's own execution and operations should have a very specific and quantifiable reason. Doing so allows you to learn the many nuances of software harmony and equips you with debugging mastery. :good:

---------- Post added at 10:09 PM ---------- Previous post was at 10:06 PM ----------

This particular operation poses no impact whatsoever. The single services script in /system/su.d controls all /system/etc/init.d scripts for execution scheduling but setprop can execute at any time with perfect results. :good:

---------- Post added at 10:11 PM ---------- Previous post was at 10:09 PM ----------

To our surprise, Dirac impacts Bluetooth output in a most enjoyable fashion. :good: