-= MFFM Template v.X.xx =- (Discontinued)

[+] Support for AOSP/Pixel and ROMS based on them

[+] Rootless Recovery installation (Thanks to OMF) [Feature Withdrawn)

[+] Monospace / Bengali font / Emoji support (user dependent)

[+] Android 12/13/14/15 ready

-= MFFM vX.xx addon Tuts =-

⚛️ Bengali Fonts ⚛️

📜 Create a folder named MFFM in your local storage. The folder should be automatically created if you flash for the first time.

📜 Rest of the Tutorial moved here: https://news.1rj.ru/str/mffmbangla/2

—————
⚛️ Monospace ⚛️

📜 To use any Monospace font, add Mono- before the name of your font and put it in MFFM folder. EG: rename Firacode-Regular.ttf to Mono-Firacode-Regular.ttf

—————
⚛️ Emoji Font ⚛️

✅ Add Emoji- before the name of your Emoji font and put it in the MFFM folder. EG: rename WhatsappEmoji.ttf to Emoji-WhatsappEmoji.ttf
✅ Then put the Emoji Script Addon in the MFFM folder.

🎁 Tools to identify fonts from Images and Websites 🎁
🔗 https://telegra.ph/Identifying-Fonts-11-20

———————-
🎁 Picking the Right Font To Use on Android UI 🎁
For a very detailed knowledge read the whole story.

If you just want to learn how to arrange and categorize with a incomplete font family to a full 20 Roboto Style family then read from this section in the article
"Replacing the Stock Font Files with Your Own"

🔗 https://telegra.ph/Picking-the-Right-Font-To-Use-on-Android-UI-03-18

———————
🎁 Where To Find Free Fonts: 🎁
🔗 https://telegra.ph/Amazing-Websites-for-Downloading-Free-Fonts-03-18

🎁 What is OMF? (A simple directory guideline for New Users)
OMF (OhMyFont) is a complete Android Custom Font using utility by using root access in android system (ie Magisk). To be more precise now, OMF is grown into a whole ecosystem of bunch of tools to utilize custom fonts on Android system. I will keep this short and precise to clarify for new users around.

OMF & OMF powered tools/modules are maintained by Nông Thái Hoàng, it's his creation. He directly maintains the whole thing. I will try to categorize the OMF tools and modules to be specific.
————

🔖 OMF (The SFPro Module):
The birth of OMF. The module utilize Apple's great typography features on android with Apple's signature system font San Francisco Pro (SFPro), SF Pro Mono, New York. I won't go for details here, I will link all the details you need to begin with if it's your very first time using this module.

OMF Git | OMF Wiki | SFPro Demo | SF Mono Demo | New York Demo
————

🔖 OMF Template:
For developers and module makers, simply for anyone who have the basic knowledge of making an android font module. The most powerful android font module template ever existed!! You can make your most customized module using the template. Download or fork the git and edit to make your font module.

Git | Instructions
————

🔖 CFI (Custom Font Installer)
CFI is a OMF based module that lets you install your custom font without any module. Now comes with GFI (Google Font Installer) which allows you install any Google Font.

Git | Instruction/How to
————

🔖 GSP (Google Sans Prime)
Google's iconic brand font Google Sans is one of the most loved fonts amongst android lovers. GSP is a successful predecessor of Unicode Google Font module by Nong and now based on OMF. Most customizable, most advanced Google Sans module you can imagine.

Git | Google Sans Demo | Google Sans Mono Demo
————
Official XDA Thread for all OMF powered modules and tools
Telegram: OMF Channel | OMF Discussion

🎁 Unofficial OMF Sub-directories 🎁

🔖 MFFM Main Channel
You will find OMF template powered custom-tailored modules here. Module contains "[OMF]" tag at the end of the name. Both variable and static modules are being posted regularly.
Also, GSP / CFI updates are only posted in this channel.

🔖 Sub - Channel of MFFM _ Scrape but butter
You will find other decent OMF-powered module here. Channel mostly maintained by another MFFM admin, also main admin sometimes.

🔖 Unofficial OMF Extensions
Remember this channel contains a neat collection of various extensions that works in OMF Ecosystem. Those are not flashable directly in Magisk/TWRP. They are to be used as OMF Extension.

🔖 Magifonts Group
You will find random users font module, generated by automated bot, which are powered by latest OMF Template.

🎁 Terminologies, Important-to-know topics to use OMF based Modules 🎁

📌 OMF Directory / OMF Folder:
It's the folder in your Local storage / Internal storage noscriptd "OhMyFont". When we speak about OMF Directory we always mean about that directory. The folder will be created automatically in your Local storage when you flash your *OMF modules for the very first time.

📌 Config File / OMF Configuration:
The config file will be saved in OMF Directory. You have the advantage of customizing your font module. Learn about variable font axes (if you are not already familiar with variable fonts) to utilize the variable section of the config. The static module only has the advantage of making the font module Bold.
To enable a feature in config file, you have to uncomment (remove the hash sign # in front), save the config and then reflash and reboot to see the changes.

Note that, in OMF (SF Pro), GSP has individual customizations, read and learn from the respective links provided before this post.

📌 Extensions:
Extensions are shell noscripts (*.sh) that can run with any *OMF based module and can be executed as a part of the installation. Extension often comes with files (ie fonts *ttf).
Read the instruction from where you are getting your extensions. Each noscript serves a different purpose. They might be customizable, if they are; then edit, customize and save before any further steps.

Extension files (including the noscript *.sh) need to be in the OMF directory to be installed. If you are ready with your extensions put them in the OMF directory and flash your OMF Powered module. The noscript will be installed as the whole installation finishes.

Remember the extensions might be conflicting, so before using multiple extensions make sure they are compatible with each other. And also make sure if the extension is not particularly made for any specific module.

Important Links for Extension: Official OMF Extensions | Unofficial OMF Extension Channel | TWRP Extension (Recovery Installation)

🗣 Android 12+ vs Magisk Hide / Zygisk Denylist vs App Crash 🗣

We are going to introduce the second phase of our journey here. With android 12 we run into a new trouble of app crash those are hidden in Zygisk Denylist due to some technicalities in Magisk Mount.
For a while we are recommending users to use recovery method, now we have another working solution.

So I will mention both of the current effective methods to overcome the app crash thing. Follow this instructions so you don't have to beat around the bush anymore.
——————————————
📌 Font Loader Zygisk Module : https://news.1rj.ru/str/mffmex/269
———————————————
📌 Rootless Recovery Installation:
A detailed post is already available for this. I am just gonna link it here.
———————————————-
📌Font Spoofing / AFDKO Extension Font Modules:
Font spoofing is basically spoofing our module fonts as pre-existing system fonts.

With this new AFDKO extension now you can use our modules directly in Magisk. Remember this applies to all OMF powered modules and tools including CFI
For this process you are gonna need to download AFDKO Extension and extract it to OMF Directory. Then flash your module.
Also make sure the module you are using is up to date with the latest OMF template.
- - -
With font-spoofed modules you also need to make sure any other extension you are using follow the font-spoofing method otherwise it will break the purpose of the module.

Configuration File Syntax Conventions

Square Brackets [ ] ¹

The square brackets ( [ ] ) indicate that the enclosed element (parameter, value, or information) is optional. You can choose one or more items or no items. Do not type the square brackets themselves in the option.

Angle Brackets < > ¹

The angle brackets ( < > ) indicate that the enclosed element (parameter, value, or information) is mandatory. You are required to replace the text within the angle brackets with the appropriate information. Do not type the angle brackets themselves in the option.

¹ Linux command line syntax

Vertical Line |

The vertical line, also called the vertical slash or upright slash ( | ), means "or". You can choose values on the left side of the vertical line or values on the right side, not both.

Font Variations ²

<axis>@<range (low)>..<range (high)>

E.g.
wght@1..1000

The wght (weight) axis has the values from 1 to 1000.

² Google Font CSS API.

Comments ³

Any line that starts in a hash ( # ) sign (and a space) is a comment which takes no effect in the config file and will be ignored by the OMF installer.

E.g.
# This is a comment bla bla bla
# Write anything you want here

Commented Options ³

A commented option is also a comment but there's no space that follows the hash ( # ) sign.

E.g.
#STATIC=true
#GS=false

Uncomment (remove the # at the start of the line) an option to enable it.
Comment out (add a # to the start of the line) an option to disable it.

³ General configuration file guide

📌 Bootloop Solution Caused by Magisk Modules (including our font modules)

📍Bootloop is a common problem for users who use Custom rom and Magisk. Due to incompatibility of the module with system, bootloop can happen with random magisk module. Today I am gonna focus on few simple ways to deal with bootloop (without reinstalling your system).

📜 Delete The Module Manually:
- boot to recovery and navigate to /data/adb/modules
- select the folder with the name of your module, open that
- tap on the checkbox and select "delete" and swipe
- then reboot to system

📜 Recovery's Dedicated Option:
If you use modified recovery like Ofox/Pbrp, there will be a dedicated feature/option to remove magisk module. EG: Ofox's "Magisk Manager".
Beside there should be Magisk as add on in recovery (Aroma) mode, you can use that too.
Usually Team Win's stock TWRP doesn't have this additional features. In that case use Manual method from above.

📜 Remove Magisk Modules Using ADB:
https://telegra.ph/Remove-Magisk-Modules-Using-ADB-02-09


📍Switching from MFFM powered module to OMF powered modules will cause definite bootloops. In that case, you must clean flash, means:

- uninstall MFFM powered module
- reboot
- install OMF powered module
- reboot

Switching from OMF to MFFM doesn't need any precaution. Just install as you do normally (uninstall OMF module -> install MFFM module -> reboot). But make sure you don't use two font modules at the same time which function in same way {By modifying font.xml (font configuration file)}

📌 Possible solution for recovery installation Errors::

🔖 For errors like: "Can't extract zip (error 123)" "System is not writable" please follow this steps.

[>] Make sure you followed the #recovery installation guides properly.
[>] Move your module to Download folder (in Internal storage) if it is located in other directories.
[>] Make sure the module name doesn't contain any spaces. If yes rename it without spaces.
[>] Mount 'System' and 'Product' partition before flashing

🔖 Additionally [if above steps fail for you]:
[+] There should be a option in recovery called "Unmount system before flashing a zip" in the beginning of the flashing window, try to untick that while you flash.
[+] Go to terminal of your TWRP and run following commands:
mount -o rw,remount /system
mount -o rw,remount /product


❌ Even after everything (above steps) fails in your case then only suggestion is to try with a different TWRP/Recovery.

✱ About KSU ✱

✪ Both OMF/MFFM template powered modules from our channel/group support KSU.

✪ Always try to clean flash font modules in KSU. (Means uninstall any other previously installed font or font related module; reboot; install new module; reboot).

✪ If you face bootloop while using KSU using any module, reboot back to your TWRP, go to your TWRP's file manager browse to data/adb/ksu using file manager and you will find a file named modules.img, delete it and reboot system.