[Android Software Development] guitardedhero:
Don't worry, what I chose to do with this recent change can only create confusion and not clarify anything lol. This recent change to the setprop script is limited to only a name change and content differences if the setprop script was updated as well, which I think did occur.

The reason for this name change is only to prevent the setprop script from executing as the scripts we place in /system/etc/init.d are executed by the single /system/su.d/arisesound_services script so that full scheduling control of all script operations from beginning of the first script to the end of the last script is possible. The arisesound_services script will execute /system/etc/init.d/arisesound_setprop but not /system/etc/init.d/ariseound_disabled_setprop because everything is targeted specifically.

Now, the reason for this current expirementation of not affecting build properties seemed to be a good idea to try when I found myself in a scenario where incapacitating the setprop solved my issue of no playback of local FLAC media. Since this is the first build to not affect build properties, I figured this was a really good and convenient way to see how many lingering issues users have been dealing with that result only from one or more hardware/software properties applied via setprop. It's even possible for one or more minor issues to go unnoticed if the fix produces noticeable results.

If you have two differently named setprops in /system/etc/init.d, delete arisesound_setprop and reboot the device. This will leave you with the most recent setprop script that has disabled in its name. It is disabled only because it can only be executed by /system/su.d/arisesound_services if existing as /system/etc/init.d/arisesound_setprop. Booting to a state where only /system/etc/init.d/arisesound_disabled_setprop exists, allows you to test the sound system with native build properties only. To enable the setprop script at any time, all that is required is renaming /system/etc/init.d/arisesound_disabled_setprop to /system/etc/init.d/arisesound_setprop and then reboot the device. :good:

That can likely be caused by the Dolby Atmos module, specifically Volume Leveler, as that increases gain output significantly when enabled, and not lower the gain somewhat when neutralizing the volume levels as it is intended. This is a quirky characteristic unique to the dap_r6.5 Dolby Atmos port.

If ICE is installed and a unique ICEpreset was specified in arise_customize.prop, that ICEpreset could be the culprit as well.

Of course, the first thing to test is always a device boot with the setprop script unable to execute to find whether one or more build properties are the cause of whatever issue.

If the setprop script has shown to not cause this issue, it's recommended to test with only the Core module installed, and v4a as well, if v4a is part of your sound system solution as the v4a module will almost always be free from having any negative impact that is not already well understood and accepted..

If this has not reproduced your volume issues, simply install one module at a time by adding the value of "true" to a module installation line in arise_customize.prop in the root of your internal storage and ensure that the value of "true" does not exist in the Core installation line.

As soon as your volume issues are reproduced, they can be traced to the module most recently installed. At that point, we'll look into what's causing this in that particular module and if it is possible to correct it at the source. :good:

The presence of libeagle.so in the targeted path listed in your audio effects configuration means that, if possible, more is needed to satisfy the prerequisites that support the libeagle.so effect library.

However, your audio effects configuration seems to be the HTC audio effects configuration and NOT the Huawei QC audio effects configuration. Can you provide your prepared arise_customize.prop, /system/etc/htc_audio_effects.conf, and /system/etc/audio_effects.conf so that I can see what you're working with? :good: