[Android Software Development] guitardedhero:
Thank you and it is our pleasure! :good:

1. The fasttrackoutputs property value is the number of ICEsound effect-chains created in addition to the one effect-chain created resulting from an adequate ICEsound installation and is observable using the dumpsys utility described in the Auditing Section of our OP:

- fasttrackoutputs 2

- Equals three effect-chains (2 + 1)

2. Many of us on the team have devoted countless hours probing the ICEsound apk and its components. It is quite amazing what this 100kB package harnesses: a massive feature-set and numerous properties and values.

Unfortunately, much of it requires deciphering and experimentation, so we are still learning more and actively probing it.

- The a2dp property in icesoundconfig.def appears to work with a system property (setprop or build.prop) of:

- audio.effect.a2dp.enable

using values of either 0 or 1 (0=false) (1=true):

- audio.effect.a2dp.enable=1

Still, default a2dp output processing support exists with neither property being true or even present, but aptX just doesn't seem to be of any relevance to the ICEsound DSP. I suggest experimenting with the icesoundconfig.def a2dp property and the system property I provided above (ignore/remove usbaudio) and see what results you get and settle with what provides the best experience for you. One of the very few immutable truths we've learned from ICEsound is that predictability is nearly an impossibility lol.

3. You are correct, the ICEsound module must already be installed or be instructed to install by arise_customize.prop when adding values to the two additional ICE parameters.

Since the ICEsound module will install before the script gets to those other two ICE components, it will already appear as an existing ICEsound installation.

3.1

use.ICEconfig=none
use.ICEsound.preset=none

- Adding values that do not exist will have the same results as if no value has added. The value "None" does exist and should be interpreted as "delete". If the two properties above each had the value of "None", the results would be no /system/etc/icesoundconfig.def and no /system/etc/icesoundpresets.def upon booting the device.

3.2

use.ICEconfig=none
use.ICEsound.preset=01

- Of course, we will only focus on the second property. Currently, the value of "01" equals the Bath Salts ICEsound present when applied to the use.ICEsound.preset property in arise_customize.prop.

3.3

use.ICEconfig=04
use.ICEsound.preset=none

- Obviously, we will only focus on the first property. Currently, the value of "04" equals the fourth ICEsound configuration that we've made available for user testing purposes to obtain a most satisfying ICEsound experience.

- Unfortunately, predictability in ICEsound is insufficient to provide just one or even no configuration at all. Many devices will only achieve ICEsound functionality by having at least one configuration property and value, but again, predictability escapes this specificity as well.

- The absence of predictability is the sole reason the available configurations are numbered rather than something more descriptive. The configuration can and will have a dramatic effect on the sound coloration and profile in addition to allowing function on a device, but again, the results vary so widely a description is simply illogical and would often be inaccurate.

Please let me know if I didn't address something or if I misunderstood anything you were seeking. :good: