• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Speech to text won't recognise "o'clock"

L

LGallyandriods

Newbie
I have a new Samsung A51 and it has the same problem my S6 had.

If I speak any number in front of the word "o'clock", it will not create the o'clock. For example, if I say "1 o'clock 2 o'clock 3 o'clock" it will only create 123. If I speak the word o'clock by itself, it will create it but not if it follows a number.

Why?
 
Samsung devices, so I assume you're referring to Bixby.

It could be because something like "1 o'clock" is ambiguous to it, like "Hey Bixby, set an alarm for 7 o'clock.", now is that AM or PM? Just a guess of course, as I never use voice assistant features myself.
 
mikedt said:
With Samsung phones the default speech to text is Bixby isn't it. So what are you actually using, Google Assistant, or something else?
Click to expand...
It can depend on the keyboard. For the sheer hell of it I just enabled it on a couple of my keyboards to see what happened:

* SwiftKey: told me I would need to install Google Voice Search for it to work. Since I have the Google app disabled through choice and was not prepared to undo that the experiment ended there.

* OpenBoard: did nothing. I assume this means that it uses the system default voice input, which for me is disabled.

* GBoard: there's obviously a connection to Google's service built directly into that app, because this worked even though the Google app is not available on my phone (it was definitely server-based, as it required an internet connection to function). So my guess is that if you use GBoard you use Google for this regardless of what the system default text to speech engine on your phone is.

GBoard would not type "7 o'clock" for me, but it also wouldn't write "o'clock" full stop: the closest it came was "oclock", but it also left out the "o", or printed something like "on clock", or ignored it altogether. It just seems to be a blind spot in Google's transcription. Since "o'clock" is perfectly well understood Stateside this can't just be an example of Google's parochialism, but I can't think of a good reason why they can't handle it, all I can say is that it seems to be a limitation of Google's system.

So maybe the workaround is to try enabling another text-to-speech system on your phone and see whether that works better?
 
I'm not sure that another speech to text app is available. As you can see in the screen shot, it is automatic.

upload_2020-8-14_8-0-59.png
 
You don't have a setting to change the text-to-speech engine? On regular Android it's in the Accessibility settings (though it can also be accessed from input settings), but I'm never sure with Samsung since they like to rearrange all of the menus.

Of course if you don't have another one installed there will only be one option.
 
You must log in or register to reply here.
Back
Top Bottom