Is it possible to send/simulate a bluetooth headset button click from the Gear to the attached phone?
My goal is to have that click activate Google Voice Search on the phone, but all the options I've tried don't work well enough.
1) Sending bluetooth commands through rooted terminal like: echo -e "AT\r" > /dev/ttySAC0
sending any command to ttySAC0 would crash the bluetooth connection. I guess this is a serial interface and isn't designed to accept text commands (I don't have a full understanding of this, just conjecture). Other devices like 'uhid' and 'uinput' didn't work either (everything just returns 1, and I don't know what that means either), I tried all the ones that showed up under 'ls -l /dev/' with 'bluetooth' in their properties.
2) Using tasker+autoremote: works when bluetooth tethering is on but is slow (command going through internet and back), and works when bluetooth direct receiving is enabled on the phone, but this drains battery a lot (Autoremote always awake listening on bluetooth). Neither one of these is a palatable side effect (slow, or battery drain).
3) Using tasker to intercept a command from the Gear media controller app
Works sometimes, I usually use the 'previous' button, but the need to 'Grab' the media button interferes with using it for music playback, and using another tasker task to enable/disable this profile leads to erratic behavior (sometimes the media player, Winamp in this case, will start working immediately, sometimes not). The bigger issue is that the media controller app stops responding after an hour or two, requiring rebooting the phone, or killing some of the Samsung Accessory services running in the background, which then relaunch themselves. I think there's too much interaction here with Tasker, Winamp, and the Samsung Accessory stuff to know what's happening though. The delay is also highly variable, which is annoying, and sometimes when the Voice Search launches I do not get the initial 'ding' audio through the Gear, though there could be a ton of reasons for that as well.
Long story short, I'm hoping being able to simulate bluetooth headset button presses/commands would solve all of the above problems, getting faster response, no/minimal extra power consumption, and be very reliable. Also, this may sound dumb, but I don't actually have a normal bluetooth headset to test with either.
Thanks to everyone that's on xda-developers, this is my first post ever, but I've been coming to this site for stuff for years.
We haven't found anything yet
(There are a few older threads around)
Oops. Should have guessed that. Thank's for the quick reply.
Brendo said:
We haven't found anything yet
(There are a few older threads around)
Click to expand...
Click to collapse
ulnah said:
Oops. Should have guessed that. Thank's for the quick reply.
Click to expand...
Click to collapse
A possible work around would be to activate Google Now on your phone, then goto gear manager and have it send notifications from Google search. Once you get some notifications from Google search, you can click the "show on device" button and it should open, and you can say "OK Google" to start start it up. (make sure you turn that feature on in the Google search settings )
My solution, for anyone interested...
I use AutoVoice rather than Google Now, although any command not matched by AV I have sent to Google Now for processing.
Anyway, there doesn't appear to be any faster way of communicating than via whatever it is that the Gear and my Note II communicate over by default. Not having the know-how to tap into this, I figured I would just use an existing method of communicating and use Tasker to intercept and pretend that was a BT button press instead.
So what I've done is just set it up so that when I use the dialer to run a USSD code that doesn't mean anything on my phone, this triggers what would ordinarily happen on a BT button press on autovoice - that is:
When variable %WIN matches "USSD code running" -> Perform task with actions: "Input - back" and then Plugin - State - Autovoice - Recognise... or whatever it is you want.
So that last action could be replaced by launching Voice Search if you want Google Now to take control.
I've probably not explained that well at all, will post a proper how to if anyone's interested.
mattytj said:
I use AutoVoice rather than Google Now, although any command not matched by AV I have sent to Google Now for processing.
Anyway, there doesn't appear to be any faster way of communicating than via whatever it is that the Gear and my Note II communicate over by default. Not having the know-how to tap into this, I figured I would just use an existing method of communicating and use Tasker to intercept and pretend that was a BT button press instead.
So what I've done is just set it up so that when I use the dialer to run a USSD code that doesn't mean anything on my phone, this triggers what would ordinarily happen on a BT button press on autovoice - that is:
When variable %WIN matches "USSD code running" -> Perform task with actions: "Input - back" and then Plugin - State - Autovoice - Recognise... or whatever it is you want.
So that last action could be replaced by launching Voice Search if you want Google Now to take control.
I've probably not explained that well at all, will post a proper how to if anyone's interested.
Click to expand...
Click to collapse
This is actually quite a clever work around, great thinking.
I can't get this to work. For example, when I use '*#111222#' and press 'dial' on my phone, it tries, then errors (this is good I think)
But when I tried to dial the same number from my Gear, I get '*#111222# not supported. Are you on null rom on your Gear?
mattytj said:
I use AutoVoice rather than Google Now, although any command not matched by AV I have sent to Google Now for processing.
Anyway, there doesn't appear to be any faster way of communicating than via whatever it is that the Gear and my Note II communicate over by default. Not having the know-how to tap into this, I figured I would just use an existing method of communicating and use Tasker to intercept and pretend that was a BT button press instead.
So what I've done is just set it up so that when I use the dialer to run a USSD code that doesn't mean anything on my phone, this triggers what would ordinarily happen on a BT button press on autovoice - that is:
When variable %WIN matches "USSD code running" -> Perform task with actions: "Input - back" and then Plugin - State - Autovoice - Recognise... or whatever it is you want.
So that last action could be replaced by launching Voice Search if you want Google Now to take control.
I've probably not explained that well at all, will post a proper how to if anyone's interested.
Click to expand...
Click to collapse
fOmey said:
This is actually quite a clever work around, great thinking.
Click to expand...
Click to collapse
Thanks mate, big fan of your work with the Gear, would have returned this thing after a day without you ROM.
ulnah said:
I can't get this to work. For example, when I use '*#111222#' and press 'dial' on my phone, it tries, then errors (this is good I think)
But when I tried to dial the same number from my Gear, I get '*#111222# not supported. Are you on null rom on your Gear?
Click to expand...
Click to collapse
Are you using the phone app on your gear or the dialer app? I am running _null.
Using the dialer means it just passes the dialer digits to the phone to process, so I simply dial "2" on the dialer and call. 2 gets picked up as a ussd code, which does nothing, but tasker intercepts and Pepper, my phone, asks me what she can do for me. I speak into my watch and she proceeds to ignore or misunderstand me.
All operating as normal.
Sent from my GT-N7105 using xda app-developers app
For some reason I thought it would have to start with '*#' to be recognized as a code, but '2' works as well.
Some quick testing shows no problems, I hope it stays that way. I had tried something similar by dialing a dummy number, having it hang up, and then start, but that took a long time and was much worse than this. Thank you!
This works excellent !
Only thing I dont like is the "unknown code" error that pops up on my phone, once I figure how to terminate that, its perfect.
fOmey said:
This works excellent !
Only thing I dont like is the "unknown code" error that pops up on my phone, once I figure how to terminate that, its perfect.
Click to expand...
Click to collapse
If it's an OCD type issue like me, trigger an overlay scene on the error message that destroys itself when the error isn't in focus, something like "Initiating...." . So mine does that, with a back action also triggered by the error. My attribute trends to lag so the error it's thrown before recognition. If after, adapt the scene to say, executing... or something. Point is, it of sight, out of mind!
mattytj said:
If it's an OCD type issue like me, trigger an overlay scene on the error message that destroys itself when the error isn't in focus, something like "Initiating...." . So mine does that, with a back action also triggered by the error. My attribute trends to lag so the error it's thrown before recognition. If after, adapt the scene to say, executing... or something. Point is, it of sight, out of mind!
Click to expand...
Click to collapse
Iv attempted to simulate a back button press with tasker, works fine if the phone is unlocked.. although if the phone is locked, im presented with a "UNKNOWN CODE" error which frustrates me
Ill have to get back to the drawing board and figure it out..
EDIT: Shortly after writing the above I came up with this, works a treat:
Code:
Task: Phone Trigger (36)
A1: AutoVoice Recognize [ Configuration:
Voice command with headset Package:com.joaomgcd.autovoice Name:AutoVoice Recognize Timeout (Seconds):0 ]
A2: Wait [ MS:0 Seconds:4 Minutes:0 Hours:0 Days:0 ]
A3: Run Shell [ Command:input keyevent 4 Timeout (Seconds):0 Use Root:eek:n Store Output In: Store Errors In: Store Result In: ]
Related
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
If I were to pair a Galaxy Gear with a M8, could I initiate a google search on my phone by pressing something on the watch? Basically I want to somewhat recreate the Moto x's ability to receive commands without the phone being on, and without an active tethering connection which will kill the battery on both devices.
Thanks so much!
my gear is setup to use google voice search/goggles/translate so i can voice command it, ask it to translate etc. caveat is i have to be BT tethered the whole time (battery life impact - i can get 18 hours on moderate use). I have the google now launcher installed and toggle between that and Nova depending on mood
works really good - when i take a photo with my gear, goggles automatically tries to identify it, i can tell my watch to launch apps and ask queries like you normally would with google voice
current limitation i have is i cannot use the hot phrase 'ok google' to initiate voice. i have to press the search i con to get started - still on the hunt on how to activate with 'ok google'
thevaristy said:
If I were to pair a Galaxy Gear with a M8, could I initiate a google search on my phone by pressing something on the watch? Basically I want to somewhat recreate the Moto x's ability to receive commands without the phone being on, and without an active tethering connection which will kill the battery on both devices.
Thanks so much!
Click to expand...
Click to collapse
animatechnica said:
current limitation i have is i cannot use the hot phrase 'ok google' to initiate voice. i have to press the search i con to get started - still on the hunt on how to activate with 'ok google'
Click to expand...
Click to collapse
Humm, "ok google" should work if Google Now has been triggered and running. Usually, you can do a followup search with "ok google".
Keeping the microphone running would be a MAJOR battery killer. Dont believe me, try it on your phone and see how quick it drains. On the Gear, tethered, you would probably get about 4 or 5 hours.
Just not quite there yet with battery technology, but hey who knows, maybe Google's Android Wear has cracked this nut and figured out a better way to initiate speech recognition.
ronfurro said:
Humm, "ok google" should work if Google Now has been triggered and running. Usually, you can do a followup search with "ok google".
Keeping the microphone running would be a MAJOR battery killer. Dont believe me, try it on your phone and see how quick it drains. On the Gear, tethered, you would probably get about 4 or 5 hours.
Just not quite there yet with battery technology, but hey who knows, maybe Google's Android Wear has cracked this nut and figured out a better way to initiate speech recognition.
Click to expand...
Click to collapse
Agreed. On the phone there is typically a setting to set the hot phrase for google now, this setting does not show up in the gear
Sent from my KFAPWI using Tapatalk
I'm using offline recognition on my gear in conjunction with Tasker and AutoVoice. I have it launch background continuous recognition whenever the screen is on, then so it when the screen turns off. I also have two orientations that turn the screen of right away without waiting for the timeout. (the positions when I naturally rest my arm on a desk and when my hand hangs at my side.) So far, this hasn't had much effect on battery life.
I use a key word of "Galaxy" to let it know I want to forward a commend to my phone, which I do with M2D Manager. I've already got quite a set of voice controls on the phone, so no need to replicate them on the watch. Otherwise, it handles the command on the watch.
The net effect here, is I lift my arm in standard watch fashion, and say commands directly. It's functionality similar to having always on recognition.
Sent from my XT1060 using XDA Premium 4 mobile app
hawkjm73 said:
I'm using offline recognition on my gear in conjunction with Tasker and AutoVoice. I have it launch background continuous recognition whenever the screen is on, then so it when the screen turns off. I also have two orientations that turn the screen of right away without waiting for the timeout. (the positions when I naturally rest my arm on a desk and when my hand hangs at my side.) So far, this hasn't had much effect on battery life.
I use a key word of "Galaxy" to let it know I want to forward a commend to my phone, which I do with M2D Manager. I've already got quite a set of voice controls on the phone, so no need to replicate them on the watch. Otherwise, it handles the command on the watch.
The net effect here, is I lift my arm in standard watch fashion, and say commands directly. It's functionality similar to having always on recognition.
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
@hawkjm73 Could you elaborate on how you have this setup exactly? This may be my answer to ditch trying to get this damn "Google Now Search" to work offline in handling voice commands such as call, ect... :fingers-crossed:
hawkjm73 said:
I'm using offline recognition on my gear in conjunction with Tasker and AutoVoice. I have it launch background continuous recognition whenever the screen is on, then so it when the screen turns off. I also have two orientations that turn the screen of right away without waiting for the timeout. (the positions when I naturally rest my arm on a desk and when my hand hangs at my side.) So far, this hasn't had much effect on battery life.
I use a key word of "Galaxy" to let it know I want to forward a commend to my phone, which I do with M2D Manager. I've already got quite a set of voice controls on the phone, so no need to replicate them on the watch. Otherwise, it handles the command on the watch.
The net effect here, is I lift my arm in standard watch fashion, and say commands directly. It's functionality similar to having always on recognition.
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
THIS! This is exactly what I am looking for. Screen on, send voice commands to the phone. How is this done?
thevaristy said:
THIS! This is exactly what I am looking for. Screen on, send voice commands to the phone. How is this done?
Click to expand...
Click to collapse
With a combination of Google Now Launcher and Offline voice recognition enabled...
https://www.youtube.com/watch?v=MY9OT1retpU&feature=youtu.be
Apologies for the delay in answering.
There are quite a few components working together here.
First and foremost: Null Rom. Without that, nothing else happens.
Second: offline voice recognition
This was pretty much taking all the language files from my phone and transplanting them to the watch, minding permissions.
Third: AutoVoice and Tasker
These are market apps and are fantastic for automation. You'll need them on both phone and watch. I'm using two profiles for this. The first turns on AutoVoice recognition in continuous mode whenever the screen turns on, and off when the screen goes off. The second profile is an AutoVoice recognize with "galaxy" as the command filter. It initiates an intent with the rest of what I say as a data payload.
Fourth: M2D manager
This is also available on the market, and needs to be on both devices. It is a Bluetooth bridge for Android intents. Tasker sends out an intent formed for M2D with the voice command as data. M2D transmitted it to the phone where it seems out a specified intent, still containing the command. Tasker listens for that intent. Once it had it, I use the AutoVoice test feature to send the command text in as if it had been spoken to the phone, so I can use all of my previously written voice control profiles. M2D also works the other way around, which I take advantage of for notifications and such.
Sent from my XT1060 using XDA Premium 4 mobile app
hawkjm73 said:
Apologies for the delay in answering.
There are quite a few components working together here.
First and foremost: Null Rom. Without that, nothing else happens.
Second: offline voice recognition
This was pretty much taking all the language files from my phone and transplanting them to the watch, minding permissions.
Third: AutoVoice and Tasker
These are market apps and are fantastic for automation. You'll need them on both phone and watch. I'm using two profiles for this. The first turns on AutoVoice recognition in continuous mode whenever the screen turns on, and off when the screen goes off. The second profile is an AutoVoice recognize with "galaxy" as the command filter. It initiates an intent with the rest of what I say as a data payload.
Fourth: M2D manager
This is also available on the market, and needs to be on both devices. It is a Bluetooth bridge for Android intents. Tasker sends out an intent formed for M2D with the voice command as data. M2D transmitted it to the phone where it seems out a specified intent, still containing the command. Tasker listens for that intent. Once it had it, I use the AutoVoice test feature to send the command text in as if it had been spoken to the phone, so I can use all of my previously written voice control profiles. M2D also works the other way around, which I take advantage of for notifications and such.
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks! I can follow most of what you said, however, when it comes to tasker, I'm a bit challenged. Right now I do have Tasker on both watch & phone along with Taskgear. With the help of some others, I have a couple profiles set on each (visa-versa) to show the battery levels respectively per other device on a widget on each.
If you could kindly share your tasker setups, I think I could pull this off! :fingers-crossed:
So the s-voice has proven fairly limited to Google Now. I've managed to get Google now (on my phone) to intercept and listen to command from my Galaxy Gear 1 stock (setting in Google Now to listen from Bluetooth). However, what would complete the equation is if I can launch Google Now from the GG. Is there an app that can do this? Preferably hook into the Power button on GG, but would I would settle for a simple widget on screen.
I've also tried the Null 23 ROM, but what I've noticed is the Google Now Bluetooth listening functionality no longer worked after that (nor did the camera app that came with NULL rom!). Since the listening part doesn't work, the only option left was to make the GG handle Google Now directly on the gear, which is not optimal (shifting more processing to watch = more processing/battery drain/slower/more mod/tethering to deal with etc)
I'm using Tmobile Note 4. I would prefer not to have to root if possible. Any help/ideas greatly appreciated!
Thanks!
I'm running null 23 with my note 3 and the listening function on Google now works. You have to enable it in settings. Combine this with tasker and tasgear, and you'll get exactly what you're seeking. Search in this forum.
nghiaxp said:
I'm running null 23 with my note 3 and the listening function on Google now works. You have to enable it in settings. Combine this with tasker and tasgear, and you'll get exactly what you're seeking. Search in this forum.
Click to expand...
Click to collapse
I'm on the Tmobile Note 4. To get Google Now (in the phone) recognition via Bluetooth, did you have to do any special config after you installed the null 23?
Also, is there any easy way to work on Tasker on the gear? After playing with custom ROMs and configuring on the gear, it doesn't seem that fun typing with fat fingers :X
Also, are you tethering with PDAnet or standard Bluetooth tether? The PDANet route with xpose framework still feels unstable (Voice on the Gear as standalone would not recognize my commands).
Same thing. Tasgear and tasker on Nul Rom,
Gear shortcut to launch tasker task to use taskger start tasker task on phone.
Tasker on phone turns on screen and launches google now
Google now on phone uses BT to listen to the gear
Tethering isn't required for this function.
When I do tether, I use Bluetooth Auto Connect on Gear which has tasker plugin
fat fingers
pingmustard said:
I'm on the Tmobile Note 4. To get Google Now (in the phone) recognition via Bluetooth, did you have to do any special config after you installed the null 23?
Also, is there any easy way to work on Tasker on the gear? After playing with custom ROMs and configuring on the gear, it doesn't seem that fun typing with fat fingers :X
Also, are you tethering with PDAnet or standard Bluetooth tether? The PDANet route with xpose framework still feels unstable (Voice on the Gear as standalone would not recognize my commands).
Click to expand...
Click to collapse
I'm also running the null Rom on my gear. I use the bluetooth tether option in the gear Bluetooth settings. So far I've tried both using Google now straight from the gear and the Bluetooth headset way. Sometimes the intent triggers without intention on the phone which seems to play havoc with spotify so currently I'm leaning more to the use of Google now via the gear alone. Also I find it easier when i can see the search, especially for note to self actions.
Anyway as the title suggests.... I'm no fan of typing on a tiny keyboard, it's a novelty and could be handy for a short text but I find holding my arm in the right position a pain after a while and it's difficult when you're typing stuff like com.orbonis.gear or whatever. Here are not 1 but 3 ways to make it easier.
1. Bluetooth keyboard. I've been using a Bluetooth keyboard with the gear off my wrist as a tiny monitor. Pros good typing experience and looks cool. Cons it can be fiddly to connect (I have to press var simultaneously on my keyboard and it can take a few go's to work) and it's not very portable.
2. Copy and paste. Although I've not been able to get copy and paste to work natively on my gear it works within tasker itself. You'd only have to type a message and a perform task once and then change the extras (which is easier than typing com.orbonis etc). However I think I've found a workaround. I was running the Swype keyboard (paid apk which I then downloaded via realapkleecher to pc, sideload to gear via adb) you can paste with this keyboard. I've found an app called clipper+ which is a syncing clipboard app. Downloaded straight from the play store tonight and was able to sync to the phone version. So I can now see my phones clipboard on the gear. When I get time I'll put Swype back on the gear and see if this does give a workaround for copy and paste.
3. Export from phone. I've not done this for tasker profiles but for apk files and zooper widgets from the phone via Bluetooth sharing from a file manager on the phone. Should be possible to do something similar for a tasker task. Just write the task on the phone and figure out how to send it lol.
Thanks for the great suggestion. I went with the bluetooth keyboard route for now. The other two routes are also viable, but I'm going to try keep it simple on the watch for now. I ended up tasker to intercept svoice and run task to kill it and invoke google voice on the phone instead.
Thanks again!
pingmustard said:
Thanks for the great suggestion. I went with the bluetooth keyboard route for now. The other two routes are also viable, but I'm going to try keep it simple on the watch for now. I ended up tasker to intercept svoice and run task to kill it and invoke google voice on the phone instead.
Thanks again!
Click to expand...
Click to collapse
Could you share the task descriptions? I'm very interested in how others use tasker with the gear. So far I've been using it for things like making Bluetooth tether a one button start and I've been looking at using apps like zooper to launch tasks. Recently I've also worked out a reasonable way to launch tasks on the watch with a command from the phone. I'll probably using that to add to my geo cache tasks on the phone. So when do something like going shopping the phone well recognise the location and the watch will bring up my shopping list, turn on Bluetooth tether, control motions/screen brightness etc.
You could create a profile on your gear that does the following:
When s voice is launched on the gear, kill it and send an intent to the phone.
On your phone, make sure Bluetooth headset is enabled in the Google search app. Then, create the following profile:
When the intent is received, wake the phone, open Google voice and start a search.
Edited original post as now getting. a collection of tasker tasks i have going on and easier to keep them in the first post but Will help below if anybody wants to copy them, also if anyone else wants to post there's that will be good.
1st) have tasker to toggle settings like wifi brightness etc when i get to work. Reverts settings back when i get home. Produces notifications on watch.
2nd) sends a message to my wife when i say launch task 1 that tells her im on my way home.
3) launches a autowear location menu on the watch. In the menu i can select wether i want high accuracy or low and wether i want location services on or off atall.
4) when i charge my phone between 2230hrs and 0625hrs the watch is switched to screen off, Bluetooth off and phone set to vibrate. When its unplugged or after 0625 the watch is switched to always on and phone is muted.
5) mobile data on and off options via autowear.
6) detects when i have lost connection to the watch and immediately turns on GPS to record the location. Then notifies me on my phone with a map view. I fix generators for a living so i need to take my watch of sometimes or when i have a shower in the gym etc. If for whatever reason i forget it which is unlikely i will know where i last had it.
7) every morning when i take my phone and watch off charge it selects a different watchface every morning at random from a predefined list. (needs watchmaker to be installed)
8) using autowear so that when i start My Tracks on the watch it automatically starts my gps task for me.
9) little on screen widget that i can control my Xbox/sky/tv changing channels, volume, play and pause, go to Fifa 15, record that, turn everything off. Accomplished using autowear, autoremote, autoinput, and a redundant tablet.
I have only just began with tasker so my methods won't be the most efficient but they work. If anyone has better ways as i mainly using auto input then please get in touch.
Could you describe which apps you used to pull this off? Thank you
Yeah sure, was a app called Tasker that i used on my phone to create it all and then a tasker plugin called tasker wear i think.
I have since been tinkering with it.
The updated version now has the following options;
1) text the wife I'm on my way home.
2) turns Wi-Fi of, auto brightness on, sync off
3) opposite of 2.
4) closes and returns back to watch face.
With option 2 and 3 i get a notification of what has beebeen switched on/ off.
With option 1 it also activates option 3 ready for when i get home.
Also if i forget to do the above especially switch evereverything on it detects when I'm nearly home and does it for me.
check AutoWear tasker plugin from joao, you can do anything with it in combination with the other Autoapps.
TheKaser said:
check AutoWear tasker plugin from joao, you can do anything with it in combination with the other Autoapps.
Click to expand...
Click to collapse
I'll have a look at that thanks, currently going to create a task that switches between gps and battery saving location as you can't turn location of anymore. So will have it switch to gps when needed and back to battery saving when not.
Also going to see if i can switch to cinema mode when charging and lost connection to the phone together and to revert back to previous or new watch face when undocked and regains connection to phone.
Hi Phil, would love to hear how you get on with that.
Hi rusty,
Just finished putting something together.
I have tasker detect when it's on charge and if between 2230 and 0625, and if so it switches the watch screen to off, and Bluetooth of.
using a profile manger, that detects that the watch it's no longer connected so switches notifications on the phone back on.
The opposite is when it's unplugged it switches Bluetooth back on, turns the watch screen to always on and the profile manager then detects the watch so turns the phone to mute but watch still vibrates.
I can now sleep at night with no lights keeping me awake and the only thing i have to do is plug my phone in.
Just to note it was pretty simple to set up with tasker and autoinput.
TheKaser said:
check AutoWear tasker plugin from joao, you can do anything with it in combination with the other Autoapps.
Click to expand...
Click to collapse
Hi kaser, as you recommended autowear do you have any experience with it as i can't get my head round it and there isn't much on YouTube or Google to help out.
phil gpx said:
Hi kaser, as you recommended autowear do you have any experience with it as i can't get my head round it and there isn't much on YouTube or Google to help out.
Click to expand...
Click to collapse
Hi, sorry for the late reply, I was on holidays.
I do have some experience. You need to download AutoApps from Google Play and suscribe to the alpha testing. Then you can download AutoWear. For this you also need to joing the Google+ community where the developer is always nice and reactive when posting bugs, questions or guidelines. Posting at the community is the best thing you can do since AutoWear is still in Alpha and it improves every day and it is not too straight forward to understand, especially how it communicates with AutoVoice and how commands and parameters are passed to Tasker.
By the way, I have a similar profile telling my girlfriend when I get to work, when I leave work and when I have parked at home coming from work, which automatically trigger depending on my location and connection to my car's bluetooth or work's WiFi. You don't really need your watch for that
Cheers for replying.
I have already downloaded it and played around but can't get my head around the processes of the app.
I followed the guide for the voice screen but cant get new screens up or start tasks etc.
I'm usually pretty good at working things out but cant with autowear.
what is it you are trying to do? Do you have the latest version of tasker?
Yeah i have the updated tasker but just can't work out how to get from the voice screen too say a "4 menu screen" that has tasks i have set up. Not sure what i want to accomplish with tasker next but i know if i can understand autowear it would help.
Have you done anything with autowear.
I have done the above tasks in the first post with autoinput and taskerwear but that is just a series of notifications that you can select to start tasks.
my main use for autowear is to send whatsapp messages from scratch (whatsapp currently only allows to reply to messages).
To achieve this I open an AutoWear Voice Screen by shaking the watch, and say "write to XXXX and say YYYY". This triggers an AutoVoice profile configured to react to "write to (?<contact>.+) and say (?<message>.+) (using Regex)
Inside the task, I do an WhatsTasker plugin contact search of the variable %contact generated by the regex command. Once found, I text the %message to this contact using whatstasker.
The best thing to do is to read the variable descriptions in the task. For example, you create your profile of AutoVoice Recognized. Inside it, before clicking configuration, you can see all the local variables available and their description. These are usable within the task. Same thing goes for any autowear task, they are usable after calling the task.
For example, in my task, after finding the contact, I have an AutoWear confirmation screen with the picture of my contact, his name, and the message I dictated. And following that I have an if %awmessage (the output of this confirmation screen) is different to cancel, then send the message.
Hope this helps a bit!
Thanks buddy, i will try and emulate this tonight once the kids are in bed. Whatsapp was one of the things i have been thinking of doing, just wish there was a way of bringing up a previous conversation without waiting for a new message.
well maybe you can capture the messages as they come, along with the sender's name, and save them in a temp file. Then create an autowear screen that shows the content of this file when requested... but I guess it would be very difficult to make it work perfectly (especially with groups).
I have managed to create and implement a mobile data on and off switch into my interactive notification popup for system settings using tasker, taskerwear and autoinput.
I now have the ability to switch wifi, mobile data, gps on and off as well as high and low accuracy location services and change profiles from one notifaction popping up.
left watch behind
Currently trying to set up a tasker profile that when i get disconnected from my watch will activate gps, stores the location, notifies you where it is and shows you on the map.
Hopefully will never need it but you never know. I.e you leave it in the gym, at work etc
Is there already something that does something similar as struggling at the moment but will crack on if there isn't.
Any one let me know about how to get nearby cell tower ID in a single variable.
Otherwise, how to convert the context in profile as a task.
Ty
Sent from my Micromax A58 using XDA Free mobile app
I'm sorrlearning tasker but i think if you create a new profile that activates when you connect to that cell tower. Then create a task and set variable %whateveryouwantto to %CellID.
You should only have to do that profile once and the variable will be set and you can use it in your profiles and tasks.
On another note i got my lost watch profile working like a charm.
Great Job
TheKaser said:
my main use for autowear is to send whatsapp messages from scratch (whatsapp currently only allows to reply to messages).
To achieve this I open an AutoWear Voice Screen by shaking the watch, and say "write to XXXX and say YYYY". This triggers an AutoVoice profile configured to react to "write to (?<contact>.+) and say (?<message>.+) (using Regex)
Inside the task, I do an WhatsTasker plugin contact search of the variable %contact generated by the regex command. Once found, I text the %message to this contact using whatstasker.
The best thing to do is to read the variable descriptions in the task. For example, you create your profile of AutoVoice Recognized. Inside it, before clicking configuration, you can see all the local variables available and their description. These are usable within the task. Same thing goes for any autowear task, they are usable after calling the task.
For example, in my task, after finding the contact, I have an AutoWear confirmation screen with the picture of my contact, his name, and the message I dictated. And following that I have an if %awmessage (the output of this confirmation screen) is different to cancel, then send the message.
Hope this helps a bit!
Click to expand...
Click to collapse
It sounds great :good:
May you please share your work with screenshots or something else so I can make it work for me?
Thanks in advance and best regards
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