Ryuki Notes

File Download Tutorial - Open the link via browser not via Telegram. - Make sure you've disabled your ad blockers in your Settings app or browser or anywhere first. Don't use dns.adguard.com nor https://dns.adguard-dns.com/dns-query DNS otherwise the genarated links won't be shown. - Watch https://youtu.be/l2CUt0L5qD4?si=HDKPEoEokdFQkJoS or https://vt.tiktok.com/ZS4SfS6Mw/ - If generated link still not showing or you can't access bicolink.com or devuploads.com then try to change DNS to 1dot1dot1dot1.cloudflare-dns.com or dns.google or use VPN instead. - "Gateway time-out Error code 504" means the server is under maintenance. Wait until next 24 hours. - If you find an inactive link, then please PM to @reiryuki. - If you still can't access the files or you don't even like waiting, then you can pay 1 USD instead to @reiryuki for 1 month of all files access and the files will be sent directly in a private group. (Khusus region Indonesia, 10000 IDR untuk 1 bulan.)

Storage Fix Script This is Termux/Terminal command to fix storage permissions in com.google.android.apps.photos. You can change the PKG= to any other else package name you want that has storage issue. Type su first and grant root access. su grant_permission() { pm grant $PKG android.permission.READ_EXTERNAL_STORAGE pm grant $PKG android.permission.WRITE_EXTERNAL_STORAGE if [ "$API" -ge 29 ]; then   pm grant $PKG android.permission.ACCESS_MEDIA_LOCATION   appops set $PKG ACCESS_MEDIA_LOCATION allow fi if [ "$API" -ge 33 ]; then   pm grant $PKG android.permission.READ_MEDIA_AUDIO   pm grant $PKG android.permission.READ_MEDIA_VIDEO   pm grant $PKG android.permission.READ_MEDIA_IMAGES fi appops set $PKG LEGACY_STORAGE allow appops set $PKG READ_EXTERNAL_STORAGE allow appops set $PKG WRITE_EXTERNAL_STORAGE allow appops set $PKG READ_MEDIA_AUDIO allow appops set $PKG READ_MEDIA_VIDEO allow appops set $PKG READ_MEDIA_IMAGES allow appops set $PKG WRITE_MEDIA_AUDIO allow appops set $PKG WRITE_MEDIA_VIDEO allow appops set $PKG WRITE_MEDIA_IMAGES allow if [ "$API" -ge 30 ]; then   appops set $PKG MANAGE_EXTERNAL_STORAGE allow   appops set $PKG NO_ISOLATED_STORAGE allow   appops set $PKG AUTO_REVOKE_PERMISSIONS_IF_UNUSED ignore fi if [ "$API" -ge 31 ]; then   appops set $PKG MANAGE_MEDIA allow fi if [ "$API" -ge 34 ]; then   appops set "$PKG" READ_MEDIA_VISUAL_USER_SELECTED allow fi appops get $PKG UID=$(grep "^$PKG " /data/system/packages.list | awk '{print $2}') if [ "$UID" ] && [ "$UID" -gt 9999 ]; then   appops set --uid "$UID" LEGACY_STORAGE allow   appops set --uid "$UID" READ_EXTERNAL_STORAGE allow   appops set --uid "$UID" WRITE_EXTERNAL_STORAGE allow   if [ "$API" -ge 29 ]; then     appops set --uid "$UID" ACCESS_MEDIA_LOCATION allow   fi   if [ "$API" -ge 34 ]; then     appops set --uid "$UID" READ_MEDIA_VISUAL_USER_SELECTED allow   fi   appops get --uid "$UID" fi } prepare_dir() { mkdir -p /storage/emulated/"$USR"/Android/data/$PKG/cache mkdir -p /storage/emulated/"$USR"/Android/data/$PKG/files } API=$(getprop ro.build.version.sdk) USR=$(id -u) [ ! "$USR" ] && USR=0 PKG=com.google.android.apps.photos grant_permission prepare_dir echo done

Hardware Services Restarter 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 have sensors issue while using any Dolby modules etc.: hsr.sensor=1 The following is for advanced users only. Always be prepared for the possibility of a bootloop/brick/permanent damage to your device and Do with Your Own Risk! - Example if you need to add and restart some hardware/vendor processes that are not listed yet in the module (if more than one, then separate with a space): hsr.add=process-name another-process-name - Example if you need to add and restart some hardware/vendor init services that are not listed yet in the module (if more than one, then separate with a space): hsr.add_init=init-service-name another-init-service-name INSTALL/REINSTALL THE MODULE AFTERWARDS and reboot.

Global Troubleshootings 2 - If apps from modules are not installed after updating ROM, then: 1. Remove the modules and reboot first 2. Normal install all apps from modules 3. Uninstall those apps again (this is the major fix) 4. Reinstall modules and reboot - In Magisk when device bootloops, se_context in all /data/adb/modules/ folders changes from system_file to adb_data_file which causes modules to not install properly afterwards and must be reinstalled. You can use this script for preventive measures: https://github.com/reiryuki/Broken-Modules-Remover-Magisk-Script - If Magisk root grant request pop up doesn't appear, then try to exclude the Magisk app from battery optimization. If you faced no sound or low sound issue on some apps while using any audio mod modules or you don't want audio mod affects your game app and notification/ringtone sound, then use this: https://github.com/reiryuki/Audio-Compatibility-Patch-Reborn-Magisk-Module

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

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.

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.

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.

Moto Troubleshootings For Dolby Moto, go here: https://t.me/ryukinotes/11 For Moto Waves, go here: https://t.me/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.

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://t.me/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.

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.

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://t.me/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://t.me/ryukinotes/11

Introducing new optionals method. Newer versions are no longer using terminal emulator command but using optionals.prop file in your /data/media/0/ (if you are not in user 0, then change the 0 to your current user). For example, see the screenshots. Create the optionals.prop file by yourself if it doesn't exist using @mtmanager or any other else root file manager. PLEASE DO NOT PUT/EDIT/WRITE IT IN /sdcard NOR /storage/emulated/0 NOR INTERNAL STORAGE BECAUSE IN SOME DEVICES, /sdcard OR /storage/emulated/0 OR INTERNAL STORAGE DOES NOT MIRROR TO /data/media/0. Read Optionals in the README of module at Github (all is lower case and no upper case). INSTALL/REINSTALL MODULE TO TAKE EFFECT.

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.

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!)

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 killall logcat pm grant com.dp.logcatapp android.permission.READ_LOGS Or run adb via PC: adb shell killall logcat adb shell pm grant com.dp.logcatapp android.permission.READ_LOGS Another method if pm grant command is failed: https://t.me/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. If the log is still showing nothing, then use any other else logcat app. Please don't put the logcat into zip/compressed file. Send it PM to @reiryuki

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://t.me/androidryukimods/141 Send me the file. This is MAGISK/KERNELSU INSTALL LOG. DO NOT send MAGISK/KERNELSU LOG because it's not related! Please don't put the file into zip/compressed file. Send it PM to @reiryuki

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.

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.