Skip to content
This repository has been archived by the owner on Jul 23, 2019. It is now read-only.

[Android] Fallback to B+W emojis in Android 5.1.1 (CM12.1) #185

Closed
aphirst opened this issue Jan 13, 2016 · 6 comments
Closed

[Android] Fallback to B+W emojis in Android 5.1.1 (CM12.1) #185

aphirst opened this issue Jan 13, 2016 · 6 comments

Comments

@aphirst
Copy link

aphirst commented Jan 13, 2016

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:

  • standard red love heart, the one before the blue one
  • two fingers making the peace symbol (V for victory)
  • the envelope, just before the envelope with speed lines behind it
  • the pencil, just before the emoji of the pencil writing on a piece of paper
  • the icon of the sun which just comes before the rainbow
  • snowflake
  • aeroplane
  • the Java symbol just before the love letter
  • most of the arrows
  • most of the geometric shapes

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. :)
Here we go.

✌❤️⭐️☀️❄️☎️✉️✂️✒️✏️✈️⬆️⬇️⬅️➡️↗️↖️↘️↙️↔️↕️◀️▶️↩️↪️⤵️⤴️✳️❇️✴️⭕️❗️‼️⁉️✖️♠️♥️♣️♦️✔️◼️◻️◾️◽️▪️▫️⬜️⬛️⚫️⚪️
... 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.

@Naudiz
Copy link

Naudiz commented Jan 22, 2016

The problem is not with EmojiOne or with the keyboard, it is with Android.
You need to reconfigure it to give the Emoji One font a higher priority.
Here's how to do it for Android 5.1.1 and 6.0.1, assuming you overwrote NotoColorEmoji.ttf with EmojiOne font:

Open /system/etc/fonts.xml
Search for:

<family>
       <font weight="400" style="normal">NotoColorEmoji.ttf</font>
</family>

cut it out, scroll up and paste it right under:

    <!-- fallback fonts -->

(it should be somewhere around line 95)

Next open /system/etc/fallback_fonts.xml
Search for:

    <family>
        <fileset>
            <file>NotoColorEmoji.ttf</file>
        </fileset>
    </family>

cut it out, scroll up and paste it right under

<familyset>

(it is right at the top, directly after the introduction comment)

Reboot and it should work now :)

@mikebe11
Copy link
Contributor

mikebe11 commented Apr 6, 2016

@aphirst Checking in on this. Did the suggestion by @Naudiz solve your B&W fallback issue?

@aphirst
Copy link
Author

aphirst commented Apr 9, 2016

@mikebe11 Ah hi, sorry, it did work! I just totally forgot to close the issue. Thanks for checking back up!

@aphirst aphirst closed this as completed Apr 9, 2016
@mikebe11
Copy link
Contributor

mikebe11 commented Apr 9, 2016

Glad to hear it! Thanks @Naudiz

@aphirst
Copy link
Author

aphirst commented Apr 14, 2016

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?

@aphirst
Copy link
Author

aphirst commented Aug 10, 2016

It seems that when installing EmojiOne using "EmojiSwitcher", the same bug is encountered. I'm going to go and report that to them now.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants