AlwaysOnHotwordDetector

pythoner6

I feel like one of the big things missing for me in graphene right now is the ability to interact via voice (e.g. while driving). I've been looking into what it would take to get something working, but I'm beginning to think that it might be a much harder task than I was thinking it might be. Even assuming I was able to piece together some things to do text to speech to text and natural language processing, it seems like hotword detection (at least in an efficient manner) might be an issue. For one finding much documentation about how voice interaction works in android has been very difficult, but more importantly I have run into what seem to be two roadblocks. The first is that it seems all of the hotword related facilities are now a "system api" and to my understanding therefore only available to privileged system apps, which would require them to be signed by the same key as graphene which obviously I don't have unless I build graphene myself (and then I wouldn't get the automatic updates). The second is that I don't know if there's any documentation about how to create a model for the AlwaysOnHotwordDetection to use - which I assume might be hardware dependent since the aosp code just says things like A KeyphraseSoundModel is a specialized {@link SoundModel} for key phrases. It contains data needed by the hardware to detect a certain number of key phrases and the list of corresponding {@link Keyphrase} descriptors. Maybe this is just going to be a dead end, but I was wondering if anyone has done any digging into what it would take to get hardware supported hotword detection working on graphene.

unwat

pythoner6

I was hoping someone with more knowledge about this subject would hop in here and share what they know. I have messed with Google Assistant once, but that's about the extent of my experience.

Firstly, I don't think there's any way to get any kind of voice-activated app to work from the lockscreen.

You can try Voice Access. It uses accessibility services to work, so it might have more privileges than a regular app. There's a way to activate it with a floating button on your screen.

There's was a bit more discussion in another thread. Maybe you can browse through it and maybe glean some more useful information to get the your desired result?

pythoner6

I'm currently leaning towards looking at having a separate always on device, since really my usecase is just while driving so I could have a specific device (e.g. using a raspberry pi or something) just installed in my car which then communicates with an app on the phone over bluetooth.

MetropleX

The only way I can envisage doing something of this kind right now and on an open source basis would be looking at something like the Mycroft AI Assistant project.

The docs for building the Android app and instructions on how to host your own instance etc can be found here:
https://mycroft-ai.gitbook.io/docs/using-mycroft-ai/get-mycroft/android

Source code: https://github.com/MycroftAI/Mycroft-Android