Open snomos opened 3 years ago
More feedback received:
It is not restricted to sjd, it turns out, it is also found in sme. And it seems to be a combination of network access and cache corruption: it works fine in the beginning, including after switching from other keyboards, but as time goes, it more and more goes into stale mode and needs to be reactivated. After removing it and reinstalling it again, it behaves properly for a while, before starting to hang/malfunction.
Slow or non-existing network connections make the hang more severe.
I can confirm that this is a problem for the north sami keyboard, as well, and has been for a long time.
A version without Pahkat services enabled was released December 13. It should fix the crash/hang, and make the keyboard usable again. This is of course just temporary while working on fixing the real issue with networking and Pahkat services.
It'd be very interesting to learn if this is still the case with 0.2.4 of divvun-dev-keyboard. How long of a timeframe are we talking about? Before the slowdowns become apparent that is. How many megabytes of "app data" is stored on the device? it would be interesting to know.
With 0.2.4 we've re-enabled pahkat.
Several SJD users have reported cases where the keyboard freezes, and must be deactivated and reactivated to be usable. In some cases it must even be reinstalled.
The following is a rough translation of a user report: