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://news.1rj.ru/str/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://news.1rj.ru/str/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.

My Mods

Don't forget to read the denoscriptions first before installing!

- https://www.pling.com/u/reiryuki
- https://github.com/reiryuki?tab=repositories

For any alpha or beta version, search for #alpha or #beta tag (that is not in notes but find it on search) @androidryukimodsdiscussions. I will not include changelog at it.

Version Grades

Alpha = Untested experimental version or tested and works with only 1 device. May still buggy for any other else devices.

Beta = Tested and works with 3 or more devices. Still buggy for some devices.

Stable = Tested and works with many more devices.

Any alpha or beta version will be uploaded with #alpha or #beta tag. That's not in /notes but you can find it in search. I will not include changelog at it. If the stable version is uploaded at pling, then the #alpha and #beta version will be deleted.

Oreality 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:

oreality.game=0

INSTALL/REINSTALL THE MODULE AFTERWARDS and reboot.

AudioFX LineageOS Troubleshootings

- If AudioFX doesn't work, then type:

  su
  afx
 
  at Terminal/Termux app while playing music

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

Magisk Install Log

Do not report if the Magisk/KernelSU install log says your ROM is unsupported nor service not found except the author is asking for it otherwise you will get warns! (unless it was supported in previous versions)

Do not send screenshot only!

If it's a Magisk Module, after installing the module, tap the top right corner of the Magisk app. It will be saved to your Download folder. See this: https://news.1rj.ru/str/androidryukimods/141 Send me the file. This is MAGISK/KERNELSU INSTALL LOG. DO NOT send MAGISK/KERNELSU LOG because it's not related!

Send it PM to @reiryuki

Logcat

Install this Logcat Reader app: https://github.com/darshanparajuli/LogcatReader/releases.

Before you open the Logcat app, install Termux first, and run this command:

su -c pm grant com.dp.logcatapp android.permission.READ_LOGS

Or run adb via PC:

adb shell pm grant com.dp.logcatapp android.permission.READ_LOGS

Another method if pm grant command is failed: https://news.1rj.ru/str/androidryukimodsdiscussions/113604

Open the app, go to settings > Buffers > checklist all (ignore if there is not), trigger the bugs so logcat can record the bugs, tap top right corner, tap save, share it to the author the saved logs. About 1 MB minimum and do not more than 10 MB. Do not filter! Do not type anything in search! FULL logcat is needed. Do not archive nor zip! If the log is still showing nothing, then use any other else logcat app.

Send it PM to @reiryuki

The Main Requirements to Install My Magisk Modules

- Using TWRP that can decrypt your /data, so you can disable modules via TWRP if bootloop/brick is occured. If you don't have TWRP for your device, then you can reflash your original boot.img via fastboot and format data if bootloop/brick is occured. Otherwise, please go out of here and don't talk to me.
- A working brain 🧠
- Not a psychopath
- Want to read the README
- DwYOR (Do with Your Own Risk!)

Touch Boost Disabler 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 other else root file manager and write any modified settings bellow inside the optionals.prop file BEFORE INSTALLING/REINSTALLING THE MODULE:

- To enable touch boost instead of disable

touch.boost=1

INSTALL/REINSTALL THE MODULE AFTERWARDS and reboot.

Mi 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 other else root file manager and write any modified settings bellow inside the optionals.prop file BEFORE INSTALLING/REINSTALLING THE MODULE:

- If you are in Miui ROM and don't want to use the Dolby Atmos:

misound.dolby=0

- To disable in-built Harman Kardon:

misound.harmankardon=0

- If MiSound app conflicted with your * Parts app, you can hide the * Parts app:

hide.parts=1

or you can simply disable your * Parts app using any root disabler/freezer and reboot. Usually * Parts app not only contains Dirac/MiSound but also contains some other ROM features. Hiding/disabling it will also remove those ROM features.

- You can reset the Mi Sound data:

data.cleanup=1

- You can also enable any #dolby_optionals here: https://news.1rj.ru/str/ryukinotes/8

INSTALL/REINSTALL THE MODULE AFTERWARDS and reboot.


Troubleshootings

- On Miui ROM, sidebar and toggle in all apps must be enabled before installing mi sound module. If you try to enable or disable it after installing the module, the sound will crack. Don't make any changes to Harman Kardon nor Mi Sound Equalizer also.

- If your built-in MiSound app does not show up after removing/disabling the module, run Terminal/Termux:

su

rm -rf /data/system/package_cache/* /data/dalvik-cache/* /data/user*/*/com.android.settings/* /data/user*/*/com.miui.misound/* /data/user*/*/se.dirac.acs/*

Reboot.

- Any workaround for the Dolby Atmos is the same as #dolby_troubleshootings notes: https://news.1rj.ru/str/ryukinotes/11

Dirac 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 other else root 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:

dirac.game=0

INSTALL/REINSTALL THE MODULE AFTERWARDS and reboot.

How to disable Android Signature Verifications?

WARNING!!!
Disabling Android Signature Verification may be unstable for some ROMs. You may need any permissiver if it causes auto reboot. What is permissiver? Google it.

Some of my apps inside modules are using android.uid.system like Miui Security and Miui Screen Recorder. This method can be a workaround to allow installation of any android.uid.system apps. If these methods bellow doesn't work in your stock ROM, then use custom ROM instead! Choose one of these modes bellow:

Riru LSPosed/EdXposed/Taichi Magisk Module/Xposed Framework mode:

- Download and install Riru Magisk Module and Riru LSPosed or EdXposed or Taichi Magisk module or Xposed Framework at github or anywhere if it has it's own website.

- Install Lucky Patcher app https://www.luckypatchers.com/download/ and use it as framework module or use any other else framework app module that can be disabling your Android Signature Verifications.

- Riru LSPosed, EdXposed, and Xposed Framework may breaks your safetynet but don't worry, there is Play Integrity Fix Magisk module Zygisk mode or Riru mode at github (don't download outside of GitHub for safety).

LP Magisk Module mode:

1) Install Lucky Patcher app https://www.luckypatchers.com/download/

2) Tap Toolbox > Patch to Android

3) Checklist "Use the Magisk module to apply the patch" or "Use Magisk module - Zygisk" (Do not check the "only patch dalvik-cache" nor patching directly to framework odex, it will cause some issues).

4) Checklist "Signature verification status always true", "Disable .apk Signature Verification", and "Disable signature verification in the package manager"

5) Tap Apply (will take long time)

6) Reboot

If it's still failed (even it's showing success) then use AOSP signatured ROM instead eg Pixel Experience. AOSP signatured ROM example: https://news.1rj.ru/str/androidryukimodsdiscussions/190038

Resign APK with ROM Owner Platform Keys mode:

If you are the owner of your own ROM or you have the platform keys of the ROM that you are using, then just resign the APK which requires signature matching so you don't need to disable the signature verification.

You can try any other else method instead like Core Patch or whatever you like if the method above doesn't work.

Moto Troubleshootings

For Dolby Moto, go here: https://news.1rj.ru/str/ryukinotes/11

For Moto Waves, go here: https://news.1rj.ru/str/ryukinotes/59

- If search location function doesn't work in Moto Widget, go to app info of Moto Widget and allow the network access

- If you are in Miui ROM, open the Moto Widget app settings, tap recents button, lock the Moto Widget app from recents to keep the app running in background


Moto 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 to activate Moto Launcher recents provider (doesn't work in some ROMs):

moto.recents=1

Don't use this kind of module @QuickstepSwitcherReleases

- You can enable camera HAL 3, EIS, & OIS with Moto Cam Magisk Module:

camera.prop=1

INSTALL/REINSTALL THE MODULE AFTERWARDS and reboot.

SKIA UI Renderer Enabler 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 other else root file manager and write any modified settings bellow inside the optionals.prop file BEFORE INSTALLING/REINSTALLING THE MODULE:

- To disable SKIA renderer instead of enable:

skia.enable=0

INSTALL/REINSTALL THE MODULE AFTERWARDS.

ANR Timeout Multiplier 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 other else root file manager and write any modified settings bellow inside the optionals.prop file BEFORE INSTALLING/REINSTALLING THE MODULE:

The default Android ANR timeout is 5 seconds and this module multiplies the timeout 12 times means 12 x 5 seconds = 60 seconds. You can change the timeout to any value you want.

This is for example to use timeout 3 times that means 3 x 5 seconds = 15 seconds:

anr.timeout=3

INSTALL/REINSTALL THE MODULE AFTERWARDS and reboot.

Device Features Enabler 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:

- Using android.hardware.ram.low to allow installing any Go version of Google apps at Play Store:

dfe.ram.low=1

INSTALL/REINSTALL THE MODULE AFTERWARDS and reboot.

Port Magisk module to ROM

- If you want to port my Magisk Module to your ROM, you need to include files (or add lines to the existing files) inside "unused" folder also (if there is "unused" folder inside the module).

- Implementing sepolicy.rule into ROM Building:

For example in sepolicy.rule:

allow priv_app hal_dms_hwservice hwservice_manager find

then you need to write:

allow priv_app hal_dms_hwservice:hwservice_manager { find };

in your priv_app.te while building ROM