this post was submitted on 01 Apr 2024
320 points (97.6% liked)
Open Source
31021 readers
606 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Been using this for about 3 months or so. The one piece missing is good swipe word recognition - its really poor compared to Gboard even after this amount of time. I spend more time correcting words than I saved nor typing them. Used swipe with Gboard for many years previously so I know hope swipe works.
Any suggestions on how to improve it?
I have found this to be the case as well.
What it has forced me to do now is to actually try to be close to the letters. When I'm swiping with gboard, I was very sloppy and it would recognize what I wrote. At this point, I'm fine being more accurate for the tradeoff.
Hmmm. Yeah I'm pretty sloppy about my letters too. Maybe I need to be a bit more precise to get the best out of it.
I have to admit that gboard is pretty amazing at the detecting my sloppiness. But... knowing everything I type and say is going to Google... well, let's just says I'm willing to tolerate the extra work so as to keep things away from them.
FUTO is definitely slower than Google's speech to text engine, but for the same reason... I think I'm completely okay with that now.
I've turned off network access for Gboard and have the offline speech recognition installed. This is why I have Helioboard + FUTO installed but don't use them, as they don't yet exceed an offline Gboard in function.
Dang. I use TrackerControl to do just that for many apps and hadn't even thought about trying to do it for gboard + gvoice because I had not know they had offline processing available for both.
Now its tempting to switch back and see... 😬 but... so far this combo of HeliBoard with swipe and FUTO have been sooo close... and its not google. 😏
In Gboard settings, under voice typing, it is the faster voice typing toggle. That brings the voice recognition library onto your device rather than using data. The only thing that does not work in Gboard after disabling network access is the gif search.
I extensively use glide typing when not using voice, and as you'll see from other comments on this post the glide typing is not so great on Helioboard.
And... I do kind of prefer Gboard's style of voice to text where I voice all of the punctuation. Pausing and thinking about what you are going to say using FUTO means it tends to end a sentence.
Yeah, I'm having to tolerate a whole bunch for this next best solution, but it's far from perfect.
It seems you and I have near identical usage style and when the same pet peeve, so I completely understand why you use it the way you do. I'm quite terrible and very very slow at typing normally. When I watch my kids text, it literally boggles my mind. It simply is impossible for me.
@uninvitedguest@lemmy.ca I decided to give try to gboard+trackercontrol. Internet access is now offfl. It blocks tenor as expected and the offline swipe seems to work as desired. (Which means light-years ahead of any other swipe I've used)
What I cannot tell is if the voice input truly is offline. I had always presumed that Gboard was relying on "Google Voice Typing" integration, but I have that keyboard disabled. I still feel wildly uncomfortable using voice with gboard. How is it so accurate without going online?
Any thoughts on how to ensure gboard voice is also 100% blocked?
Put your phone in airplane mode and test the voice input again. The experience should be the same.