Closed RobSteward closed 1 year ago
Hi Rob,
I remember there was a discussion about Lineage OS once with a similar problem. The reason was that Lineage OS has no native
service for speech recognition integrated or it is disabled because it is bound to the (disabled? non-existing?) Google services. If ASR engine is set to native the service will throw an error if the app tries to use it.
Can you try the microphone setup in settings -> media devices
just to see if the microphone in general is working? If the recording works but you can't hear anything try to set the gain to ~10 for a start.
If it works you can switch to the SEPIA STT server as alternative and host your own, fully private speech recognition.
Fair enough. Can't have convenience and privacy :D.
Will look into setting up a SEPIA SST server
at some point.
Can't have convenience and privacy :D
Well ... not quite yet 😅, but the STT server is getting better and easier to install with every update ^^. The good microphones of modern smart phones help with the recognition quality as well, just be sure to run the mic setup once to find (and store) a good gain setting.
Technically it is even possible to run one of the STT engines on device but the user experience isn't very good on most devices yet and the app size increases from 5MB to 50MB :-|, so I'm not yet willing to include it for experimentation only.
It is probably fair to mention that Google Android STT is able to run offline, even on my old 2017 Samsung A3, but of cause you still don't know what they do with the data and you never really know which mode (online/offline) is active.
Describe the bug Microphone blocked and unable to use voice on Android mobile app
SEPIA client and server versions
To Reproduce Steps to reproduce the behavior:
Expected behavior Microphone access allowed and listening mode started
Additional context
https://user-images.githubusercontent.com/13047378/179981733-c08c47fb-1b42-4f8d-927c-35c09fe11792.mp4