Yes, you can follow the tutorial at https://github.com/seasalt-ai/snowboy if you're handy enough. Otherwise I'll probably build in the training into hotword plugin myself in a while, but I currently have a lot of exams and deadlines for university, so that will take some weeks.So now that snowboy is gone is there a way to train a new wakeword?
Sadly im on windows and pretty new to coding.. so guess ill have to wait.. good luck with your examsYes, you can follow the tutorial at https://github.com/seasalt-ai/snowboy if you're handy enough. Otherwise I'll probably build in the training into hotword plugin myself in a while, but I currently have a lot of exams and deadlines for university, so that will take some weeks.
The website worked perfectly for me, thanks a ton! I was worried I'd have to make a Linux computer and learn how to code betterI've been looking into ways to train new hotwords yourself and published a simple website (created by rhasspy) to do so: snowboy.jolanrensen.nl (if the url doesn't work yet, hotwordplugin-image-kmpzomnrva-uc.a.run.app should. The DNS is still updating or whatever).
From my experience the results are not very good however... Even with like 10 samples, which makes sense, since the original Snowboy website had thousands of samples. So, hopefully someone has the time (and money) to host something similar to what Snowboy had before. If all works well for a couple of days,
I'll add a link to my new website in the Hotword Plugin app as well, but I hoped the results would be better...
(Remember there are still some fully trained samples at Github)
I don't have experience with bixby (since I don't use samsung devices) but maybe the "voice search" action in Tasker can do the trick?OK, so I can't figure out how to make Bixby start listening. If I simulate the Bixby key press it doesn't continue to listen and I don't know how the phone would know when to stop pressing the button if I have it continuously press the button. I was thinking that I could open the Bixby Voice app with one of its sub-activities, but it says Tasker doesn't have permission. Any help would be greatly appreciated.
Worked great, thanks. There are so many features and options in Tasker that I'll probably never get through them all, especially with constant updates, not that I'm complainingI don't have experience with bixby (since I don't use samsung devices) but maybe the "voice search" action in Tasker can do the trick?
I think so! The audio source option lists all the possible audio sources given by the android system, so if your device detects the microphone, of the sources should be the mic you're looking for.Is it possible to add a headset mic, Bluetooth or wired, as an audio source to have the app listen to?
What would it be called? I get the same options whether my headphones are connected or not.I think so! The audio source option lists all the possible audio sources given by the android system, so if your device detects the microphone, of the sources should be the mic you're looking for.
I don't know, I think maybe one of the voice ones. Like I said, I just took all of them from the android sdk and listed them in the settings.What would it be called? I get the same options whether my headphones are connected or not.
Interesting idea, I'll check, thanks for the effort(that's not sarcasm, I'm sincere)I don't know, I think maybe one of the voice ones. Like I said, I just took all of them from the android sdk and listed them in the settings.
Maybe there's an app on the Play store to test all mic types on your device![]()
I think if the microphone type selected is unavailable it will respond with that message (usually this is when the app is in the background and it tries to access the mic, hence the message). These are all the types available to me: https://developer.android.com/reference/android/media/MediaRecorder.AudioSourceI tried every mic and none were the headphones. I went into another room and said the hotword, making sure it worked first by saying it next to my phone. Some mics didn't work at all, it said it couldn't get microphone access from the background, while the app was in the foreground. The same kinda thing happened with an app I used to test the microphones like you suggested. Are certain mics off limits to regular apps?
So I read this,I think if the microphone type selected is unavailable it will respond with that message (usually this is when the app is in the background and it tries to access the mic, hence the message). These are all the types available to me: https://developer.android.com/reference/android/media/MediaRecorder.AudioSource
Oh I think this mic is actually for voice call recording... And that permission apparently is not for 3rd party apps according to Android Developers. So, I don't think that one would so the trick (and I might actually remove it since it requires a permission my app cannot ask for lol)So I read this,
"VOICE_CALL
Voice call uplink + downlink audio source
Capturing from VOICE_CALL source requires the Manifest.permission.CAPTURE_AUDIO_OUTPUT permissio n."
Does that mean I can give that permission to the Hotword Detection app with an ADB command and it will have access to that audio source?
So I can't just give it permission with an ADB command?Oh I think this mic is actually for voice call recording... And that permission apparently is not for 3rd party apps according to Android Developers. So, I don't think that one would so the trick (and I might actually remove it since it requires a permission my app cannot ask for lol)
No, the app needs to specify which permissions it wants. But apparently the voice mic sources are for call recording anyways, so they're not useful. So "Default", "Mic", "Unprocessed", and "Camcorder" are the ones to try. If none of those work I'm afraid you're out of luck. I did get it to work once with a usb microphone however, but I never tried it via bluetooth. I think bluetooth requires hooking into a call-service or something, so make sure it connects to it like a headset. Not something that's currently present in the app or that I have the time for at the moment to figure out if it's even possible with the Snowboy hotword recognition etc.So I can't just give it permission with an ADB command?
You might be able to access it apart from the hotword recognition and just relay it to the hotword recognizer, kinda like the app Buttons for Alexa. I haven't gotten too far into learning coding or making apps, although I'll get to it soon, so if this is irrelevant information then just ignore me. Either way I hope you can find time to figure that out, I wanted to trigger Tasker tasks while away from my phone, and maybe mess with some external microphones attached to one of my spare phones so I can trigger tasks from anywhere. Anyway, I have a lot of ideas that will probably never happen, but it's fun to imagine them anywayNo, the app needs to specify which permissions it wants. But apparently the voice mic sources are for call recording anyways, so they're not useful. So "Default", "Mic", "Unprocessed", and "Camcorder" are the ones to try. If none of those work I'm afraid you're out of luck. I did get it to work once with a usb microphone however, but I never tried it via bluetooth. I think bluetooth requires hooking into a call-service or something, so make sure it connects to it like a headset. Not something that's currently present in the app or that I have the time for at the moment to figure out if it's even possible with the Snowboy hotword recognition etc.
Might look at it in the future though![]()
As long as you use Magisk to systemize an app you're fine. Magisk modules are applied at boot.Isn't everyone using this plugin already heavily invested into Tasker which uses the accessibility service too? Wouldn't that mean it's not that big a difference?
ATM I have no other ideas to make it a system app. Magisk systemize module doesn't show HWP. Copying the apk to /system/app/ isn't possible, even with root. TiBa with root doesn't get the job done either. I'm wondering if it's not an Android 11 prohibition.
BTW, don't you run into problems with OTA updates once you've systemized an app?
Put it on my to do list, but again, don't have time atm. Thanks for letting me knowSome advise from the Tasker subreddit https://www.reddit.com/r/tasker/comments/miurdl/_/gt8gtec Ask the dev to give the app SYSTEM_ALERT_WINDOW permission, this will allow it to operate in the background; which is likely a cause (in newer Android, apps are limited what they can do in background).
create a new profile based on event picking up calls, make it switch off service.This might be a silly question but if your app locks up the microphone how can I talk on the phone if someone calls me?