[Android Software Development] guitardedhero:
You guys are doing a phenomenal job handling the flurry of test builds even with little to no information provided with them. I'm getting very useful reports that I'm using to hopefully button this baby up in 24 hours or less. I am so ready and I know you guys are too but this is the worst time to settle in order to finally call it complete.

I can almost guarantee that this will be the longest testing phase in the life of this project and you guys handled it with proficiency. It's almost too easy to forget that there was even a Genesis build as Exodus has been a journey that I and likely many of you have never experienced until now. The growth and progress during this Exodus chapter is more than I ever could have imagined when preparing Exodus 0.1. Now on the brink of Exodus 1.0, we are more than well equipped to achieve whatever objective we set our sights on.

To provide some clarity for the enigmatic changes of late, here is some information regarding many questions many of you have been trying to figure out on your own. Before i do that, please know that I never purposely try to hide or keep anything from you guys. I rely on you guys more than you know and there's no better way to maximize everyone's time and to get the most helpful feedback than from blind tests. I have a very organized way of how I like to do a lot of things in these projects and blind testing is my preferred method when I'm testing something quite focused like bass, clarity, soundstage, or many other things. Being presented with a test build out of nowhere with no details should be your clue that there is something in that build to listen for. Obviously, this is limited to only test builds and not all of them either.

Presets have been abandoned. Originally, they were used to test for different combinations to see what stood out so it could be the default and only sound profile. The HTC 10 Dolby Atmos presets have been abandoned just recently as I was finally convinced the /system/etc/tfa data did more harm than good which is the backbone of the HTC 10 Dolby Atmos presets. Not using /tfa anymore renders those presets useless in my opinion. Lastly, the benefit of any of those and the audio_effects presets simply did not warrant the confusion they cause.

Similarly, Advanced Linux Sound Architecture is abandoned completely. I made up my mind to do this a few weeks ago, but I wanted to wait until the last minute to do so. Like the /tfa data, the ALSA utilization does more harm than good in my opinion, assuming ALSA does anything good at all. It is clear to me that the sound system is significantly enhanced by its removal.

HTC 10 Dolby Atmos is still the GUI-less stock Dolby system for Exodus with nothing changed besides the lack of the abandoned HTC 10 Dolby Atmos presets. Configuring this Dolby's settings is performed by adjusting values in the provided tweak.prop's.

The K4 Note Dolby Atmos ported by ahrion, one of two Dolby Atmos GUI Add-On's, still requires Permissive Selinux and deep_buffer to be removed from the output policy file on the device. The main bug it suffers from is the seemingly unadjustable EQ graph. Hopefully, this is not a deal breaker, as it is of no consequence to me, using just Music, Open, and everything else either Off or unchanged with Audiophile 7.0 v4a profile.

Everyone knows Dolby Atmos dap_r6.5.

:good:

Have you tested this issue without flashing tweakprop.zip?

/system/lib64/libsonydseehxwrapper.so

:good:

Noted. :good:

Noted. :good: