F-Droid upgraded me from LeanType v 3.8.2 to v 3.8.9. Upon upgrade, I noticeed two issues with key presses being recorded. If I tapped the period, a period would not be recorded. After tapping the period key several times, it finally recorded a period. This happens across all apps I type in regularly. The expected behavior is that I tap the period key once, a period will then appear at the cursor.
This also happened with the colon (:) key. I would longpress the v, the colon would show up in the hint, or whatever is called. In v 3.8.2, if I released the v key at that point, a colon would appear at the cursor. That is the expected behavior. In v. 3.8.9, nothing would happen after I released the v. I would have to repeat the process, selecting the colon twice after two separate long presses to get one colon.
I upgraded to v. 3.9 in F-Droid, and still these issues persisted. I uninstalled LeanType 3.9 and re-installed v. 3.8.2, and the issues disappeared with the rollback.
I'm currently using Android 16 on a Pixel 6 with all Google services disabled.
All-in-all, however, I really appreciate the level of customizability in LeanType, and I thank you for it.
F-Droid upgraded me from LeanType v 3.8.2 to v 3.8.9. Upon upgrade, I noticeed two issues with key presses being recorded. If I tapped the period, a period would not be recorded. After tapping the period key several times, it finally recorded a period. This happens across all apps I type in regularly. The expected behavior is that I tap the period key once, a period will then appear at the cursor.
This also happened with the colon (:) key. I would longpress the v, the colon would show up in the hint, or whatever is called. In v 3.8.2, if I released the v key at that point, a colon would appear at the cursor. That is the expected behavior. In v. 3.8.9, nothing would happen after I released the v. I would have to repeat the process, selecting the colon twice after two separate long presses to get one colon.
I upgraded to v. 3.9 in F-Droid, and still these issues persisted. I uninstalled LeanType 3.9 and re-installed v. 3.8.2, and the issues disappeared with the rollback.
I'm currently using Android 16 on a Pixel 6 with all Google services disabled.
All-in-all, however, I really appreciate the level of customizability in LeanType, and I thank you for it.