yashsingh1/xdaforums huggingface dataset:
[Magisk] grandpajiver:
The developer spelled out the instructions quite well, provided what would happen if you adjusted your font weight, and additional options. Maybe adding a few commented out lines to the configuration file for the GS=false and OTF options could be added to the configuration file... but I could probably take a guess where they would go (probably under the OPSZ option).

I would rather edit a static text file that will overwrite itself with an update/incorrect configuration, which will prevent bootloops, rather than click the volume keys frequently to adjust stuff.

The Wiki provided a nice explanation, and gave good background information on how font weights and styles work.

Honestly, I prefer this to other font modification modules I had installed (FontConfig, other systemless font replacement modules).. it has way more customization than other modules. After you edit the text file on your phone, save a copy if there is an update.

Thanks, @nongthaihoang for the module. It is really well done.
[Magisk] nongthaihoang:
There are unlimited number of possibilities for the config. Imagine how many different combinations of 4 axis values from the demo link in the OP. How does that fit on "allow customization directly from Magisk". Are you willing to press the volume key hundreds, thousands of time instead of typing few lines of text to get what you want? I don't think so. It's not even possible to do it that way.

"Great power comes great responsibility". The config is there but not for everyone, it's only for those who spent time to read and understand. The module works without the need of configuring anything. You can stay with the default settings.
[Magisk] nongthaihoang:
The config only contains essentials. Other hidden ones are like a reward for those who read the wiki.

You can add these options anywhere in the config file doesn't matter. The whole config file will be parsed by the installer.

And you're welcome. 🤗
[Magisk] radz_:
Tried flashing this module in OOS 11 OnePlus 7T Pro, it didn't work unfortunately.😥

Is there a workaround? It was great in OOS10
[Magisk] nongthaihoang:
I agree. Stick with the one that suits you. Time past, things changed, i.e. the font itself changed, Android got updated. What works for today, may completely don't work tomorrow. Besides, man power is limited but there are a lot of ROMs. I can only make sure the font works as it should be on my devices. Everyone, if possible, contribute the solution to make the fonts works best for your devices.
[Magisk] nadeemakhtar1994:
Can someone help me. Since weeks i have been trying to use a font module for Chococooky font. Using android 11 miui 12.5 . Neither CFI works neither Font freak. How to use ChocoCooky font
[Magisk] nongthaihoang:
I can't help you with such little information you provide. At least make sure I can reproduce your issue.
[Magisk] nadeemakhtar1994:
What is there not to understand? I am using Miui 12.5 Rom based on Android 12 on my Poco F3 Gt device. Your module CFI used to work flawlessly in android 10 where i placed the ttf files of my Chococooky font in the CFI folder and then flash the module in magisk but now it does nothing. Font remains default roboto.

Tried your Omf module as well creating magisk file through template still doesn't work. Font does not change. Cfi was probably the only good thing for fonts whose development u stopped saying 2.3 is 'pre final' . Where is the final then? In short none of your magisk module work on miui 12.5 anymore
[Magisk] nongthaihoang:
- Firstly on your previous message, you'd provided:

+ Android 11

+ MIUI 12.5

+ CFI

- Now you've given more info:

+ Android 12

+ Device Poco F3

+ CFI 2.3

+ Steps that you did.

- It's better but not enough. This is generally what information you need to provide when reporting issues:

+ Magisk/TWRP version

+ Magisk/TWRP install log

+ Device ✓

+ ROM (official/custom)

+ Android version ✓

+ Module version ✓

+ Steps you do ✓

+ Related files (i.e fonts)

And anything that you think may be helpful.

The more information you provide the better I can help you.
[Magisk] nongthaihoang:
To save time, please note that custom ROMs are not supported.
[Magisk] Pete396:
btw it broke vlc media player subtitles.
[Magisk] nongthaihoang:
It's true. VLC doesn't work with variable fonts.
[Magisk] K1569GHENT:
I can't find the font files inside of the zip - please help.
[Magisk] nongthaihoang:
I stop redistributing fonts due to copyright issues. Try searching on web.
[Magisk] Camarada_Gabe:
Yes! I came here for the same reason. I was using the San Fracisco Plus module on my old cell phone. I changed my cell phone recently and couldn't find the old module anymore. Until I found out it was discontinued and I found this one. I tried the "tailed lowercase L", but it's not as discreet and pretty as the old one.
[Magisk] Camarada_Gabe:
That's exactly what I was going to suggest. A change through OTF, such as tailed lowercase L, would be perfect
[Magisk] nongthaihoang:
There are few people also ask about the old lowercase L. It's a minor modification but it seems people get used to it. I should bring it back for historical reason.
[Magisk] Tiez:
what is name this text editor app?
[Magisk] Zilla0617:
Mixplorer
[Magisk] nongthaihoang:
Wish granted.

OTF = custom lowercase L
[Magisk] Camarada_Gabe:
I saw it now and installed it. One question: was it exactly like that in the old module? I remember the tip of the L being more slanted.

Anyway, thank you very much!
[Magisk] nongthaihoang:
No. Not likely. Because the old font had only one Regular style that has it. This one has it all weights. And the modification means to be subtle and unnoticable.
[Magisk] Camarada_Gabe:
Understand. It's just that I thought the main purpose of these changes was to differentiate from the uppercase i. But there's no problem. It was just a curiosity
[Magisk] nongthaihoang:
If you thought it that way. There are "high legibility" or "tailed lowercase L" OTF already.

They are official font features not custom one. Read throughout the Wiki and GitLab README to know more.
[Magisk] Camarada_Gabe:
I already know these OTF and tried the tailed lowercase L, but I didn't think it was very cool. The old lowercase L served well the function of being different from the uppercase i while being subtle.

Anyway, even though this new version isn't too different from uppercase i, I still prefer it.
[Magisk] Camarada_Gabe:
Today's update removed the custom lowercase L :confused:

Update: Other OTFs not working too
[Magisk] nongthaihoang:
Fixed. I uploaded wrong font file.
[Magisk] nongthaihoang:
Updated CFI to support Android 12. Check 2nd post.
[Magisk] Dinevski:
Can someone confim that OMF works on MIUI EU 12.5.1 Android 10

I tried to follow the WIKI and all that stuff with the MultiRoms scripts but either I am missing something or some details are missing in the Wiki.

I also tried the CFI but when i flash it my phone wont boot and i have to delete the module in recovery

I really like to have the SF Rounded font on my device.
[Magisk] nongthaihoang:
I can't give you a comfirmation for your specific ROM. But this is the list of tested custom MIUI ROMs (not include Global):

- Miui eu 11

- Miui china 11

- Miui eu 12

- Miui china 12

- Miui Mix 12

- Miui OneOS 12.
[Magisk] Dinevski:
Thank you for the reply! I must be doing something wrong.

Can you please give me a simple list of what steps I need to make to install the San Francisco Rounded Font with OMF.

From what i understood from reading the forums earlier you had the font files included in the ZIPs and now they are not included. I think here is my mistake, I am maybe putting the TTF font files in the wrong place, but in the wiki there is no clear explanation of where to put the files (in the module zip, or in the OhMyFont Folder/subfolder)...
[Magisk] nongthaihoang:
I can't understand clearly what you're trying to ask. You mentioned San Francisco and then jumped to TTF files and then jumped to module zip/folder. You didn't even put proper question marks.

This question is understadable so I will only answer this one.

I wrote the whole wiki so I don't have to waste my time to answer each and every question every single time.

Please full fill the prerequisites before using.
[Magisk] Dinevski:
Sorry to waste your time but the problem is I don't understand your Wiki. Probably the other visitors are having the same difficulties... especially the ones that are new to this and that haven't used modules already.

There are no simple clear instructions on how to install OMF and make it work.

If i only put OMF.zip and 90_rom.sh in a folder and then flash the zip in Magisk, my device does not boot.

Thats why I asked for simple info of the steps I need to do to have OMF on my device. Something like:

1. PUT OMF, extension and XXX in one folder. > 2. Flash in Magisk > 3. Reboot. > 4. say thanks to the developer for wasting his time...

From comments in this forum we can see other users had difficulties installing it properly just because they tried to flash it directly from the Downloads folder where they also had additional random files.
[Magisk] nongthaihoang:
This is quite true. That's why I added the Prerequisites as mandatory. What or where in the wiki that you don't understand? I would like to hear and improve it if it's reasonable.

- There is no simple instruction because all modules are Magisk modules that you flash in Magisk Manager to install. The modules works on Stock Android out of the box.

- If you just read completely the GitLab README, in the Extension section, you find that "Multi-ROM" will "Support ROMs/devices other than Pixel". And if you wonder how to use it, also if you had read the Wiki, you already knew how to use it in here.

You used the word "in a folder" and "in one folder". I pressume you don't know where the folder is. Again please read the configurations.

The reason we see people come here and ask for troubleshooting is because those who read throughout the GitLab README and the wiki already know how to use the modules and get on with their lives.

