KernelSU/SUList/APatch Issues

- Many KernelSU/SUList/APatch users don't want to READ the installation guide says my module doesn't work/force close but they don't even disable Unmount Modules by Default in their KSU app settings nor include their launcher app & package names in the superuser list/whitelist. If they have included launcher & those package names but they don't reboot. It has been explained in the README Installation Guide but many users don't even want to READ anything. Dang.

- This is how to disable unmount modules in Apatch: https://t.iss.one/androidryukimodsdiscussions/228103 or https://t.iss.one/androidryukimodsdiscussions/228128

- If the above still doesn't solve the problem, try to install Meta Module OverlayFS module or Meta Magic Mount module or something similar, depends on ROM compatibility.

Miui Apps Optionals

You can create /data/media/0/optionals.prop file yourself if it's not exist yet (if you are not in user 0, then change the 0 to your current user) using @mtmanager or any file manager and write any modified settings bellow inside the optionals.prop file BEFORE INSTALLING/REINSTALLING THE MODULE:

- You can use HEVC encoder in Miui Screen Recorder Min29 if your ROM is supported:

miui.hevc=1

If your ROM is not supported then screen recording will fail.

- To turn any Miui App Magisk Module into Global mode instead of original China mode:

miui.global=1

- To activate recents provider of Miui Home Magisk Module:

miui.recents=1

Don't use this kind of module @QuickstepSwitcherReleases

- If you have display brightness issue:

miui.code=0

- To show Sky feature in Miui Gallery AI:

miui.features=1

(Delete any other else miui.features)

- If there is no playback while recording with system sounds, you can change gallery mode to lavender instead of cepheus:

miui.features=lavender

(Delete any other else miui.features)

If system sound option is gone, that means your framework.jar is not supported. To check is your framework.jar support system sounds playback or not, run terminal:

su

grep -E 'createAudioRecordForLoopback|FOR_LOOPBACK' /system/framework/framework.jar

If there is no output, that means unsupported.

INSTALL/REINSTALL THE MODULE AFTERWARDS and reboot.

360 Reality Audio Upmix Optionals

You can create /data/media/0/optionals.prop file yourself if it's not exist yet (if you are not in user 0, then change the 0 to your current user) using @mtmanager or any file manager and write any modified settings bellow inside the optionals.prop file BEFORE INSTALLING/REINSTALLING THE MODULE:

- The sound effect is applied to rerouting and patch stream by default for game apps. You can disable it if there is a problem with it:

tsra.game=0

- There is a setting for mono speaker devices although I don't see any difference with that:

tsra.mono=1

INSTALL/REINSTALL THE MODULE AFTERWARDS and reboot.

Bug Report for Brick/Bootloop/Forced Reboot to Recovery/Auto Reboot/Random Reboot/Stuck After Boot

- At the first time, you need to install this module: https://github.com/reiryuki/Boot-Logcat-and-dmesg-Magisk-Module

- For Magisk users, let it bootloop and wait about 3 minutes. After that, go to Recovery and run terminal in Recovery:

touch /sdcard/disable

