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

Wakeword service #9

Open
nshmyrev opened this issue Jan 21, 2022 · 3 comments
Open

Wakeword service #9

nshmyrev opened this issue Jan 21, 2022 · 3 comments

Comments

@nshmyrev
Copy link
Contributor

https://medium.com/picovoice/no-way-google-build-your-own-wake-word-service-on-android-339a0189ff4c

@WuerfelDev
Copy link

It seems like this is a privilege of system apps in Android 12 :(

The impact of these changes is as follows:

  • Nonsystem apps using the AlwaysOnHotwordDetector class fail to compile against the Android 12 API because the API was removed from the public surface.
  • Existing system apps using the AlwaysOnHotwordDetector class might be denied from using sound trigger features at runtime. To address this issue and allow these apps to access the microphone through sound trigger, declare the RECORD_AUDIO and CAPTURE_AUDIO_HOTWORD permissions for these apps.

https://source.android.com/setup/start/android-12-release#alwaysonhotworddetector

@paolo-caroni
Copy link

If I am not mistaken, the purpose of this app is to provide a system STT on android.
the wakeword service is required for voice assistants, such as "dicio", which are an app that uses STT (and in this specific case implements an internal STT instead of using the system one).
Imho vosk-android-service must not use wakeword.

@Doomsdayrs
Copy link
Contributor

Close issue as offtopic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants