It is one of the oldest issues on GitHub. I assume you're using either AOSP Keyboard or OpenBoard, beacsue so far it seems that it only happens on those keyboards. I don't know about AOSP Keyboard, but with Openboard, in the Text Corrections section, if you disable "Show correction suggestions" it should work properly now. Link to issue: https://github.com/dessalines/jerboa/issues/194 There is a comment there from the user MV-GH who has posted a screenshot (it's near the bottom) of the option you need to toggle off and it will work properly. If you need correction suggestions, I'd recoomend either switching the keyboard or switching the client.
this post was submitted on 08 Aug 2023
35 points (92.7% liked)
Jerboa
10270 readers
3 users here now
Jerboa is a native-android client for Lemmy, built using the native android framework, Jetpack Compose.
Warning: You can submit issues, but between Lemmy and lemmy-ui, I probably won't have too much time to work on them. Learn jetpack compose like I did if you want to help make this app better.
Built With
Features
- Open source, AGPL License.
Installation / Releases
Support / Donate
Jerboa is made by Lemmy's developers, and is free, open-source software, meaning no advertising, monetizing, or venture capital, ever. Your donations directly support full-time development of the project.
Crypto
- bitcoin:
1Hefs7miXS5ff5Ck5xvmjKjXf5242KzRtK - ethereum:
0x400c96c96acbC6E7B3B43B1dc1BB446540a88A01 - monero:
41taVyY6e1xApqKyMVDRVxJ76sPkfZhALLTjRvVKpaAh2pBd4wv9RgYj1tSPrx8wc6iE1uWUfjtQdTmTy2FGMeChGVKPQuV - cardano:
addr1q858t89l2ym6xmrugjs0af9cslfwvnvsh2xxp6x4dcez7pf5tushkp4wl7zxfhm2djp6gq60dk4cmc7seaza5p3slx0sakjutm
Contact
founded 2 years ago
MODERATORS
I use GrapheneOS with stock keyboard and the issue is there. It really shouldn't be up to the end user to change the keyboard though and the fix you describe doesn't work unfortunately. It should be fixed on Jerboa. It doesn't happen in other apps.
Really? Worked for everyone else? Also, I totally agree, but the dev doesn't seem to have done anything. Edit: the issue arises from The keyboard, not from the app itself
Very strange. Works on my other phone running Samsung's flavor of Android.not on my GrapheneOS though.
Thank you, that was exactly it. Using AOSP Keyboard with text correction. And thanks for the github link!
No problem!
Thanks for posting the GitHub link.
Yes, and it is very annoying. ~~However it does not seem to be happening now with Jerboa 0.0.42.~~
Edit: This is still happening for me too, as of Jerboa 0.0.42, with the AOSP keyboard. It does not happen in any other apps.
I use v0.0.42 and I still get it
Updating the version to 0.0.42 didn't help in my case.
@whatever and @Flyswat, you're right, it still happens with Jerboa 0.0.42. I didn't realize the behavior was related to the specific keyboard in use.
Worse: When jumping back and forth sometimes the text appears at another postion than the cursor and overwrites words it for some reason considers the one you are typing.
Same with me. Makes writing really hard because you really don't wont to add something later or chaos ensures.
Yes. I have found you have to tap the end of the comment to erase any spaces there, then continue typing the comment. Otherwise it will type in the middle of a sentence somewhere.
As theshatterstone54@feddit.uk suggested: Turning off auto correction ('Autokorrektur') solves the problem with my AOSP keyboard temporarily.
Let's hope there will be a better fix in the future, because as a non native english speaker I rely heavily on auto correction. Changing keyboard would be annoying, my fingers just got used to this one. And changing to another client than Jerboa would be sad as well, it's the only client on f-droid.
I have a similar issue with the line break and the numbers. Double tapping it will copy the last word word If I enter a number it wil also copy it4it.
I've never not had this issue while writing a comment since I first downloaded it, back to v0.0.35 around 2 months ago. Hopefully it'll be addressed soon.
It's quite frustrating, but I ended up being used to work around it (mainly tapping multiple times to the end of the comment). Feels like whacking an old TV to make it work.