Wearshell+Tasker Recipes (& Wearshell +Tasker+Autovoice Recipes) - Wear OS Software and Hacking General

It's time to post some of recipes I find useful. I drive for a living so operating my mobile gadgets HandsFree+EyesFree is how I have to do it.
[Rooted Watch + Rooted Phone Required ]
Most of these recipes incorporate the Autovoice App that uses Google App to grab spoken commands, HOWEVER, just switching out a variable in these recipes/tasks for your specific input will get the job done ... if you're interested in Autovoice off your watch the final pages of this thread are informative http://forum.xda-developers.com/xposed/modules/mod-google-search-api-t2554173 ... sadly though, it looks like no-one who has Marshmallow ON THEIR PHONE has a working flow at this time.
ANNOUNCEMENT: This new 5.0 version of wearshell comes included with some better versions of some recipes so far posted here by me, especially tts. here is the thread: http://forum.xda-developers.com/android-wear/development/app-wearshell-t2902242
FROM THAT THREAD:
WearShell version 0.6.0 has just been released.
I also put together some BeanShell commands for download:
https://goo.gl/2mA1uU
These commands are included:
Wearshell Command Collection 1
brightness
filepull
filepush
killws
mediaplayer
openuri
tts
unzip
vibrate
volume
WearShell Command Collection 2:
https://goo.gl/2mA1uU
battery
md5
notify
record
showimage
startapp
sysload
toast
uptime
zip
Wearshell Commands Collection 3
WearShell 0.6.0 has just been released. It includes support for Result Intents, sensors support and bug fixes.
alarm
charging
freestorage
heartrate*
light*
stepcount
stt
timer
wifioff*
wifion*
Commands marked with * I could not test because my G Watch is lacking the sensors and WiFi support. If you find any errors please let me know, I'll try to fix them.
Hope it's useful
...................
I'll leave this thread up and adding recipes, because these recipes usually don't require a file to be loaded onto the watch, they just run from an intent. so I can add things to the list and others too.
All I know is these work on my Huawei Watch with 1.4 update and Galaxy Note 3 on KK4.4.2. Please post recipes you find useful (and earn my undying gratitude) and I'll repost what I find and post ones I've made.
[Quick Summary on How These Work: Wearshell installs on phone and watch. the Wearshell app ON PHONE doesn't even need to be running to function because it sleeps until a tasker intent sent to it wakes it up, then Wearshell connects to it's companion app ON WATCH (companion app is tiny and uses like zero battery) and passes code to the companion app that it then executes the code. Wearshell is an awesome bridge to pass shell commands and java code via tasker]
Thanks and hopefully enjoy.

---

Reboot Watch By Voice
"Ok Google Reboot"
PROFILE: "i named it watch reboot"
Event> Plugin>Autovoice>Recognized> Command: "reboot"
TASK: "i named it watch reboot"
Add Action> System>Send Intent
ACTION
de.fun2code.android.wear.shell.EXEC
EXTRA
bsh: Runtime.getRuntime().exec("su -c reboot");
LEAVE ALL OTHER FIELDS AS IS

---

Set Watch Brightness by Voice
"Ok Google Brightness xxx"
(xxx's are a number between 0 - 254 to set brightness level)
PROFILE: "i named it watch brightness"
Event> Plugin>Autovoice>Recognized> Command: "brightness" (then I speak a number between 0-254)
Advanced> Replacements:to =2,+=, =,:=,-=,one=1,two=2,three=3,four=4,five=5,six=6,seven=7, eight=8,nine=9,ten=10,eleven=11,twelve=12,thirteen =13,fourteen=14,fifteen=15,sixteen=16,seventeen=17 ,eighteen=18,nineteen=19,twenty=20
TASK: "i named it watch brightness"
Add Action> Variables> Variable Set
NAME
%spokenbrightness
TO
%avcommnofilter
Add Action>Task> If
CONDITION
%avcommnofilter > 254
Add Action> Variable> Variable Set
NAME
%spokenbrightness
TO
254
Add Action>Task>Endif
Add Action>Task> If
CONDITION
%avcommnofilter < 20
Add Action> Variable> Variable Set
NAME
%spokenbrightness
TO
20
Add Action>Task>Endif
Add Action> System>Send Intent
ACTION
de.fun2code.android.wear.shell.EXEC
EXTRA:
bsh: Runtime.getRuntime().exec("su -c settings put system screen_brightness %spokenbrightness; su -c input keyevent 26");
LEAVE ALL OTHER FIELDS AS IS
Notes: you might have noticed that the second if condition prevents the watch from going below brightness level 20. also that "input keyevent 26" that you see there just simulate a power button click on my phone which clears the Google search results from the screen of my watch so that I have my watch face back when the task completes

---

Voice Search Results in UC Mini Browser on Watch (VERY fast+smooth over Bluetooth)
"Ok Google search lions tigers and bears"
[Instructions on easy installing UC Mini Browser after the recipe]
PROFILE: "i named it watch uc mini"
Event> Plugin>Autovoice>Recognized> Command: "search"
TASK: "i named it watch uc mini"
Add Action>Variable>Variable Set
NAME
%url2wearshell
TO
"https://www.google.com/search?site=&source=hp&q=%avcommnofilter"
Add Action> System>Send Intent
ACTION
de.fun2code.android.wear.shell.EXEC
EXTRA
bsh: import android.content.Intent; import android.net.Uri; uri = %url2wearshell; intent = new Intent(Intent.ACTION_VIEW, Uri.parse(uri)); intent.addFlags(Intent.FLAG_ACTIVITY_NEW_TASK); context.startActivity(intent);
LEAVE ALL OTHER FIELDS AS IS
Install
grab "UC Mini Browser" from the playstore on your phone and use an app like "Apk Share" to get the apk, then on the watch go to developer options enable "adb debugging" and "adb over bluetooth," then use the app "Apps2Wear" from playstore to sideload it (it'll take a few tries, and make sure on the watch you clicked ok to allow connections over adb) ... then grab " /system/app mover root" from the play store and sideload it with "Apps2Wear" (it'll take a few tries) then run "/system/app mover root" on the watch to install "UC Mini Browser" as a system app (so that it gets permission to use the internet)...you might get a weird error saying it couldn't move UC Mini, but it moved 'enough of it' (the base apk) to get this working. So reboot for good measure and it'll be ready. (btw: because 'enough' of UC Mini got moved to system folder it won't survive a factory reset like a fully installed system app and will need a reinstall.)
Usage:
on my Huawei Watch there is no back button, so I recommend you open some links from the Google results 'in the background' (long press the links), then use the tabs button on the bottom bar to switch between pages (this speeds up browsing too). also I recommend you go to settings in UC Mini (bottom right corner on my watch and hard to click) and go to Customize and check "Hide Bottom Bar" = this gives you full screen without losing the bottom bar, it's great.

---

Text Messages Automatically Spoken On Your Watch (Watch TTS)
[ ** This recipe needs work to be good, but it's 'good enough' to allow me to keep my eyes on the road, and much better solutions are on the way I'm sure. Also, It requires a tiny tasker app to be made and sideloaded (it's only 5 easy actions to input)..]
The tasker app we'll make in this recipe is named "Watch Speak"
THE APP FACTORY APP::
TASK: "I named it watch Speak"
Add Action>File>Read File
FILE
/sdcard/speak.txt
TO
%watchspeak
Add Action>Variables>Variable Search and Replace
VARIABLE
%watchspeak
SEARCH
€ (<--- don't type this, but see that weird symbol?)
STORE RESULTS IN
%watchspeak
REPLACE MATCHES
...check the box
REPLACE WITH
' (<--- see that apostrophe?)
Add Action>Variables>Variable Search and Replace
VARIABLE
%watchspeak
SEARCH
¥ (<--- don't type this, but see that weird symbol?)
STORE RESULTS IN
%watchspeak
REPLACE MATCHES
...check the box
REPLACE WITH
" (<--- see that quote mark?)
Add Action> Alert>Say
TEXT
%watchspeak
LEAVE ALL OTHER FIELDS AS IS, UNLESS YOU WANT TO
CHANGE SPEED AND PITCH
Add Action>Task>Stop
IN TASKER:
PROFILE: "I named it Watch Speak"
Event> Phone>Received Text
TASK: "I named it Send Watch Speak"
Add Action>Variables>Variable Set
NAME
%watchSpeak
TO
text from, %SMSRN. it says, %SMSRB
Add Action>Variables>Variable Search and Replace
VARIABLE
%watchspeak
SEARCH
' (<---don't route this, but see that apostrophe?)
STORE RESULTS IN
%watchspeak
REPLACE MATCHES
...check the box
REPLACE WITH
€ (<--- don't type this, but see that weird symbol?)
Add Action>Variables>Variable Search and Replace
VARIABLE
%watchspeak
SEARCH
" (<---don't type this, but see that quote mark?)
STORE RESULTS IN
%watchspeak
REPLACE MATCHES
...check the box
REPLACE WITH
¥ (<--- don't type this, but see that weird symbol?)
Add Action> System>Send Intent
ACTION
de.fun2code.android.wear.shell.EXEC
EXTRA
bsh: Runtime.getRuntime().exec("su -c echo '%watchspeak' >| /sdcard/speak.txt"); Runtime.getRuntime().exec("su -c monkey -p com.gmail.paulporter1.watchspeak -c android.intent.category.LAUNCHER 1");
LEAVE ALL OTHER FIELDS AS IS
Add Action>Task>Stop
NOTES:
(a) the weird symbols ¥ and € in search and replace are because I do not know how to transfer the symbols ' and " from a variable into linux commands that are embedded in java code, because ' and " will break a command that is supposed to put text into a file, that file being the /sdcard/speak.txt file that our tasker app on the watch reads from, but without those symbols tts can't speak words correctly, so we switch them then switch them back.
(b) on my Huawei Watch the texts won't read out loud if you are actively using the watch (which I like actually) but you might get a duplicate reading once the watch goes idle.

---

Voice Command Your Watch To Read Last Text Message
PROFILE: "i named it repeat message"
Event> Plugin>Autovoice>Recognized> Command: "repeat message"
TASK:
(just use/reuse the task from the previous post, the task that resides on the phone)

---

Automate theater mode
This is a repost originally posted by ShadowEO.
In the task, add a Send Intent action with these parameters:
On:
Action: de.fun2code.android.wear.shell.EXEC
Extra: bsh: Runtime.getRuntime().exec("su -c settings put global theater_mode_on 1");
Off:
Action: de.fun2code.android.wear.shell.EXEC
Extra: bsh: Runtime.getRuntime().exec("su -c settings put global theater_mode_on 0");
Off will turn off theater mode, however still leave the watch screen off, however the screen will come back on with the next tap and theater mode will be off.

---

Notifications Automatically Spoken On Your Watch (Watch TTS
Use/Reuse the same recipe from a few posts back for speaking text messages, but just change these lines:
From this:
Add Action>Variables>Variable Set
NAME
%watchSpeak
TO
text from, %SMSRN. it says, %SMSRB
to this:
Add Action>Variables>Variable Set
NAME
%watchSpeak
TO
notification, %NTITLE

---

Change LCD Density By Voice
"Ok Google density xxx"
(where. xxx is a number I speak between 180-340)
PROFILE: "i named it watch density"
Event> Plugin>Autovoice>Recognized> Command: "density" (then I speak a number between 180-340)
Advanced> Replacements: to =2,+=, =,:=,-=,one=1,two=2,three=3,four=4,five=5,six=6,seven=7,eight=8,nine=9,ten=10,eleven=11,twelve=12,thirteen=13,fourteen=14,fifteen=15,sixteen=16,seventeen=17,eighteen=18,nineteen=19,twenty=20
TASK: "i named it watch density"
Add Action> Variables> Variable Set
NAME
%spokendensity
TO
%avcommnofilter
Add Action>Task> If
CONDITION
%avcommnofilter > 340
Add Action> Variable> Variable Set
NAME
%spokendensity
TO
340
Add Action>Task>Endif
Add Action>Task> If
CONDITION
%avcommnofilter < 180
Add Action> Variable> Variable Set
NAME
%spokendensity
TO
180
Add Action>Task>Endif
Add Action> System>Send Intent
ACTION
de.fun2code.android.wear.shell.EXEC
EXTRA:
bsh: Runtime.getRuntime().exec("su -c wm density %spokendensity; su -c input keyevent 26");
LEAVE ALL OTHER FIELDS AS IS

---

Pablo, tonight i want test all. Its wonderful.
I m curious how work speaker tts! Are there delay with this method?
Inviato dal mio SM-N9005 utilizzando Tapatalk

---

vingar said:
Pablo, tonight i want test all. Its wonderful.
I m curious how work speaker tts! Are there delay with this method?
Click to expand...
Click to collapse
you rock man, good luck. the watch will vibrate then 7-10 seconds later it talks. (the watch reads out emojis too, like ??? makes it say 'smiley face ring penguin) ... android is cool

---

pablo71 said:
you rock man, good luck. the watch will vibrate then 7-10 seconds later it talks. (the watch reads out emojis too, like ??? makes it say 'smiley face ring penguin) ... android is cool
Click to expand...
Click to collapse
Pablo you have a PM!

---

Any alternative for nonrooted phones? Don't want to root my new s7 edge yet... I miss the simple root and warranty from the nexus :/
Sent from my SM-G935F using XDA-Developers mobile app

---

[email protected] said:
Any alternative for nonrooted phones? Don't want to root my new s7 edge yet... I miss the simple root and warranty from the nexus :/
Click to expand...
Click to collapse
most of the tasker tasks I've exported as apps/apks and sideloaded onto my watch work just fine, and I don't think root is needed for any of that. just use your watches button combination to reboot into bootloader, then select recover mode, connect cable to your computer and use adb commands to sideload apps. there are some good threads in Android Wear section that I've been using to do stuff.

---

pablo71 said:
most of the tasker tasks I've exported as apps/apks and sideloaded onto my watch work just fine, and I don't think root is needed for any of that. just use your watches button combination to reboot into bootloader, then select recover mode, connect cable to your computer and use adb commands to sideload apps. there are some good threads in Android Wear section that I've been using to do stuff.
Click to expand...
Click to collapse
Thanks! I would simply use Adb reboot bootloader as usual on my nexus 4 and 7.
But saw the root needed disclaimer in your first post.
Sent from my SM-G935F using XDA-Developers mobile app

---

pablo71 said:
most of the tasker tasks I've exported as apps/apks and sideloaded onto my watch work just fine, and I don't think root is needed for any of that. just use your watches button combination to reboot into bootloader, then select recover mode, connect cable to your computer and use adb commands to sideload apps. there are some good threads in Android Wear section that I've been using to do stuff.
Click to expand...
Click to collapse
So this part of your statement: "most of the tasker tasks I've exported as apps/apks and sideloaded onto my watch work just fine"
I've been adding profiles in Tasker on my phone with WearShell installed and they are not working on my watch, I really wanted the brightness changes to be triggered by connect and disconnect from my home wifi network. I guess now I understand why the tasks don't work, since I have not sideloaded them into my watch. I also tried the automate theater mode that fails as well,
I totally missed the fact that they need to be exported as apps and sideloaded into the watch via adb. I missed that in this thread and the WearShell thread. Gah!

---

Pkt_Lnt said:
So this part of your statement: "most of the tasker tasks I've exported as apps/apks and sideloaded onto my watch work just fine"
I've been adding profiles in Tasker on my phone with WearShell installed and they are not working on my watch, I really wanted the brightness changes to be triggered by connect and disconnect from my home wifi network. I guess now I understand why the tasks don't work, since I have not sideloaded them into my watch. I also tried the automate theater mode that fails as well,
I totally missed the fact that they need to be exported as apps and sideloaded into the watch via adb. I missed that in this thread and the WearShell thread. Gah!
Click to expand...
Click to collapse
no no, I didn't explain myself very well in the previous post ... these recipes I've posted are not apks to sideload ... what I was referring to in the previous post is a few little Tasker apks I've side-loaded onto my watch, but I did not include those in this thread because this thread was for recipes that included wearshell ... pardon me for not communicating clearly in the previous post. If you wouldn't mind copying and pasting the intents in Tasker that are being sent to wearshell I would like to see them
this would set brightness to full, the number 254 does that in this intent
SEND INTENT
ACTION
de.fun2code.android.wear.shell.EXEC
EXTRA
bsh: Runtime.getRuntime().exec("su -c settings put system screen_brightness 254");
LEAVE ALL OTHER FIELDS AS IS

---

pablo71 said:
no no, I didn't explain myself very well in the previous post ... these recipes I've posted are not apks to sideload ... what I was referring to in the previous post is a few little Tasker apks I've side-loaded onto my watch, but I did not include those in this thread because this thread was for recipes that included wearshell ... pardon me for not communicating clearly in the previous post. If you wouldn't mind copying and pasting the intents in Tasker that are being sent to wearshell I would like to see them
Click to expand...
Click to collapse
Brightness:
Wifi disconnect (this actually has about 15 steps for various changes to the phone for sound and security)
Code:
Action: de.fun2code.android.wear.shell.EXEC
Extra: bsh: Runtime.getRuntime().exec("su -c settings put system screen_brightness 254 ");
Wifi connect (same, changes to sound and security)
Code:
Action: de.fun2code.android.wear.shell.EXEC
Extra: bsh: Runtime.getRuntime().exec("su -c settings put system screen_brightness 106 ");
I have also tried removing the space after the number and before the quote, since other bsh: entries I have seen don't show the space.
Code:
Extra: bsh: Runtime.getRuntime().exec("su -c settings put system screen_brightness 106");
Theater:
Start sleep tracking (Sleep as Android works as a plugin with Tasker, I set silent mode and try to start theater)
Code:
Action: de.fun2code.android.wear.shell.EXEC
Extra: bsh: Runtime.getRuntime().exec("su -c settings put global theater_mode_on 1");
End sleep tracking when alarm sounds (again, Sleep as Android as a plugin for Tasker allows the sleep tracking to terminate on alarm and run an intent)
Code:
Action: de.fun2code.android.wear.shell.EXEC
Extra: bsh: Runtime.getRuntime().exec("su -c settings put global theater_mode_on 0");

---

Pkt_Lnt said:
Brightness:
Wifi disconnect (this actually has about 15 steps for various changes to the phone for sound and security)
Code:
Action: de.fun2code.android.wear.shell.EXEC
Extra: bsh: Runtime.getRuntime().exec("su -c settings put system screen_brightness 254 ");
Wifi connect (same, changes to sound and security)
Code:
Action: de.fun2code.android.wear.shell.EXEC
Extra: bsh: Runtime.getRuntime().exec("su -c settings put system screen_brightness 106 ");
I have also tried removing the space after the number and before the quote, since other bsh: entries I have seen don't show the space.
Code:
Extra: bsh: Runtime.getRuntime().exec("su -c settings put system screen_brightness 106");
Theater:
Start sleep tracking (Sleep as Android works as a plugin with Tasker, I set silent mode and try to start theater)
Code:
Action: de.fun2code.android.wear.shell.EXEC
Extra: bsh: Runtime.getRuntime().exec("su -c settings put global theater_mode_on 1");
End sleep tracking when alarm sounds (again, Sleep as Android as a plugin for Tasker allows the sleep tracking to terminate on alarm and run an intent)
Code:
Action: de.fun2code.android.wear.shell.EXEC
Extra: bsh: Runtime.getRuntime().exec("su -c settings put global theater_mode_on 0");
Click to expand...
Click to collapse
I assume that all the other fields in this Send Intent action are left as is, so these intents are written perfectly. Now, the things that I'm about to say next are probably things you already know, but Tasker is extremely finicky with profiles, especially cloned profiles, and you have to back out of Tasker completely using the back button to activate profiles. Sometimes I have to delete profiles that should be working, and then recreate them. Once I do that they work flawlessly forever. Sometimes I have to turn the profiles on and off as well. Also I am pretty sure you are using the latest version of wearshell, because I read in that Forum that the previous version of wearshell did not work with the screen off on the phone. Hopefully the wearshell companion app is in memory on the watch so that it can receive communication from the app on the phone. You could try opening the app on the phone and starting and stopping at the server just to wake the it up and testing to see if they are running.. That server, by the way, is not part of any of this, you probably already know that the server is just to run test code through a web server interface that is on the watch. But running that server would be a great way to check that the companion app and the phone app are both operating and talking to each other.
EDIT: In tasker, is 'allow external access' granted in the settings? I'm not that great at tasker, but I think something like that in settings could be it maybe

---

pablo71 said:
I assume that all the other fields in this Send Intent action are left as is, so these intents are written perfectly. Now, the things that I'm about to say next are probably things you already know, but Tasker is extremely finicky with profiles, especially cloned profiles, and you have to back out of Tasker completely using the back button to activate profiles. Sometimes I have to delete profiles that should be working, and then recreate them. Once I do that they work flawlessly forever. Sometimes I have to turn the profiles on and off as well. Also I am pretty sure you are using the latest version of wearshell, because I read in that Forum that the previous version of wearshell did not work with the screen off on the phone. Hopefully the wearshell companion app is in memory on the watch so that it can receive communication from the app on the phone. You could try opening the app on the phone and starting and stopping at the server just to wake the it up and testing to see if they are running.. That server, by the way, is not part of any of this, you probably already know that the server is just to run test code through a web server interface that is on the watch. But running that server would be a great way to check that the companion app and the phone app are both operating and talking to each other
Click to expand...
Click to collapse
Yes, I know the idiosyncrasies of Tasker, I've been beta testing for a couple years, and if you saw the complexity of my myriad tasks.....
When I have the WearShell running, I get a screen wakelock that keeps the display on. I don't have it running because joschi70 in the WearShell thread stated (in response to you) it does not have to run for broadcasts .I have tried running it and still nothing changes on the watch.
Actually the server is only needed if you use the web API or the web interface itself.
If you use broadcasts to send commands it should work without having to start the WearShell server on the phone.
Click to expand...
Click to collapse
I did see the message on the watch that WearShell was installed. Of course, it does not show in the apps menu.