Edit: What's the problem if you flash the modules in Download folder with bunch of other files? Magisk Manager only read the module that you browse to.
[Magisk] TheLastJediVII:
It works in One UI? I'm planning to buy the next Galaxy S and don't want to miss this module
[Magisk] nongthaihoang:
I don't own any samsung device with One UI so I can't tell you. And there are currently only OnePlus device testers. I have not really met any true OneUI user that said the modules doesn't work so I presume they are all working fine.
[Magisk] D3ZOXY:
Hello. I found 2 bugs, can they be solved?

1. Some hyperlinks have double underscores. (sh 1)

2. Is it possible to make this variant of font bolder? (sh 2)

Phone: Realme X2 (RMX1991). Android 10, Realme UI 1.
[Magisk] nongthaihoang:
Realme is not official supported because there has been no any Realme testers.

But I still tried replicating your issues.

1. I can't find double-underline anywhere.

2. I installed the same browser Valvidi and take the same screen shot. See attachments.
[Magisk] D3ZOXY:
I can test builds for Realme devices.

Obviously you can't see those bugs, because your smartphone is supported and tested.
[Magisk] nongthaihoang:
Because we have to exchange a lot of files. Contact me on Telegram (with the same username here) if possible.
[Magisk] nongthaihoang:
CFI now supports variable fonts. Check GitHub for Usage.
[Magisk] looper2890:
can i set ur only and leave the rest of the Upright empty for Google Sans Prime.
[Magisk] nongthaihoang:
Sure you can. The result is you have only ONE font style every where if that's what you want.
[Magisk] zaingraphiics:
I'm using this GSP module on Android 12 but capital letters like C & G were different on Android's previous version. They used to be rounded but now they're different.
[Magisk] nongthaihoang:
The latest Google Sans version is now a variable font (VF). What you see are just the variations of it. All the information about VF and how to take advantages of them can be found on the module's GitHub link and all over the Internet. I'm not going to go into detail here.

All the control over how the font looks are in your hands. The only thing that matters is you are able to take it or not.?
[Magisk] Toni Suwanto:
Where to put twrp extension, tried add both files, create twrp folder to ohmyfont folder, add the files to omf.zip but none work. Using orangefox but i think doesn't matter
[Magisk] nongthaihoang:
"Tried" you said. Of course it won't work if you try. Because you tried that means you don't know exactly how to do it. Then please read throughout the wiki.
[Magisk] nongthaihoang:
One correction: the folder name is OhMyFont.
[Magisk] Toni Suwanto:
Thanks for correction, it sensitive to uppercase. Work now
[Magisk] lokogan:
Hi, it appears that this module breaks Zygist and Magisk Hide on Canary and Alpha builds of Magisk. Once installed, all apps on Deny list or Magisk hide list will crash on launch. I am on Pixel 3, A12 stock ROM. OMF module used 2021102601.
[Magisk] nongthaihoang:
That is correct. On Android 12, once you hide apps in Magisk, the apps don't have access to the modules anymore. And they will crash because of that.
[Magisk] lokogan:
Is there any potential workaround/solution to this issue? Thanks.
[Magisk] nongthaihoang:
Unhide your apps or don't use font modules or install systemly, i.e. TWRP.
[Magisk] lokogan:
Thank you for the explanation.
[Magisk] nongthaihoang:
CFI now supports install hundreds of fonts from Google Fonts. Library by using Google Font Installer extension.
[Magisk] muserjulian:
How to make statusbar font look thicker?
[Magisk] nongthaihoang:
There's no any specific font for status bar. In other words, you have to make everything bolder and status bar text will be bolder as well.
[Magisk] freemannhp:
Flashed GSP.zip with an a12 aosp rom, all things including setting menu work well except Gmail. Unread email seems not to bold enough as stock font. It is difficult to tell them from read emails.
[Magisk] nongthaihoang:
Can you show screenshots of the "difficult"?
[Magisk] freemannhp:
The top one is unread.
[Magisk] nongthaihoang:
The unread text is not even bold. It's regular. In the attached ss is how it looks like by default. Did you adjust the config file?
[Magisk] freemannhp:
No, everything is default, is there any instructions to adjust config?
[Magisk] nongthaihoang:
It's not default from your ss. Gmail uses GS Text (aka opsz 17) by default. Can you show your config?
[Magisk] nongthaihoang:
No suspicious. But the fact that the font you are using doesn't not even looks like default GSP. This leads me to other questions. How the rest of the text looks like, besides Gmail? And how they look with stock font? Which ROM?
[Magisk] freemannhp:
The right one is after flashing gsp.zip.
[Magisk] nongthaihoang:
With the above ss, it's confirm that somehow you're not using default GSP. Maybe your ROM has altered font configurations of GSP with its. The system font is changed but not fully working.

Last change: send the /system/etc/fonts.xml file and ss of installed Magisk modules list.
[Magisk] freemannhp:
Fonts.xml
[Magisk] freemannhp:
I have to zip it to upload
[Magisk] nongthaihoang:
Not this one. I meant the one after installing GSP. But before doing that.

Disable the Pixelify module first (this module has GS font inside and overwrites GSP) to see if GSP works?
[Magisk] muserjulian:
I faced the same thing too.
[Magisk] freemannhp:
You are r pi

You are right, pixelify breaks GSP. Is there workaround to keep both?
[Magisk] nongthaihoang:
The guy above has installed many modules that conflict with font modules.

What do you mean by the same thing? Disable all others modules to check if they are conflicted with GSP first.
[Magisk] nongthaihoang:
"Extra Pixel". Try disabling that.
[Magisk] muserjulian:
Okay disabled extrapixel
[Magisk] nongthaihoang:
Conflicted modules can't be use together. You knew that right? Why don't you just use GS font (maybe disabled, try enabling it somehow) included the Pixelify module.
[Magisk] muserjulian:
A12 has 2 fonts right? Google sans and google sans text. Do you have google sans text module sandalone?
[Magisk] nongthaihoang:
Text or not is just a value of "opsz 17" or "opsz 18" respectively in the config file. Check GitLab for info.
[Magisk] muserjulian:
After i uninstall extra pixel it's been like this for minutes:'
[Magisk] nongthaihoang:
Lol. Are you aware of that you are asking me about someone else' module which I have no idea about.

Troubleshooting with that module owner. It didn't uninstalled itself probably.
[Magisk] EIOQ:
Hi! Why «rounded corners» don't works in GSP? «true» in config but no result
[Magisk] nongthaihoang:
Idk why you fail to make it work. There is no log or whatever to determine your issue. But I do know it's working fine for everyone else.
[Magisk] EIOQ:
Deleted config files then reinstalled module, corners remain square.

Then I clean installed OMF but the same, square corners.

Maybe it's the firmware? Xiaomi.eu 12.5.18, poco f3
[Magisk] nongthaihoang:
There are contradictions. First you talk about GSP and now OMF. They're different things.

Second, you doubt about firmware but why not just give the log as I mentioned for troubleshooting.
[Magisk] EIOQ:
I meant that I tried both modules.

Tell me where can I get the required log?
[Magisk] nongthaihoang:
- "Both modules"? Aren't you talking about "rounded corners" which belongs to GSP exclusively. I really doubt if you know what you're doing?

- Magisk install log.
[Magisk] nongthaihoang:
This is how to get the log just in case it's your first time. Tap the Save button at the corner of the Magisk flashing screen.
[Magisk] EIOQ:
So, I will try to explain ... before OMF automatically rounded corners during installation, and GSP after enabling the "true" option in the configuration file.

Now, when installing OMF, the corners remain square. When installing GSP too (option is included in the config)

At the moment I have removed all modules, deleted the OMF folder, installed the GSP module, the corners remained square.

Why? I'm trying to figure it out.
[Magisk] EIOQ:
This?
[Magisk] nongthaihoang:
- Let me rephrase my previous message. "Rounded corners belongs to GSP exclusively". Whatever you did with OMF is not relevant.

- I still haven't seen any log from you despite our back and forth messages. Sorry I won't reply any further.
[Magisk] EIOQ:
The fact remains, rounded corners does not work with GSP. The log was attached in the previous message, for some reason xda does not load it.
[Magisk] ahmadairfan:
Hi there. Tried to install via TWRP (non-root extensions), but it says "/system/fonts is not found", giving error 123. Tried to mount /system manually, still the same. MIUI Global 12.0.4, apollopro.
[Magisk] nongthaihoang:
I have no idea. Try getting the recovery log after the error, it may gives a hint.
[Magisk] satpanos:
Hello, does anybody have a TWRP flashable of GSP ? I find it very difficult to create one myself
[Magisk] nongthaihoang:
GitHub - nongthaihoang/custom_font_installer: Custom Font Installer for Android

Custom Font Installer for Android. Contribute to nongthaihoang/custom_font_installer development by creating an account on GitHub.

github.com

Follow the 4th bullet.
[Magisk] muserjulian:
The status bar font changed to Google sans text and looks thinner on latest version. How to make it looks thicker ?
[Magisk] nongthaihoang:
Yours is not how the default status looks like. It should be like this:

Please check your ends.
[Magisk] muserjulian:
This is from previous upload. Maybe it's the rom problem
[Magisk] muserjulian:
ATTACH]

Please check your ends.

[/QUOTE]

From the previous update seems fine maybe it's the rom problem
[Magisk] nongthaihoang:
Probably. Because the status bar text is Medium weight. There is no way it was Regular as in your previous message.
[Magisk] Ridho1:
I had been using OMF for months, and then I tried GSP. With UR grad value of 30, it is sooo perfect for me. Thank you very much Hoàng!
[Magisk] muserjulian:
The status bar keeps showing google sans although i flashed omf. This happens on Pixel Experience ROM, but in other roms working fine:')
[Magisk] nongthaihoang:
Nothing wrong. It's an expected behavior — OMF does not replace GS. Take your time to read everything on its GitLab and Wiki.
[Magisk] reynaldio19:
Sir, why is it that sometimes when there is a heads up notification, the system ui is restarts ( force close ). I tried not to apply OMF and it's normal. is there any solution?
[Magisk] muserjulian:
I just noticed there's something different with letter 'a' like in iOS Note font. Is this part of SF Pro or different font?
[Magisk] nongthaihoang:
I have no idea. Have not heard any related reports. There's no solution if you don't know the root cause. In the meantime do not use OMF.
[Magisk] nongthaihoang:
It's called "one storey a" google it.

A font can have as many alternative characters as it wants.
[Magisk] muserjulian:
Oh i see. It's such a cool font. Unfortunately it only appears on italic version.
[Magisk] gaduaxe:
Hi @nongthaihoang

So after flash Magisk OMF.zip, how can I use SF Pro font as my mainly font?

In OMF.zip I only see Google Sans.ttf font, I read wiki but no luck/.

Thanks
[Magisk] nongthaihoang:
OMF is only for Google Pixels/stock Android skin.
[Magisk] madscenes:
Hi, Great module loving it. I was just wondering if you could release another version of GSP with opsz set 18 for everything?

I can use a different version by using CFI and separate Google Sans ttf files, but it doesn't give the variable fonts, and I also like the weight of the your font. I just don't like how the character look when opsz is set to 17.

I dug up the config and saw that for regular text and light font maybe you've set it to 17 and for the rest it's at 18. If I edit it the config file, rezip and try to flash it through magisk it fails.
[Magisk] nongthaihoang:
Home · Wiki · Nông Thái Hoàng / Oh My Font · GitLab

Advanced Android Typography

gitlab.com
[Magisk] madscenes:
I'm sorry, but having difficulties with this...

I want to add the opsz 18 version of GS instead of what's in GSP and I tried to add GS by following the instructions to add the config lines but reflashing the module after making the changes is not working. Can someone help?
[Magisk] nongthaihoang:
Google apps use their own GS font.
[Magisk] muserjulian:
single-storey "a" part of OTF features right? Is there any way to enable it like straight-sided six and nine?
[Magisk] madscenes:
For some reason here in XDA GSP changes the font for XDA but when changing fonts manually using CFI it doesn't change for this site, there's something there.
[Magisk] Kellwa:
Hi

Thank you for the mod, i used CFI and its changing the font as expected, but am having a problem after flashing it

there is some conflict with MagiskHide/Zygisk DenyList

after flashing CFI all apps selected in the denylist stops working, when opened it crashes immediately without any error message

for example: Revolut, Binance, Play Store, Zoom, Vodafone, etc ...

Device: OnePlus 5

Rom: Xtended Android 12

Magisk v23016 (canary)

also tested on Magisk v23 stable, same issue

Could you please help to fix it.

Thank you in advance.
[Magisk] nongthaihoang:
Magisk vs Android 12 problem.

Download and extract this AFDKO to OhMyFont folder. Then flash CFI as normal.
[Magisk] Kellwa:
Thank you very much , it solved the problem
[Magisk] madscenes:
Were you able to fix this, if so can you please share how?
[Magisk] nongthaihoang:
That's normal. It's how GS looks like now. Find alternatives if it doesn't fit you.
[Magisk] madscenes:
I was able to do it by editing the opsz in system/etc/fonts.xml and setting all to 18

This is how Google Sans should look imo, it's more pleasing to the eyes in it's original style..

Though many apps and sites still use other fonts, which maybe normal I guess.
[Magisk] muserjulian:
How to enable OTL features in the new version sir? I tried like this but it didn't work
[Magisk] nongthaihoang:
Learning how to read, understand and use the config file first.

Home · Wiki · Nông Thái Hoàng / Oh My Font · GitLab

Advanced Android Typography

gitlab.com