Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Voice input does not work and icon doesn't appear #1367

Open
fallsdevil opened this issue Feb 16, 2025 · 6 comments
Open

Voice input does not work and icon doesn't appear #1367

fallsdevil opened this issue Feb 16, 2025 · 6 comments
Labels
bug Something isn't working

Comments

@fallsdevil
Copy link

Describe the bug

To Reproduce
By activating "voice input" in the toolbar, the icon does not appear, even activating in the "fixed" option. Strangely the icon appears sometimes, but by clicking on it, nothing happens. I tested using the Gboard and funned correctly, and already used the HeliBoard on another Samsung A01 Core device, Android 10 GO Edition and worked. But in mine, it is like this, I tried to update Google's voice recognition and move the system settings and found nothing relevant.

Expected behavior
that some permission pop-up pars appear to use the microphone for this function to work. I entered the app information and looked at the permissions, but I didn't have that voice permission.

Screenshots

App version
2.3

Device:

  • Model: Samsung Galaxy A10s
  • OS: Android 11
@fallsdevil fallsdevil added the bug Something isn't working label Feb 16, 2025
@yaomtc
Copy link

yaomtc commented Mar 2, 2025

I'm on GrapheneOS (Android 15) and the default AOSP keyboard has a mic button present but it doesn't work for me. On Heliboard, same issue as yours, mic button won't show up. My voice input app is set to Dicio. I don't see any other options on F-Droid.

@Helium314
Copy link
Owner

that some permission pop-up pars appear to use the microphone for this function to work

It does not work that way. Like AOSP Keyboard, HeliBoard voice input button switches to a "shortcutInputMethod" as Android calls it. The button only appears if getShortcutInputMethodsAndSubtypes actually returns any subtypes.
So if you do not have any voice input methods (e.g. Sayboard) installed, the button will not show up.

My voice input app is set to Dicio.

If you have a voice input method installed and the button still does not show up, then I don't know what is wrong. I remember that was an issue with GrapheneOS, but it was fixed by a contributor. Maybe with Android 15 it's showing up again?

@soupslurpr
Copy link

soupslurpr commented Mar 8, 2025

I'm on GrapheneOS (Android 15) and the default AOSP keyboard has a mic button present but it doesn't work for me. On Heliboard, same issue as yours, mic button won't show up. My voice input app is set to Dicio. I don't see any other options on F-Droid.

This isn't a GrapheneOS issue at all. Dicio doesn't have a voice input keyboard option. Both AOSP keyboard and Heliboard just switch to an enabled voice input keyboard if it exists. You need to enable it from Settings > System > Keyboard > On-screen keyboard.

You can download a voice input keyboard and then it should work. You can try mine called Transcribro https://github.com/soupslurpr/Transcribro or Sayboard if you prefer https://github.com/ElishaAz/Sayboard.

@yaomtc
Copy link

yaomtc commented Mar 8, 2025

Ah, I see. Seems odd that Dicio is an option in Languages>Voice input despite needing to open the app to use that "text to speech popup" that apparently can't be triggered outside the app. I'll give your app a try.

@soupslurpr
Copy link

Languages > Voice input is a separate thing. It's a user-preferred app which other apps can use for speech to text. There's no UI provided by the voice input app; it needs to be provided as appropriate by the app that's calling it.

Whereas what AOSP keyboard and Heliboard are asking for is just switching to a voice input keyboard if the user has one enabled, they don't have control over it at all.

@yaomtc
Copy link

yaomtc commented Mar 9, 2025

Thank you for explaining!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants