Inconsistent! Used to be pretty robust but now it won't launch the voice screen 9 out of 10 whichever method I use. I get a pretty useless toast message saying the screen has launched and it never appears! May have to root and go back to my old method.
Gerat idea, great feature set But there are so many ins-outs, obscure parameters, and weird "bugs-but-not", firmware differences, and a few bugs, at the moment I'm struggling too much with it to make it worth the effort. The environment (Android Wear and its hard & firmware) is way behind where this app is. I'm tired of Youtube documentation, though. I personally really need it all in organized print. Tasker's sending the vars, but the watch isn't consistently reacting. It's crazy making, for everyone.
I installed this hoping to add some cool features to my watch but All it did was constantly trigger the shake to talk even when not moving my wrist at all, essentially making my watch a useless bracelet that vibrates constantly. I assume they have not made this compatible with AW2.... wish there was a way I could use this because it seemed promising. It took me some very tedious and careful work to uninstall it without triggering this ultra sensitive shake feature....
I specifically wanted a way of disabling always on display in the evening and in the car to save battery. Problem is that my watch is 2.0 with ambient display. This app just turns the display fully on or off rather than changing the native setting. Sad face
When it works it's ace. However No consistently. When I shake to wake the phone sees the log but the watch is not listening. When it dose work it's ace, just need it to work every time.
I've bought several of the author's Tasker plugins, and unfortunately they are all very rough, buggy, unpolished and generally difficult to use. This one in particular seems more like a "private alpha" than an app you would actually charge money for. The UI is very technical and essentially unusable without constantly referring to the "manual". For example: When creating a new notification, there is an input box labelled "Command". What do you think that covers? Is it a command that is sent to the watch? No. It is in fact used to specify a trigger event, i.e when this happens on your watch, the AutoWear action that you are currently configuring will be executed – independent of Tasker. In other words, "Command" can be "the screen turns on". In Tasker, this would be a "(trigger) Event" or profile "condition".
Comment here: https://plus.google.com/u/0/+Jo%C3%A3oDias/posts/ZmbF5UUMu7K
- added Emoji Screen where you can draw emojis to trigger profiles in Tasker
- added Image Screen where you can display a zoomable image on your watch
- added device selector in the main app
- disable/enable wifi on your watch with tasker
- disable/enable shake with tasker
- other smaller features and bugfixes