Sayboard intermittently stops transcribing in any app - GrapheneOS

[yo-scottie-oh]

Description of the issue:

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 stopped working. I cannot get Sayboard to transcribe anything.

About my system:

• GrapheneOS stable release channel (currently build 2024111800).
• Pixel 7a

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.

Steps to reproduce the issue:

1. Open the Messaging app.
2. Tap any conversation.
3. Tap to put cursor in text field, which brings up the keyboard.
4. Tap mic icon in top right corner of keyboard, which brings up the Sayboard interface w/ the word "Ready" below the outlined mic icon.
5. 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.
6. Speak some words.

Observed behavior:

Nothing happens - nothing gets transcribed.

Expected behavior:

My spoken words should be transcribed into the text box.

EDIT: Since posting this issue, I've also tried FUTO keyboard + voice input and cannot get that one to transcribe my voice, either, despite having granted microphone access. This makes me think there's some other issue with my overall device's configuration, not Sayboard itself. That said, I'm kinda stumped. An internet search for grapheneos voice input not working does not yield any useful results. If anyone has any idea how I might resolve this issue, I would appreciate it. Being unable to use any voice input is a major impediment for me. Thank you.

[ElishaAz]

Thanks for the bug report.

1. Does entering punctuation / space works?
2. Can you please try reinstalling Sayboard?

This might be related to Android 15, which was recently released. I'll have to check it in a VM.

[yo-scottie-oh]

1. Yes, entering punctuation through Sayboard works. The issue seems specific to the voice input.
2. Reinstalled Sayboard, but this did not resolve the issue.

FWIW I also posted in an Android forum. I've only gotten one response so far, from another user who confirms they have the same issue:

I’m on a 7a stock and have the same issue.

[yo-scottie-oh]

@ElishaAz as of this morning, voice transcription is working again. I don't know what changed—I'm still on the same GrapheneOS build, and as far as I know, I haven't changed any of my phone's settings. I double checked the mic access in the quick settings drawer—it is enabled, and I believe it was enabled the entire time or else I wouldn't have been able to record video with sound. I can't think of any other variables.

I suppose we can close this issue unless you plan to do any additional troubleshooting. Either way, thanks for chiming in.

[yo-scottie-oh]

Update: It has stopped working again. Last time I tested (this morning), it worked, but when I wanted to actually use it this afternoon, it wouldn't work. I'm still not sure what's changing, so I can't say if this is user error on my part, some inherent flaw with the OS, or something else.

[yo-scottie-oh]

Another update: When I tested this morning, it worked again. Over the last week, the pattern seems to be that it works when I test it in the mornings, but then at some point throughout the day (whenever I want to actually use it), something causes it to stop working, and then it magically starts working again when I test it the next morning.

Again, the issue seems like it's not specific to Sayboard, but I'll continue documenting my experience in case anyone else reads this.

I still haven't figured out what's causing the on-again-off-again behavior.