Name | Modified | Size | Downloads / Week |
---|---|---|---|
aadisabler-README.txt | 2023-11-08 | 5.0 kB | |
aadisabler-13.zip | 2023-11-08 | 6.8 MB | |
aadisabler-12.zip | 2023-11-08 | 7.6 MB | |
aadisabler-11.zip | 2023-11-08 | 7.4 MB | |
aadisabler-10.zip | 2023-11-08 | 6.3 MB | |
Totals: 5 Items | 28.1 MB | 0 |
WARNING: READ THIS BEFORE INSTALLING It is not guaranteed, or even likely, that this module is compatible with your device. Installation on an incompatible device may cause bootloop or boot failure. I accept no responsibility for any loss or damage caused. INSTALL AT YOUR OWN RISK! COMPATIBILITY There is no way to predict with confidence whether this module will be compatible with a given device. I created it for my own personal use and it has only been tested on my phones (Moto G5, Redmi Note 8, both running custom ROMs). The module replaces one of the core Android system files with a copy that I have modified to block the system calls that turn on antialiasing. The file was created by downloading the AOSP source code, making two small changes and then compiling using the standard toolchain that is supplied with the source code. My modifications should not affect compatibility. What does affect it is whether the Android system the file is being inserted into was compiled from the same source code using the same toolchain. Ideally this would be the case for all Android systems but many manufacturers customise the Android systems installed on their devices. Usually these changes are cosmetic and don't affect the underlying core system but some manufacturers, such as Xiaomi, do change the core system. My module will not work on those devices - MIUI is not compatible. Most custom ROMs should be compatible and so should devices running close to 'stock' Google Android. Examples include Google Pixel, Motorola and Sony. But nothing is guaranteed. Read the rest of this file before you install the module. BEFORE INSTALLATION Back up your data! Recovery from bootloop or boot failure should usually be possible without data loss but nothing is guaranteed, so do a full back up before installing the module. Know how to recover an Android device from bootloop or boot failure caused by an incompatible Magisk module. The beauty of Magisk is that changes made by a Magisk module are not permanent, they can be reverted simply by deleting or disabling the module. So before installing you should make sure you know how to do this in the case where your device bootloops or will not boot up at all - you won't be able to access the Magisk Manager app to remove the module so other methods must be used. Before installing you should enable usb debugging on your device and have adb and fastboot installed on your pc and working. Connect your device to your pc and use the 'adb devices' command to confirm that adb can communicate with your device. Here are some methods that may work: 1. Android Safe Mode. When you boot your device to safe mode Magisk disables your modules and they remain disabled when you subsequently reboot normally. You can then use the Magisk manager app to delete the module. 2. Custom Recovery. If your device has a custom recovery, boot to recovery and access the file system from there to delete the module. Magisk modules are stored in data/adb/modules. 3. ADB. At the command prompt type this adb command: adb wait-for-device shell magisk --remove-modules 4. Fastboot. Put your device into fastboot mode and re-flash the original (Magisk free) boot.img. You will then have to delete the module before re-installing Magisk. 5. Factory Reset. If all else fails you can use the nuclear option: boot to recovery and do factory reset. This will delete the module, along with all your personal files and apps. Make sure you know the credentials for any Google or vendor accounts on the device. You will need them to get past factory reset protection and recover your device. I strongly recommend that you research this topic thoroughly before installing. INSTALLATION IMPORTANT! There are four version of the module, each is intended for a specific version of Android. The number at the end of the filename tells you which version it is for. Only install the one that matches the Android version on your device! Download the correct module for your device and then use the Magisk Manager app to install it in the usual way. AFTER INSTALLATION After all that, assuming the module has worked, you will find antialiasing disabled in the Android system and most (but not all) apps. But not on websites! Android web browsers do not use the system text renderer to render web site text. Instead they either use their own internal text renderer or the system webview, neither of which are affected by my module. To remove antialiasing on web pages you have to disable it inside the browser itself. Among Android browsers only Firefox (Beta and Nightly versions only) and various forks of Firefox allow this. To proceed: Type about:config into the Firefox address bar and hit enter. In the search box that appears, enter this: gfx.text.disableaa That entry will appear below. Toggle the setting from false to true and then close and re-open Firefox. Text on web pages should now be free of antialiasing.