yashsingh1/xdaforums huggingface dataset:
[Magisk] Looki75:
Yeah, I didn't see that but this is because (as I wrote in the changelog) I switched to Mac and this is the kind of hidden folders MacOS is spreading all-over...

This shouldn't neither affect how the module works, nor add a big deal of bytes to the file size.
[Magisk] kamilmirza:
same here

Android 10, Havoc 3.0 ROM
[Magisk] Looki75:
I didn't notice anything like that on my system...

Could you please post a screenshot?

Thanks
[Magisk] Looki75:
Could you please precise your request?

I don't understand what you suggest...
[Magisk] Looki75:
Where is it messed up?
[Magisk] kamilmirza:
attached some screenshots of v15
[Magisk] kamilmirza:
can anybody share v14

nevermind got it

v14 attached
[Magisk] kamilmirza:
[MENTION=2468642]Looki75[/MENTION]

attached same screenshots with v14
[Magisk] answa:
Great. Thanks
[Magisk] CarbonGTR:
Google Pixel phone uses both the Google sans and Product Sans font in its UI. Would it be possible to create a module to replicate that?
[Magisk] EVR_PR:
Mine has exactly the same issue as [MENTION=4369704]kamilmirza[/MENTION] phone. As you can see on v15 the font stretches and thins out, making it look like it's using thin and light weights all over. It even throws the padding off in some areas that it didn't before.
[Magisk] Looki75:
Ok guys, it seems that compiling the fonts with my new Mac brings a whole bunch of issues...

I'll power up my old PC and make a "new" v15 version (will be named v16)...

Stay tuned
[Magisk] Looki75:
Do you have any additional information?

1. In my understanding, "Product Sans" is synonymous with "Google Sans"... I thought both names designate the same font.

2. Where in the UI each font is used?

And, I cannot build a module which will use a certain font in some contexts and another in other contexts...
[Magisk] Looki75:
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 :)
[Magisk] emonkhan826:
Thank you so much :)
[Magisk] Arda Süzen:
I used your module on los17 and working awasome. Thank you :)
[Magisk] CarbonGTR:
1. Yes it is.

2. I'll try my best to answer as I don't own a Pixel.

• The System UI uses Product Sans. (Eg - Status Bar, Quick Settings Panel and System UI)

• All the headline fonts use Product Sans while the body uses Roboto

• Lockscreen fonts are fully Product Sans which again comes under System UI

• The Keyboard Font is Product Sans

You can look into Pixel Experience fonts and/or Pixel system dumps for reference :good:

Edit - Adding Pictures for reference.

Settings App

Notification Panel

Quick Settings Panel

Notification Settings
[Magisk] romantissm:
Thank you!

Do I need to remove V14 before flashing the new one?
[Magisk] Ghd182:
No, it replaces the old module automatically✌?
[Magisk] romantissm:
Thanks mate
[Magisk] Gruber008:
After clean flashing stock ROM I can't seem to make this module work for some reason, I tried flashing a couple of times but no luck. (Yes, I've selected Roboto font in the settings)

OnePlus 5, OOS 9.0.9, Magisk 20.2 - everything was working just fine for about 6 months.
[Magisk] carol:
- deleted -
[Magisk] Pranav Peddi:
Does this work with Android 10 OnePlus 6? I'm on the latest beta.
[Magisk] lotrzyk0:
Cant download v16 from first post

Wysłane z mojego Mi 9 SE przy użyciu Tapatalka
[Magisk] Looki75:
Shalll be working.

It's working with Android 10 on both my OnePlus 3T and 7Pro...
[Magisk] Looki75:
What error?
[Magisk] lotrzyk0:
Waiting for response and 0%...

Wysłane z mojego Mi 9 SE przy użyciu Tapatalka
[Magisk] Looki75:
File is accessible and has been downloaded already, so I guess there is some sort of connectuon issue on your side?

Are you able to download other files from other xda threads?
[Magisk] Gruber008:
I'm still having issues with your module since I updated Magisk to 20.2.

Can anyone confirm it works on 20.2?
[Magisk] lotrzyk0:
No, I cant. Could you share file on some server? I would be grateful :)

Wysłane z mojego Mi 9 SE przy użyciu Tapatalka
[Magisk] Ghd182:
On Redmi Note 5 (MIUI 11 9.12 26) with Magisk 20.2 this module is working perfectly ✌?

Also I have to thanks [MENTION=2468642]Looki75[/MENTION] for solving the issue introduced by MIUI 11 about notification titles too slim... now they are perfect and without this module they continue to look uglier ????
[Magisk] Gruber008:
Thank you for the information, I guess it collides with JoyPixels module now even though it wasn't before.

It's really weird being on "stock" font like you said, it all seems ugly. :laugh:
[Magisk] Amitbadoni001:
Surprisingly, neither this nor the Google Sans module by Nongthaihoang worked on my phone. Font is Roboto everywhere even after installing this module. My phone is Redmi Note 4 and it's running on Official Lineage 16 with Magisk 20.2.

PS - Google Product Sans 2.2R by Pirasalbe which is available within Magisk app works on my phone.
[Magisk] Looki75:
I am on Magisk 20.2 and it works perfectly.

However, I had the module installed prior to the Magisk upgrade...

Let me try to uninstall/reinstall the module to double check and I'll let you know the result.

Stay tuned
[Magisk] Gruber008:
Thanks for helping me out! :)

In the meantime I installed the font mentioned one post above and it really does work while your doesn't. (versions 14, 15 and 16 were tested)
[Magisk] Looki75:
Could you screenshot the content of your /system/fonts folder?
[Magisk] Amitbadoni001:
I'm sorry I've removed this module but I did check that folder when your module wasn't working. Google Sans.ttf (Medium, Condensed etc) font was there.
[Magisk] Looki75:
Alright...

I confirm that module doesn't work if installed on/with Magisk 20.2.

That's cool ?

A new bug to chase and exterminate ?

Let me put my bugs-buster suit on, and I start right now working on it... yeah, I too want my module back on my phone!!!! ?
[Magisk] Looki75:
I mean screenshot the folder when no font module is installed (mine or others).
[Magisk] Amitbadoni001:
I'm using a font module currently. I'll uninstall it tomorrow and share the screenshot here.

---------- Post added at 09:32 PM ---------- Previous post was at 09:30 PM ----------

Awesome! So this is not just a problem with my phone.

I want to ask two questions from you dev!

1. What's the difference between yours module and the other two font modules I mentioned in my last to last reply?

2. Why is your module not available within the Magisk app? (Magisk => Downloads)
[Magisk] Looki75:
UPDATE: V17 - compatibility with Magisk 20.2

Download from first post.

This should solve all recent issues...

Let me know if this is not the case :)
[Magisk] Looki75:
My module corrects some alignment issues existing in all other modules (see first post).

+ I completed the fonts so that some other languages are supported (I particularly took care of cyrillic, since I use extensively russian language)

Note: completion was made merging different files / fonts (I didn't design glyphes) but I never found any other blend as much complete as mine - that was true at the time I first issued the module, but since then, I stopped comparing with other modules, so that might not still be the case...

I just never took the time to find-out how to put the module in there...
[Magisk] Gruber008:
Thank you, all works perfectly, just like it did before 20.2 :highfive:
[Magisk] adriansticoid0312:
Hi. This is my favorite module for the font. But can you look at the "Wi-Fi" text issue? The hyphen in "Wi-Fi data usage" and preference looks wrong. Thank you!
[Magisk] Looki75:
Could you please be more explicit?

What is the issue exactly?

I don't see anything wrong on your screenshot...
[Magisk] adriansticoid0312:
Sorry If my description was vague. Have a look at the "Wi-Fi preference" text in my screenshot. The hyphen and the letter F is touching. And then look at the "Use Wi-Fi" text above, they look normal and not touching. Please zoom in a bit so you can see it clearer. Thank you.

Sorry for bad english.
[Magisk] Looki75:
Ah ok I see it now...

I'll try to find the bug.

Thanks for letting me know
[Magisk] Looki75:
UPDATE: V18 - solved some hyphens alignment issues

Download from first post !!!

:)
[Magisk] adriansticoid0312:
That was so fast! Thank you so much!
[Magisk] Looki75:
Yeah...

These days I feel like being in a productive closed-loop...

?

So people, if you identified any bug, it's probably the best time ever to report it ?
[Magisk] Looki75:
Announcement !

Dear followers,

I just opened a GitHub repository for this module:

https://github.com/Looki75/looki75productsansfont

I encourage everyone to report any issue with relevant material by opening an issue on GitHub:

https://github.com/Looki75/looki75productsansfont/issues/new

Especially, opening an issue on GitHub will guarantee that the issue is not "forgotten"...

Also, future releases will be published on GitHub:

https://github.com/Looki75/looki75productsansfont/releases

I will probably continue publishing the zip file here on xda as well for people who are not comfortable with the use of GitHub...

(I don't blame - I was like that just 3 days ago... but as many things, it's not tough to understand if you put some time into it)

Note:

I submitted a request to have my module integrated in the Magisk repo, so that you can download and install my module directly from the download section of the Magisk app... (thanks to [MENTION=5992482]Amitbadoni001[/MENTION] for pushing me towards that direction)

