• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[FONT][Magisk Module] Google Sans font - systemlessly

Search This thread

SGS5Korea

Member
Feb 26, 2021
15
9
Thank you Looki75, this module working perfect on my Galaxy S5 Lineage OS 18.1
 

Attachments

  • IMG_20210622_071256.jpg
    IMG_20210622_071256.jpg
    2.9 MB · Views: 81

dannejanne

Senior Member
Mar 23, 2011
2,384
824
Norrköping, Sweden
Working well on MIUI 12.5 stable China ROM on my Mi 11 Lite 5G. Thank god because "åäö" were messed up in my language with the default font and Chinese theme store don't have the product sans font unlike xiaomi eu ROM.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 142
    Hello,

    This is a module to install Google Sans font (aka Product Sans) systemlessly through Magisk.
    You say: "Yet another Google Sans module"
    Well sure, except that I made an important correction in the font design, read below...

    So I wanted to install Google Sans font on my device.
    You might know that is is not free to use...
    All copies I could find on XDA and other places had the same issue.
    The issue is that when you place a digit before a linebreak, if you click at the end of the line, the cursor is shown in the middle of the digit (see attached). I don't know if this glitch is only present on OnePlus 3T, but it drove me crazy...
    :eek:

    Then I spent hours trying to find different copies of that font....
    All copies had the same glitch on my device...
    So I tried looking for the issue in the font files themselves... and I finally found that the linebreak character (unicode U+0A) had a width defined at 0... whereas in any other font, it has a non-0 value (value depends on the font).
    I corrected this issue and now it is working perfect!!!
    :good:

    Also I corrected the colon for the lockscreen time (U+EE01 in Roboto-light).

    So attached is what I believe to be the only Google Sans (aka Product Sans) font module that doesn't have this issue...

    Tested only on my OnePlus 3T.
    As usual: make backups... blah blah.... I cannot be held responsible... blah blah....
    :)


    Donations:
    www.paypal.me/bulotchka

    Thanks to my generous donators:
    @matheuseduardo

    GitHub:
    Repository: https://github.com/Looki75/looki75productsansfont
    Report an issue / a bug: https://github.com/Looki75/looki75productsansfont/issues/new
    Releases: https://github.com/Looki75/looki75productsansfont/releases/latest

    Changelog:
    * V20: Thicker underlining line
    * V19: Solving underlining issues
    * V18: Solved some hyphens alignment issues
    * V17: Compatibility with Magisk 20.2
    * V16: Correcting the glitches introduced in V15. V16 was generated with my PC which resulted in much lighter files and (hopefully) solving the V15 glitches
    * V15: Improved compatibility with latest versions of MIUI roms + fixed south-east and south-west arrows
    * V14: Getting back to V10 because I found yet other bugs which just add to the list of issues due to the switch from V10 to V11
    * V13: Integrating missing glyphes that I forgot to merge from V10 to V11
    * V12: Correcting lockscreen colon issue on certain ROMs
    * V11: Updated with latest Google Sans font versions + definitely removed EMOJIs from both Magisk and TWRP zip files
    * V10: Correction of small issues with the font itself + removed EMOJIs (the EMOJIs from your ROM will be preserved)
    * V9: Additional fonts RobotoCondensed-Medium, RobotoCondensed-MediumItalic, RobotoNum-3L, RobotoNum-3R
    * V8: Underline FIX for all weights of font (thanks @rocketsauce83)
    * V7: Missing glyphes imported from usual ROBOTO


    How to properly install
    First of all:
    - Install module in Magisk
    - Reboot
    - On some phones (eg OnePlus), there is the possibility to choose a system-wide font from a selection. In this case, you need to make sure you select "default font" or "Roboto".


    How to check if the module works
    1. Open Gboard keyboard and look for capitalized letters Q and O. If they look like perfect circles, the module is probably applied correctly.
    2. Still in Gboard keyboard, look for figures 6 and 9. If they look like a small perfect circle with added straight line, the module is probably applied correctly.
    If checks 1 and 2 failed, double check you did properly install the module.

    If you cannot apply the module, then send me:
    * a screenshot of Gboard "CAPS" and "figures" screens
    * a zip file with the content of your /system/fonts folder
    If there is a font that I didn't take into account, I might be able to identify it and patch my module.


    If the module seems to be applied correctly, then go further:
    3. Look elsewhere in your system. If somewhere Q, O, 6 and 9 don't look like in Gboard, it means a specific font is used in that specific screen/app.

    If you think a specific font is used somewhere, then send me:
    * a screenshot of the place you where you found a specific font is used
    * a zip file with the content of your /system/fonts folder
    If there is a font that I didn't take into account, I might be able to identify it and patch my module.


    Apps known to use a specific font: aCalendar


    Have fun!
    Cheers
    15
    thank you so much! any chance to make a twrp flashable version of the zip? thanks!

    @All,

    UPDATE: V8 with Underline FIX for all weights of font (thanks @RocketSauce83) + TWRP-flashable ZIP made available

    Enjoy ;)
    12
    Guys,

    I'm really sorry... I had to update once more...

    UPDATE: V14 - basically getting back to V10 because I found yet other bugs which just add to the list of issues due to the switch from V10 to V11...

    Better I should have stick with V10 :crying::crying::crying:
    12
    UPDATE: V16 - basically correcting the glitches introduced in V15. V16 was generated with my PC which resulted in much lighter files and (hopefully) solving the V15 glitches

    Download from first post.

    Enjoy :)
    11
    Everyone,

    UPDATE: V13 - integrating missing glyphes that I forgot to merge from V10 to V11... sorry guys...

    @DvLAx3l thanks for your help in troubleshooting the latest remastered version... :eek::good: