[Android Software Development] guitardedhero:
To expound on your last bit of info, here are the facts:

Dolby ports are not dependent on ViPER4Android and will function just fine in its absence.

The relationship between the two of which you mentioned is the necessity for an existing ViPER4Android installation to be complete and for ViPER4Android to process audio during playback.

If both, ViPER4Android and a Dolby port, are installed, there is nothing to be gained by probing the Dolby GUI without first ensuring that ViPER4Android is functioning and processing appropriately.

If the expected ViPER4Android behavior is found and then Dolby is found to perform less than expected, then and only then is it sound to debug the Dolby installation.

A user's greatest tool and asset debugging Dolby and any other DSP application and effect is the dumpsys utility - outlined and explained comprehensively in the OP's Auditing Section. This utility is used throughout the development of our sound systems and takes out all potential guesswork regarding the effectiveness of what we introduce into the project during initial testing of newly sourced content.

The value of the dumpsys utility cannot be overstated - if, at any time, you wonder whether "abcxyz" effect is working, examine your dumpsys output during audio playback. It's amazing to me this free and universal tool is still under the radar for many and never mentioned in nearly all other sound modification threads.

Still, subsets of sound enthusiasts cry foul over our project's validity and, by default, assume most of you know no better, while at the same time, choose to NOT inform the inquisitive user of ways to assess the installation and effectiveness of content with no source(s) whatsoever. I can guarantee each and every one of you these allegations are NOT the result of any auditing procedures whatsoever.

As important to us as genuine effect building and processing is, the source of that content is as well. After all, we consider activities in custom recovery as being serious and critical. It is only responsible to provide as much information as is available regarding anything and everything we suggest placing on your device.

Finally, it's a most logical assertion to weigh the development of a project by the amount of source and auditing information. Consider a scenario where an offering is developed using the dumpsys utility throughout its entire development: Why on earth would the dumpsys utility not be explained and encouraged for every tester? I have no answer lol. :good:

---------- Post added at 10:41 PM ---------- Previous post was at 10:37 PM ----------

The AROMA zip? V4a processing, if installed? Please provide the dumpsys output to pastebin for me to examine. :good:

---------- Post added at 10:49 PM ---------- Previous post was at 10:41 PM ----------

You were not wrong. You've obviously learned a lot about the nuances of multiple effects and how some behave and interact differently with some other effects. Your assistance was far from what is common and typical outside this thread. What I added to your post's explanation was something rarely explained in these thousands of pages, certainly less than is appropriate, so feel good and confident about what you deleted. In fact, were it not for your post, my most long overdue Dolby/v4a explanation would still be waiting to be understood. :highfive: