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

- Swipe down for notification panel and closing app animation doesn't work except the OPlus Launcher is used as recents provider. To enable the recents provider (for Android 14 and up only):

oplus.recents=1

Don't use this kind of module @QuickstepSwitcherReleases

INSTALL/REINSTALL THE MODULE AFTERWARDS and reboot.


Troubleshootings

- You may need to disable your built-in launcher and reboot afterwards if it's conflicting with OPlus Launcher recents provider.

- If your device using hardware navigation bar, run this terminal command to remove the empty space at the bottom screen:

su

settings put secure settings_navigation_bar_combination 2

To reverse it back just change the value 2 to 0.

ZRAM Swap Configurator Optionals

What's ZRAM Swap? Read this: https://news.1rj.ru/str/ryukinotes/58. For more detailed information, please read it at Android & Google documentation instead! This module is a tool for advanced users only. There will never recommendations nor restrictions. All at user respective policies. Do not use this if you don't even know what is this! DwYOR!

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:

ZRAM Swap Configurator resizes your device ZRAM Swap disk to 3 GB as default. But you can use ANY different value. M for Mega Byte. G for Giga Byte. This bellow is for example only. You can modify to any M or G value you want:

- Example to resize your device ZRAM disk to 768 MB instead:

zram.resize=768M

- Example to resize your device ZRAM disk to 4 GB instead:

zram.resize=4G

You can also use percentage (%) of RAM size as ZRAM size. This bellow is for example only. You can modify to any percent (%) you want:

- Example to resize your device ZRAM disksize to 75% of RAM size instead:

zram.resize=75%

- Example to resize your device ZRAM disksize equals to RAM size instead:

zram.resize=100%

- Disables your device ZRAM disk instead:

zram.resize=0

You can also change the comp_algorithm instead of your default kernel/ROM/device setting. Example of algorithm from newer to older is zstd, lz4, lzo, & deflate. This bellow is for example only. You can modify to any type of algorithm you want, DEPENDING ON YOUR KERNEL SUPPORT:

- Example to change your device ZRAM comp_algorithm to zstd instead:

zram.algo=zstd

- Example to change your device ZRAM comp_algorithm to lz4 instead:

zram.algo=lz4

- Swap priority is set to 0 by default. You can also set higher priority. For example, if you want to change priority to 5:

zram.prio=5

- /proc/sys/vm/swappiness is set to 100 by default. If you want to set a lower value like 99 for example:

zram.swps=99

- If you want to enable /proc/sys/vm/swap_ratio_enable:

zram.swpre=1

- This setting can only be set if zram.swpre=1. If you want to change /proc/sys/vm/swap_ratio to 99 for example:

zram.swpr=99

- swap_free_low_percentage is set to 1 by default. If you want to set another value like 3 for example:

zram.sflp=3

- If you don't want swap_free_low_percentage to be set and let ROM default setting:

zram.sflp=def

- swap_util_max is set to 99 by default. If you want to set another value like 90 for example:

zram.sum=90

- If you don't want swap_util_max to be set and let ROM default setting:

zram.sum=def

- swap_compression_ratio is set to 0 by default. If you want to set another value like 2 for example:

zram.scr=2

- If you don't want swap_compression_ratio to be set and let ROM default setting:

zram.scr=def

REINSTALL THE MODULE AFTERWARDS and reboot.

Miui App Vault global mode

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

Notes:
- Do not use the same prop names with different value! For example if you are using dolby.bass=96 then you cannot use dolby.bass=true nor dolby.bass=false nor dolby.bass=def.
- THESE OPTIONALS ARE NOT FOR SHOWING TOGGLERS < read this please

- To skip vendor manifest patch only if it causes bootloop/softbrick (don't use this if it's not!):

dolby.skip.vendor=1

- To skip system manifest patch if it causes bootloop/softbrick (don't use this if it's not!):

dolby.skip.system=1

- To skip system_ext manifest patch if it causes bootloop/softbrick (don't use this if it's not!):

dolby.skip.system_ext=1

- If using early mount causes device bootloop/softbrick (don't use this if it's not!):

dolby.skip.early=1

