129
submitted 7 months ago* (last edited 7 months ago) by Lettuceeatlettuce@lemmy.ml to c/opensource@lemmy.ml

Heliboard 1.2 has just released. This version fixes a bug with certain Android devices not providing haptic feedback or audio feedback.

Thanks devs!

Heliboard V1.2

[Edited] Ironically my keyboard auto corrected its own name to "helipad." Embarrassing ๐Ÿ˜ตโ€๐Ÿ’ซ

all 27 comments
sorted by: hot top controversial new old
[-] BeatTakeshi@lemmy.world 12 points 7 months ago

Is this the continuation of their fork of OpenBoard?

[-] scott@lem.free.as 11 points 7 months ago
[-] schizoidman@lemmy.ml 10 points 7 months ago

With the ability to set bottom padding and the vibration issues being fixed. I feel like it is a good replacement for FlorisBoard.

[-] Lettuceeatlettuce@lemmy.ml 3 points 7 months ago

I've been using it for the last several weeks and I really like it!

[-] SatyrSack@lemmy.one 7 points 7 months ago

My favorite new feature here is vertically swiping the spacebar for vertical cursor movement. Not as good as iOS's spacebar cursor implementation, but a welcome improvement over that of any other Android keyboard I have tried.

[-] Vigilante@lemmy.today 6 points 7 months ago

Can we get this on fdroid ?

[-] JustEnoughDucks@feddit.nl 4 points 7 months ago

It's also on izzyondroid, but only the previous version with the bug.

If someone is using auroradroid like they probably should right now, then it is easy to get it there. Hopefully the fixed build comes through soon

[-] Lettuceeatlettuce@lemmy.ml 2 points 7 months ago

Not sure if it's in fdroid by default, but you can get it directly from the github repo through Obtainium.

[-] Vigilante@lemmy.today 2 points 7 months ago

Yea but that isn't the same thing at all tho

[-] Lettuceeatlettuce@lemmy.ml 2 points 7 months ago

Yeah I know, just listing options.

[-] Vigilante@lemmy.today 2 points 7 months ago

Ok just sayin so no one gets confused

[-] nu11@sh.itjust.works 2 points 7 months ago

Do you get a conflict error when updating via obtanium?

[-] Lettuceeatlettuce@lemmy.ml 3 points 7 months ago

For the latest version from 1.0 going to 1.2, yes. They have a note about it. You need to uninstall 1.0 and reinstall 1.2 from Obtainium.

Just a quirk for this version only apparently.

Make sure to back up your configuration before uninstalling if you want to keep your settings.

[-] nu11@sh.itjust.works 2 points 7 months ago

Thanks. I had already uninstalled/reinstalled after commenting, just by chance. I don't know why it didn't occur to me to look at github... Thanks.

Glad it was only for this build.

[-] Lettuceeatlettuce@lemmy.ml 1 points 7 months ago

No prob, and yeah I agree.

[-] otter@lemmy.ca 6 points 7 months ago* (last edited 7 months ago)

Oh that was fast. I just tried it and switched back to my default because of the bug.

I'll try it again ๐Ÿ˜›

Edit:

Looks good! Hello from HeliBoard

I had to uninstall and reinstall to fix the issue (updating with the new APK didn't work). I'll try it out a few days and see how it goes.

Is there a list somewhere of other stuff that's being worked on? Some I'd enjoy:

  • ~~better emoji support~~ this looks OK, I was looking in the wrong place
  • gif insertion
  • on device translation while typing
[-] PoorPocketsMcNewHold@lemmy.ml 1 points 7 months ago

Yeah, they butchered the signing key validity https://github.com/Helium314/HeliBoard/issues/624

[-] echa@lemmy.ml 3 points 7 months ago

awesome keyboard, thanks for sharing.

[-] Lettuceeatlettuce@lemmy.ml 2 points 7 months ago

No prob! I've been really liking it so far.

[-] walderan@sh.itjust.works 3 points 7 months ago

Just figured out yesterday that OpenBoard is abandoned and jumped over to Heliboard, thanks to the announcement for 1.0 in this community. The top comment mentioning FUTO Voice Input, was also a great find.
The only annoying part is that I now have to retrain my recommendations for HB, since OB unlike HB, offers no way to extract your settings, and I found no method to access the settings files in newer Android. Thankfully, since HB offers import/export, it will be the last time.

[-] Amaterasu@lemmy.world 1 points 7 months ago

Feedback: Review the red underline incorrect assignment to correct words from secondary keyboards. For example, if we have English keyboard as the primary keyboard with its own dictionary the words don't get underlined red. If we change to a secondary keyboard, like for example Spanish, French, Portuguese, etc... and they have their own dictionaries, no matter if the word is correct it will get underlined in red like if is incorrect when it is not.

[-] DreadPotato@sopuli.xyz 1 points 7 months ago

I just wish the autocorrect would work...at the moment there is zero difference when I change how aggressive it is in the settings, and it barely makes any suggestions or corrections to typos.

this post was submitted on 02 Apr 2024
129 points (99.2% liked)

Open Source

31358 readers
273 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 5 years ago
MODERATORS