After updating my Huawei Mate S to Android Marshmallow EMUI 4.0.1 (CRR-L09C432B361) I am having screen overlay issue. Sorry, I can't give screenshot. Gallery, facebook upload, Gmail etc. are not working properly. I am getting a message like this- "Screen overlay detected- To change this permission setting you first have to turn off the screen overlay from Settings > Apps". When I click on Settings tab, it takes me to a settings section named "Draw over other apps". When I click on the relevant app, I find some of their permissions denied, which I can't turn on. I did some googling and found some other related posts mostly indicating to disable some kind of screen filtering apps or clean master which I don't have. Tried resetting, then wiping cache data, didn't fix. Tried disabling developer options, didn't work. Can anyone help to solve this issue.
As you probably know by now & as I understand it, this is a security measure, which will trigger Marshmallow to pop-up 'Screen overlay detected...' warnings each time you try to change an app's permissions (i.e. for the apps that are affected by this 'drawing over other apps' feature).
There are 2 ways to get around this so you are allowed to freely change apps' permissions (do one or the other - whichever is more convenient for you):
1. Go to Settings > Apps > access 'Advanced' (near the bottom) > under 'Advanced' subsection, access 'Draw over other apps'. Here, individually change the settings of ALL the apps to 'No' (in other words, disable 'Permit drawing over other apps' for every app). Once done, you can freely change apps' permissions in Settings > Apps > [name of app] > 'Permissions' without the annoying 'Screen overlay detected...' warning popping-up every time. Once you have correctly changed the permissions (for every app that's not working properly), you should return to individually change each of the apps' settings to 'Yes' in the 'Draw over other apps' section (in other words, re-enable 'Permit drawing over other apps' for every app).
or (easier for me)
2. Reboot your phone into Safe Mode (click here if you need to know how). Once in Safe Mode, you can freely change apps' permissions in Settings > Apps > [name of app] > Permissions without the annoying 'Screen overlay detected...' warning popping-up every time. Once you have correctly changed the permissions (for every app that's not working properly), restart the phone as normal.
For both of the above & If you prefer, all changeable apps' permissions can also be easily done via Settings > Apps > access 'Advanced' (near the bottom) > access 'App permissions'.
If some apps are still not working as they should, check to see that the affected apps have 'Yes' below their name in the Apps > Advanced > 'Draw over other apps' section, AND they have ALL their permissions enabled under the Settings > Apps > [name of app] > 'Permissions' section.
GaT7 said:
As you probably know by now & as I understand it, this is a security measure, which will trigger Marshmallow to pop-up 'Screen overlay detected...' warnings each time you try to change an app's permissions (i.e. for the apps that are affected by this 'drawing over other apps' feature).
There are 2 ways to get around this so you are allowed to freely change apps' permissions (do one or the other - whichever is more convenient for you):
1. Go to Settings > Apps > access 'Advanced' (near the bottom) > under 'Advanced' subsection, access 'Draw over other apps'. Here, individually change the settings of ALL the apps to 'No' (in other words, disable 'Permit drawing over other apps' for every app). Once done, you can freely change apps' permissions in Settings > Apps > [name of app] > 'Permissions' without the annoying 'Screen overlay detected...' warning popping-up every time. Once you have correctly changed the permissions (for every app that's not working properly), you should return to individually change each of the apps' settings to 'Yes' in the 'Draw over other apps' section (in other words, re-enable 'Permit drawing over other apps' for every app).
or (easier for me)
2. Reboot your phone into Safe Mode (click here if you need to know how). Once in Safe Mode, you can freely change apps' permissions in Settings > Apps > [name of app] > Permissions without the annoying 'Screen overlay detected...' warning popping-up every time. Once you have correctly changed the permissions (for every app that's not working properly), restart the phone as normal.
For both of the above & If you prefer, all changeable apps' permissions can also be easily done via Settings > Apps > access 'Advanced' (near the bottom) > access 'App permissions'.
If some apps are still not working as they should, check to see that the affected apps have 'Yes' below their name in the Apps > Advanced > 'Draw over other apps' section, AND they have ALL their permissions enabled under the Settings > Apps > [name of app] > 'Permissions' section.
Click to expand...
Click to collapse
Thanks mate for ur detailed instructions, it's solved and I am relieved...
plesae help
Feroztex said:
Thanks mate for ur detailed instructions, it's solved and I am relieved...
Click to expand...
Click to collapse
one does not work for me
I have a problem after update to B361, I can't use somes apks with my internet data (only with Wifi) like Youtube, Pokemon Go, Snapchat.
I checked and every app have all the permissions (incluyed internet data permissions) so I don't know what to do.
Any help?
Hi,
Try to flash this by TWRP Recovery, it should fix Screen overlay permissions
http://www.mediafire.com/?ouxua6rkkagi3g9
edzamber said:
Hi,
Try to flash this by TWRP Recovery, it should fix Screen overlay permissions
http://www.mediafire.com/?ouxua6rkkagi3g9
Click to expand...
Click to collapse
Don't you need the phone to be rooted to do that?
I suspect most users would have an unrooted phone.
GaT7 said:
Don't you need the phone to be rooted to do that?
I suspect most users would have an unrooted phone.
Click to expand...
Click to collapse
No, just need twrp Recovery or similar
edzamber said:
Hi,
Try to flash this by TWRP Recovery, it should fix Screen overlay permissions
http://www.mediafire.com/?ouxua6rkkagi3g9
Click to expand...
Click to collapse
Thanks man! it worked...do you have problems with apps using mobile data?? beacause i have somes apps that only works with wifi and every app is with all permissions
edzamber said:
Hi,
Try to flash this by TWRP Recovery, it should fix Screen overlay permissions
http://www.mediafire.com/?ouxua6rkkagi3g9
Click to expand...
Click to collapse
What exactly does this do? Install GooglePackageInstaller?
xdapowerapps said:
What exactly does this do? Install GooglePackageInstaller?
Click to expand...
Click to collapse
no, install from TWRP mode, it works for me, thanks my friend
edzamber said:
Hi,
Try to flash this by TWRP Recovery, it should fix Screen overlay permissions
http://www.mediafire.com/?ouxua6rkkagi3g9
Click to expand...
Click to collapse
Will this also work on Nougat? Running resurrection remix 5.8 on Mi max Hydrogen. Running LMT Pie launcher prevents me from granting any permissions or sideloading any APKs. Is this specifically for the Mate S?
If it's safe to flash on nougat on the Mi Max, I could try it on Mi Max.
I did some research and found a way to make the quick settings tiles disappear on the lock screen. Note that your device needs to be rooted using either SuperSu or Magisk.
The first thing you have to do is download Tasker.
On the Tasker app, make a new profile
Event --> Display --> Display Off
Now make a task, we will name this task "Hide Tiles"
New Task --> Code --> Run Shell
Now important, if you're rooted with SuperSu then use the first code, if you're rooted with Magisk then use the second one.
First code is (without quotes): "settings put secure sysui_qs_tiles 0"
Second code is (WITH quotes): /sbin/su -c "settings put secure sysui_qs_tiles 0"
This is the profile that will hide the tiles when the phone is locked, now we need a profile where it shows them after the password/fingerprint is used on the phone.
Go ahead and create a new profile
Event --> Display --> Display Unlocked
Now make a task, we will name it "Show Tiles"
(SuperSu uses the first code, Magisk uses the second one)
New Task --> Code --> Run Shell
First code (without quotes): "settings put secure sysui_qs_tiles wifi,cell,location,dnd,rotation,bt,battery,flashlight,hotspot,airplane,inversion,saver,cast"
(From the screenshot you will learn which name refers to which tile, you can then add/remove/reorder them however you want)
Second code (WITH quotes): /sbin/su -c "settings put secure sysui_qs_tiles wifi,cell,location,dnd,rotation,bt,battery,flashlight,hotspot,airplane,inversion,saver,cast"
If these codes don't work with Tasker, you can use them in Secure Settings but instead of (New Task --> Code --> Run Shell) you have to do (New Task --> Plugin --> Secure Settings --> Configuration --> Action --> Run Command)
The code you'll have to use is the one we used for Supersu (it will work for both Magisk and SuperSu users) but make sure you check the USE ROOT box)
I have tried this on a Nexus 5X running Oreo 8.1 OPM3 and it works every single time.
Let me know if you have tried this on your phone so we'd know which devices it works on. Thank you!
nice, but too bad it crashes on miui based roms
Worked with Secure Settings an Oneplus 3t, Skydragon-Rom.
Thank you! :good:
There are some Quicksettings i don't know the name to let it show after unlock. Can anybody help me?
The tiles from the first picture would be great to know the correct name.
This is very interesting, thanks for the question.
[MODULE] MultiFunctions (+Bootloop/Blackscreen Resolver For Apps, Modules & HideList)
Check The Module Of MultiFunctionsPlus From This Thread https://forum.xda-developers.com/apps/magisk/module-social-media-cache-advanced-t3799155:
- MultiFunctionsPlus Is The Successor Of MultiFunctions
- The Main Difference: The Pre-Activated Functions = Flashing MultiFunctions Only = Flashing MultiFunctionsPlus + Activator Or Deactivating The Pre-Activated Functions = Flashing MultiFunctions + Deactivator = Flashing MultiFunctionsPlus Only
Click to expand...
Click to collapse
MultiFunctions
Introduction:
A Module To Do The Next Functions [Clearing DalvikCache-PlayStoreWithServices-MagiskHideList, Changing The SELinux Mode, Booting The Android Into Safe Mode, Opening Magisk In Core Only Mode, Controlling The Virtual Memory (Swap), Changing The Swappiness Value, Keeping MagiskDaemon-MagiskHide Running & Changing DoubleTap2Wake(DT2W) Status].
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Installing/Configuring Apps, Modules Or HideList, Check The Pre-Activated Functions (+Bootloop/Bootscreen/Blackscreen Resolver For Apps, Modules & HideList) In Below
- P.S. All Functions Are Deactivated/Disabled By Default And The Needing To Activate Each Wanted Function Is Described In Below
- P.S. All Functions Can Be Used With Any-Rooting-Tool Except The Ones For Magisk Users Only As Described In Below
Current Version: MultiFunctions v1.0.3.4.1.6A9 - Deactivator v1.0.0.1
- For Magisk Users Only, Disable Magisk Core Only Mode From The Section Of Settings In Magisk Manager Which Is Required As An Essential Step To Activate Any Function (Disabling Magisk Core Only Mode & Rebooting The Device Are Required To Load The Modules)
- For Activating Any Function, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> The Function --> Delete The File Of Disable From The Folder Of Active (Or Copy The File Of Disable To The Folder Of Inactive) --> Reboot
Changelog:
v1.0.3.4.1.6A8/9: Improving The Code & Executing The Code In The Background To Overcome The Issue Of Blocking The Other Scripts From Starting Early Due To The Execution Time Of Code Is Too Long Which Is Also Related To Rooting-Tool/Rom/Kernel Itself
v1.0.3.4.1.6A6: Taking A Copy Of The Current Config [/data/DreamerMods/MultiFunctions] To [/data/DreamerMods/4U] During The Upgrading Process
v1.0.3.4.1.6: Fixing Minors, Adding [Vnswap & Zswap] To The Function Of [Swap Controller], Adding [UKSM & KSM] To The Functions Of [Swap Controller & Swappiness Changer] & Supporting More Devices For The Function Of [DT2WStatus Inverter]
v1.0.3.4.1.5: Fixing Minors
v1.0.3.4.1.4B8: Fixing Minors & Adding Function [DT2WStatus Inverter] For Changing DoubleTap2Wake(DT2W) Status
v1.0.3.4.1.4B6: Fixing Minors & Adding Sub-Function [Hide Enabler] To The Function Of [MagiskHideList Cleaner] For Enabling MagiskHide Once At Booting
v1.0.3.4.1.4: Fixing Minors & Adding One More Function [MagiskDaemonHide Keeper]
v1.0.3.4.1.3: Adding A Backup Feature To The Function Of MagiskHideList Cleaner
v1.0.3.4.1.2: Adding More Functions [Swap Controller & Swappiness Changer]
v1.0.3.3: Adding More Functions [DalvikCache Cleaner, PlayStoreWithServicesData Cleaner, MagiskHideList Cleaner, SELinuxMode Inverter, SafeMode Enabler & MagiskCoreOnlyMode Enabler]
v1.0.3.0: Initial Release
Created: May.09.2019
Updated: Nov.17.2019
Download Link: Click Here (To Ensure That The Module Will Work Properly, Kindly Do What Are Mentioned In The Description)
** Magisk Installer: It Supports Magisk Only
- For The Module Which Is Ended Its Name With v1500, It Supports Magisk v15.0(1500) To v17.3(17300)
- For The Module Which Is Ended Its Name With v17000, It Supports Magisk v17.0(17000) To v17.3(17300)
- For The Module Which Is Ended Its Name With v18000, It Supports Magisk v18.0(18000) To v18.1(18100)
- For The Module Which Is Ended Its Name With v18000, It Supports Magisk v18.0(18000) To v18.1(18100)
- For The Module Which Is Ended Its Name With v19000, It Supports Magisk v19.0(19000) To v20.1(20100)
- For The Module Which Is Ended Its Name With v19000P, It Supports Magisk v19.0(19000) To The Latest Version
** Unity Installer: It Supports Any-Rooting-Tool Such SuperSU, Lineage-AddOnSU & Magisk
- P.S. If You Flash The Same Version Of Module Twice, The Module Will Remove Itself But If The Version Of Second Time Is Higher Than The Version Of First Time, The Module Will Update/Upgrade Itself
- But For The Module Which Is Ended Its Name With Unity1.5.x, It Supports Magisk v15.3(1530) To The Latest Version
- But For The Module Which Is Ended Its Name With Unity4.x, It Supports Magisk v18.0(18000) To The Latest Version
- But For The Module Which Is Ended Its Name With Unity5.x, It Supports Magisk v19.0(19000) To The Latest Version
Installation:
- Magisk Manager --> Modules --> Add (+) --> Choose The Downloaded File --> Reboot
- Or Flash It Thru A Custom-Recovery Such TWRP Recovery --> Reboot
- Or Flash It Thru ADB Sideload --> adb sideload TheFileNameOfModule.zip --> Reboot (P.S. Renaming The File To Have A Short One Is Recommended Such mfm.zip Before Using ADB Sideload)
- Or Using A Flash-Tool (Flasher) Such EX Kernel Manager, FK Kernel Manager, FlashFire Or Flashify --> Flash ZIP File --> Reboot
The Description:
1- DalvikCache Cleaner (Advanced Dalvik/ART Cache Cleaner)
- Clearing The Dalvik Cache
- Doing The Same Functionality Of Wiping Dalvik/ART Cache Thru TWRP Recovery
- Resolving/Fixing Some Issues With The Installed Apps
- Removing All Remnants Of The Uninstalled Apps
- Maybe It Takes About 5 Min. To Finish The Process
- After Doing Its Functionality, Check The Free Space Of Internal Storage Which Should Be Increased/Maximized A Little Bit
- Activating The Function = Doing Its Functionality & Disabling Itself
- For Activating The Functionality Of DalvikCacheCleaner, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> DalvikCacheCleaner --> Delete The File Of Disable From The Folder Of Active --> Reboot
Click to expand...
Click to collapse
2- PlayStoreWithServicesData Cleaner (Advanced PS-GMS Data Cleaner)
- Clearing The Data Of Google Play Store & Google Play Services
- One Of The Methods To Resolve/Fix The Battery Draining & Re-Check PlayStore Device Certification Status
- After Doing Its Functionality, Check PlayStore Device Certification Status (Google PlayStore --> Settings --> Play Protect/Device Certification) Which Should Be Hidden For A While During Getting Its Status From Google
- Activating The Function = Doing Its Functionality & Disabling Itself
- For Activating The Functionality Of PlayStoreWithServicesDataCleaner, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> PlayStoreWithServicesDataCleaner --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
Click to expand...
Click to collapse
3- MagiskHideList Cleaner (Including MagiskHide Enabler & MagiskHideList Backup) [For Magisk Users Only]
- Clearing MagiskHideList [All Added Apps/Activities/Processes In MagiskHideList]
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Adding App/Activity/Process To MagiskHide, Flash This Module
- Activating The Function = Doing Its Functionality, Taking A Backup Of HideList & Disabling Itself
- For Activating The Functionality Of MagiskHideListCleaner, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> MagiskHideListCleaner --> Delete The File Of Disable From The Folder Of Active --> Reboot
- Additional Feature (Deactivating The Main Function + Putting A Copy Of The File Of HideList.txt Into The Folder Of Retrieving [Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> MagiskHideListCleaner --> BackUp --> Copy The File Of HideList.txt To The Folder Of Retrieving --> Reboot] = Retrieving/Restoring The Last MagiskHideList Before Activating The Function)
- Additional Feature (Deactivating The Main Function + Activating The Sub-Function Of BackUp [Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> MagiskHideListCleaner --> BackUp --> Delete The File Of Disable From The Folder Of Active --> Reboot] = Taking A Backup Of HideList)
- Additional Feature (Activating The Sub-Function Of Hide Enabler [Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> MagiskHideListCleaner --> Hide --> Enabler --> Copy The File Of Disable To The Folder Of Inactive --> Reboot] = Enabling MagiskHide Once At Booting)
Click to expand...
Click to collapse
4- SELinuxMode Inverter (Advanced SELinux Mode Changer)
- Inverting The Default Android SELinux Mode During Startup ([From Permissive To Enforcing] Or [From Enforcing To Permissive])
- This Function Changes The SELinux Mode For The Entirety Of The Device's Uptime Until Next Reboot
- The Default Android SELinux Mode Can Be Either Enforcing Mode Or Permissive Mode Which Depends On The Installed/Flashed Rom/Kernel
- SELinux Enabled Kernel/SELinux Development Mode Is A Main Point To Use The Function (The Installed/Flashed Rom/Kernel Must Have The Ability To Switch Between Enforcing Mode & Permissive Mode)
- Enforcing Mode Is Preferable For Security (Specially Banking Apps) & Permissive Mode Is Preferable For Mods (Specially Audio Mods)
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of SELinuxModeInverter, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SELinuxModeInverter --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
- Some Issues Which Are Related To Magisk/Rom/Kernel Itself Can Be Resolved Using A Different Modes [Where The Wait Mode (The Default One) Can Be Used For Resolving The Issue Of Bootloop/Bootscreen/Blackscreen Which Changes The SELinux Mode Within 5 Min. After Rebooting & The Fast Mode Can Be Used For Changing The SELinux Mode At Booting But You Need Firstly To Do What Are Mentioned In The General Steps]
- For Activating The Fast Mode, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SELinuxModeInverter --> Copy The File Of Disable To The Folder Of Wait --> Reboot
- For Activating The Wait Mode, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SELinuxModeInverter --> Delete The File Of Disable From The Folder Of Wait --> Reboot
=============================
The General Steps- SELinux Enabled Kernel/SELinux Development Mode Is Required Which Means The Installed/Flashed Rom/Kernel Has The Ability To Switch Between Enforcing Mode & Permissive Mode
- To Check The Above Mentioned Ability, Install Terminal Emulator From PlayStore --> Open It -->
-----> For Getting The Current Android SELinux Mode, Write su --> Click On Enter --> Write getenforce (Most Devices) Or sestatus (Some Devices) --> Click On Enter
-----> For Setting The Current Android SELinux Mode, Write su --> Click On Enter --> Write setenforce 0 (For Permissive Mode) Or setenforce 1 (For Enforcing Mode) --> Click On Enter
-----> Check Again The Current Android SELinux Mode
-----> If The Mentioned Steps Worked/Succeeded, Activate The Function Of SELinuxModeInverter
-----> Enforcing Mode Is Preferable For Security (Specially Banking Apps) & Permissive Mode Is Preferable For Mods (Specially Audio Mods)
-----> For Magisk Users, Disable Magisk Core Only Mode From The Section Of Settings In Magisk Manager
-----> For Activating The Functionality Of SELinuxModeInverter, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SELinuxModeInverter --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
-----> Some Issues Which Are Related To Magisk/Rom/Kernel Itself Can Be Resolved Using A Different Modes [Where The Wait Mode (The Default One) Can Be Used For Resolving The Issue Of Bootloop/Bootscreen/Blackscreen Which Changes The SELinux Mode Within 5 Min. After Rebooting & The Fast Mode Can Be Used For Changing The SELinux Mode At Booting]
-----> For Activating The Fast Mode, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SELinuxModeInverter --> Copy The File Of Disable To The Folder Of Wait --> Reboot
-----> For Activating The Wait Mode, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SELinuxModeInverter --> Delete The File Of Disable From The Folder Of Wait --> Reboot
-----> If The Mentioned Steps Didn't Work/Succeed, It Means The Flashed Rom/Kernel Hasn't The Ability To Switch Between Enforcing Mode & Permissive Mode So Flash Another Rom/Kernel Which Supports The Ability Of Changing SELinux Mode
- P.S. Maybe The Flashed Rom/Kernel Hasn't The Ability To Switch Between Permissive Mode & Enforcing Mode During Startup So You Can Use Only The Wait Mode (Not The Fast Mode)
- For Magisk Users, If You Want To Get Accurate Feedback From getenforce/sestatus, Disable Magisk Hide (Magisk Manager --> Settings --> Disable Magisk Hide) And After Finishing, Enable Magisk Hide Again [P.S. Magisk Hide Will Hide That Your Device Is In Permissive Mode To Pass The SafetyNet]
Click to expand...
Click to collapse
5- SafeMode Enabler
- Booting The Android Into Safe Mode
- In-Case Of Facing A Bootloop Issue Due To Installing/Configuring An App, Flash This Module
- The Function Disables All Installed Apps (User Apps) & Also The Root Access By Enabling Safe Mode & After Booting, Uninstall Any App Which Caused The Bootloop/Issue (From Settings --> Apps --> The App --> Storage --> Clear Cache --> Clear Data --> Uninstall) Then Reboot (Rebooting The Android Is Required To Get Back To The Normal Mode)
- Safe Mode Gives The Device The Ability To Not Open Any App Which Is Installed As A User App, And A "Safe Mode" Badge Will Appear In The Lower Left Corner Of The Screen
- Activating The Function = Doing Its Functionality & Disabling Itself
- For Activating The Functionality Of SafeModeEnabler, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SafeModeEnabler --> Delete The File Of Disable From The Folder Of Active --> Reboot
Click to expand...
Click to collapse
6- MagiskCoreOnlyMode Enabler [For Magisk Users Only]
- Opening Magisk In Core Only Mode
- In-Case Of Facing A Bootloop Issue Due To Flashing A Module, Flash This Module
- The Function Disables All Magisk Modules By Enabling Magisk Core Only Mode & After Booting, You Can Disable Magisk Core Only Mode From The Section Of Settings In Magisk Manager Then Removing/Disabling The Module(s) Which Caused The Bootloop/Issue From The Section Of Modules In Magisk Manager Then Reboot (Rebooting The Android Is Required To Load The Rest Of Modules)
- Core Only Mode Gives The Device The Ability To Get Into The Android Directly With User Interface Which Means The User Can Use The Device With All Features/Functionalities Except Magisk Modules Even Before Removing The Module(s) Which Caused The Bootloop/Issue
- Enabling Core Only Mode Keeps MagiskSU, MagiskHide & Systemless Hosts Activated, But No Modules Are Loaded/Enabled
- Activating The Function = Doing Its Functionality & Disabling Itself
- For Activating The Functionality Of MagiskCoreOnlyModeEnabler, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> MagiskCoreOnlyModeEnabler --> Delete The File Of Disable From The Folder Of Active --> Reboot
Click to expand...
Click to collapse
7- Swap Controller (RAM Management)
- Swap Is A Part Of Android RAM Management Which Depends On 2 Important Factors Which Are Swap Space & Swappiness Value
- Swap Is A Virtual Memory Which Allows Physical Memory RAM To Be Extended Using A Portion Of Internal Storage Where Android Moves Inactive Processes/Apps Into Virtual Memory To Make Space For New/Active Ones
- The Function Is Divided Into 2 Sub-Functions [Enabler & Disabler] For Improving Responsiveness/Performance
- Swap Enabler Re-Calculates Swap Space & Sets The New Size But Swap Disabler Sets Swap (Total) Size To Be 0 [It Can Be Checked Using DiskInfo From PlayStore]
- The Default Swappiness Value Is 35 For Swap Enabler & 0 For Swap Disabler
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of SwapEnabler, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SwapController --> Enabler --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
- For Activating The Functionality Of SwapDisabler, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SwapController --> Disabler --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
Click to expand...
Click to collapse
8- Swappiness Changer (RAM Management)
- Swap Is A Part Of Android RAM Management Which Depends On 2 Important Factors Which Are Swap Space & Swappiness Value
- Swap Is A Virtual Memory Which Allows Physical Memory RAM To Be Extended Using A Portion Of Internal Storage Where Android Moves Inactive Processes/Apps Into Virtual Memory To Make Space For New/Active Ones
- There Are 3 Levels Of Swappiness Value [Low For 10, Mid For 30 & High For 60] For Improving Responsiveness/Performance [It Can Be Checked Using DiskInfo From PlayStore]
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of Low Swappiness, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SwappinessChanger --> Low --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
- For Activating The Functionality Of Mid Swappiness, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SwappinessChanger --> Mid --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
- For Activating The Functionality Of High Swappiness, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SwappinessChanger --> High --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
Click to expand...
Click to collapse
9- MagiskDaemonHide Keeper (MagiskDaemon-MagiskHide Running Keeper) [For Magisk Users Only]
- The Function Is Divided Into 2 Sub-Functions [Hide & Daemon] For Keeping Both Of Magisk-Daemon & Magisk-Hide Running
- Hide Keeper Aims To Resolve The Issue Of Intermittent Work Of MagiskHide By Re-Enabling MagiskHide Every A Certain Time
- Daemon Keeper Aims To Resolve The Issue Of Losing Root Access Randomly (Or Magisk Is Not Installed) By Re-Starting MagiskDaemon Every A Certain Time
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of Hide Keeper, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> MagiskDaemonHideKeeper --> Hide --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
-----> Some Issues Which Are Related To Magisk/Rom/Kernel Itself Can Be Resolved Using A Different Modes [Where The Wait Mode (The Default One) Can Be Used For Re-Enabling MagiskHide Every 20 Min. & The Fast Mode Can Be Used Re-Enabling MagiskHide Every 10 Min.]
-----> For Activating The Fast Mode, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> MagiskDaemonHideKeeper --> Hide --> Copy The File Of Disable To The Folder Of Wait --> Reboot
- For Activating The Functionality Of Daemon Keeper, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> MagiskDaemonHideKeeper --> Daemon --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
-----> Some Issues Which Are Related To Magisk/Rom/Kernel Itself Can Be Resolved Using A Different Modes [Where The Wait Mode (The Default One) Can Be Used For Re-Starting MagiskDaemon Every 5 Min. & The Fast Mode Can Be Used Re-Starting MagiskDaemon Every 2 Min.]
-----> For Activating The Fast Mode, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> MagiskDaemonHideKeeper --> Daemon --> Copy The File Of Disable To The Folder Of Wait --> Reboot
Click to expand...
Click to collapse
10- DT2WStatus Inverter (DoubleTap2Wake Enabler/Disabler)
- Inverting The Default DT2W Status During Startup ([From Disabled To Enabled] Or [From Enabled To Disabled])
- This Function Changes The DT2W Status For The Entirety Of The Device's Uptime Until Next Reboot
- The Default DT2W Status Can Be Either Enabled Or Disabled Which Depends On The Installed/Flashed Rom/Kernel
- The Installed/Flashed Rom/Kernel Must Support The Feature Of DT2W (DoubleTap2Wake)
- Activating The Function = Inverting The Default DT2W Status
- For Activating The Functionality Of DT2WStatusInverter, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> DT2WStatusInverter --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
Click to expand...
Click to collapse
*** Re-Flashing The Module Of MultiFunctions With Keeping The Same Configurations:
- Re-Flash The Module Of MultiFunctions (Don't Reboot) & Move The Folder Of MultiFunctions From The Folder Of 4U [/data/DreamerMods/4U] To The Folder Of DreamerMods (/data/DreamerMods) Then Reboot
Click to expand...
Click to collapse
*** The Pre-Activated Functions (+Bootloop/Bootscreen/Blackscreen Resolver For Apps, Modules & HideList): Activating Some Functions For Once To Resolve Some Issues
- Flash The Module Of MultiFunctions (Reboot Now) For Activating Some Functions [DalvikCache Cleaner, MagiskHideList Cleaner, SafeMode Enabler & MagiskCoreOnlyMode Enabler] For Once To Resolve Some Issues
- Booting The Android Into Safe Mode For Giving The Ability To Remove Any App/Its Data Manually Which Maybe Caused The Bootloop/Issue (Rebooting The Device Manually Is Required To Get Back To The Normal Mode)
- Clearing DalvikCache For Removing All Remnants Of The Uninstalled Apps & Resolving/Fixing Some Issues With The Installed Apps
- Clearing All Apps/Activities/Processes From MagiskHideList Which Maybe Caused The Bootloop/Issue [For Magisk Users Only]
- Opening Magisk In Core Only Mode To Deactivate All Modules For Giving The Ability To Remove Any Module Manually Which Maybe Caused The Bootloop/Issue (Disabling Magisk Core Only Mode & Rebooting The Device Are Required To Load The Modules) [For Magisk Users Only]
- Flashing/Re-Flashing The Module Of MultiFunctions Will Activate The Above Mentioned Functions (Even-If Magisk Is In Core Only Mode For Magisk Users)
=============================
*** P.S. IF You Want To Flash The Module Of MultiFunctions With Dectivating The Pre-Activated Functions, Do The Next Steps ***- Flash The Module Of MultiFunctions (Don't Reboot) & Flash The Module Of Deactivator (Reboot Now)
Click to expand...
Click to collapse
*** FAQ/Notes:
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Installing/Configuring Apps, Modules Or HideList, Check The Pre-Activated Functions (+Bootloop/Bootscreen/Blackscreen Resolver For Apps, Modules & HideList) In Above
- After Flashing The Module Of MultiFunctions, MagiskHideList Will Be Cleared And For Retrieving/Restoring The Last MagiskHideList, Check The Function Of MagiskHideList Cleaner In Above
- For Flashing The Module Of MultiFunctions With Deactivating The Pre-Activated Functions, Check The Pre-Activated Functions In Above
- All Functions Are Deactivated/Disabled By Default And The Needing To Activate Each Wanted Function Is Described In Above
- In Case Of Deleting The Folder Of Any Unwanted Function Such SELinuxModeInverter (/data/DreamerMods/MultiFunctions/SELinuxModeInverter) & Rebooting The Device, The Code Will Not Check This Part/Function Which Is Equivalent To The Permanent Deactivation/Removal Of This Part/Function So The Same Step Can Be Done With Any Unwanted Function (P.S. For Retrieving/Restoring This Part/Function, Deleting The Folder Of Status & Rebooting The Device Are Required)
- For Activating Any Function, Deleting The File Of Disable From The Folder Of Active (Or Copying The File Of Disable To The Folder Of Inactive) From /data/DreamerMods/MultiFunctions/TheFunction (P.S. Negating The Negation Is A Form Of Affirmation) & Rebooting The Device Are Required
- Disable Magisk Core Only Mode From The Section Of Settings In Magisk Manager Which Is Required As An Essential Step To Activate Any Function (Disabling Magisk Core Only Mode & Rebooting The Device Are Required To Load The Modules)
- For Re-Flashing The Module Of MultiFunctions With Keeping The Same Configurations, Check The Details In Above
- The Current Version Of MultiFunctions4Magisk Resolved The Issue Of Blocking The Other Scripts From Starting Early Due To The Execution Time Of Code Is Too Long Which Is Also Related To Rooting-Tool/Rom/Kernel Itself (Such Losing The Functionality Of Xposed After Installing The Module Or Activating Any Function)
Click to expand...
Click to collapse
General Info:
- To Disable The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Check Box/The True Icon --> Reboot
- To Enable The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Uncheck Box --> Reboot
- To Uninstall The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Bin Icon --> Reboot
- To Disable The Module For All Users [Non-Magisk Users & Magisk Users], Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> Copy The File Of Disable To The Folder Of Status --> Reboot
- To Enable The Module For All Users [Non-Magisk Users & Magisk Users], Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> Delete The File Of Disable From The Folder Of Status --> Reboot
- To Uninstall The Module For All Users [Non-Magisk Users & Magisk Users] (Unity), Re-Flash The Module
>>>Dreamer(3MF)<<<
>>> Sharing A Good Thought Is Gold <<<
----------------------------------------------------------------------------------------------------------------
Other Modules
----------------------------------------------------------------------------------------------------------------
Reserved For News/Updates #1
Reserved For News/Updates #2
Updated MultiFunctions4Magisk To 1.0.3.4.1.2!
Changelog: Adding More Functions [Swap Controller & Swappiness Changer]
- For The Module Which Is Ended Its Name With v1300, It Supports Magisk v13.1(1310) To v13.6(1360)
- For The Module Which Is Ended Its Name With v1400, It Supports Magisk v14.0(1400) To v15.3(1531)
- For The Module Which Is Ended Its Name With v1500, It Supports Magisk v15.0(1500) To v17.3(17300)
- For The Module Which Is Ended Its Name With v17000, It Supports Magisk v17.0(17000) To v17.3(17300)
- For The Module Which Is Ended Its Name With v18000, It Supports Magisk v18.0(18000) To v18.1(18100)
- For The Module Which Is Ended Its Name With v19000, It Supports Magisk v19.0(19000) To The Latest Version
- For The Module Which Is Ended Its Name With Unity, It Supports Any-Rooting-Tool Such As SuperSU, Lineage-AddOnSU & Magisk
Very handy module! Thanks for this
Just saved me from a bootloop with a bad app
This is a life saver! Thank you!
Install core module only
Hello, I have used coreonly module v1.0.0A(1800) successfully on pie on a galaxy A8 2018, please can you explain how to only install core only module from the multi function version.
Is there a way to only flash what you need as I tried the multi function zip but then had to setup magic hide list etc as the zip wiped the settings.
Thank you
Phil
Very nice module.:good:
philcoo2 said:
Hello, I have used coreonly module v1.0.0A(1800) successfully on pie on a galaxy A8 2018, please can you explain how to only install core only module from the multi function version.
Is there a way to only flash what you need as I tried the multi function zip but then had to setup magic hide list etc as the zip wiped the settings.
Thank you
Phil
Click to expand...
Click to collapse
Using The Latest Version Which Is Currently 1.0.3.4.1.3, Copying The File Of HideList.txt To The Folder Of Retrieving & Rebooting The Device For Getting Back The Last Magisk Hide List Before Activating The Function Of MagiskHideList Cleaner (/data/DreamerMods/MultiFunctions/MagiskHideListCleaner/BackUp).
=============================
Updated MultiFunctions4Magisk To 1.0.3.4.1.3!
Changelog: Adding A Backup Feature To The Function Of MagiskHideList Cleaner
- For The Module Which Is Ended Its Name With v1300, It Supports Magisk v13.1(1310) To v13.6(1360)
- For The Module Which Is Ended Its Name With v1400, It Supports Magisk v14.0(1400) To v15.3(1531)
- For The Module Which Is Ended Its Name With v1500, It Supports Magisk v15.0(1500) To v17.3(17300)
- For The Module Which Is Ended Its Name With v17000, It Supports Magisk v17.0(17000) To v17.3(17300)
- For The Module Which Is Ended Its Name With v18000, It Supports Magisk v18.0(18000) To v18.1(18100)
- For The Module Which Is Ended Its Name With v19000, It Supports Magisk v19.0(19000) To The Latest Version
- For The Module Which Is Ended Its Name With Unity, It Supports Any-Rooting-Tool Such As SuperSU, Lineage-AddOnSU & Magisk
This module is garbage.
This is the most worthless piece of ****!
Polmk099 said:
This module is garbage.
This is the most worthless piece of ****!
Click to expand...
Click to collapse
Don't use it then. You can always give constructive feedback rather than being and complete idiot.
For Activating The Functionality Of DalvikCacheCleaner, Use Any Root File Explorer Such MiXplorer...
I need create folders in data?
mkdante381 said:
For Activating The Functionality Of DalvikCacheCleaner, Use Any Root File Explorer Such MiXplorer...
I need create folders in data?
Click to expand...
Click to collapse
No, You Don't Need To Do That But You Need To Access The Mentioned Path & Do What Are Mentioned Using Any Root File Explorer To Enable Its Functionality.
=============================
Updated MultiFunctions4Magisk To 1.0.3.4.1.4!
Changelog: Fixing Minors & Adding One More Function [MagiskDaemonHide Keeper]
- For The Module Which Is Ended Its Name With v1300, It Supports Magisk v13.1(1310) To v13.6(1360)
- For The Module Which Is Ended Its Name With v1400, It Supports Magisk v14.0(1400) To v15.3(1531)
- For The Module Which Is Ended Its Name With v1500, It Supports Magisk v15.0(1500) To v17.3(17300)
- For The Module Which Is Ended Its Name With v17000, It Supports Magisk v17.0(17000) To v17.3(17300)
- For The Module Which Is Ended Its Name With v18000, It Supports Magisk v18.0(18000) To v18.1(18100)
- For The Module Which Is Ended Its Name With v19000, It Supports Magisk v19.0(19000) To The Latest Version
- For The Module Which Is Ended Its Name With Unity, It Supports Any-Rooting-Tool Such As SuperSU, Lineage-AddOnSU & Magisk
Dreamer(3MF) said:
No, You Don't Need To Do That But You Need To Access The Mentioned Path & Do What Are Mentioned Using Any Root File Explorer To Enable Its Functionality.
=============================
Updated MultiFunctions4Magisk To 1.0.3.4.1.4!
Changelog: Fixing Minors & Adding One More Function [MagiskDaemonHide Keeper]
- For The Module Which Is Ended Its Name With v1300, It Supports Magisk v13.1(1310) To v13.6(1360)
- For The Module Which Is Ended Its Name With v1400, It Supports Magisk v14.0(1400) To v15.3(1531)
- For The Module Which Is Ended Its Name With v1500, It Supports Magisk v15.0(1500) To v17.3(17300)
- For The Module Which Is Ended Its Name With v17000, It Supports Magisk v17.0(17000) To v17.3(17300)
- For The Module Which Is Ended Its Name With v18000, It Supports Magisk v18.0(18000) To v18.1(18100)
- For The Module Which Is Ended Its Name With v19000, It Supports Magisk v19.0(19000) To The Latest Version
- For The Module Which Is Ended Its Name With Unity, It Supports Any-Rooting-Tool Such As SuperSU, Lineage-AddOnSU & Magisk
Click to expand...
Click to collapse
I don't have this folders, after installing this module. How activate 1 option, example clear dalvik cache?
mkdante381 said:
I don't have this folders, after installing this module. How activate 1 option, example clear dalvik cache?
Click to expand...
Click to collapse
Kindly Send The Reply For The Following
- Did You Download The Proper Version For The Used Rooting-Tool?
- Did You Reboot The Device After Flashing The Module?
- Are You A Magisk User? And If So, Send The Screenshot Of The Main Screen Of Magisk Manager, The Screenshot Of The Flashed Modules (Magisk Manager --> Modules), The Screenshot Of SuperUser Of Magisk (Magisk Manager --> SuperUser) & Magisk Log (Magisk Manager --> Log --> Magisk)
- Which File Explorer Do You Use? And Did You Grant Root Access To It?
I have Magisk 19.3. Your instructions are incomplete. I don't have this folders, after installing this magisk module. Pls for instruction step by step.
Old your module are super simple. You install clearcachedalvikcache and after restart module clear cache and dalvik.
Where download your old modules?
Edit:
Ok after installing all folders are in data folder. All is OK.
In My opinion better installer is in Unity, but with choosing function. Example put 1 to clear dalvik and data cache, put 2...
[BUG] Cannot Remove Module
This module did not disable swap on my OnePlus 7 Pro. Therefore, I tried to remove it from Magisk, and it keep showing up under Modules. I can disable it, but cannot remove it. It just keeps saying "Module will be removed at next reboot." The /data/DreamMods directory is still there.
I have Magisk 19.3 / 7.3.0, and used MultiFunction v1.0.3.4.1.4(v19000). I tried reinstalling, and deleting again, but no good - it's still there.
I found that the module's uninstall.sh script has no functionality in it - just comment lines from the Magisk template.
Also, I noted that after installing, it boots to Safe mode with continual 'Phone is starting' message. Have to force power down. (Very bad.) Then on powering up the phone, it reboots. (Probably a crash.) The third time, it finally comes up.
Any clue how to get rid of it completely?
jdhedden said:
Any clue how to get rid of it completely?
Click to expand...
Click to collapse
I removed the /data/DreamerMods and /data/adb/modules/Multifunction dirs, and that seemed to do it. However, I can't be sure it didn't leave anything behind elsewhere. <sigh>
Bad programmer. No cookie.
jdhedden said:
This module did not disable swap on my OnePlus 7 Pro.
Therefore, I tried to remove it from Magisk, and it keep showing up under Modules. I can disable it, but cannot remove it. It just keeps saying "Module will be removed at next reboot." The /data/DreamMods directory is still there.
I have Magisk 19.3 / 7.3.0, and used MultiFunction v1.0.3.4.1.4(v19000). I tried reinstalling, and deleting again, but no good - it's still there.
I found that the module's uninstall.sh script has no functionality in it - just comment lines from the Magisk template.
Also, I noted that after installing, it boots to Safe mode with continual 'Phone is starting' message. Have to force power down. (Very bad.) Then on powering up the phone, it reboots. (Probably a crash.) The third time, it finally comes up.
Any clue how to get rid of it completely?
Click to expand...
Click to collapse
jdhedden said:
I removed the /data/DreamerMods and /data/adb/modules/Multifunction dirs, and that seemed to do it. However, I can't be sure it didn't leave anything behind elsewhere. <sigh>
Bad programmer. No cookie.
Click to expand...
Click to collapse
Check The Following Quotes:
Introduction:
A Module To Do The Following Functions [Clearing DalvikCache-PlayStoreWithServices-MagiskHideList, Changing The SELinux Mode, Booting The Android Into Safe Mode, Opening Magisk In Core Only Mode, Controlling The Virtual Memory (Swap), Changing The Swappiness Value & Keeping MagiskDaemon-MagiskHide Running].
- After The Installation [Flashing/Re-Flashing] & 1st Reboot, Some Functions [DalvikCache Cleaner, MagiskHideList Cleaner, SafeMode Enabler & MagiskCoreOnlyMode Enabler] Are Activated To Resolve Some Problems & Disabling Themselves After Doing Their Functionalities
Click to expand...
Click to collapse
*** Activated Functions After Flashing/Re-Flashing The Module Do The Next Procedures/Steps
- After The Installation [Flashing/Re-Flashing] & 1st Reboot, Some Functions [DalvikCache Cleaner, MagiskHideList Cleaner, SafeMode Enabler & MagiskCoreOnlyMode Enabler] Are Activated To Resolve Some Problems & Disabling Themselves After Doing Their Functionalities
- Booting The Android Into Safe Mode For Removing Any App/Its Data Which Maybe Caused The Bootloop/Issue [Rebooting The Device Manually Is Required After That]
- Clearing DalvikCache
- Clearing All Added Apps/Activities/Processes In Magisk Hide List Which Maybe Caused The Bootloop/Issue [For Magisk Users]
- Opening Magisk In Core Only Mode To Deactivate All Modules For Removing Any Module Which Maybe Caused The Bootloop/Issue [For Magisk Users]
- Flashing/Re-Flashing The Module Will Activate The Above Mentioned Functions Even-If Magisk Is In Core Only Mode [For Magisk Users]
Click to expand...
Click to collapse
Current Version: 1.0.3.4.1.4
- For Magisk Users, Disable Magisk Core Only Mode From The Section Of Settings In Magisk Manager Which Is Required As An Essential Step To Activate Any Function
- For Activating Any Function, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> The Function --> Delete The File Of Disable From The Folder Of Active (Or Copy The File Of Disable To The Folder Of Inactive) --> Reboot
Click to expand...
Click to collapse
7- Swap Controller
- Swap Is A Part Of Android RAM Management Which Depends On 2 Important Factors Which Are Swap Space & Swappiness Value
- Swap Is A Virtual Memory Which Allows Physical Memory RAM To Be Extended Using A Portion Of Internal Storage Where Android Moves Inactive Processes/Apps Into Virtual Memory To Make Space For New/Active Ones
- The Function Are Divided Into 2 Sub-Functions [Enabler & Disabler] For Improving Responsiveness/Performance
- Swap Enabler Re-Calculates Swap Space & Sets The New Size But Swap Disabler Sets Swap (Total) Size To Be 0 [It Can Be Checked Using DiskInfo From PlayStore]
- The Default Swappiness Value Is 35 For Swap Enabler & 0 For Swap Disabler
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of SwapEnabler, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SwapController --> Enabler --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
- For Activating The Functionality Of SwapDisabler, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SwapController --> Disabler --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
Click to expand...
Click to collapse
8- Swappiness Changer
- Swap Is A Part Of Android RAM Management Which Depends On 2 Important Factors Which Are Swap Space & Swappiness Value
- Swap Is A Virtual Memory Which Allows Physical Memory RAM To Be Extended Using A Portion Of Internal Storage Where Android Moves Inactive Processes/Apps Into Virtual Memory To Make Space For New/Active Ones
- There Are 3 Levels Of Swappiness Value [Low For 10, Mid For 30 & High For 60] For Improving Responsiveness/Performance [It Can Be Checked Using DiskInfo From PlayStore]
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of Low Swappiness, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SwappinessChanger --> Low --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
- For Activating The Functionality Of Mid Swappiness, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SwappinessChanger --> Mid --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
- For Activating The Functionality Of High Swappiness, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SwappinessChanger --> High --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
Click to expand...
Click to collapse
Man just give us the seperate modules