Watermelon GrapheneOS Is it necessary to also restore the keyboard to enabled state in the keyboard settings? I can see that the toggle is locked in the enabled position, but it doesn't necessarily mean that the operating system ignores the saved state (enabled/disabled) for it too, in case there's a severe bug allowing it to be disabled somehow. Thanks
PANICBUTTON Even if I switch off the default keyboard in System>Keyboard>On-screen keyboard, pressing the language switch key reactivates it and switches to it.
pizzaiolo One workaround that worked for me was using adb to disable the app: adb shell pm disable-user com.android.inputmethod.latin
Novalissoide pizzaiolo forcing the system keyboard to disable creates a risk of bricking. In that the keyboard to unlock now relies on a user-installed third party app. If that keyboard glitches, e.g. after a OS update reboot, you will need the stock keyboard option ready.
pizzaiolo Well, sadly it seems GOS updates reenable the app anyway, so I think that's covered. The thing about the AOSP keyboard is that it does not support non-Latin alphabets, so it's not ideal if we hope for i8n.
horde pizzaiolo Well, sadly it seems GOS updates reenable the app anyway, so I think that's covered. Yes, because some users were locked out of their phones (their keyboard wasn't showing up as it didn't support direct boot) and couldn't type their password to open their device.