Related
Not sure who this will or will not be of use to but I wrote a little script to import directions from Google Maps on my N4 to my truck.
This is an automation macro that runs on your computer to process the location info sent from your phone and imports it into OnStar.
Here's how to set it up:
1. Install and log in to Dropbox on your computer and your phone.
2. Install Firefox and the iMacros Firefox add-on on your computer.
3. Login to OnStar.com with Firefox on your computer and check the "Remember Me" box.
4. Run the attached program which will install a background monitor app and handle your imports.
When you're ready to send a location to your vehicle go to your phone and do this:
1. Click Share.
2. Share to Dropbox.
3. Make sure you're in the top folder in your Dropbox and click Upload.
4. Leave the file name as the default "myfile.txt" and click OK.
5. Wait about 1 minute for processing to complete.
6. In your vehicle press the OnStar hands-free calling button and say "Virtual Advisor"
7. OnSar will inform you that you have one saved destination named "Android Destination" and ask if you'd like directions there. Say yes.
Done. Your vehicle is now routing you to your destination.
Here's a video of the computer side scripts running if you want to see it run.
Let me know what you think and if anyone actually find this useful.
Disclaimer: I am no developer, just someone who got sick of having to clear my phone data every hour or two to get rid of that stupid notification. I spent four hours last night deeply researching and looking at code to figure this out for myself and you guys as I know this is a major pain. I am proud to report back to you that after a day of resetting, and fully powering down my phone many times the notification has not came back. This took a TON of trial and error. I'm glad I can finally give something back to this community after all its provided me. I also do not claim to be the founder of this fix, although I feel I have certain variations of the fix that are my own. Whether or not my particular fixes are placebo or not I cannot say as I do not understand programming that well, but in my own testing they seemed to make the difference.
Side effects: None that I have noticed yet. Phone calls, texts, picture messages come through fine. I haven't had any problems. I am guessing if you change any of the setting in the phone app itself the settings may or may not be lost. That remains to be seen. You may need to re-apply the fix each time and likely with every new ROM flash. Let us know.
Let's get to it!
NOTE: I AM USING GOOGLE VOICE AND HAVE IT SET AS MY VOICEMAIL. DO NOT KNOW IF THIS MATTERS OR NOT.
Step 1: You will need to be rooted. Reboot to make sure you have the new voicemail notification.
Step 2: I will be using FX Explorer for this process. You will need to download the FX root add-on from the play store as well. If you have another root explorer and can figure out what I am saying that's fine.
Step 3: Open FX Explorer. Under the "Files" section tap "System (Root)" you'll likely get a warning dialog of some sort or su will ask for permissions. Grant them and accept the disclaimer warning if applicable.
Step 4: Next tap on the "data" folder. Within it, there will be another data folder. Tap the proceeding "data" folder.
Step 5: locate and tap the "com.android.phone" folder. Within it, tap on the "shared_prefs" folder. You should see a file called "com.android.phone_preferences.xml" you will want to long press on that file. You will tap "open with" after that you tap "Text Editor"
Step 6: fully replace the text within this file with the following:
<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<map>
<string name="vm_number_key_cdma">##########</string>
<int name="vm_count_key_cdma" value="0" />
<boolean name="button_voicemail_notification_vibrate_key" value="false" />
</map>
Click to expand...
Click to collapse
IMPORTANT: THE ########## WILL BE YOUR 10 DIGIT PHONE NUMBER. REPLACE THOSE WITH YOUR PHONE NUMBER.
Step 7: Tap "File" up on the upper left corner and then tap "Save" after this, press your back button so you are back in the folder where you can see this file.
I do not know if the rest of this tutorial is required to be followed starting at Step 8 but its what I did. You can do it if you want to follow exactly what I did to receive my results.
Step 8: Long press on "com.android.phone_preferences.xml" and tap "Copy" tap your back button so that you are just outside of the "shared_prefs" folder and then tap the clipboard in the upper right corner. It will bring up a prompt to which you will press "Paste." long press the pasted "com.android.phone_preferences.xml" file and tap rename. Rename the file to "com.android.phone_preferences.xml.bak"
Step 9: Long press on your newly named "com.android.phone_preferences.xml.bak" and tap "copy." Go back into the "shared_prefs" folder and tap the clipboard up in the top right corner. Tap "paste" again. You should see your "com.android.phone_preferences.xml" and "com.android.phone_preferences.xml.bak" files together.
Step 10: Long press the "com.android.phone_preferences.xml" and tap "Permissions." Ensure that the permissions say "0660" or that you tap "read" and "write" only under the "Owner: radio" and "Group: radio" fields. Make sure there is nothing in the "Exec" field has permissions.
Step 11: go into your notifications on the top of your screen and long press on the voicemail notification. Tap "App Info." Force stop your phone application so that the notification disappears up top. Reboot or shut down your phone a few times. You should no longer see the notification anymore.
Step 12: Enjoy not seeing this annoying little **** of a notification again!
Ugh can a moderator please move this to Nexus 5 General please?
i very much appreciate you finding this fix and posting it.
i had this exact problem with a Nexus 5 of mine this weekend. what i did to fix it was get on sprint's online chat and had them fully disable sprint voicemail. i use GV so i don't care if sprint provide's VM or not. after they disable VM, i went in and did a force stop / clear data on the phone/voice messaging app. this clears the notification. rebooted phone and as of 24 hours now, the notification has not returned.
PaulB007 said:
Disclaimer: I am no developer, just someone who got sick of having to clear my phone data every hour or two to get rid of that stupid notification. I spent four hours last night deeply researching and looking at code to figure this out for myself and you guys as I know this is a major pain. I am proud to report back to you that after a day of resetting, and fully powering down my phone many times the notification has not came back. This took a TON of trial and error. I'm glad I can finally give something back to this community after all its provided me. I also do not claim to be the founder of this fix, although I feel I have certain variations of the fix that are my own. Whether or not my particular fixes are placebo or not I cannot say as I do not understand programming that well, but in my own testing they seemed to make the difference.
Side effects: None that I have noticed yet. Phone calls, texts, picture messages come through fine. I haven't had any problems. I am guessing if you change any of the setting in the phone app itself the settings may or may not be lost. That remains to be seen. You may need to re-apply the fix each time and likely with every new ROM flash. Let us know.
Let's get to it!
NOTE: I AM USING GOOGLE VOICE AND HAVE IT SET AS MY VOICEMAIL. DO NOT KNOW IF THIS MATTERS OR NOT.
Step 1: You will need to be rooted. Reboot to make sure you have the new voicemail notification.
Step 2: I will be using FX Explorer for this process. You will need to download the FX root add-on from the play store as well. If you have another root explorer and can figure out what I am saying that's fine.
Step 3: Open FX Explorer. Under the "Files" section tap "System (Root)" you'll likely get a warning dialog of some sort or su will ask for permissions. Grant them and accept the disclaimer warning if applicable.
Step 4: Next tap on the "data" folder. Within it, there will be another data folder. Tap the proceeding "data" folder.
Step 5: locate and tap the "com.android.phone" folder. Within it, tap on the "shared_prefs" folder. You should see a file called "com.android.phone_preferences.xml" you will want to long press on that file. You will tap "open with" after that you tap "Text Editor"
Step 6: fully replace the text within this file with the following:
IMPORTANT: THE ########## WILL BE YOUR 10 DIGIT PHONE NUMBER. REPLACE THOSE WITH YOUR PHONE NUMBER.
Step 7: Tap "File" up on the upper left corner and then tap "Save" after this, press your back button so you are back in the folder where you can see this file.
I do not know if the rest of this tutorial is required to be followed starting at Step 8 but its what I did. You can do it if you want to follow exactly what I did to receive my results.
Step 8: Long press on "com.android.phone_preferences.xml" and tap "Copy" tap your back button so that you are just outside of the "shared_prefs" folder and then tap the clipboard in the upper right corner. It will bring up a prompt to which you will press "Paste." long press the pasted "com.android.phone_preferences.xml" file and tap rename. Rename the file to "com.android.phone_preferences.xml.bak"
Step 9: Long press on your newly named "com.android.phone_preferences.xml.bak" and tap "copy." Go back into the "shared_prefs" folder and tap the clipboard up in the top right corner. Tap "paste" again. You should see your "com.android.phone_preferences.xml" and "com.android.phone_preferences.xml.bak" files together.
Step 10: Long press the "com.android.phone_preferences.xml" and tap "Permissions." Ensure that the permissions say "0660" or that you tap "read" and "write" only under the "Owner: radio" and "Group: radio" fields. Make sure there is nothing in the "Exec" field has permissions.
Step 11: go into your notifications on the top of your screen and long press on the voicemail notification. Tap "App Info." Force stop your phone application so that the notification disappears up top. Reboot or shut down your phone a few times. You should no longer see the notification anymore.
Step 12: Enjoy not seeing this annoying little **** of a notification again!
Click to expand...
Click to collapse
Thanks for this, PaulB007!
I have a Samsung Galaxy S III on Sprint, so mine turned out a little differently... but I used the info you posted here and wrote up the process for that device here.
Thanks again!
This method may or may not work depending on your ROM, I have had mixed results after further testing..
PaulB007 said:
This method may or may not work depending on your ROM, I have had mixed results after further testing..
Click to expand...
Click to collapse
Update: it seems that the "<string name="vm_number_key_cdma">##########</string>" is important to always have in the file mentioned in the OP. Without it the fix likely just won't work.
Just thought I'd throw this out there. I cleared the reoccurring icon by disabling "voicemail display" in Google voice app settings. The app is really outdated (long time GV user here) and IMO, I think it's a compatibility issue with the app. Once you uncheck "voicemail display" option, you won't see voicemails in your call log, but you can still see, read, and get a GV notification of your voicemail through the GV app.
Sent from my Nexus 5 using Tapatalk
Using a build derived from 5.0.1 lrx22c on Sprint.
This fix works until something on my phone (no notification, 0 stays) decided to add a new line
<int name="vm_count_key_cdma0" value="1" />
....so I disabled write permissions for radio and group: radio. Now the voicemail notification is gone for good and actual voice mail notification still seems to work.
jerryparid said:
Using a build derived from 5.0.1 lrx22c on Sprint.
This fix works until something on my phone (no notification, 0 stays) decided to add a new line
<int name="vm_count_key_cdma0" value="1" />
....so I disabled write permissions for radio and group: radio. Now the voicemail notification is gone for good and actual voice mail notification still seems to work.
Click to expand...
Click to collapse
What do you mean by radio? Like teleservice or?
tjeeeeee said:
What do you mean by radio? Like teleservice or?
Click to expand...
Click to collapse
In FX. Click hold on file -> Permissions -> Turn off write for Group: Ratio....
But the permission didn't stick. After a reboot, the write permission was back. But....
<int name="vm_count_key_cdma0" value="0" />
<int name="vm_count_key_cdma" value="0" />
...stayed at 0. My phone hasn't spawned a third line with value = "1".
New theory is that as long as there is no 1 in the file, there should be no issues with phantom voicemail.
Anyone have any update on this? This is ruining my N5 experience on Sprint.
I'd say it varies I run the m8 gpe and it hasn't come back using this method but I also did an edit to the phone apk as well so I'm not sure what worked and what didn't
For future reference, this CM 12 based ROM has fixed my issues.
http://forum.xda-developers.com/goo...m-resurrection-remix-4-4-2-kitkat-v5-t2706610
I'm running version 4.4, not rooted, Moto x. Utilizing Tasker, what is the easiest way to have the touchless control prompt "ok google now" directly initiate/bring up the Utter voice command app to it's listening state? I can accomplish this no problem with the screen on and unlocked, but I want the ability to also launch it with the screen off/inactive. I am most familiar with utter but will be fine using any voice command app if necessary. I just want to be able to utilize UItter voice command capabilities without it always being in a permanent listening state, which really drains my phone's battery life. Thanks for any suggestions!
I am also interested in this. The following thread should give you some leads:
http://forum.xda-developers.com/moto-x/general/moto-x-offline-recognition-solved-t2571466
Utter
masterfisher166 said:
I'm running version 4.4, not rooted, Moto x. Utilizing Tasker, what is the easiest way to have the touchless control prompt "ok google now" directly initiate/bring up the Utter voice command app to it's listening state? I can accomplish this no problem with the screen on and unlocked, but I want the ability to also launch it with the screen off/inactive. I am most familiar with utter but will be fine using any voice command app if necessary. I just want to be able to utilize UItter voice command capabilities without it always being in a permanent listening state, which really drains my phone's battery life. Thanks for any suggestions!
Click to expand...
Click to collapse
I use the Ok Google now trigger intent xposed module and in tasker use it to launch the utter! Shortcut available from the playstore so that way I have always listening capability without the battery drain that permanent recognition from utter brings and it works perfectly everytime, the alternative is to use touchless controls together with auto voice recognise within tasker and get the Google now api xposed module so that you're still using Google now but tasker tasks can be implemented by voice in Google now, hope that helps although you need to be rooted which I have only just reread your comment to see that you are not
Without root, your options are a bit limited. Utter! Has a direct shortcut to launch its voice recognizer? If so, you can say "OK, Google now, open (utter! shortcut name) app" Kinda awkward, but it should work.
Sent from my XT1060 using XDA Premium 4 mobile app
<br />
I use the Ok Google now trigger intent xposed module and in tasker use it to launch the utter! Shortcut available from the playstore so that way I have always listening capability without the battery drain that permanent recognition from utter brings and it works perfectly everytime, the alternative is to use touchless controls together with auto voice recognise within tasker and get the Google now api xposed module so that you're still using Google now but tasker tasks can be implemented by voice in Google now, hope that helps although you need to be rooted which I have only just reread your comment to see that you are not<br/>
Can you elaborate on this? I'm not a big Tasker user.
Sent from my XT1053 using Tapatalk
Touchless utter
overthatscreen said:
<br />
I use the Ok Google now trigger intent xposed module and in tasker use it to launch the utter! Shortcut available from the playstore so that way I have always listening capability without the battery drain that permanent recognition from utter brings and it works perfectly everytime, the alternative is to use touchless controls together with auto voice recognise within tasker and get the Google now api xposed module so that you're still using Google now but tasker tasks can be implemented by voice in Google now, hope that helps although you need to be rooted which I have only just reread your comment to see that you are not<br/>
Can you elaborate on this? I'm not a big Tasker user.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
Download and install utter quick launch from the playstore and the okgooglenowtriggerintent module from xposed, once you have activated it and rebooted in xposed framework open tasker and create a new profile, hit event then in the popup start to type intent and send intent will appear, hit that and in the action section type the following:
com.hawkjm.okgooglenowtriggerintent.AUDIO_TRIGGER
Press back and new task popup will appear, choose application and select utter quick launch, make sure tasker is running and the new profile is active in tasker and keep pressing back until tasker exits, now everytime you say ok Google now utter will listen instead of Google now, you might want to customise the response from your command in utter, I changed mine simply to yes each time I activate utter and bear in mind that it has nothing to do with the wake up command settings in utter, I hope that all makes sense
If it's the tasker tasks in Google now that you are interested in then download autovoice from the playstore and the Google search api from the xposed framework application downloads section and activate it and reboot,
Open autovoice and scroll to the bottom and make sure that Google search api is enabled then open the Google search api app that you downloaded (should now be an icon) swipe across to the right and make sure autovoice is there, if not then reboot, if so open tasker, create a profile, select state, plugin, autovoice recognised then next to configuration hit the edit button, scroll to command filter and type the Phrase that you want to be recognised for example Toggle bluetooth, back out of it and hit the tick, then select the task that you want to perform (the possibilities are endless) and back out of tasker until it closes then try out your command, create new profiles for each autovoice command that you want to execute,
Google search will try and search for whatever you say even though it will execute your task, if you're fine with that then leave it as it is, if you want Google search to close after executing certain commands then under each task that you create press plus, select if and make the top line look like this:
%avsource ~ googlenow
Then hit back, hot plus and type kill application and select that option, search for google search and tick use root,
Hit back again and hit plus and type end if and select it and then hit back until tasker exits. Now whenever you say that particular command Google now will execute it and then return to where you were previously, if you don't want to do that for each task simply create a profile for recognising the Phrase homepage and have it run the task homepage
mpd81 said:
Download and install utter quick launch from the playstore and the okgooglenowtriggerintent module from xposed, once you have activated it and rebooted in xposed framework open tasker and create a new profile, hit event then in the popup start to type intent and send intent will appear, hit that and in the action section type the following:
com.hawkjm.okgooglenowtriggerintent.AUDIO_TRIGGER
Press back and new task popup will appear, choose application and select utter quick launch, make sure tasker is running and the new profile is active in tasker and keep pressing back until tasker exits, now everytime you say ok Google now utter will listen instead of Google now, you might want to customise the response from your command in utter, I changed mine simply to yes each time I activate utter and bear in mind that it has nothing to do with the wake up command settings in utter, I hope that all makes sense
If it's the tasker tasks in Google now that you are interested in then download autovoice from the playstore and the Google search api from the xposed framework application downloads section and activate it and reboot,
Open autovoice and scroll to the bottom and make sure that Google search api is enabled then open the Google search api app that you downloaded (should now be an icon) swipe across to the right and make sure autovoice is there, if not then reboot, if so open tasker, create a profile, select state, plugin, autovoice recognised then next to configuration hit the edit button, scroll to command filter and type the Phrase that you want to be recognised for example Toggle bluetooth, back out of it and hit the tick, then select the task that you want to perform (the possibilities are endless) and back out of tasker until it closes then try out your command, create new profiles for each autovoice command that you want to execute,
Google search will try and search for whatever you say even though it will execute your task, if you're fine with that then leave it as it is, if you want Google search to close after executing certain commands then under each task that you create press plus, select if and make the top line look like this:
%avsource ~ googlenow
Then hit back, hot plus and type kill application and select that option, search for google search and tick use root,
Hit back again and hit plus and type end if and select it and then hit back until tasker exits. Now whenever you say that particular command Google now will execute it and then return to where you were previously, if you don't want to do that for each task simply create a profile for recognising the Phrase homepage and have it run the task homepage
Click to expand...
Click to collapse
Great topic! Learning more about integrating Google Now and AutoVoice, but i have some doubts yet
I have a MotoX and do not want to leave the continuous mode autovoice on because MotoX has dedicated processor for voice recognition, intend
use "OK Google Now" to enable the continuous mode autovoice.
Could be accomplished?
"OK NOW GOOGLE", "MOTO X" "TURN ON TV"
^MotoX feature
^Enable AutoVoice
^Action
dont like Utter!...
Easily acomplished
klucilla said:
Great topic! Learning more about integrating Google Now and AutoVoice, but i have some doubts yet
I have a MotoX and do not want to leave the continuous mode autovoice on because MotoX has dedicated processor for voice recognition, intend
use "OK Google Now" to enable the continuous mode autovoice.
Could be accomplished?
"OK NOW GOOGLE", "MOTO X" "TURN ON TV"
^MotoX feature
^Enable AutoVoice
^Action
dont like Utter!...
Click to expand...
Click to collapse
You can accomplish it a couple of ways, if you use the okgooglenowintent xposed module as described above and instead of choosing utter quick launch you choose autovoice recognise as your task and give your commands that way (using this xposed module doesn't use autovoice permanent recognition, it uses the same as the touchless control does its just intercepting and switching touchless control for whatever app you replace it with so it doesn't drain any battery)
Or you can get the Google search api xposed module and set it up like I have above so that all of your tasker tasks are accomplished using Google now, so for example at screen off "OK Google Now turn on the tv" and providing you have the tasker task setup using the autovoice recognised profile or will perform the task for you
Just to clarify, using autovoice recognised under profile in tasker does not drain the battery as it's not the same thing as continuous listening mode in autovoice and you are using the moto x dedicated core for listening for your ok Google now command
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 all,
I have created a task that executes..
1. Launch App (Viper Smart Start, the Car's remote start app).
2. Wait (2 seconds)
3. Actions (Plugin : TouchTask > Tap Method > Point (x, y) Selection: 750 800
4. Wait (2 seconds)
5. Go Home
When i execute this task (named Start Car) manually everything works as expected.
But now I need to tie this to AutoVoice.
I'd like to invoke this task via voice command.
Can someone please guide me through steps on how I can go about this?
Ideally i'd like to use the keyword, "Viper Start my car"
There's a good tutorial here
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers