this post was submitted on 23 Nov 2024
11 points (100.0% liked)

Ask Android

2073 readers
20 users here now

A place to ask your questions and seek help related to your Android device and the Android ecosystem.

Whether you're looking for app recommendations, phone buying advice, or want to explore rooting and tutorials, this is the place for you!

Rules
  1. Be descriptive: Help us help you by providing as many details as you can.
  2. Be patient: You're getting free help from Internet strangers, so you may have to wait for an answer.
  3. Be helpful: If someone asks you for more information, tell us what you can. If someone asks you for a screenshot, please provide one!
  4. Be nice: Treat others with respect, even if you don't agree with their advice. Accordingly, you should expect others to be nice to you as well. Report intentionally rude answers.
  5. No piracy: Sharing or discussing pirated content is strictly prohibited. Do not ask others for a paid app or about how to acquire one.
  6. No affiliate/marketing links: Posting affiliate links is not allowed.
  7. No URL shorteners: These can hide the true location of the page and lead people to malicious places.
  8. No lockscreen bypasses: Please do not comment, link, or assist with bypassing lock screens or factory reset protection.
  9. No cross-posting: Please take the time to make a proper post instead of cross-posting.
Other Communities

founded 1 year ago
MODERATORS
 

EDIT 4 - FINAL EDIT - Dec 3: I'm marking this issue Resolved now that it's been about a week since I've last had this issue. Thanks to all who chimed in in the comments.

EDIT 3 - Nov 26: It's working again as of this morning, so what I've observed over the last week is that it intermittently stops working in the afternoons when I want to actually use it, then magically starts working again when I test it in the mornings. This on again, off again is driving me mad. Does anyone have any idea why it stops working at random points throughout the day and then starts working again in the mornings? Sigh...

EDIT 2 - Nov 25: Aaaand it's stopped working again. 😢 Double checked the mic availability in quick settings, restarted my device, no dice. When I tested this morning, it worked, but whenever I want to actually use it, it doesn't work—so frustrating. If anyone has any ideas what could cause intermittently stop transcribing, I would greatly appreciate it.

EDIT 1 - Nov 25: I tested this morning, and it's working again. I don't know what changed—I'm still on the same build of GrapheneOS, same version of Sayboard, etc. As far as I can tell, the issue has magically resolved itself. I'm happy that I have voice transcription again, and by troubleshooting I learned some things about my device along the way, so I'll take the W. Thanks to everyone who chimed in.

ORIGINAL 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 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:

  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:

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!

top 8 comments
sorted by: hot top controversial new old
[–] SidewaysHighways 2 points 2 weeks ago (1 children)

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

[–] [email protected] 2 points 2 weeks ago

Did the issue just start happening in the last couple days for you, too?

[–] [email protected] 2 points 2 weeks ago (1 children)

Sorry, idk, I just checked and it worked for me on my Motorola g73, so maybe it's a problem specifically with Pixels?

[–] [email protected] 2 points 2 weeks ago

I just tested this morning and it's working again for me. I don't know what if anything changed in my device's configuration, but I'll take the W. Thanks for chiming in.

[–] pirat 1 points 2 weeks ago (2 children)

Possibly asking a dumb question here, but is your mic access available? There's a tile for it in the quick settings drawer.

[–] [email protected] 1 points 2 weeks ago

It just stopped working again. Worked when I tested this morning, and then this afternoon when I wanted to use it, it didn't work. Any other ideas I can try? 😢

[–] [email protected] 1 points 2 weeks ago

It's working again as of this morning, but I double checked and yes, the mic access was available (and I do believe it was enabled the entire time, even while I was having the issue). Either way, thanks for chiming in.

[–] [email protected] 1 points 2 weeks ago

You should try reporting this bug to GrapheneOS. Do you experience this bug in other phones? If not appears to be something specific to Your custom ROM.