-
Notifications
You must be signed in to change notification settings - Fork 531
[Android] Fallback to B+W emojis in Android 5.1.1 (CM12.1) #185
Comments
The problem is not with EmojiOne or with the keyboard, it is with Android. Open /system/etc/fonts.xml
cut it out, scroll up and paste it right under:
(it should be somewhere around line 95) Next open /system/etc/fallback_fonts.xml
cut it out, scroll up and paste it right under
(it is right at the top, directly after the introduction comment) Reboot and it should work now :) |
@mikebe11 Ah hi, sorry, it did work! I just totally forgot to close the issue. Thanks for checking back up! |
Glad to hear it! Thanks @Naudiz |
Are there likely to be any plans to make installer .zips for Android users (presumably of various versions) to ease installation for non-Google-Play users, or anything similar? |
It seems that when installing EmojiOne using "EmojiSwitcher", the same bug is encountered. I'm going to go and report that to them now. |
I tested EmojiOne 2016 on my mum's Android 4.4.4 (CM11) device (both with a manual copy of the ttf, and with the .zip provided in a PR by @samantha-cruz, and everything seemed to work fine. There were of course some emoji "missing" but that's due to not using an appropriately updated keyboard - all emoji that rendered did so correctly using the one from EmojiOne.
I then tested on my own 5.1.1 device (CM12.1), in both ways, and what I get is a couple of the emoji showing up as those ugly little B+W icons. The ones which do so were consistent from when I tested with the ttf and the aforementioned .zip, and the ones I can find when I skim through now are:
I'll try to post the emoji somewhere so that I know their actual character codes, and also screenshots in an empty chat. Bear with me. :)
✌❤️⭐️☀️❄️☎️✉️✂️✒️✏️✈️ ⬆️⬇️⬅️➡️↗️ ↖️ ↘️ ↙️ ↔️ ↕️ ◀️ ▶️ ↩️↪️⤵️ ⤴️ ✳️❇️✴️⭕️❗️‼️ ⁉️ ✖️♠️ ♥️ ♣️ ♦️ ✔️◼️◻️◾️◽️▪️▫️⬜️⬛️⚫️⚪️
... and ♨️
I haven't tested any other keyboards yet, but I get this behaviour in the AOSP default keyboard and in Telegram-FOSS, though those two keyboards seem to put some things in different orders.
If there's any information I can provide, I'd be happy to try to help.
The text was updated successfully, but these errors were encountered: