[Android Software Development] guitardedhero:
Hey guys! It seems like the recent issues are mostly fixes with 2.1.5, that's great news. Embarrassingly, ever since the 6p and 5x were released, I was certain that /vendor/etc/audio_effects.conf needed any entries of additional effects added to the /system.

If deleting /vendor/etc/audio_effects.conf without an existing /system/vendor/etc/audio_effects.conf, that leaves the device with only /system/etc/audio_effects.conf. That file from the Deuteronomy installation is /customize/etc/stock_audio_effects.conf for those devices which is, in fact, stock with only v4a entries added.

This prevents the other effects from entering the effects chain in this scenario.

What I am most interested in is if:

moving /vendor/etc/audio_effects.conf to /system/vendor/etc, if this directory exists,

or

moving the file to /system/etc if there is no /system/vendor/etc,

solves everything for 64 bit Nexus devices.

Please test this as much as you can as the results will be in the next update which is only waiting to ensure various issues are, indeed, resolved. Before this 64 bit Nexus workaround, the focus was on full One Plus 3 support and full HTC native Dolby support, so please report anything that will help me provide a satisfactory update. :good:

Keep in mind that reports of issues experienced with the Dolby Atmos must include results having tested the default sound system and its default setprop as well so that focus is directed appropriately. :good:

I, too, experienced the impossible driver installation with the ViPER4Arise 2.3.4.0 Driverless Add-On and can only blame the apk at this time as I did not try the official 2.3.4.0 apk, but it never failed me before in the past either. Immediately, I prepared a ViPER4Arise 2.3.4.0 Add-On with preinstallation of the Super Quality driver, so please use this one which should be in the current Extras for Deuteronomy zip at our AndroidFileHost. The Add-On is also available separately in the ViPER4Arise folder next to the individual sound system folders in the root directory of our AndroidFileHost's Generic Devices section.

Furthermore, the Extras for Deuteronomy zip is not a zip to be used in recovery but the zips within the archive can be used in recovery. :good:

Please let me know if there is anything else at all that I can clarify for you, I'll be available all evening now that the brief break away is over (wife mandated lol).

Lastly, we're honored that many of you are having the best experiences with our work! It means everything to us as it is a privilege to be able to interest you enough to get a piece of your time to check out our sound systems, give it a test spin, and contribute with your reviews, reports, suggestions, or even just introducing yourself. We know offline life can be very demanding so we appreciate any online time we get from you guys! :good:

---------- Post added at 05:55 PM ---------- Previous post was at 05:41 PM ----------

Unfortunately, Marshmallow is the minimum OS for ahrion's latest Dolby Atmos ports. However, dap_r6.5 is fully compatible with KitKat and the zip can also be flashed any time after the sound system because of its patching of the audio_effects.conf instead of overwriting the configs. :good:

I will certainly look into that this evening. I'm afraid I am unfamiliar with Samsung's Adapt Sound so any info you can provide will help quite a bit. Is it an apk? Or /soundfx library? Entries in /system/etc/audio_effects.conf or /system/vendor/etc/audio_effects.conf? Any related files in /system/etc or related property lines in /system/build.prop or your setprop output?