
AC Chapin
- Flag inappropriate
- Show review history
Sadly this is watch disablingly bad. I only got it as part of a tasker solution to enable google's reminders to actually show up on my Fossil Carlyle watch. It actually *did* make that happen while I had it on (which admittedly is better than Google has ever done). The app's intended use however is for voice commands, and it tries to set up a watch shake gesture to listen for them. Since I didn't want that, I set shake detection to disable, so the shake to listen screen should never have come up, right? For a little while it seemed to be fine, but then: "Please wait" and "AutoWear Listening" started appearing on the watchface on constant, rapid-fire, repeat. The phone app Log lists THOUSANDS of "New Last Command: null;" entries. Through diligent (frantic) tapping through this constant barrage I tried restarting the watch, going through setup from the phone app again (it congratulated me on the fact that it "heard me say null"), and uninstalling and and reinstalling it on the watch (2 minutes clear and then the barrage started up again.) Finally (more frantic tapping) I uninstalled this app it from the watch again for blessed relief. (btw the help link in the app goes to Google+(!) I mean, I miss it too but...) RESPONSE TO DEVELOPER-- pulled out of the original review: " I also tried deleting the shake to listen Screen from the phone app several times, but although each time I confirmed the delete, it just stayed there in the Screen list." I did not create this or any Screen myself; there were no other screens in the list.
20 people found this review helpful
But was that screen on the list? can you try deleting it?

Andrew Jn
- Flag inappropriate
- Show review history
Works very badly on GW4. Tasker profiles aren't triggered by autowear commands. Predefined commands sometimes work but just randomly. Custom commands aren't working at all. I can see a toast message on my phone that the autowear command was received, but Tasker ignores it. Moreover, the toasts stop arriving after a couple of minutes. It seems like the autowear app itself stops listening to or sending commands and states. All battery restrictions are off, and all permissions are granted.
I'm trying to update the app on Google Play with a fix but they're not letting me right now. Can you please check this thread about it: https://www.reddit.com/r/tasker/comments/187p5de/dev_need_help_guessing_why_google_is_blocking/

Luke Lo Presti
I've been using AutoWear to creat custom complications on my Galaxy Watch 4 with persistent notification data from my phone along with Tasker and AutoNotification. Recently the app broke with the new One UI 5 update on the Galaxy Watch. The dev has gone out of his way and been super helpful in addressing these issues and even provided private APKs for testing which is much appreciated! Highly recommend!
3 people found this review helpful
Thank you very much :) Glad I could help!