Dolby Troubleshootings

- Recommended to use Kitsune Mask in Read-Only ROMs https://t.me/androidryukimodsdiscussions/100091 otherwise, Dolby module (except Magic Revision) will be turned to hwservicemanager restarts method. It may break some system services & root hides on some ROMs. If ROM does not allow hwservicemanager restarts, you will get bootloop.

Another option:

Some ROMs are not allowed to write system/vendor caused by encrypted /data. You can decrypt your /data using this: https://forum.xda-developers.com/t/deprecated-universal-dm-verity-forceencrypt-disk-quota-disabler-11-2-2020.3817389/

If it's not the problem, try this: https://forum.xda-developers.com/t/script-android-10-universal-mount-systemrw-superrw-featuring-makerw-read-write.4247311/ or https://forum.xda-developers.com/t/guide-how-to-make-your-system-rw-super-r-w-read-write-able.4258745/

Can I use Magisk OverlayFS module instead?

No. It doesn't run in pre-init whereas Dolby manifest.xml needs pre-init.

- If you have sensors issue, or Bluetooth audio issue with OPSoundTuner UI, or still facing bootloop/softbrick even your ROM is RW, then READ #dolby_optionals!

- If you have in-built Dolby in your *Parts.apk (Advanced settings app), then you may need to disable the *Parts.apk using any root disabler/freezer and reboot afterwards. Usually *Parts.apk not only contains equalizer but also contains several other ROM features. Hiding/disabling it will also remove those ROM features.

- If your early mount dir is in /cache/, then do not ever wipe your /cache. If your /cache is wiped by another reason, then you need to remove Dolby module and REBOOT FIRST, then reinstall the Dolby module.

- Sometimes Dolby needs to reboot twice to restart sensors service.

- Some Dolby are changing/spoofing your system properties. If you have issues with that, use any other else instead. No solution for this.

- To disable FX for loudspeaker in Dolby Moto, tap 'About' then tap multiple times the text/image.

- If Dolby effect is stopped working or it's only working while opening the UI, run at terminal:

su

SVCS="vendor.dolby.hardware.dms@1.0-service vendor.dolby.hardware.dms@2.0-service vendor.dolby_v3_6.hardware.dms360@2.0-service"
killall $SVCS
sleep 1
for SVC in $SVCS; do
if [ ! "$(pidof $SVC)" ]; then
$(realpath /vendor)/bin/hw/$SVC &
fi
done
sleep 1
killall com.dolby.daxservice com.dolby.atmos com.oplus.audio.effectcenter
echo done

If there is "segmentation fault" or dms service is not registered https://t.me/androidryukimodsdiscussions/112081 then read #dolby_troubleshootings_2 https://t.me/ryukinotes/10

- If your inbuilt Dolby is not working after uninstalling any Dolby Magisk module, run at terminal:

su

rm -rf /data/user*/*/*dolby* /data/vendor/dolby /data/vendor/media/dax_sqlite3.db

Reboot afterwards.

- Can a dax-default.xml be used to another Dolby?

Usually it doesn't work because the dax-default.xml depends of vendor.dolby.hardware.dms@*-service compatibility.

- Why Apple Music and Tidal app can't detect Dolby/Spatial format in my device even I have installed Dolby module?

It's different thing. Apple Music and Tidal detects AC3/AC4 Dolby format decoder support from ROM framework.jar and whether libstagefright_omx.so is loading libstagefrightdolby.so or not and not detecting Dolby soundfx. AC3/AC4 decoder can only be added via ROM building, not via Magisk module nor any script. But why AC3/AC4 while FLAC is better and even best? There is no compression in FLAC.

- To turn on/off Dolby Magic Revision, tap the top title of the UI.

- What's the difference of Dolby Atmos and Dolby Digital Plus?

They are just the name of UI. DDP and old Dolby Atmos is using DS soundfx. Newer Dolby Atmos, Moto Dolby, & Dolby Audio they are using DAP soundfx that requires ROM/device manifest.xml support.

- Smart Audio equals to dynamic profile. It doesn't mean to change profile automatically.

- No need to remove your Dolby in-built to install my Dolby modules.

- If you have zygisk issue, then uninstall Dolby, reboot, then reinstall Dolby.