-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gboard Issue #114
Comments
What exactly do you mean with "refuse to show up"? And btw, which Android version do you use? |
So, I could only find one difference between Noto Emoji and Blobmoji. |
There's no hole or anything, they just aren't there. It skips right to the next emoji (🧡 "Orange Heart" U+1F9E1). I'm on Android 12 on a OnePlus 9 Pro, build LE2125_11_C.48, although IIRC this was also affecting Android 11.
This restored U+2764, but only to the search menu and recently used emoji list. The normal list still doesn't have it. Here's some screenshots of it (using Blobmoji-test.ttf as NotoColorEmoji.ttf in /system/fonts): |
I installed this module and I don't have such issues personally, but could just be me However weird issue I noticed is that it doesn't work in Chrome, or at least the web engine itself the rest of the UI e.g. address bar is fine? I assume the address bar uses Androids native UI toolkits, and the actual browser is just a canvas with OpenGL or however these things work Firefox with werks but very slowly in Firefox on Android nature :P |
Still an issue w/ Emoji 15 on my Pixel 6 Pro. |
@C1710 could you let me know how exactly you prepared that .zip file, so I can do it myself in the future (assuming my phone doesn't fix itself)? |
Does not appear to have been fixed with 15.1 beta, sadly. |
❤️ (Red Heart, U+2764) and♥️ (Heart Suit, U+2665) refuse to show up in Gboard. The rest of Android displays them fine. This issue occurs when using both the latest release and the latest Blobmoji.ttf in the fonts folder of the repo. Swapping back to the default NotoColorEmoji.ttf file fixes this behavior, as does using other emoji fonts, so it isn't an issue with Gboard (or if it is, it's only this font that's triggering it).
The text was updated successfully, but these errors were encountered: