Hi everyone,
I thought I would post this as a separate thread for the Tasker project I have started working on. Please see below information and if you have any questions or development ideas for the project, please comment back!
Please Try The New Google Drive link below. I am aware of sharing issues at the moment, I am unsure why this is happening but please try the new link and let me know!
This will listen for "Ok, Google" or "Hey, Google" IF the screen is on and proximity sensor is not covered - this is incase it is triggered in your pocket like it kept doing for me! ?
There's also a task in this project which you can create a tasker task shortcut widget to toggle the Hotword plugin on and off.
This task requires to have AutoInput installed, from the AutoApps made by Taskers developer. You can have it free on a 24hr basis by watching a video though.
Following people's comments about push notification issues, such as Gmail, I've included a "fix" which is a timed event profile which runs a simple task to turn auto sync off and on - this then tricks syncing process and gives you push notifications for Gmail and other Google apps.
It is currently set at 4 hours, to save battery but feel free to change to what ever you need by editing the profile event.
Required Apps:
Tasker
Hotword Tasker Plugin
Working Google Apps/Services on device.
Google Assistant app
Profile Optional Apps:
AutoInput
AutoNotification
Firstly, install "Hotword Tasker Plugin".
[url]https://play.google.com/store/apps/details?id=nl.jolanrensen.hotwordPluginFree[/URL]
Then, install Tasker if you don't already have it. This is a paid app, but totally worth it when you have a look at it.
Also, download the tasker project file I have made for this. See below changelog and download links!
Open the Hotword Plugin app, click the red + circle at the bottom, choose both Google options - so you have "Ok, Google" and "Hey, Google" and press OK.
Edit both options and turn off the "Play ding sound" option. I found it annoying anyway as Google makes its own noise.
Then, click app settings on top right, choose "start listening on boot".
After this, you can click "microphone service" to ON Position, top right of the screen.
This starts the plugin and at same time it interrupts Huawei "Celia" from listening I found.
Then, import Tasker project "Google Hotword" that you have downloaded.
To do this, open Tasker, click the house icon in the bottom, left corner. Then, click "Import Project", navigate to where you've downloaded the project file to and select the file.
Then, soon as that's added, try "Hey, Google" or "Ok, Google". At this point it should all be working!
Changelog:
Version 1.0.3:
Changed action for HotwordPlugin from launching a Voice Command to launching Assistant instead, as it was launching then Google / Voice Command was redirecting itself to a Google news feed page with search bar, thus stopping the voice input.
Version 1.0.2:
Added profile to detect if camera is opened as it interferes with apps which audio, i.e video recording.
**This profile requires AutoNotification to be installed as a plugin, part of AutoApps by Taskers Dev.**
Version 1.0.1:
Scrap all other links, I hadn't put the profile in to the project so no idea if it had it included in the previous exports but try this one guys ?
Downloads:
Version 1.0.3
Google Drive
https://drive.google.com/file/d/1SU_0eoWk9JTt3testJ-i7LfDBFdm56O-/view?usp=drivesdk
Version 1.0.2
Google Drive
https://drive.google.com/file/d/1ArFMF5nXLTPbmz0tsweDXLTDUuabL_HE/view?usp=drivesdk
Version 1.0.1
Google Drive
https://drive.google.com/file/d/13yZVxDfIYv82Htlz4zb-9F8j8H1I8Wh5/view?usp=sharing
If you like what I've done, don't forget to click thanks as I know this is bugging a lot of people!
Your links to tasker and google drive do not work.
DevliegereM said:
Your links to tasker and google drive do not work.
Click to expand...
Click to collapse
Thanks for bringing this to my attention, I'll look at the links in the next couple hours as I'm working at the moment!
DevliegereM said:
Your links to tasker and google drive do not work.
Click to expand...
Click to collapse
Please try again, I have updated the link section of my post!
Where am I supposed to import that file, or from where....
..
New version updated and changelog updated.
I didnt understand how i "import" the downloaded google hotword and where?
Guercan said:
I didnt understand how i "import" the downloaded google hotword and where?
Click to expand...
Click to collapse
New version uploaded and see added import instructions.
I tried all the steps, but seems like it didnt work on my Huawei P40 Pro (ELX-NX9)
zoold3vil said:
I tried all the steps, but seems like it didnt work on my Huawei P40 Pro (ELX-NX9)
Click to expand...
Click to collapse
Where did you get stuck, maybe I can help.
I apologise for long replies but I don't usually do things like this anymore.
GlennBrownie said:
Where did you get stuck, maybe I can help.
I apologise for long replies but I don't usually do things like this anymore.
Click to expand...
Click to collapse
I have followed all the steps but still could not activate the voice.
My device has been upgraded recently to EMUI 11.0 (Beta), i'll try again if it's work this time.
Is there possibility to make it work when screen is off?
Robalo said:
Is there possibility to make it work when screen is off?
Click to expand...
Click to collapse
No, unfortunately, due to the limitations of the Hotword Plugin permissions it can't work with the screen off.
If you wish to raise that as feedback to the developer of the plugin, maybe they will research this, but it's out of my hands to be honest.
Related
Only for The Google Now for ICS Project users!
Simple addition for those who use Google Now on Android 4.0 with ARMv6 and want to take advantage of voice recognition. It won't work correctly on older versions of Google Voice Search, and it will not bring Google Now itself to your phone.
You can immediately start the voice recognition (without pressing the button) by holding down Search button for a while. Launcher shortcut is also available.
Changelog
Code:
1.3.2:
- Tweaked Manifest and minimal API Level to make this available for older devices with custom 4.0 ROMs
1.3:
- Renamed and repackaged to meet Google Play Android Developer Program Policy and Google Play Android Developer Distribution Agreement (DDA)
- You need to uninstall the old version first
- Fixed the bug when sometimes the first search did not work
- It is now possible to turn the voice talkback off
- The donate model was complete disaster, so buy it or let it go :)
1.2:
- App now integrates with the microphone icon on Google Now search widget
1.1:
- App now speaks back to you
- Fixed crash
Download
On Google Play
APK Mirror is no longer available.
good app..just tried it ..it can be a replacement for the current no voice search
the only small issue i found is ..i need to press enter again in google NOW ..once the words are translated and kept in search box ..to complete the search
(or is this actually not supposed to happen and i missed something ?)
I must have missed that. Will take a look at it
Does not work. Cannot find class com.google.android.voicesearch.IntentApiActivity.
Desire S, latest Theos0o vesion 5 Google Now app installed in /system/bin. Any idea?
agree with ganeshp. have to press enter again after the words are inputted into the search box.
can it be set to start by just pressing the search key and not long hold cause I have set long hold being voice command.
very good app. what happens is that asks you to complete the search options ...
could not be like the google search now on jb???
I guess in the next updates will be made ...
thanks!!!!
It's very good! I wish it spoke back to you tho
Sent from my Kangdemnationed/Jellified Incredible 2
I love the idea of this app - great job! Would it be possible to add voice calling capability?
great share!Thanks for your job.
can you make another option instead of search button since sgs2 has no search button? like long press home or menu button? thanks!
edit: my rom (slimrom) doesn't have long press menu for search
Works fine. I was wondering how I can make this pop up when I hit my search button on my search bar. Right now the search that comes up doesn't use Google now
Sent from my HTC One S using xda app-developers app
Thanks for your support! Little update is up, but I've ran out of time for today .
Changelog
1.1:
- App now speaks back to you
- Fixed crash
There is no solution for the "you have to press enter" issue yet. But I will work on it! Other features depend on my time and your donations ).
rzabcio said:
Does not work. Cannot find class com.google.android.voicesearch.IntentApiActivity.
Desire S, latest Theos0o vesion 5 Google Now app installed in /system/bin. Any idea?
Click to expand...
Click to collapse
Same here:
Code:
07-13 16:16:41.911: E/AndroidRuntime(2029): android.content.ActivityNotFoundException: Unable to find explicit activity class {com.google.android.voicesearch/com.google.android.voicesearch.IntentApiActivity}; have you declared this activity in your AndroidManifest.xml?
Nexus One, AOSP 4.0.4, latest Theos0o vesion 5 as system app
Edit: As fof the updated version i can't see it!? Market description still says Version 1.0?
Edit2: You beat me in answering my question before I even asked it!
Just check the updates, I think I fixed that . It might take a few minutes before it gets available on Google Play.
EDIT: Well, it seems that it can take hours... Google Play became very slow in distributing changes lately. Still better than Apple AppStore and BlackBerry AppWorld though :-D.
It is finally available! Please let me know whether it still crashes.
With updated version there is another error. In deed, I can run the application, but the effect is the same, as within standard Google Now: "Didn't catch that!"
I must have something broken in standard voice recognition system, cause it does not work everywhere...
::EDIT:: NEVERMIND. While experimenting with voice input I have removed Voice Search app. After reinstalling everything works. Thanks!
Great to hear
Working so far. The speaks back to you part is simply speaking out my search, not speaking out the answer. e.g.
I say, "what is 10+10", then press search on the keyboard, it will say "searching for what is 10+10" then shows the result of 10+10=20. But it does not speak "10+10=20" is this how it should work?
Yes it is . It's just simple utility I made so I don't have to type everything in, but it does not actually alter Google Now! features. There are ways to improve it and implement some more magic, but I'm not sure it's worth it .
could not be found
this looks awesome but when i try and download it it gives me an oops could not be found or a oops there was a problem try again later message, never seen those before anyone know whats going on?
any chance of posting an apk?
edit: started working
Hi,
I'm wondering if some of you KLD / KLG / MX / etc unit owners are using google voice commands. I can't use it properly on my unit, it crashes all the time. Sometimes it works, but usually it crashes. I'm using Malaysk rom. Is there anybody who can you use google voice without any problems? Or is there a simpel solution to fix my issues? I'm using a external mic connected with a jack to the backside of my unit.
I have spent a lot of time with this issue. My views are that the OEM version of the Google app is the only stable version(for voice use) for these HUs. My JY solution was to extract the Velvet.apk from the factory ROM. After updating to a Malsysk ROM, I replaced the pre updated apk back to the older factory version. You will lose out out on some updated features, but having a working voice command is nice tradeoff.
Velvet.apk, OEM JY Version
https://drive.google.com/file/d/0B0iQtPEIFgeHR3hQdGlvd2RrVUk/view?usp=sharing
Missing features.
carter.w.jason said:
I have spent a lot of time with this issue. My views are that the OEM version of the Google app is the only stable version(for voice use) for these HUs. My JY solution was to extract the Velvet.apk from the factory ROM. After updating to a Malsysk ROM, I replaced the pre updated apk back to the older factory version. You will lose out out on some updated features, but having a working voice command is nice tradeoff.
Velvet.apk, OEM JY Version
Click to expand...
Click to collapse
Hi, Does your okay google now allow you to make phone calls, send email etc.... what features are you loosing out by going this route. Thanks!!!!
aledesma said:
Hi, Does your okay google now allow you to make phone calls, send email etc.... what features are you loosing out by going this route. Thanks!!!!
Click to expand...
Click to collapse
Phone calls? No. I believe this is a common issue, there is no phone hardware onboard. Though I'm not that familiar with that feature.
Email and other task could be handled with Autovoice if Google app can not. Again, not that familiar.
For me, the main missing feature was choice of navigation app. Nav questions will only launch GMaps, newer version can launch Waze or your nag app choice, by default.
carter.w.jason said:
I have spent a lot of time with this issue. My views are that the OEM version of the Google app is the only stable version(for voice use) for these HUs. My JY solution was to extract the Velvet.apk from the factory ROM. After updating to a Malsysk ROM, I replaced the pre updated apk back to the older factory version. You will lose out out on some updated features, but having a working voice command is nice tradeoff.
Velvet.apk, OEM JY Version
https://drive.google.com/file/d/0B0iQtPEIFgeHR3hQdGlvd2RrVUk/view?usp=sharing
Click to expand...
Click to collapse
Thanks for your comment. I tried your solution and its working better, i still get some errors time to time, but is much better...thanks
[
aledesma said:
Hi, Does your okay google now allow you to make phone calls, send email etc.... what features are you loosing out by going this route. Thanks!!!!
Click to expand...
Click to collapse
If you have a phone connected via BT you can make phone calls using OK Google.
Tumke32 said:
Hi,
I'm wondering if some of you KLD / KLG / MX / etc unit owners are using google voice commands. I can't use it properly on my unit, it crashes all the time. Sometimes it works, but usually it crashes. I'm using Malaysk rom. Is there anybody who can you use google voice without any problems? Or is there a simpel solution to fix my issues? I'm using a external mic connected with a jack to the backside of my unit.
Click to expand...
Click to collapse
I've read some posts in the Malaysk ROM thread and many people have modded their units by opening them up and re-runing the internal mic. It's that mic, not the external, that is used for voice commands and apparently it is an unshielded wire that allows for a lot of interference and therefore unreliable google voice. I'm still foggy on the voice dialing but someone somewhere got this to work but not through the native bluetooth app. I think I read that they used the RK3066/Rk3188 app in the google play store or something...I'm just getting started with my unit and it's not even installed yet. Hopefully some of this was insightful for you.
newt_dunbarton said:
I've read some posts in the Malaysk ROM thread and many people have modded their units by opening them up and re-runing the internal mic. It's that mic, not the external, that is used for voice commands and apparently it is an unshielded wire that allows for a lot of interference and therefore unreliable google voice. I'm still foggy on the voice dialing but someone somewhere got this to work but not through the native bluetooth app. I think I read that they used the RK3066/Rk3188 app in the google play store or something...I'm just getting started with my unit and it's not even installed yet. Hopefully some of this was insightful for you.
Click to expand...
Click to collapse
I am using the latest Malaysk ROM dated 10th January 2016 for RK3188 1024*600. It lets me speak Ok Google and Call (contact name) to the phone when after pressing the call button. The way it works for me is:
1. Whatever is playing on the unit, it stops when I press the call button on my steering;
2. It launches the unit's dial screen;
3. I say 'OK Google', it launches the ok google listener on the phone;
4. I say 'Call (contact name)' and it calls.
Few things I had to manage before this started working was:
1. Enable the option to receive commands over bluetooth in Google Now settings in the phone;
2. Enable to XPOSED MTC in the XPOSED framework in the head unit;
3. Change the setting to integrate with phone's google now interface (something like that) in XPOSED MTC module.
Hope this helps.
Can you elaborate on this process please?
carter.w.jason said:
I have spent a lot of time with this issue. My views are that the OEM version of the Google app is the only stable version(for voice use) for these HUs. My JY solution was to extract the Velvet.apk from the factory ROM. After updating to a Malsysk ROM, I replaced the pre updated apk back to the older factory version. You will lose out out on some updated features, but having a working voice command is nice tradeoff.
Velvet.apk, OEM JY Version
https://drive.google.com/file/d/0B0iQtPEIFgeHR3hQdGlvd2RrVUk/view?usp=sharing
Click to expand...
Click to collapse
Did you go to file manager and replace the Malaysk version? Where is it located? or did you simply install with with apk instal app. Than you so much!!!!
aledesma said:
Did you go to file manager and replace the Malaysk version? Where is it located? or did you simply install with with apk instal app. Than you so much!!!!
Click to expand...
Click to collapse
Uninstalled with Titanium Backup. Velvet.apk is located in /system/priv-app. Copy/Paste replacement Velvet.apk using Root Explorer. !!! Set file permissions to 644 with Root Explorer !!! Reboot.
shaiq123 said:
I am using the latest Malaysk ROM dated 10th January 2016 for RK3188 1024*600. It lets me speak Ok Google and Call (contact name) to the phone when after pressing the call button. The way it works for me is:
1. Whatever is playing on the unit, it stops when I press the call button on my steering;
2. It launches the unit's dial screen;
3. I say 'OK Google', it launches the ok google listener on the phone;
4. I say 'Call (contact name)' and it calls.
Few things I had to manage before this started working was:
1. Enable the option to receive commands over bluetooth in Google Now settings in the phone;
2. Enable to XPOSED MTC in the XPOSED framework in the head unit;
3. Change the setting to integrate with phone's google now interface (something like that) in XPOSED MTC module.
Hope this helps.
Click to expand...
Click to collapse
Hi,
1. Enable the option to receive commands over bluetooth in Google Now settings in the phone;
Were can i find this option? I have a nexus 5 and i updated my google now, but there no option like that in google now. Or do you mean the option "bluetooth headset" under voice?
3. Change the setting to integrate with phone's google now interface (something like that) in XPOSED MTC module.
I can't find any options in Xposed MTC related to what you are writing. Are you sure this option is in Xposed MTC?
Thank you!!!
carter.w.jason said:
Uninstalled with Titanium Backup. Velvet.apk is located in /system/priv-app. Copy/Paste replacement Velvet.apk using Root Explorer. !!! Set file permissions to 644 with Root Explorer !!! Reboot.
Click to expand...
Click to collapse
I will give it a shot!!!
Hi there,
I to have been wondering about the best way to get voice dialling working and as my google voice crashes the HU more often than not, I think it is best to do this as shaiq123 has suggested by pressing the call button the steering wheel and then Ok Googling the phone to make the call.
But my phone goes to lock screen in the car and that stops this working. What I would like is that when my phone connects to the car bluetooth it
1) stops it going to lockscreen
2) activates wifi hotspot
3) activates 'ok google' if it is not normally activated
and it reverses on disconnecting.
Is this something easily done or do I need some kind of app to do this?
A final thing that would be helpful, is that it would be useful to give the play music command to direct the HU to play music from an HU attached SD card rather than the phone memory. Is there a way to also configure that (i.e. that the command would seek music stored on HU rather than phone first?)
Cheers
Mr Bigglesworth said:
Hi there,
I to have been wondering about the best way to get voice dialling working and as my google voice crashes the HU more often than not, I think it is best to do this as shaiq123 has suggested by pressing the call button the steering wheel and then Ok Googling the phone to make the call.
But my phone goes to lock screen in the car and that stops this working. What I would like is that when my phone connects to the car bluetooth it
1) stops it going to lockscreen
2) activates wifi hotspot
3) activates 'ok google' if it is not normally activated
and it reverses on disconnecting.
Is this something easily done or do I need some kind of app to do this?
A final thing that would be helpful, is that it would be useful to give the play music command to direct the HU to play music from an HU attached SD card rather than the phone memory. Is there a way to also configure that (i.e. that the command would seek music stored on HU rather than phone first?)
Cheers
Click to expand...
Click to collapse
You could achieve the first part using Tasker, you would just create a profile to run your tasks that actives when your phone connects to the headunit. Its a great app for automating stuff like that.
dc5daft said:
You could achieve the first part using Tasker, you would just create a profile to run your tasks that actives when your phone connects to the headunit. Its a great app for automating stuff like that.
Click to expand...
Click to collapse
Thanks - in fact this morning I have downloaded the trial for Tasker as well as Automate to see if they can do what I am looking for.
I've decided what would be really helpful would be if I could
1) Use app to detect when phone connects to car HU via bluetooth
2) Launch Wifi Hotspot
3) set the camera button to unlock screen and activate google voice
Now 1&2 look like its not too difficult and may even be doable using the Sony Smart Connect app (on a Z2, not rooted).
3 doesn't seem to be as instantly obvious. In tasker, I put in a new profile>event>hardware>button camera, also selected non beginner settings so could pit priority to highest and activate stop event, then put the task as launch voice search app - but it just keeps doing the camera?
Mr Bigglesworth said:
Thanks - in fact this morning I have downloaded the trial for Tasker as well as Automate to see if they can do what I am looking for.
I've decided what would be really helpful would be if I could
1) Use app to detect when phone connects to car HU via bluetooth
2) Launch Wifi Hotspot
3) set the camera button to unlock screen and activate google voice
Now 1&2 look like its not too difficult and may even be doable using the Sony Smart Connect app (on a Z2, not rooted).
3 doesn't seem to be as instantly obvious. In tasker, I put in a new profile>event>hardware>button camera, also selected non beginner settings so could pit priority to highest and activate stop event, then put the task as launch voice search app - but it just keeps doing the camera?
Click to expand...
Click to collapse
Create a new Profile>State>Net>BT Connected then click the magnifying glass next to name and select the name of your headunit. This will mean whenever your bluetooth is connected to the headunit it will run the tasks associated with it. It will give you the option to name and create a task once you create your profile then create new>Net>WiFi Tether and set to On.
I have a Z2 as well and just tried the camera button as a profile and it didn't work for me either, you'll need to do some googling on that, not sure why it doesnt work. It's best to set a flash (Alert>Flash) in your task as a test to see if your task runs but I'm sure you need to need to have root to unlock the screen.
dc5daft said:
Create a new Profile>State>Net>BT Connected then click the magnifying glass next to name and select the name of your headunit. This will mean whenever your bluetooth is connected to the headunit it will run the tasks associated with it. It will give you the option to name and create a task once you create your profile then create new>Net>WiFi Tether and set to On.
I have a Z2 as well and just tried the camera button as a profile and it didn't work for me either, you'll need to do some googling on that, not sure why it doesnt work. It's best to set a flash (Alert>Flash) in your task as a test to see if your task runs but I'm sure you need to need to have root to unlock the screen.
Click to expand...
Click to collapse
Thanks for this - and yes this where I had got to (which make me feel better!). And I too think the camera button may not be workable without root.
I think I need to change my plans and see if I can prevent the lockscreen to come on when connected to this bluetooth device. That way I can fall back to using ok google as the lockscreen prevents ok google from completing requests.
Okay - think I've done that and it was easy enough, now have a profile which when connected to HU through bluetooth does (1) set off wifi tether and (2) Set keyguard off. Then with (3) double tap to wake screen and (4) Ok google should be able to do what I need it to.
Last thing I'm wondering if you could do is to create a large voice dial icon (double normal size etc) on screen (in case initial ok google doesn't work)...
So far my attempts to google this answer have come up empty. I can open Google Maps driving mode with AutoShortcut no problem. But making it actually close is turning out to be impossible.
If I try to do a "Kill App", it doesn't kill the notification, leaving it in a bizarre half-open state. Has anyone found an intent or something that can actually kill this off properly?
Have you tried to run a Go Home action before killing the app?
Yes, unfortunately does not help at all. Even gave it ~3 second wait.
Vincent Law said:
So far my attempts to google this answer have come up empty. I can open Google Maps driving mode with AutoShortcut no problem. But making it actually close is turning out to be impossible.
If I try to do a "Kill App", it doesn't kill the notification, leaving it in a bizarre half-open state. Has anyone found an intent or something that can actually kill this off properly?
Click to expand...
Click to collapse
Try code run shell: am force-stop com.google.android.apps.maps & tick "use root". Change the package name if is necessary.
My device is not rooted, is that going to do anything?
Vincent Law said:
My device is not rooted, is that going to do anything?
Click to expand...
Click to collapse
Root is needed to run that command.
But did you try to kill another app with the method you've tried for google maps? Is it working?
So I managed to work out a solution to this, and it involves using the AutoNotifications plugin. I use the plugin to instruct Tasker to press the "end navigation / stop driving" button in the notification tray, which does the correct thing. For those looking to replicate, it's an "internal action", so use the first internal action, not one of the action button options that most guides suggest.
Vincent Law said:
So I managed to work out a solution to this, and it involves using the AutoNotifications plugin. I use the plugin to instruct Tasker to press the "end navigation / stop driving" button in the notification tray, which does the correct thing. For those looking to replicate, it's an "internal action", so use the first internal action, not one of the action button options that most guides suggest.
Click to expand...
Click to collapse
i am trying to "stop driving" using autonotification and cant figure it out. Can you please be more specific than "internal action" which internal action. What variable did you using for the stop driving button. I am trying to use autonotification query and action but i cant figure out which variable in the query to use for the action.
thanks
Vincent Law said:
So I managed to work out a solution to this, and it involves using the AutoNotifications plugin. I use the plugin to instruct Tasker to press the "end navigation / stop driving" button in the notification tray, which does the correct thing. For those looking to replicate, it's an "internal action", so use the first internal action, not one of the action button options that most guides suggest.
Click to expand...
Click to collapse
I'm new to autonotification - I have it set up to query for the "Maps" notification, and it's returning the %anapp variable correctly - I can even click on the notification and bring the focus back to the maps app - but how the heck do you fire this "internal action" to stop driving? I'm sure it must be obvious...
Bulldoguk72 said:
I'm new to autonotification - I have it set up to query for the "Maps" notification, and it's returning the %anapp variable correctly - I can even click on the notification and bring the focus back to the maps app - but how the heck do you fire this "internal action" to stop driving? I'm sure it must be obvious...
Click to expand...
Click to collapse
I just spent a few days trying to figure this out. Here is how I was able to get it working:
Create a new task / add these to a current task:
A1 - Add Action - Plugin, AutoNotification, Query. Tap Edit, Select "Maps" from Apps and under Advanced tap Internal Actions Big, tap the Tag icon. It should populate with %aninternalactions.
A2 - (Only needed for debugging) Add Action, Alert, Flash, tap the Tag and choose %aninternalactions, then edit to choose the first value in the array - %aninternalactions(1)
A3 - Add Action, Plugin, AutoNotification, Actions. Tap Intercept Action, tap the tag and choose %aninternalactions, then edit it again to - %aninternalactions(1)
To test, start driving mode and run the task manually. You should see the button GUID flash (if you enabled A2) and Driving Mode should end :good:
It works now
I figured out a solution.
Tasker gives you the advise to use ADB Wifi.
Here's what I did:
- enable and go to developer settings
- check ADB debugging
- check ADB while charging (only needed, if it stops working for you when you disconnect your USB cable. Try without first!)
- then run from your PC `adb tcpip 5555` to enable adb over wifi
- use Tasker Action "kill app", uncheck "Use Root".
Maps (or Driving Mode) can finally be killed this way.
Tried on Huawei Mate 20 Pro (LYA-L29) running Android 10 (10.0.0.214)
How are you able to open Google maps?
Mine opens for a millisecond then closes.
MSK1 said:
How are you able to open Google maps?
Mine opens for a millisecond then closes.
Click to expand...
Click to collapse
Hi, MSK1,
I searched for a long time for this solution, so maybe this one will help you out.
You can launch Google Maps directly into Navigation mode via using an intent.
You may find this one interesting. https://forum.xda-developers.com/showpost.php?p=46600949&postcount=3
Mine looks like this.
google.navigation:q=Zip+City,+Street+Number
Happy Driving!
Best Regards.
3di said:
Hi, MSK1,
I searched for a long time for this solution, so maybe this one will help you out.
You can launch Google Maps directly into Navigation mode via using an intent.
You may find this one interesting. https://forum.xda-developers.com/showpost.php?p=46600949&postcount=3
Mine looks like this.
google.navigation:q=Zip+City,+Street+Number
Happy Driving!
Best Regards.
Click to expand...
Click to collapse
Thanks.
I found an easier way.
I downloaded the "navigation shortcut" app from the play store.
When I launch this as an app from tasker then the navigation stays on.
Sent from my EVR-N29 using Tapatalk
Hi everyone!
After my first plugin I had an idea of creating another one, but this time not an "action" but an "event".
The free but ad-supported version of the plugin can be found here and if you want to support the development and don't have ads you can find the paid one here.
Of course the description can be found there, but as a quick recap, this plugin can listen for hotwords and signal Tasker when a hotword is recognized!
It uses Snowboy Hotword to listen to the mic and process what it hears super fast and completely locally.
Hotword models can be found and trained at the Snowboy Website and the downloaded model can be imported in my plugin.
Next from Tasker you can create an event of the Hotword Plugin and tap on the hotword you want to react to, next you can do with it what you want!
You can listen to multiple hotwords at the same time and run a different event for each one. So for example if you shout "lights on" the lights might turn on and if you shout "play music" the music starts playing.
You can see it as AutoVoice Continuous but a lot faster and more consistent, plus you can train any hotword you like and pronounce it in any language you prefer (to be defined at the website).
Of course you can modify the sensitivity if you feel like it can't hear you or if it goes off all the time and you can start or stop the service via a Tasker action if you like.
Personally I use the app in combination with my ADB shell plugin to launch assistant on my NVIDIA Shield AndroidTV handsfree by shouting "hey google" to an old android phone lying besides the tv.
Since a lot of time went into developing this plugin and making it work (a way lot more than my last plugin) I put it in the Play Store for the price of a small coffee but since I know people like free apps, I decided to also create an add supported version.
Again, you can find the free version here and the ad-free version here (Of course I will update both at about the same time when I fix something).
So if you like the idea and want to try it out please have a look!
And if you have any questions, troubles, ideas, bugs (yes I'm sure they're there even after thoroughly testing), please leave them below!
Edit: If you don't have access to the Google Play store, I just uploaded both versions to XDA Labs:
Paid version
Free version
If you don't have access to the Google Play store, I just uploaded both versions to XDA Labs:
Paid version
Free version
I don't think it is your fault, but it seems that this hot word detection system is way too sensitive for me, it detected words when there were only noises.
sadly, but the idea was promising though
alienyd said:
I don't think it is your fault, but it seems that this hot word detection system is way too sensitive for me, it detected words when there were only noises.
sadly, but the idea was promising though
Click to expand...
Click to collapse
That happens when the sensitivity is too high, have you adjusted the sensitivity setting in the app?
For me the same happens when I set the sensitivity to 10 and when I set it to 0, nothing will ever trigger. For the phone and words I'm using, the sweet spot is around 4 or 5
yeah, thanks for the reply. I did play around with the sensitivity on default and then some lower level, however it still seemed to trigger to often. Maybe a little bit more playing around would help, or, may be it's just the nature of my language...
Great app, does the work pretty good but why does it have to disable google assistant. When this app is listening, assistant stops listening. Why can't they both work together. Or can we configure this app to trigger assistant and not the Google app itself.
@Humpie does it work when the screen is off ?
Comparison to Autovoice
Hi,
Just wondering about the difference between this and Autovoice, or if there is an integration that would make sense.
Thanks.
I was hopeful, but even at the lowest sensitivity setting available, it still triggers when the tv is on downstairs and completely quite upstairs.:crying::crying:
ngreen1980 said:
I was hopeful, but even at the lowest sensitivity setting available, it still triggers when the tv is on downstairs and completely quite upstairs.:crying::crying:
Click to expand...
Click to collapse
kind of my problem too...
alienyd said:
yeah, thanks for the reply. I did play around with the sensitivity on default and then some lower level, however it still seemed to trigger to often. Maybe a little bit more playing around would help, or, may be it's just the nature of my language...
Click to expand...
Click to collapse
ngreen1980 said:
I was hopeful, but even at the lowest sensitivity setting available, it still triggers when the tv is on downstairs and completely quite upstairs.:crying::crying:
Click to expand...
Click to collapse
alienyd said:
kind of my problem too...
Click to expand...
Click to collapse
Hmm, what you could try is to download a hotword from snowboy.kitt.ai that is a bit more trained. In my experience they are a lot more consistent and trigger more accurately.
I do find it strange that even the lowest sensitivity setting still triggers it Did you stop and start the service just to be sure after changing it?
I am thinking about enabling more steps of sensitivity btw, but I'm not sure if I can make it even lower. I'll try though
scissorscrush said:
Great app, does the work pretty good but why does it have to disable google assistant. When this app is listening, assistant stops listening. Why can't they both work together. Or can we configure this app to trigger assistant and not the Google app itself.
Click to expand...
Click to collapse
Unfortunately this is how the audio record function works in Android. Only one app at a time can access the microphone. Google has made an exception for the built-in "Okay Google" (and I'm not sure how they do it), but fortunately a workaround is possible. You can enable and disable the listening service of my plugin from within Tasker.
So what you can do is create a new profile for when the event "Hey google" (for instance) in hotword Plugin triggers and create a task wherein you put "stop hotword plugin", "Voice command" (which triggers assistant) and after a while "start hotword plugin" again. (Or you can just enable it yourself from the notification)
It's also possible to stop and start hotword plugin automatically when assistant is in the foreground (I think), but I haven't managed to get it to work myself as Assistant is an overlay app and the detection of which app is running can be a bit slow in Tasker...
madkiran said:
@Humpie does it work when the screen is off ?
Click to expand...
Click to collapse
Certainly, yes!
PhilipTD said:
Hi,
Just wondering about the difference between this and Autovoice, or if there is an integration that would make sense.
Thanks.
Click to expand...
Click to collapse
My plugin is comparable to the continuous listening mode of AutoVoice, however there is a difference. AutoVoice can continuously listen to what everyone says, convert it to text and then pass that on to Tasker where you can make something happen when a certain word is heard. I did try this before creating this app, but it can be very slow, especially when more words are heard after the hotword you want. AutoVoice will listen until it hears that you stopped talking and then send all it heard to Tasker. It will also often just not get the word correct, so it's not handy to be used as hotword detection.
In comparison, my plugin uses a different engine (not the google speech recognition engine, but Snowboy) which is specifically designed to recognize trained hotwords. So the downside is that you have to train a certain hotword before you can use it, but this does result in a way more accurate detection. It's also way faster as it doesn't have to wait til everyone is silent again and stopped talking, it just instantly triggers after you say the word and signals Tasker.
You can integrate this with AutoVoice if you like, well, more like, let it work together to create something awesome. You can create a task for when a certain hotword is triggered where you stop my plugin from listening, start an AutoVoice prompt where you can say your command (like "set the tv to 10") and then afterwards start my plugin again.
Want to give this a try.
Continuous listening usually leads to too much battery drain.
Is the problem handled in the plugin? Tasker monitors sensors and hardware by intervals which is why it in itself does not eat the battery. Using Tasker's scheme would have (optionally) long waits to test audio when the screen is off.
Where is this "voice command" option.
Could you give us an example of your Tasker settings that allow you to use this instead of gAssistant?
I paid, cause I love this idea. Can't wait to try it, but I wholeheartedly support anything better than "OK Google"!
Dovidhalevi said:
Want to give this a try.
Continuous listening usually leads to too much battery drain.
Is the problem handled in the plugin? Tasker monitors sensors and hardware by intervals which is why it in itself does not eat the battery. Using Tasker's scheme would have (optionally) long waits to test audio when the screen is off.
Click to expand...
Click to collapse
It will lead to battery drain, but this is necessary. It would be extremely unreliable if it stopped listening for a while, as in, it would stop working and no longer react to your hotword which defies the entire purpose of the app.
phishfi said:
Where is this "voice command" option.
Could you give us an example of your Tasker settings that allow you to use this instead of gAssistant?
I paid, cause I love this idea. Can't wait to try it, but I wholeheartedly support anything better than "OK Google"!
Click to expand...
Click to collapse
"Voice command" can be found under the Tasker actions under the Input tab. Thank you very much
I attached an example of how you can launch assistant whilst pausing my plugin from listening for a while so assistant can actually hear you.
You can execute this task for the hotword event you like so "hey google" or "computer" whatever you like and have set up in the hotword plugin
Humpie said:
It will lead to battery drain, but this is necessary. It would be extremely unreliable if it stopped listening for a while, as in, it would stop working and no longer react to your hotword which defies the entire purpose of the app.
Click to expand...
Click to collapse
So the question becomes, with any of these things, how I want to use them. Use a Tasker script to toggle the service. For example, if phone is face down, turn it off. Or if I pick up the phone, turn it on. Scripts have "exit" options to reverse the toggle.
I would want to do this with OK Google as well but this plugin offers the option, Google does not.
Dovidhalevi said:
So the question becomes, with any of these things, how I want to use them. Use a Tasker script to toggle the service. For example, if phone is face down, turn it off. Or if I pick up the phone, turn it on. Scripts have "exit" options to reverse the toggle.
I would want to do this with OK Google as well but this plugin offers the option, Google does not.
Click to expand...
Click to collapse
This is indeed possible to achieve with my plugin, however if your phone supports always listening OK Google with screen off already, it usually has a dedicated chip for this that uses very little power. I know my 6P does and leaving OK Google to always listening results in no significant more battery drain
Beta 1.0 released
I will like to start saying a very big thank you to @bggold who asked me to consider this in the first place
While there isn't any way to use the nice Google Assistant voice, and it's still rough around the edges, this demonstrates how we can use Android Auto in a multi-lingual environment as well as how to read out and reply emails.
The concept is very simple, instead of relaying on Android Auto to read out the notifications I have created a small app which mimics that behaviour, with some extras:
1) It try to do a language detection for each test, and use the appropriate TextToSpeech
2) It allows the user to select which app notification does he/she want's to read
3) If the content is really long (like a lengthy email) the app will prompt the user if it want's to go ahead with the message readout or not
4) If notification supports quick-reply the app will prompt the user for a reply (in the same language as the the original message)
Planning to support a lot of languages but there I will need user input, I have translated the basic strings to around 70 languages using Google translator, but I can tell it's not quite right (I can see with the languages I do speak)
Best part, app won't be affected by 3rd party restriction at all and it won't require root either, however I'm pretty sure Google will not allow it on the PlayStore
Beta version available now on XDA Labs.
App will be payable, however current beta is free so grab a copy while you can
To use the app you will need to enable unknown sources in Android Auto, simply open Android Auto, go to About, tap the "About Android Auto" header 10 times till you become a developer, then from the 3 dotted right menu select developer options and enable "Unknown sources"
Emil Borconi said:
Beta 1.0 released
I will like to start saying a very big thank you to @bggold who asked me to consider this in the first place
While there isn't any way to use the nice Google Assistant voice, and it's still rough around the edges, this demonstrates how we can use Android Auto in a multi-lingual environment as well as how to read out and reply emails.
The concept is very simple, instead of relaying on Android Auto to read out the notifications I have created a small app which mimics that behaviour, with some extras:
1) It try to do a language detection for each test, and use the appropriate TextToSpeech
2) It allows the user to select which app notification does he/she want's to read
3) If the content is really long (like a lengthy email) the app will prompt the user if it want's to go ahead with the message readout or not
4) If notification supports quick-reply the app will prompt the user for a reply (in the same language as the the original message)
Planning to support a lot of languages but there I will need user input, I have translated the basic strings to around 70 languages using Google translator, but I can tell it's not quite right (I can see with the languages I do speak)
Best part, app won't be affected by 3rd party restriction at all and it won't require root either, however I'm pretty sure Google will not allow it on the PlayStore
Beta version available now on XDA Labs.
App will be payable, however current beta is free so grab a copy while you can
To use the app you will need to enable unknown sources in Android Auto, simply open Android Auto, go to About, tap the "About Android Auto" header 10 times till you become a developer, then from the 3 dotted right menu select developer options and enable "Unknown sources"
Click to expand...
Click to collapse
Thanks for making this app!
After first start it asked for notification permission and then it was gone to build the list of installed apps/services - endless...
So I've forced close the app after minutes, went to app info/permissions, and enabled unselected permissions for it.
After that the app works now, as it should!
I'll test the functionality today while using AA in my car.
Regards bitstra
bitstra said:
Thanks for making this app!
After first start it asked for notification permission and then it was gone to build the list of installed apps/services - endless...
So I've forced close the app after minutes, went to app info/permissions, and enabled unselected permissions for it.
After that the app works now, as it should!
I'll test the functionality today while using AA in my car.
Regards bitstra
Click to expand...
Click to collapse
Thanks. It was 3 am )) updating the app now.
This is exactly what I needed. Unfortunately I couldn't get it to work. Using Samsung S9 plus running Oreo. Gave read permission to the app, enabled developer settings on Android Auto, enabled unknown sources, enabled whatsapp and Gmail.
Whatsapp notifications haven't changed and it continues to read the foreign text in English. Gmail notifications don't pop up at all.
Any suggestions?
yavuzyay said:
This is exactly what I needed. Unfortunately I couldn't get it to work. Using Samsung S9 plus running Oreo. Gave read permission to the app, enabled developer settings on Android Auto, enabled unknown sources, enabled whatsapp and Gmail.
Whatsapp notifications haven't changed and it continues to read the foreign text in English. Gmail notifications don't pop up at all.
Any suggestions?
Click to expand...
Click to collapse
Not sure if you saw but there is a new release. It fixes this issue. Just remember to reboot after updating.
Unfortunately I have the same problem as @yavuzyay. I'm using a Samsung Galaxy S6 edge with Android 7.0 and Carnotifier Beta v3.
Thanks to @yavuzyay for bugreport and Turkish language input.
I have identified the problem where the app was crashing in case you where using AA on the phone only, and this has been now fixed.
@CeldeSuS - Are you phone only or are you using AA on the car? If phone only, download the new beta 1.4
Emil Borconi said:
@CeldeSuS - Are you phone only or are you using AA on the car? If phone only, download the new beta 1.4
Click to expand...
Click to collapse
I'm using AA on the car (Alpine X802D-U head unit). I'll try the new beta anyway and report back.
Awesome. Works perfectly.
V4 work fine with SM960F(android 8.0) & RLink1 !
Great job!
Very good stuff!
I use it with the now playing feature - basically phone picks up music on the radio,.detects the song and artist and throws a notification. This app picks that up and shows it as a notification on the car screen! I have disabled read out. So it stays as a simple notification.
Quick question - haven't been able to try it - if I set zero seconds as the duration, will it leave the notification forever?
Tested but not working as expected. Line is an application which doesn't support Android Auto.
Positive: Yes, Car Notifier shows there is a message on Line.
Negative: Can't do anything, it won't read the message, the notification stays in grey color and nothing happens when I click on the message.
Cheers
Tom
tom1807 said:
Tested but not working as expected. Line is an application which doesn't support Android Auto.
Positive: Yes, Car Notifier shows there is a message on Line.
Negative: Can't do anything, it won't read the message, the notification stays in grey color and nothing happens when I click on the message.
Cheers
Tom
Click to expand...
Click to collapse
You can't click the notification to have it read at this time. If you want them read to you enable the read option.
"Read out notifications" is enabled in the settings, my Honda headunit is hacked and I have root access, so I don't think this is related to that.
Cheers
Tom
tom1807 said:
"Read out notifications" is enabled in the settings, my Honda headunit is hacked and I have root access, so I don't think this is related to that.
Cheers
Tom
Click to expand...
Click to collapse
I'm sure you have but have you checked all the permissions?
CarNotifier asks only permissions to Microphone and Phone, both are granted.
Wondering now whether it has something to do with the new Android Auto v3.8.584554 where some on Reddit claim, that notification is broken
Cheers
Tom
Edit: Maybe the the new AA version interferes with CarNotifier, because AA can show now also message preview
More edit: My friend tested on the Samsung S7 (I have a OnePlus 3T). Also on his mobile nothing happens with Line.
Can't read out and nothing happens in AA when click on it
Is there an app for Speed cams like in your obd2aa app, to have only the speed cam notification?
tom1807 said:
CarNotifier asks only permissions to Microphone and Phone, both are granted.
Wondering now whether it has something to do with the new Android Auto v3.8.584554 where some on Reddit claim, that notification is broken
Cheers
Tom
Edit: Maybe the the new AA version interferes with CarNotifier, because AA can show now also message preview
More edit: My friend tested on the Samsung S7 (I have a OnePlus 3T). Also on his mobile nothing happens with Line.
Can't read out and nothing happens in AA when click on it
Click to expand...
Click to collapse
I am running the new aa and it is working. Get Emil a bug report right after it happens.
The only thing you can do at this time is swip away the notifications. Clicking them will not do anything.
Thanks
After more testing, I do believe the culprit is Line. Gmail works as expected, Facebook also (just for test).
However, Line refuses, which is actually the reason to install the program in the first place.
Probably one of the few programs which won't work.
Great program though.
Cheers
Tom
Hi guys.
I'm finally back in the UK and in front of my PC, I've also managed to tied up quiet a few of my loose ends and I have no big project starting this year. I will dedicated the last 2 weeks of this years to the following:
1) Looking into fixing some of the FC for obd2aa, also try to find a solution for non-standard PIDs
2) Get AA GateWay to Beta/Stable version (most work needs to be done on this app)
3) Fix some issues and FC with HUR (including Waze sound cut off).
4) Get the carNotifier to a stable version.
January and February are again fully booked so I will focus on stability rather then adding new features especially because obd2aa and HUR and fairly mature apps with most of the functions already covered.
For some reason I'm not really getting any notifications from XDA and being a lot on the road I don't visit the site too often lately, therefore I will kindly ask you if you need support, please email me directly to [email protected].