eclexicMar 4

#Heliboard is gathering gesture typing data, so that we can implement a #FOSS alternative to the closed gesture typing library Heliboard currently relies on. The data we collect will be released under the CC BY-SA 4.0

I also made a video including details & instructions.

Boosts Please! The greater the diversity of people & languages in the data, the better we can test for correctness.

PT: https://makertube.net/w/cQECfDkuLGR9eUQquUEo4K

YT: https://youtu.be/CyjumVTWtJA

Text (instructions only):
https://github.com/Helium314/HeliBoard/wiki/Tutorial:-How-to-Contribute-Gesture-Data

Help Make Gesture Typing Better

PeerTube
Show threadJamey Sharp

@theeclecticdyslexic I'm so glad somebody's working on open gesture typing. The instructions in https://github.com/Helium314/HeliBoard/wiki/Tutorial:-How-to-Contribute-Gesture-Data didn't work for me, though.

I installed Heliboard from F-Droid. It didn't show gesture-related settings, so I did "Load gesture typing library"; it says I need arm64-v8a, so I followed the ARM64 link in the tutorial and downloaded the 1.1MB .so file; but Heliboard reported "Unknown library file. Are you sure you got it from a trusted source ...?" and after confirming, the app closed. On re-opening it, the gesture menu items still aren't present. (Due to my F-Droid installation's repository data being stale I got version 3.6 at first, but I upgraded to 3.7 and tried the same steps with the same result.)

Is there any debugging information I can provide? I haven't used adb in years but can probably figure that out again.

Tutorial: How to Contribute Gesture Data

Customizable and privacy-conscious open-source keyboard - Helium314/HeliBoard

GitHub
Mar 4 at 10:44amWeb
Show threadMarkus SeifertMar 4

@jamey @theeclecticdyslexic same problem here. Pixel7a with Googles stock Android, Heliboard from fdroid. ARM64v8a recognized, downloafed the "ARM64" ...so file and at loading the App closes.

Edit: OS and App are both set to german, if this helps?

Show threadeclexicMar 4

@markusseifert @jamey that's very surprising that it didn't work for you both. On many pixel devices they actually have the library out of the box, and don't even need to load it.

I will double check I didn't make a mistake of some kind! Maybe I mixed up two links.

Edit: just tried it. It's a problem with that version of the library MindTheGapps seems to have applied optimisations for. I'll replace the links with older versions. Shouldn't have assumed all versions worked!

Show threadCadenMar 4
@theeclecticdyslexic @markusseifert @jamey I had the same problem on a Pixel 8 (GrapheneOS) and got it to work by using the library from the tau branch of MindTheGapps. That's 5 years old though so there may be a more up to date one that works
Show threadeclexicMar 4

@tarix29 @markusseifert @jamey links are updated now. :-)

Sorry about the confusion everyone!

Show threadeclexicMar 4

@markusseifert @jamey

https://gitlab.com/MindTheGapps/vendor_gapps/-/blob/fe250848941171fe339ca9a44bc9a42aefb0be7d/arm64/proprietary/product/lib64/libjni_latinimegoogle.so

This one should work for arm64. It's much older, and loaded fine on my device.

arm64/proprietary/product/lib64/libjni_latinimegoogle.so · fe250848941171fe339ca9a44bc9a42aefb0be7d · MindTheGapps / vendor_gapps · GitLab

GitLab.com

GitLab
Show threadJamey SharpMar 4
@theeclecticdyslexic @markusseifert Yes, that works for me. Thank you! I'm glad we could help validate the instructions; I hope that helps you to get more training data 😁
Show threadMarkus SeifertMar 5

@theeclecticdyslexic @jamey works fine, the first 200 swipes were gathered and sent.

Thank you for your work!