(https://github.com/Magisk-Modules-Repo/submission/issues)

But when I checked the history of submissions, I have seen that recently all "fonts" module were rejected: it seems fonts modules are not welcome on the Magisk repo for some reason...

This sound strange as there are about 17 fonts modules already existing in the Magisk repo and they are getting updated regularly...

So finger crossed, I hope mine will be accepted...
[Magisk] EVR_PR:
There are still some issues on my Pixel 4. See attached for example..
[Magisk] Looki75:
Pixel is already with Google Sans out of the box, isn't it?

Could you please send me the list of files on /system/fonts?
[Magisk] EVR_PR:
Pixel 4 uses a combination of Google Sans for titles and headers and Roboto for content. I included a zip file with the complete list of fonts in the folder you requested.
[Magisk] Looki75:
Could you please look at this (present) post on your phone and send the screenshot of this very post ?

1. Wi-Fi

2. Wi-Fi

3. Wi‐Fi

4. Wi‑Fi

5. Wi‒Fi

6. Wi–Fi

7. Wi—Fi

8. Wi―Fi

9. Wi⁃Fi

10. Wi−Fi

11. Wi─Fi

12. Wi──Fi
[Magisk] EVR_PR:
As requested. Thanks for your help! Really appreciate it.
[Magisk] Looki75:
Ok, on my device the issue is not showing on items 3 and 4, contrary to what shows your screenshot...

I think on your phone, the system is using another font instead of Roboto... or for some reasons, the module is not successful overriding the native Roboto...

Could you please send me those files from your fonts folder: SourceSans*
[Magisk] EVR_PR:
Here you go.
[Magisk] Looki75:
From your previous screenshot, I can tell that my module doesn't apply at all...

My assumption is that the Source Sans Pro font is used instead of Roboto.

I'll post here a testing version including overriding Source Sans Pro... we'll see if it works...
[Magisk] EVR_PR:
That's strange because whenever I flash your module, everything that uses Roboto switches to Google Sans (settings, Pixel launcher text, Gboard, etc.)
[Magisk] Looki75:
In your latest screenshot, check "6" figure... it is definitely not from my module (the figures in your status bar clock, however, are indeed from my module).

Please check attached testing module... (deleted - I prefer not to have test versions here and there)
[Magisk] Ghd182:
This is on MIUI... Maybe I'm not doing anything useful posting this screenshot, but that's my feedback if it might help ✌?
[Magisk] EVR_PR:
Perfect! Thank you! See attached.
[Magisk] Looki75:
Last questions, just to be sure:

* Could you confirm that the initial "Wi-Fi settings" screenshot was taken with my module V18 active and running (really V18, not V17) ?

* And that the corresponding same "Wi-Fi settings" screenshot that you just attached was taken with V19TEST active and running ?

Thanks
[Magisk] Ghd182:
These bugs are WhatsApp-related or somehow solvable within this module?
[Magisk] EVR_PR:
Now that you mention it, when I went to flash the Test version, Magisk showed v17 even though I had flashed v18 earlier. After flashing test, the Magisk module now shows v18 and everything seems to be okay.
[Magisk] Looki75:
I think it is device-related...

On mine, everything is fine, see attached...
[Magisk] Looki75:
In the testing module, I didn't have time to update the version number...

In v18, the correct V18 version shall show.

Please flash again V18 from first post and check again.

I suspect you had v17 when you first reported the issue.

Please let me know.
[Magisk] EVR_PR:
I guess it was user error on my end. I apologise. Attached settings menu screenshot with v18 module.
[Magisk] Looki75:
Ok thanks.

So let's forget about V19TEST.

Cheers
[Magisk] maxq1:
hi, OP. your work is one of the reasons why I root/use Magisk. so thanks!

hope you could help me out though. since v17 (now on v18 & magisk 20.3) on my OP 6T (10.3) i'm getting these weird characters on different apps. especially that one on my screenshot of TiBu. on Viber i'm getting that weird character too instead of an emoji, i think. did i just fail to install an emoji pack or what? TIA!
[Magisk] Looki75:
1. What shall be written in the first screenshot? Which language?

Could you write in a post the exact text it should read?

And more generally: which language(s) do you use on your phone?

2. On second screenshot, that should be a star...

Do you see it here?

Titanium Backup ★ root needed

Cheers
[Magisk] maxq1:
that's the thing, man! see attached screenshot please. not sure what language but that's under Waze
[Magisk] Looki75:
On my device I do see this star...

In my font, the character is not defined, so it shall fall back on a kind of "default". Obviously your "fall back" is failing.

This is not an issue with my module.

Could you please post a screenshot of the modules you have installed?

And: on which language is configured your phone?
[Magisk] Looki75:
Ok, have a look at the "6" figure in your latest screenshot...

It doesn't have the shape it should have...

I think my module is not active on your system...

Please check
[Magisk] Deluriane:
Im on V18 and Magisk 20.3 and I don't have issues like that. Maybe it's on your end. I attached a screenshot as well
[Magisk] Looki75:
Yeah, I assume [MENTION=2610368]maxq1[/MENTION] has a conflicting module...
[Magisk] discodestroyer10:
First of all - absolutely brilliant work.

Second of all: please, never buy a Pixel phone or we'll all loose your support! ?

And thirdly:

Have I got an underline issue or is this how it should be? On 1+7pro with stock font it looks better. Screens attached (1) stock, 2) with your module)
[Magisk] RYU810:
I can't find it in font display or it just normal?

Samsung Note 9 / Pie
[Magisk] Deluriane:
If you flash this, it will replace the font "default" as stated in the instruction on how to install. It wont be listed as Google Sans in Font styles.
[Magisk] RYU810:
Thats right,thx for info.
[Magisk] Deluriane:
No problem, glad to help out :laugh: :good:
[Magisk] Looki75:
Could you open an issue on GitHub for the underlining bug ?

(please follow instructions in first post)

Thanks
[Magisk] Looki75:
UPDATE !!!

V19: Solving underlining issues

Download from first post...

Cheers
[Magisk] maxq1:
thank you so much for helping out guys. it's not the module & it works great! turns out my phone can't read any emojis :D. it's a partition thing for 1+: for whatever reason, 1+ created a hidden partition to house fonts & some apps/settings :(. dirty flashing my rom worked. sorry for all the trouble
[Magisk] discodestroyer10:
Thanks, it's working!

Ps. Don't want to be picky - it's pure aesthetics - but the underline itself is quite thin(?) Since I like your module more than the other one posted here because your is more "bold", I think it would benefit to match both underline and font style together?

English isn't my first language and I'm not sure if I have expressed myself clearly. Picture attached.

Regards.
[Magisk] Looki75:
Agreed.

I'll work on that for v20.
[Magisk] Looki75:
UPDATE !!!

* V20: Thicker underlining line

Download from first post or GitHub

Cheers
[Magisk] adriansticoid0312:
Someone give this guy a medal. And a cookie.
[Magisk] 73sydney:
Thanks for your work, but heads up that your github releases link is borked

Currently its linked as

https://github.com/Looki75/looki75pr...sfont/releases

Should be of course:

https://github.com/Looki75/looki75productsansfont/releases/

Or even better, always poitjing to latest release:

https://github.com/Looki75/looki75productsansfont/releases/latest
[Magisk] Looki75:
Thanks for pointing this.

Updated. :)
[Magisk] Looki75:
For info, my request to have my module integrated in Magisk's repo has been rejected...

Sorry guys but you will have to continue downloading my module either from first post or GitHub...

Cheers
[Magisk] glavinstone:
Thank you so much for your efforts :)
[Magisk] Looki75:
Happy to serve! ?

[MENTION=9350973]All[/MENTION]

I put a lot of efforts in this module and try to help and listen to all of your suggestions and bug reports.

If you think my work is worth something, and if you feel like giving me a medal or a cookie, you can do so by donating here:

www.paypal.me/bulotchka

?
[Magisk] kahntran:
Thanks for the work :D

Working on my phone

OnePlus 6

Android 10 (10.3.0)

Magisk 20.3

TWRP-3.3.1-16
[Magisk] Amitbadoni001:
Hello dev!

Some fonts do not appear in DictBox dictionary app as you can see in the screenshot (check "origin") !
[Magisk] Looki75:
Can your give me a link to this exact app you are using?

There are tons of "DicBox" apps on playstore...
[Magisk] Looki75:
Can your give me a link to this exact app you are using?

There are tons of "DicBox" apps on playstore...

Also, give me a screenshot of your installed Magisk modules.

+ Info requested in first post to check if my module is working correctly.

Thanks
[Magisk] Amitbadoni001:
1. https://play.google.com/store/apps/details?id=com.grandsons.dictsharp

2. Only three modules - (Your module) v20, Call Recorder - SKVALEX v2.1.0, Disable Screenshot and Camera sounds v1. 4. Sorry couldn't take screenshot because phone is showing error ("Couldn't take screenshot due to limited storage space" even though my internal memory has 8GB empty space)

3. Yes, everything is fine in Gboard.
[Magisk] Looki75:
About the app, please give all necessary information.

Which languages pair, which word was that, etc...

I would like to reproduce the bug on my phone.

I need to have the exact same screen on my phone...
[Magisk] Looki75:
On your screenshot we can see that this app is mixing a whole bunch of different fonts.

I suspect those buggy characters are from some foreign languages... and/or from another font that the app wants to use but is not accessible...

As long as I cannot reproduce on my phone and as long as I don't know what *should* be written, there is little I can do about your issue...
[Magisk] Ice Bear:
Thank you so much for this!
[Magisk] BreckZeBoulay:
Nexus 5X with LOS 15.1, perfect ! :good:

Thx ! :)
[Magisk] M1810:
Font seems to take more space than roboto on homescreen, calculator used to be "Calculato..." And now it's "Calcu..." Or whatsapp is now "whatsa..."
[Magisk] Looki75:
Correct... it is a bigger font than Roboto...
[Magisk] imreezm:
Working fine on Nitrogen Pie (OP6 + OP3)
[Magisk] creeve4:
[MENTION=2468642]Looki75[/MENTION] The underline on text is too low. Otherwise it is working and looking good.
[Magisk] j-a-d-z:
Same here with stock 8.1 on my Nexus 5X.

But everything fine on my wife's Moto X Play with stock 7.1.1. :eek:
[Magisk] AC130PL:
It seems, that 8.1.0 is making problems :/
[Magisk] neekless:
In the module you linked, The fonts are named GoogleSans because they are meant to be GoogleSans.

In this module, the fonts are named Roboto because they are meant to replace the Roboto in the system. Your phone will treat these fonts named Roboto as Roboto, even though they are actually GoogleSans.
[Magisk] neekless:
Your module is missing RobotoCondensed-Medium and RobotoCondensed-MediumItalic (they are present in Android Pie). I have attached them in the zip along with GoogleSans-Medium and GoogleSans-MediumItalic. Hope you can do your merging and add them to the module.
[Magisk] padre629:
Hi!!!

Fonts are working perfectly on RR 6.2.1 (Samsung Note 4)

I promise to install your module when I unlock the bootloader of my Redmi Note 5 Pro

Thanks for your awesome job!
[Magisk] wiki.alphajoza:
Underlining has a problem in v7. The under line is to much downward.
[Magisk] Aftab_khatri:
Yes underline is very far. And bold things like icon names in pull down toggles are not bold. All font same
[Magisk] marregazza:
Hello there. Just ask noob question. Why the '1' character is different in design even I use the same font ( Google sans)? Is it any way to make it same? It never happened on other font, except Google sans.

The picture attached, lockscreen and homescreen
[Magisk] Looki75:
Ok my device, underlined text is ok...
[Magisk] Looki75:
What is the second picture?

Which widget/app?
[Magisk] j-a-d-z:
For me it is ok with Moto X Play at 7.1.2 but not ok with Nexus 5X at 8.1.
[Magisk] marregazza:
Digital Clock widget, from Google clock

Edited : problem solved. Using 3rd party clock widget
[Magisk] Aftab_khatri:
For me its very far. Sir please fix issue.
[Magisk] Deluriane:
Also tried to reproduce the issue but can't seem to make the "Origin" come up on my end, so can't confirm if it's a user problem or the Font.

---------- Post added at 09:51 AM ---------- Previous post was at 09:47 AM ----------

What kind of dictionary module did you download to have the origin part. Downloaded a bunch of english dictionary add-on but none had the origin.
[Magisk] 73sydney:
Been there myself mate, my Gpay SQL Fix module was "rejected for not doing enough" despite running sql commands, hiding apps in magisk etc, and rudely rejected by a couple of people as well - i refuse to deal with them. So currently people can only find it through my sig or when i update my post in the google pay magisk threads, or if they stagger across it there.

I now how much of a pain it is, especially when i get asked why it isnt in the repo and i have re-explain why :)

Worth pointing out even some of the magisk crowd are still wondering why it isnt in there, over 4,000 downloads and counting :)

Worth pointing out the most visible people in magisk arent the ones with the attitude issues that reject submissions rudely...dunno why they let those that do still rate submissions....
[Magisk] Looki75:
Not the first time, probably not the last time either...

People report some kind of issue, and when we dig into it, they just disappear...

Maybe they realized that the issue was on their side... In which case it would be nice and respectful to let us know about it...

??*♂️

(I just ran into that dictionary app that I installed the other day trying to reproduce the issue...)
[Magisk] adriansticoid0312:
Hi. Got another request in mind. Can you make it so that the upper case India and lower case Lima look different from each other? Because right now they look exactly the same. Thank you!