• General
  • Which keyboard is most likely to replace the AOSP keyboard on GrapheneOS?

  • [deleted]

missing-root I don't agree that it has bad UX OOBE. Other than that, solid points. The stock apps look bad but that is UI. They function like expected.

    [deleted] yeah I think the gallery is the worst app, the rest is okay. LineageOS updated all the AOSP apps to material you, this should be very useful if the licenses are compatible?

    Simple Keyboard on fdroid. Open source and looks like Gboard. Last update was 4 months ago.
    Doesn't ask for network permissions.

    Simplemobiletools is bought up, all the F-Droid apps will not receive updates.

    Many are already packaged as part of the FossifyOrg fork of the same codebase.

    16 days later

    Hey y'all, sorry for asking again but curious to know of any recent recommendations here (as opposed to starting a new thread). I am not personally opposed to using the stock GrapheneOS keyboard (would prefer it, honestly) but I want to be able to theme the bottom black bar that is always there under the keyboard and is not overridden by the light or dark setting. I am trying to avoid inconsistencies with display for long-term burn-in reasons. Looks like Floris is still not updated recently and I'm not familiar with what others might be trustworthy at the moment.

    Thanks in advance!

      I like the AnySoftKeyboard very much: https://anysoftkeyboard.github.io/

      I've been using it for 3-4 years and love all the tweaks and customization options. Disclaimer: I haven't tested a lot of keyboards. I picked this for the good features and the privacy aspect.

      • [deleted]

      https://twitter.com/GrapheneOS/status/1584022806735781888

      Our thread at https://twitter.com/GrapheneOS/status/1580679185923964928 explains why we're so reluctant to bundle third party apps and that includes replacing these AOSP apps with an actively developed third party keyboard. We've been considering switching to shipping FlorisBoard but it's not quite ready to go.

      We don't currently have the resources to develop our own keyboard app so we can either ship AOSP keyboard or a third party keyboard app with only minor changes to whatever we choose. It must have Direct Boot support, which we implemented and submitted for FlorisBoard already.

      Direct Boot support enables using keyboard before the first unlock of the profile using it. It needs to be able to function when the profile's data is still at rest and not available to the OS to fully replace AOSP keyboard. FlorisBoard can do that now, but has features missing.

      https://twitter.com/GrapheneOS/status/1601437948133904384

      FlorisBoard is what we eventually plan to use instead of AOSP keyboard but FlorisBoard isn't at version 1 yet and is missing some basic features despite having advanced stuff like swipe typing working already.

      It's AOSP keyboard with minor modifications such as disabling learning based on your typing by default for improved privacy. You can use any other keyboard including the stock Pixel OS one which is Gboard. We may one day bundle FlorisBoard instead but it's missing some things.

      https://twitter.com/GrapheneOS/status/1759231287724794316

      If you want a keyboard with more features than the one included in GrapheneOS, consider using FlorisBoard. We may eventually be able to switch to a new keyboard as the basis for the one in GrapheneOS. At the moment, no third party keyboard meets our requirements.

      a month later

      As for florisboard, would you suggest we use the latest beta version provided on github or the latest stable version of 2022?

      OfflinePuffin

      We'll have to wait and see what license they will use. For now I can't see any license, i.e. it's proprietary even if the source code is available to see.

        I've looked into every keyboard suggested in this thread and they've all been absolute ass (as of today) and not at all comparable in functionality to gboard.... except heliboard seems really promising if you use the regular version and load in google's swipe support library. Hopefully florisboard gets it together as judging by their roadmap the keyboard might be usable by version 0.6, but at their current pace of development that may take years.

        Viewpoint0232

        OK we will have to wait and see

        If the keyboard is the correct license, but the speech to text model are not would it still be considered?
        I would think the speech to text models can be packaged separately since the futo voice app downloads them...?

        a month later

        I'm a new user of this OS and was looking for a way to add swipe, so i'd like to add that heliboard + google's swipe library works great here.