Copy /sdcard/disable file to the module folder that causes bootloop inside /data/adb/modules/ and /data/adb/modules/BootLogcat/ also. (This method cannot be working if your /data is encrypted and your custom recovery can't access it. So, you need to decrypt your data or find custom recovery for your device that can access your encrypted /data. How to decrypt? Ask Google.) Some custom recoveries has a feature to disable module so you don't need to do above. Do not remove the module nor installing Uninstaller.zip, just disable it!

Reboot system

For KSU users, use /data/adb/ksu/ modules/ instead. If you don't find it, then flash your original boot.img then just do bellow even no disabled module ↓

After the module is disabled, then send #zfolder to @reiryuki via PM. Tap here: https://t.iss.one/ryukinotes/57

Send also #magisk_install_log to @reiryuki via PM. Tap here: https://t.iss.one/ryukinotes/72

IF YOU DON'T SEND BOTH FILES ABOVE, YOU WILL GET WARNS AND BE IGNORED.

For HyperOS users, read this: https://t.iss.one/androidryukimods/2218

Magisk Delta is now Kitsune Mask

What is Kitsune Mask? Go here instead: @huskydg

Please don't asking question about Kitsune Mask furthermore here because this is not Kitsune Mask support group and I am not the dev.

How to move to Kitsune Mask from Magisk Official?

- If you have Dolby module installed (except Magic Revision), remove it and reboot first! Otherwise, Dolby early/pre init mount manifest.xml writes installation may fail.

- Download the latest version of Kitsune Mask from here only: https://www.pling.com/p/2280310/

WARNING!!!

The latest version code of Kitsune Mask stable is 26400 and debug is 27001 for now. If you find higher version code, then it is fake and potentially MALWARE and it's known has broken early-mount.d function. According to information, the Kitsune Mask site was previously hacked: https://t.iss.one/huskydg/345

- Normal install the app

- Copy the .apk and rename the copied to .zip using any file manager

- Install the .zip via the official Magisk app or via custom recovery

- Reboot

- Uninstall the official Magisk app

- Open the Kitsune Mask app

- Click OK if there is "Requires Additional Setup" pop-up, it will reboot automatically. If you don't click OK, sepolicy.rules dir and early/pre init mount dir will not be working.

- If you face root detection issue, then use the Magisk Hide or even SUList feature

- You don't need to remove KernelSU nor Apatch because they ain't conflicted with Kitsune Mask nor Magisk. You can use both but you can only use modules on one of them. Just install Kitsune Mask via TWRP or patch manually your boot.img via Kitsune Mask app. Install the patched boot.img via TWRP or fastboot.

OZO Widening Audio Optionals

You can create /data/media/0/optionals.prop file yourself if it's not exist yet (if you are not in user 0, then change the 0 to your current user) using @mtmanager or any file manager and write any modified settings bellow inside the optionals.prop file BEFORE INSTALLING/REINSTALLING THE MODULE:

- The sound effect is applied to rerouting and patch stream by default for game apps. You can disable it if there is a problem with it:

ozo.game=0

INSTALL/REINSTALL THE MODULE AFTERWARDS and reboot.


Troubleshootings

You can boost internal speaker sound by running this command in Termux:

su -c resetprop persist.audio.sys.boostmode 1

To turn it off:

su -c resetprop persist.audio.sys.boostmode 0

Or:

su -c resetprop -p --delete persist.audio.sys.boostmode

Audio Effect Deep Field Optionals

You can create /data/media/0/optionals.prop file yourself if it's not exist yet (if you are not in user 0, then change the 0 to your current user) using @mtmanager or any file manager and write any modified settings bellow inside the optionals.prop file BEFORE INSTALLING/REINSTALLING THE MODULE:

- If you want higher volume gain of voice call, tts, assistant, call assistant, and accessibility:

vafx.voice=1

- libvafx_gfx.so is applied to rerouting and patch stream by default. If you don't want it, you can disable it:

vafx.game=0

- VAFX new mode is activated by default. If you have any issue with that, you can disable it:

vafx.new=0

INSTALL/REINSTALL THE MODULE AFTERWARDS and reboot.


Troubleshootings

- If VAFX app or vafx command doesn't work, probably you have to turn your device to permissive. Read #global_optionals!

Post Process Stream Mode

These optionals turns any global type sound effects into post process type sound effects.

You can create /data/media/0/optionals.prop file yourself if it's not exist yet (if you are not in user 0, then change the 0 to your current user) using @mtmanager or any file manager and write any modified settings bellow inside the optionals.prop file BEFORE INSTALLING/REINSTALLING THE MODULE:

Values:

m = music stream (no need to use this on DTS modules because it's already enabled by default)
r = ringtone stream
a = alarm stream
s = system stream
v = voice call stream
n = notification stream
b = bluetooth_sco stream
f = dtmf stream
e = enforced_audible stream
y = accessibility stream
t = tts stream
i = assistant stream
c = call_assistant stream
p = patch stream (no need to use this on DTS modules because it's already enabled by default in newer version)
g = rerouting stream (no need to use this on DTS modules because it's already enabled by default in newer version)

Notes:
- p & g is for game apps
- Using "m" option is NOT RECOMMENDED because the music FX chain will be DOUBLE CHAINED into both global type FX and post process type FX (except for AudioFX LineageOS, Sony Sound Enhancement, Sound Alive, & Audio Effect Deep Field). Actually, global type soundfx can be chained together with post process type soundfx by enabling the global type soundfx BEFORE PLAYING MUSIC. Disabling it while music is playing causes it cannot be enabled again except you stop the music first, enable it, and play the music again. But if Global type FX is not chained with post process FX even though you have done the trick above in your ROM, "m" option could be the workaround. This bug will be fixed soon in the next version. All new versions of Dolby modules are already fixed so double chain will not gonna be happen.

The usage is:

stream.mode=<your_values>

Example for enable music stream only:

stream.mode=m

Example for enable, ringtone stream, & alarm stream:

stream.mode=ra

Example for enable ringtone stream, alarm stream, & voice call stream:

stream.mode=rav

Example for enable ringtone stream, alarm stream, voice call stream, & notification stream:

stream.mode=ravn

Those options above only for example. You can modify values based on your needs.

INSTALL/REINSTALL THE MODULE AFTERWARDS and reboot.

Hi-Res Audio Enabler Troubleshootings

- You can check via #logcat and search bitwidth  and play music to confirm is your ROM supported or not. If you see 24 bitwidth or 32 bitwidth and no any resetting to 16 bitwidth, that means your ROM is supported, otherwise it's not supported.

- To check is your ROM already applied 24 or 32 bit width, run this terminal command:

su -c getprop persist.vendor.audio_hal.dsp_bit_width_enforce_mode

If there is no 24 or 32 output then the ROM is not applied Hi-Res yet. (This is not for checking that the ROM supports Hi-Res or not, use logcat instead!).

- Don't trust any other apps

- If accidentally deleted /data/adb/modules/HiResAudio folder manually without removing the module via Magisk app, you have to run this after reboot:

su -c resetprop -p --delete persist.vendor.audio_hal.dsp_bit_width_enforce_mode

and reboot again.


Optionals

You can create /data/media/0/optionals.prop file yourself if it's not exist yet (if you are not in user 0, then change the 0 to your current user) using @mtmanager or any file manager and write any modified settings bellow inside the optionals.prop file BEFORE INSTALLING/REINSTALLING THE MODULE:

- To enable 32 bit width instead of 24 bit width:

hires.32=1

- To keep 16 bit width on loudspeaker:

speaker.bit=16

- To keep 24 bit width on loudspeaker if hires.32=1:

speaker.bit=24

- You can enable audio format PCM 24 bit packed/32 bit patch to audio output flag deep buffer playback. But it causes low sound issue or even no sound issue at all in some devices. This even doesn't work in most Android 13 and cause some audio mods doesn't work:

hires.pcm=1

You can check is it applied or not via Terminal Emulator (sample rate will be showed here also):

su

dumpsys media.audio_flinger | grep -B31 AUDIO_OUTPUT_FLAG_DEEP_BUFFER

If the Hal Format: is not AUDIO_FORMAT_PCM_24_BIT_PACKED/AUDIO_FORMAT_PCM_32_BIT, that means it doesn't work and will cause some issues.

Audio Compatibility Patch Magisk module is disabling audio output flag deep buffer and redirecting to audio output flag primary, so not recommended to use Audio Compatibility Patch Magisk module if there is no problem with deep buffer.

- You can
also enable audio format PCM 24 bit packed/32 bit to audio output flag primary (low latency playback). BUT THIS OPTION IS ONLY IF hires.pcm=1:

hires.primary=1

To check in terminal (sample rate will be showed here also):

su

dumpsys media.audio_flinger | grep -B35 AUDIO_OUTPUT_FLAG_PRIMARY

- You can enable audio format pcm float instead of 24 bit packed/32 bit like on Pixel 6 Pro. BUT THIS OPTION IS ONLY IF hires.pcm=1:

hires.float=1

- You can change the sample rate BUT THIS OPTION IS ONLY IF hires.pcm=1.

To enable sample rate 44100:

sample.rate=44

To enable sample rate 88200:

sample.rate=88

To enable sample rate 96000:

sample.rate=96

To enable sample rate 128000:

sample.rate=128

To enable sample rate 176400:

sample.rate=176

To enable sample rate 192000:

sample.rate=192

To enable sample rate 352800:

sample.rate=352

To enable sample rate 384000:

sample.rate=384

Some sample rates may be unsupported by device. DTS soundfx only supports default sample rates 44100 and 48000. Sound Enhancement soundfx doesn't support sample rate greater than 96000.

CAUTIONS!!! INSTALL/REINSTALL THE MODULE AFTERWARDS and reboot.

Do not asking which option you have to use! Just experiment it by yourself!

Bug Report / Fix / Feedback

Not allowed to say doesn't work/bootloop nor telling/reporting crash/bug/issue nor asking any fix without providing required files written in this #bug_report or #bug_report_bootloop (even the bug is weird or the crash is not from my apps). If it still violates, warnings will be given immediately. WARNINGS WILL NOT BE REMOVED UNTIL THIS #bug_report OR #bug_report_bootloop FILES ARE SENT or you say you have got the fix yourself. Conveying issues without data is like spreading hoaxes. I don't like that. There are no psychologists nor magicians here. Everything is data.

Sending logs/bug_report that is not via PM will not be approved. Logs/bug report must be via PM @reiryuki. Do not send to group. Any logs/bug report sent to group will be ignored (except you are blocked by me). Any .zip files will also be deleted automatically in group.

Anyone reporting modules with old/deprecated version will also get warns.

If you're reporting bug without following the installation guide and this #bug_report or #bug_report_bootloop, you will receive warnings.

Make sure you don't reporting about "Known Issues" that is written in each README of modules!

For audio mods, you have to install AML, dirac misoundfx Remover, AOSP soundfx Remover (except for Lineage AudioFX), & Sound Alive FX Remover Magisk Module (for Samsung device except you are using Sound Alive Magisk Module), do not use NLSound nor Ainur Narsil Magisk Module, otherwise not apporoved!

1) If it's a Magisk module, disable any other else module first (except the module you want to report, AML, dirac misoundfx Remover, AOSP soundfx Remover, Sound Alive FX Remover, and any Core Magisk modules. But if you are reporting for AML Ryuki Mod, then you need to enable all audio mod module you have), only use latest version can be approved (IF THE LATEST IS ALPHA/BETA, THEN USE ALPHA/BETA INSTEAD!  Search #alpha or #beta at finder if there!), explain what's not working, and send required files bellow via PM.

2) Take a MAGISK/KERNELSU INSTALL LOG #magisk_install_log (NOT MAGISK/KERNELSU LOG) if it's about Magisk module tap here: https://t.iss.one/ryukinotes/72
If you are still sending Magisk log instead of Magisk Install Log, you will receive a warning until you send the right Magisk Install Log.

3) Take a full #logcat tap here: https://t.iss.one/ryukinotes/73

4) Take #zfolder tap here: https://t.iss.one/ryukinotes/57

If you PM me without doing above, means no fixes and no answers or you may be blocked. You can only report 1 module per report. If you miss any file, you may be ignored.

------------- Any missing stuffs --------------
------------ will not be approved -------------

Bug report contains 7 stuffs:

1) Explanations
2) Magisk/KernelSU install log if it's a Magisk module #magisk_install_log
3) Disabled any other else modules (except the module you want to report, AML, dirac misoundfx Remover, AOSP soundfx Remover, Sound Alive FX Remover, and any Core Magisk modules. But if you are reporting for AML Ryuki Mod, then you need to enable all audio mod module you have.)
4) Full logcat #logcat
5) Z folder #zfolder
6) Screenshot all super user lists for KSU users
7) Send bug report via PM @reiryuki

If you miss one of them, re-read above please. If you don't understand, learning is the best you can do. If you feel that this is too complicated, then just go out from here. Thank you.

If facing brick/bootloop/auto reboot/forced reboot to recovery/stuck after boot, go to #bug_report_bootloop instead: https://t.iss.one/ryukinotes/45

If your report is not answered immediately, then be patient because I only have one brain while there are so many of you.

Asking fixes without doing above or sending bug report without disabling any other else modules are REJECTED/IGNORED. If you still nagging, then you will get warns.

Note: 3 warns will only mute in the group, not ban, unless there is a specific reason. But in DM, 3 warns means blocked.

For who can't access pling.com, try to change your private DNS to

1dot1dot1dot1.cloudflare-dns.com

or

dns.google

or use VPN

You can also change address pling.com to opendesktop.org or store.kde.org or linux-apps.com

If you still unable to access, the website must be under maintenance. It's usually happen. Just be patient. Try again tomorrow. Or just report it to [email protected].

Sound Enhancement Troubleshootings

- If Sound Enhancement FX doesn't work, then type:

su
sefx

at Terminal/Termux app while playing music.

- If Sound Enhancement still not working, you need to play music with any music app that has external EQ option first like Xperia Music, YouTube Music, or Spotify.

- Disable the "No active profiles" notification and ignore it, it's nothing. If notification is greyed out, do not disable Android Signature Verification. Or use any notification remover app root at playstore if there.

- DSEEHX and Clear Phase toggler is turning off automatically after switching/stopping song or phone's rebooted. It's not a bug. That's how it is on unsupported/non-Xperia audio service.

- Actually, DSEEHX is only working in Xperia vendor, otherwise the toggler can only be used to disable Sound Enhancement effect.

- Any workaround for the Dolby is the same as #dolby_troubleshootings notes: https://t.iss.one/ryukinotes/11 and #dolby_troubleshootings_2 notes https://t.iss.one/ryukinotes/10


Optionals

You can create /data/media/0/optionals.prop file yourself if it's not exist yet (if you are not in user 0, then change the 0 to your current user) using @mtmanager or any file manager and write any modified settings bellow inside the optionals.prop file BEFORE INSTALLING/REINSTALLING THE MODULE:

- You can enable any #dolby_optionals here: https://t.iss.one/ryukinotes/8

- Dolby is enabled by default. If you want to disable it:

se.dolby=0

Then you can use any other else Dolby afterwards.

INSTALL/REINSTALL THE MODULE AFTERWARDS and reboot.

Z Folder Script

- Make sure the modules are installed correctly

- Install Termux app at Play Store or any other else Terminal Emulator app

- Download z.sh file here: https://www.pling.com/p/2183312/ then move it to /sdcard/

- Type "su" at the Termux app, press enter and grant root access

- Run this command bellow at the Termux app (just copy and paste):

su

sh /sdcard/z.sh

Wait until it's finished. After running the command above, z folder will be created automatically in your internal storage. Zip/compress it and send me the zipped/compressed /z folder. (/sdcard means your internal storage. That's not external sdcard).

Send it PM to @reiryuki

Simple Explanation of ZRAM Swap

An app task memory 100 MB for example  > 100 MB running in RAM while the app is opened > If we go directly to home without closing the app, the 100 MB will be cached in RAM > If we open another new app and the RAM is full enough, the 100 MB will be compressed to 35 MB and it's still in RAM, not going anywhere, so we have 65 MB free RAM for the new app. This compression is called as ZRAM Swap. ZRAM is swapping from normal file to compressed file and vice-versa, so it's also called as Swap. ZRAM Swap is faster, better, & safer than the old and depracated Swap Partition and Swap File, so do not use swap partition nor swap file if you are using ZRAM Swap.

Moto Waves Troubleshootings

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

- If Moto Waves G doesn't work in your Android 11, then use Moto Waves V2 instead and vice-versa.

- I have installed Moto Waves correctly but why still doesn't work?

Moto Waves is a little bit different from other audio mods. Not all ROMs are supported. Actually it depends on the vendor audio hal in terms of support for the ROM whether it is suitable or not. Different devices will also have different vendor audio hal, even the ROM is the same.

- If icon launcher doesn't show up, open the app via quick settings and tap 'Show icon in the app tray'

- To disable FX for loudspeaker, tap 'About' then tap multiple times the text or the image. This is also for Dolby Moto.

- If the FX is stopped sometimes, install this: https://github.com/reiryuki/AOSP-soundfx-Remover-Magisk-Module with Audio Modification Library Magisk module: https://t.iss.one/ryukinotes/34

- If you are using Samsung device and the FX is cracking, install this: https://github.com/reiryuki/Sound-Alive-FX-Remover-Magisk-Module and Audio Modification Library Magisk module: https://t.iss.one/ryukinotes/34

- If Moto Waves doesn't work caused by dirac or misoundfx, install this: https://github.com/reiryuki/dirac-misoundfx-Remover-Magisk-Module and Audio Modification Library Magisk module: https://t.iss.one/ryukinotes/34

- Only if you got problem with camera/flash light/wifi/bluetooth/cellular, wipe dalvik cache via recovery and reboot. If the issue still there, delete /data/adb/modules/MotoWaves/system/vendor/lib/libc++_shared.so, wipe dalvik cache and reboot.

- You can change any configuration settings under /data/adb/modules(_update)/MotoWaves/system/vendor/etc/maxx_conf.ini using any root manager.

- For Moto Waves automation: https://github.com/reiryuki/Sound-Mods-Automator


Optionals

You can create /data/media/0/optionals.prop file yourself if it's not exist yet (if you are not in user 0, then change the 0 to your current user) using @mtmanager or any file manager and write any modified settings bellow inside the optionals.prop file BEFORE INSTALLING/REINSTALLING THE MODULE:

- The sound effect is applied to rerouting and patch stream by default for game apps. You can disable it if there is a problem with it:

waves.game=0

- To use Moto Waves Edge 30 Pro (pstar) config instead (only for Moto Waves V2 XT and G 5G Plus):

waves.config=pstar

- To use Moto Waves Edge (racer) config instead (only for Moto Waves V2 XT and G 5G Plus):

waves.config=racer

- To use Moto Waves G 5G Plus (nairo) config instead (only for Moto Waves V2 XT):

waves.config=nairo

- To use Moto Waves XT (nio) config instead (only for Moto Waves G 5G Plus):

waves.config=nio

What is the different between them?
You tell me.

INSTALL/REINSTALL THE MODULE AFTERWARDS and reboot.

Sound Alive Optionals

You can create /data/media/0/optionals.prop file yourself if it's not exist yet (if you are not in user 0, then change the 0 to your current user) using @mtmanager or any file manager and write any modified settings bellow inside the optionals.prop file BEFORE INSTALLING/REINSTALLING THE MODULE:

- You can use these optionals bellow to disable some loaded soundfx in Sound Alive Magisk Module if it causes bootloop or no sound issue in your device.

To disable soundbooster fx:

sa.soundbooster=0

To disable mysound fx:

sa.mysound=0

To disable myspace soundfx:

sa.myspace=0

To disable dolby soundfx:

sa.dolby=0

To disable proxy soundfx:

sa.proxy=0

To disable volumemonitor soundfx (only if sa.proxy=0) :

sa.volumemonitor=0

Spatializer soundfx now is disabled by default to prevent bootloop/conflict. But if you still want to enable it:

sa.spatial=1

- You can also enable any #dolby_optionals here: https://t.iss.one/ryukinotes/8

INSTALL/REINSTALL THE MODULE AFTERWARDS and reboot.

Volume Booster Optionals

You can create /data/media/0/optionals.prop file yourself if it's not exist yet (if you are not in user 0, then change the 0 to your current user) using @mtmanager or any file manager and write any modified settings bellow inside the optionals.prop file BEFORE INSTALLING/REINSTALLING THE MODULE:

- The default volume boost is 100. You can apply any different value you want. For example, if you want to boost volume to 150:

volume.boost=150

Example if you want to boost volume to 96:

volume.boost=96

Example if you want to decrease volume to 50:

volume.boost=50

INSTALL/REINSTALL THE MODULE AFTERWARDS and reboot.

Mic Fix Optionals

You can create /data/media/0/optionals.prop file yourself if it's not exist yet (if you are not in user 0, then change the 0 to your current user) using @mtmanager or any file manager and write any modified settings bellow inside the optionals.prop file BEFORE INSTALLING/REINSTALLING THE MODULE:

You can change the microphone volume to ANY value you want.

This is just for example if you want to change microphone volume  to 7:

mic.volume=7

REINSTALL THE MODULE AFTERWARDS and reboot.

AM3D Zirene Sound Optionals

You can create /data/media/0/optionals.prop file yourself if it's not exist yet (if you are not in user 0, then change the 0 to your current user) using @mtmanager or any file manager and write any modified settings bellow inside the optionals.prop file BEFORE INSTALLING/REINSTALLING THE MODULE:

- The sound effect is applied to rerouting and patch stream by default for game apps. You can disable it if there is a problem with it:

am3d.game=0

INSTALL/REINSTALL THE MODULE AFTERWARDS and reboot.

Arkamys Audio Troubleshootings

- Arkamys audio is only apply FX for internal speaker. If you want to apply the FX to headphone and Bluetooth audio also, you can enable/disable it by using terminal command. Type:

su
akm

Then read and follow the guide there. Example: https://t.iss.one/androidryukimods/1410.

DTS Troubleshootings

- The sound effect can cause no sound issue in unsupported device audio service.

- No support for PUBG Mobile mic issue nor any other else game mic issue

- If you are using Samsung device and the FX is cracking, install this: https://github.com/reiryuki/Sound-Alive-FX-Remover-Magisk-Module and Audio Modification Library Magisk module: https://t.iss.one/ryukinotes/34

- Doesn't work with music player which forcing to compress offload playback like in-built Mi Music on Miui ROM

- DTS must change/spoof your ro.product.model to pass the license check. This may create some issues like in stock rom camera etc. There is no workaround for this.

- DTS is working in enforcing for my device. If it's not working for your device then read #bug_report notes.

- To turn off Audio Wizard service, run terminal:

su

am stop-service com.asus.maxxaudio/.AudioWizardService
killall com.asus.audiowizard

- To turn on Audio Wizard service, run terminal:

su

am start-service com.asus.maxxaudio/.AudioWizardService
killall com.asus.audiowizard


Optionals

You can create /data/media/0/optionals.prop file yourself if it's not exist yet (if you are not in user 0, then change the 0 to your current user) using @mtmanager or any file manager and write any modified settings bellow inside the optionals.prop file BEFORE INSTALLING/REINSTALLING THE MODULE:

- To use DTS Ultra UI from ZTE instead of Audio Wizard UI in Audio Wizard Asus Zen 6 Magisk Module:

dts.zte=1

- If you have problem with ro.build.product changes, you can enable library patch:

dts.patch=1

But sometimes this makes dts license check failure on some devices.

- The sound effect is applied to rerouting and patch stream by default for game apps. If you don't want it, you can disable it:

dts.game=0

INSTALL/REINSTALL THE MODULE AFTERWARDS and reboot.