New-ish Android user here. About a week ago, I installed Sayboard through the Neo Store and started using it to transcribe voice to text in the default Messaging app in GrapheneOS. It worked flawlessly for a couple days; however, within the last day or two, it has just magically stopped working. I cannot get Sayboard to transcribe anything. I’ve tested with FUTO, same issue.
I initially posted a detailed issue on Sayboard’s GitHub, then I tried FUTO and experienced the issue there as well, so now I realize it seems to be more of an issue with my device’s configuration. For the life of me, I cannot figure out what it could be.
Does anyone have any other ideas I might try? More details below…
What I’ve tried so far:
- I’ve double checked app permissions - Sayboard has permission to record audio.
- I’ve checked for app updates - I’m using the latest version of Sayboard (v4.2.1).
- I’ve tested in multiple apps - for example, the Messaging app, Mull web browser, and Markor text editor.
- I’ve confirmed the issue is not with the mic itself. For example, I can record audio in the Camera app.
- I’ve searched the internet for grapheneos voice input not working, which does not yield any useful results.
Steps to reproduce the issue:
- Open the Messaging app.
- Tap any conversation.
- Tap to put cursor in text field, which brings up the keyboard.
- Tap mic icon in top right corner of keyboard, which brings up the Sayboard interface w/ the word “Ready” below the outlined mic icon.
- Tap the outlined mic icon. The mic icon changes from outlined to solid, and the text changes from “Ready” to “Say something.” A little green bubble also appears in the top right of my screen indicating that my mic is in use.
- Speak some words.
Observed behavior:
I’ve tried the same steps w/ Sayboard and FUTO and gotten the same result - nothing gets transcribed.
Expected behavior:
My spoken words should be transcribed into the text box.
About my system:
- GrapheneOS stable release channel (currently build 2024111800).
- Pixel 7a
Thank you!
I’m on a 7a stock and have the same issue.
Did the issue just start happening in the last couple days for you, too?