Voice search

Skip to first unread message

Jean-Pierre ジャン=ピエール

Nov 1, 2022, 9:43:02 AM11/1/22
to aedict...@googlegroups.com
Hello Martin,

I've been using Aedict3 for years now, and I'm still pleased of it.
However, I think since the last time I reinstalled the application, the integrated voice search seems to have changed. Maybe I forgot something, but I cannot find the solution in helps and web.

I think (maybe I dreamed ??) that when using the voice search, a list of possible matching words was appearing and that I was just to select the right one (in case of many homophons).

Could you clarify this point to me please ?

Thank you very much for your work !

With best regards,


Martin Vysny

Nov 4, 2022, 2:02:16 AM11/4/22
to aedict...@googlegroups.com
Hi Jean,

thank you for your e-mail, I'm happy to know that Aedict is serving
you well :)

Aedict never performed the speech-to-text itself. Aedict always relied
on the Android built-in speech recognition capabilities (or any
additional software that was capable of handling the
"android.speech.action.RECOGNIZE_SPEECH" intent), to perform
voice-to-text conversion. The speech recognition software then returns
one or more strings (= readings); 2 or more in case of homophones.

Could it be that an Android upgrade changed this behavior, or maybe you
have installed another software which handles the
"android.speech.action.RECOGNIZE_SPEECH" intent?

I'm not using this functionality much myself so I haven't noticed the
change, but now I tried a couple of homophones and Android always seems
to return just one result (maybe the most common one). Looks like Google
upgraded or changed something...

Best regards,
> --
> Please support the Aedict development, by subscribing for Aedict
> Ultimate in Google Play - thank you very much!
> ---
> You received this message because you are subscribed to the Google
> Groups "aedict-users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to aedict-users...@googlegroups.com
> <mailto:aedict-users...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/aedict-users/CALmbtD3Kda5pYMANW57LBmrdGq%3DUxQEhjGEVsuN6xw69tpju3Q%40mail.gmail.com <https://groups.google.com/d/msgid/aedict-users/CALmbtD3Kda5pYMANW57LBmrdGq%3DUxQEhjGEVsuN6xw69tpju3Q%40mail.gmail.com?utm_medium=email&utm_source=footer>.
Message has been deleted


Nov 4, 2022, 5:42:43 PM11/4/22
to aedict-users
Hi Martin,

Thank you for your clear answer.
So maybe as you said, there was a change on my phone or an evolution in the way of working of the Google-Android Speech-to-Text feature.

I will go on searching if possible to find what was the cause of this new behaviour, and if found, will keep informed here.

 Best regards,
Reply all
Reply to author
0 new messages