- Some Dolby modules are modifiying blobs at installation to fix conflict with in-built Dolby or any other else Dolby module like DDP. But if it doesn't work or if you still want to use original unmodified blobs:

dolby.mod=0

If you want to use modified blobs and this will also fix storage issue:

dolby.mod=1

- To fix sensors issue (fingerprint, proximity, gyroscope, etc):

dolby.fix.sensor=1

This causes bootloop in some ROMs.

- For Dolby Audio Moto G Pro, if you don't want ro.product.brand changes/spoofs, you can use older/legacy libswdap.so instead:

dolby.legacy=1

- For Dolby Moto G Pro and OnePlus 8 Visible, if default libraries doesn't work in your ROM, you can use old libraries instead:

dolby.10=1

- For Mi Sound Dolby, if it's not working or if you don't want ro.product changes/spoofs, you can use libswdap.so from rhode instead of the original one:

dolby.rhode=1

- For Dolby Atmos Spatial Sound Moto Edge 30 Ultra, you can disable the Dolby Atmos and use the Spatial Sound only:

moto.dolby=0

- The default max_edit_gain in Dolby Moto Edge 30 Ultra, G52, & G Pro is 192. You can use higher max_edit_gain from 193 until 576 using dolby.gain=<your_value>. For example to change max_edit_gain to 384:

dolby.gain=384

For other Dolby (except MiSound Dolby), value greater than 192 will be activating max/min limit 36 dB.

- To enable deeper bass GEQ frequency:

dolby.deepbass=1

- To disable deeper bass GEQ frequency:

dolby.deepbass=0

- Force enable bass boost enhancer and changing the values (all profile):

dolby.bass=96

You can try a different value like 48 or 192 or any value you want. The minimum value is 1. No limit for maximum value. 0 means unmodified.

- If you just want to force enable bass boost enhancer without changing the default values:

dolby.bass=true

- Force disable bass boost enhancer (all profile):

dolby.bass=false

- Let bass boost enhancer with the default vendor settings:

dolby.bass=def

- Volume leveler is disabled by default. To force enable volume leveler settings (all profile):

dolby.volumeleveler=1

- Using original volume leveler settings :

dolby.volumeleveler=def

- Force enable virtualizer for all profile:

dolby.virtualizer=1

- Force disable virtualizer for all profile:

dolby.virtualizer=0

- For Dolby Atmos ZTE A2019 Pro, you can use apps from Razer instead:

dolby.razer=1

- For Dolby Atmos OnePlus 8 Visible, you can use DaxUI instead of OPSoundTuner. This will fix UI force close while enabling bluetooth audio:

dolby.daxui=1

- For Dolby Audio Moto G6, you can use black theme UI instead of newer white theme:

dolby.blackui=1

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

dolby.game=0

INSTALL/REINSTALL THE MODULE AFTERWARDS and reboot.

Dolby Troubleshootings 2

- Dolby service fail to run in some devices if dolby manifest.xml is patched in /system_ext. If it happens, then remove Dolby and restore your original manifest.xml using Manifest Restore Magisk Script: https://github.com/reiryuki/Manifest-Restore-Magisk-Script and reboot afterwards, use Kitsune Mask, then use optionals.prop dolby.skip.system_ext=1 and reinstall Dolby.

Dolby service also fail to run in some devices if dolby manifest.xml is patched in /vendor. If it happens, then remove Dolby and restore your original manifest.xml using Manifest Restore Magisk Script: https://github.com/reiryuki/Manifest-Restore-Magisk-Script and reboot afterwards, use Kitsune Mask, then use optionals.prop dolby.skip.vendor=1 and reinstall Dolby.

- Dolby Atmos Magic Revision will not conflict with any other else Dolby so you don't need to remove Dolby Atmos Magic Revision to install any other else Dolby.

- Magisk Alpha causes bootloop in Dolby modules which require manifest.xml patch. I don't know why. Use official Magisk instead.

- If you want to disable your Dolby in-built ROM instead, just disable/freeze daxService app and reboot afterwards. But you don't need to do this if you want to install my Dolby modules.

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

Dolby Troubleshootings

- Recommended to use Kitsune Mask in Read-Only ROMs https://news.1rj.ru/str/ryukinotes/49 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, your device will BOOTLOOP.

Another option:

If you are using Magisk official, If ROM is Read Only when installing via app, then try to install via Recovery.

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/noscript-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 https://github.com/HuskyDG/magic-mount 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 need 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://news.1rj.ru/str/androidryukimodsdiscussions/112081 then read #dolby_troubleshootings_2 https://news.1rj.ru/str/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 noscript. 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 noscript 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.

RULES

- You have to solve the math by Shieldy bot quickly to join this group first, otherwise you will be kicked (there is no ban nor block) by the bot and you can try again next time.

- For APK UI modder of my audio mod modules, you can share your modded UI apk only and you have to use mod.ui=1 feature in #global_optionals. Not allowed to duplicate my modules.

- Make sure you are read all changelogs I wrote in pling, so you don't need to be confused by old chats that are no longer valid

- Not allowed to bring personal problems/asking pirated stuffs/advertisement/ads/advertising/spamming/swear words/bothering other member.

- Sharing stickers/links/images/files are forbidden to ensure the security of this group. But you can boost https://news.1rj.ru/str/boost/androidryukimodsdiscussions to remove the restrictions.

- Not allowed to run any bot noscript to this group because it's spamming to admin "Recent actions"

- Please read the README, /notes, #mods https://news.1rj.ru/str/ryukinotes/67, #faqs https://news.1rj.ru/str/ryukinotes/31, & search Google first before asking anything and before you're being annoying.

- Read here if you don't wanna be banned: https://news.1rj.ru/str/androidryukimods/536

- Always use English. If you can't speak English, use this: https://play.google.com/store/apps/details?id=com.google.android.apps.translate . If you still don't understand, go to PM instead. Allowed to use any other else language only if replying to any other member (if they are understand the language). Otherwise it is still not allowed and the thread will be deleted.

- Discussing about any Android development is allowed.

- Respect each other's opinion.

- I am NOT responsible for my modules that is obtained outside of my www.pling.com/u/reiryuki

- Telling/reporting bug/issue/saying "I have the same issue" without sending required files in #bug_report or #bug_report_bootloop is not allowed and will get warns immediately.

- Always remember that Root = DwYOR!

- TAGGING AUTHOR WITHOUT SENDING A COMPLETE #bug_report or #bug_report_bootloop FILES IS NOT ALLOWED AND WILL GET WARNS

- Sending crash link only without sending full #logcat will also be warned (even you delete the message afterwards or left)

- DO NOT ASKING DOES IT WORK ON/IS IT WORKING ON/WORKS IN/COMPATIBLE WITH/SUPPORT FOR/MODULE FOR/CAN IT BE USED ON/IS IT SAVE FOR! Please read requirements and give it a try instead!

- DO NOT PM ADMIN FOR REQUEST! Type to this group here instead!

- You can introduce my modules in any platform of yours but do not re-upload my files. Re-uploading every files from pling.com/u/reiryuki is not allowed anywhere. Every files in pling.com/u/reiryuki is licensed. Do not re-upload my files that are already uploaded to pling.com/u/reiryuki. Put the pling.com/u/reiryuki/ link instead.

- You can modify my modules for yourself only but not allowed to share it publicly. If you want to suggest any better change, just pull a request there or open a discussion.

- Do not mention @reiryuki in your github commit if it's referring to my repositories! Just put the repo link instead!

- Pornography and racism will be immediately banned

- Anyone using LGBTQ symbols/text in it's name, bio, user name/ID, display picture, sticker, gif, or video will be banned instantly. Please go to psychologist instead.

- If a violation is found, admins will give warns up to an instant permanent ban.

- Asking to be an admin with no reason will be banned instantly.

- Impersonating to another member will be banned instantly.

- Slandering about viruses/trojans/malware against my files will result in a warning until ban. Please read #false_positive notes!

- If you find a member bothering you, don't answer anything but just report to admins.

- Due to large number of scams and spams using China language, the use of China language in this group will be automatically banned.

- Be careful of scammers/fraudsters/psychopaths on Telegram that offers fake jobs or helps. Block them and report to admin.