LeanType using non-system emoji font

[Purpose-arch]

Describe the bug
LeanType uses non-system emoji font, I have module changing system emoji font and LeanType apparently using built in emoji font
Few versions earlier (don't remember the exact version), everything worked just fine
I noticed that LeanType have that 'built-in' emoji font not only in keyboard so far, but also in app itself (in search input field, for example)

App version
3.9.5 standard full

Device:

• Model: Nothing Phone 1
• OS: crDroid16

[LeanBitLab]

Describe the bug LeanType uses non-system emoji font, I have module changing system emoji font and LeanType apparently using built in emoji font Few versions earlier (don't remember the exact version), everything worked just fine I noticed that LeanType have that 'built-in' emoji font not only in keyboard so far, but also in app itself (in search input field, for example)

App version 3.9.5 standard full

Device:

• Model: Nothing Phone 1
• OS: crDroid16

Using EmojiCompat (Current State)

Pros:

• Backwards Compatibility: Guarantees that newer Unicode emojis will render properly on older Android versions (down to API 21) that do not have updated system font files. Emojis won’t show up as tofu (☐).
• Consistency: Emojis look identical within LeanType regardless of which Android device or OS version the app is running on.

Cons:

• Ignores System Customizations: Overrides system-level custom emoji fonts (such as those installed via Magisk modules, root font tools, or OEM themes).
• Increased Startup & Memory: Takes extra startup time to initialize the downloadable font provider and loads an additional font into the app’s memory space.

Using System Emoji Font (Proposed State)

Pros:

• Respects User Customizations: Respects system-wide custom emoji font modifications (Magisk modules, root, custom ROM fonts). - Emojis in the app’s settings and search field will match the system’s look.
• Consistency with OS: The app UI matches the OS theme and custom fonts.
• Lighter Footprint: Removes startup overhead and extra memory allocation from downloading/caching duplicate emoji fonts.

Cons:

• Tofu on Older OS Versions: If a user runs an older Android version (e.g., Android 8 or 9) without system updates or font modules, newly introduced emojis might render as tofu (☐) inside the app’s search box or settings.

Note: This only affects the app’s standard text fields (like settings and search input). The keyboard’s key draw canvas remains unaffected, as LeanType already has a separate option to load a user-supplied custom emoji font for the keyboard layout

[LeanBitLab]

Describe the bug LeanType uses non-system emoji font, I have module changing system emoji font and LeanType apparently using built in emoji font Few versions earlier (don't remember the exact version), everything worked just fine I noticed that LeanType have that 'built-in' emoji font not only in keyboard so far, but also in app itself (in search input field, for example)

App version 3.9.5 standard full

Device:

• Model: Nothing Phone 1
• OS: crDroid16

lets try to have an option
not sure if it works

[LeanBitLab]

Describe the bug LeanType uses non-system emoji font, I have module changing system emoji font and LeanType apparently using built in emoji font Few versions earlier (don't remember the exact version), everything worked just fine I noticed that LeanType have that 'built-in' emoji font not only in keyboard so far, but also in app itself (in search input field, for example)

App version 3.9.5 standard full

Device:

• Model: Nothing Phone 1
• OS: crDroid16

check if the system emoji toggle works on v3.9.6