I’m using Signal on my Kompakt, but in the last two versions (7.67.1 and 7.68.4), I’m experiencing an issue where my keyboard doesn’t open when I launch the app and try to type a message for the first time. To get the keyboard to appear, I have to lock my phone and unlock it again, press the home button and return to the app, or find some other way to “kickstart” the keyboard.
Hm, interesting.
I have the same keyboard-won’t-appear bug.
I can choose the , and it opens the emoji view, but when I press the again, it keeps the “space for keyboard area” but won’t display the keys (and they’re not “hidden”, I just tried - it’s just blank).
If I choose the icon (in a Signal group chat) though, and then close the camera, and then click in the typing area, the keyboard pops up (so “opening the camera” is enough to trigger it but still “stay in the app”).
I have Signal v.7.68.4 (from Aurora store), and the FUTO keyboard (from F-droid), installed.
(In the github thread, someone with a Huawei (i.e. not Mudita) and Signal v.7.67.1 has the same problem, so it’s probably a Signal problem?)
Yes, I experience exactly the same thing as you describe. The issue is probably with Signal, as my keyboard works in other apps that require it, like the SMS app and notes.
The similarity with the Huawei user is that they are also running Android 12. Maybe there’s something there that is causing the problem.
Are you using the stock keyboard.
Just tested it with SIGNAL I have 7.68.4 which I think has been updated recently. Everything works fine on my end with the NATIVE Mudita keyboard
The bug in Signal seems to be related to having disabled animations via Developer Options. If animations are enabled, the keyboard works, regardless of the keyboard used. (@urszula@pSE)
Hm, I have neither enabled Developer Options, nor disabled animations, and the keyboard (now trying out Thumb-Key, from F-droid) still doesn’t work without going back-and-forth.
But I (have inkOS v.0.3, and) used Settings Search { to look for ani
Found a “Remove animations - Text and display”, which was off.
Turned that setting on (and Force closed Signal). Keyboard still didn’t work, but now “as expected, per your instruction”.
Turned that setting off again (and Force closed Signal, again). Now the keyboard works, as expected, and per your instruction.
Weird and strange, but it works.