Keyboard not working with sailfish apps

On my Xperia 10 111 keyboard doesn’t work.
All other apps are OK.
Also, it is not possible to save contacts from apps like Telegram and Signal.

REPRODUCIBILITY:
OS VERSION:
HARDWARE:
UI LANGUAGE:
REGRESSION:

DESCRIPTION:

PRECONDITIONS:

STEPS TO REPRODUCE:

EXPECTED RESULT:

ACTUAL RESULT:

MODIFICATIONS:

ADDITIONAL INFORMATION:

If you want this to be a bug report, please fill out the template.

It is for example not clear what you mean what is not working wrt. keyboard.

4 Likes

Also please explain what “111 keyboard” means.

Additionally, open a separate bug report for the different topic of “Also, it is not possible to save contacts from apps like Telegram and Signal.” (apparently that is supposed to address only Android apps), but please do search first, if one already exists (IIRC that is the case; if so you may chime in to the discussion there).

2 Likes

Stupid question, have you tried shutting down and restarting the OS? For some things that didn’t work, this way they work again.

Xperia 10 III.
Restart doesn’t help

The correlation between people who think they don’t need to fill in the template and those who really needs it is quite strong.

@olf
111 is just a failed attempt to write III, in Xperia 10 III.

What does “all other apps are OK” mean in this context?
Are you calling the keyboard an app and comparing to everything else? Why?

The virtual keyboard (i.e. on-screen, assuming that is even what you mean) works just fine on a fresh install.
So presumably you have done something to make it stop working. Did you attempt to install a custom one?
Did it ever work for you before? When did it stop? We are not psychic - you need to include these things if you expect anyone to be able to help.

1 Like

Hmm might be coincidence, but I just had the keyboard fail/not working after a fresh reboot.

The maliit service was in a restart loop. Error messages said it could not connect to the xt9 socket.
Indeed the xt9 service had crashed for an unknown reason.

The Socket file in /run/activeuser was present, but the xt9 daemon was not.

Starting the xt9 service manually made the keyboard work again.

Note the failure was not immediately after boot, but after typing a single letter (in whisperfish).

So, reliability of the maliit service should be improved, it should run even without xt9 being functional.

I found this in the journal:

Sep 03 10:05:48 PGXperiiia10 xt9-server[17776]: Starting loading dynamic keyboard
Sep 03 10:05:48 PGXperiiia10 xt9-server[17776]: [2B blob data]
Sep 03 10:05:48 PGXperiiia10 xt9-server[17776]: Error adding a dynamic key: 71
Sep 03 10:05:48 PGXperiiia10 xt9-server[17776]: coords: 165 734 265 932
Sep 03 10:05:48 PGXperiiia10 xt9-server[17776]: Content: ,
Sep 03 10:05:48 PGXperiiia10 xt9-server[17776]: Error adding a dynamic key: 71
Sep 03 10:05:48 PGXperiiia10 xt9-server[17776]: coords: 809 734 909 932
Sep 03 10:05:48 PGXperiiia10 xt9-server[17776]: Content: .
Sep 03 10:05:48 PGXperiiia10 xt9-server[17776]: ET9STATUS ET9Handle_KDB_Request(ET9KDBInfo*, ET9WordSymbInfo*, ET9KD
B_Request*): 2

I do have “sfos-patch-keyboard-xt9-intelligence” and other kbd related patches installed. And the Whisperfish emoji thing.

SFOS version: 4.4.0.72

feature-xt9-0.0.7-1.3.2.jolla.aarch64
harbour-neuntrainer-0.9.7-1.3.1.jolla.noarch
jolla-keyboard-settings-xt9-0.8.28.3-1.7.2.jolla.aarch64
jolla-xt9-0.5.19-1.5.2.jolla.aarch64
jolla-xt9-cp-0.2.12-1.3.2.jolla.aarch64
jolla-xt9-server-0.5.19-1.4.61.jolla.aarch64
patterns-sailfish-xt9-0.0.7-1.3.2.jolla.aarch64
sfos-patch-keyboard-xt9-intelligence-1.1.0-2.noarch
2 Likes