ro. wrote:I had a play with the "Remove location dependency" option, but not knowing how it worked, I've now ended up with three actions all with the same name ("lights"). They all show up on the "Linked commands"/"Command associations" page, but I can't delete any of them with a long press.
The "Autowear instructions" page is blank. I presume this is for Android Wear?
"Enable/Disable autowear inergration" - spelling mistake
When selected, this goes to a page called "Autovoice intergration" - different spelling mistake, and shouldn't it say "Autowear"?
Is there any way to start the voice prompt if you set "App icon launch"/"Launch get voice from app icon" to off?
If you leave a menu page up long enough for the screen to go blank, when you wake up the screen, not only has the menu disappeared, but the whole app has vanished.
I'll fix the remove linked items as there is an error if more than one device has the same name. This was on my to do list, but just got bumped to the top.
Thanks for pointing out the language errors, I'll fix that also. I'm sure there are more as most of the UI made during my lunch breaks
You can start the voice prompt by any of the following:
1) App icon
2) A notification in the notification bar (which will show up on the lock screen on android 4.0 and above). This is how I use the app, as the notification is only shown when I am on my home network(s) (see wifi dependency for notification).
3) With AutoVoice, by tapping the google now search box or by saying "OK Google" on some devices.
4) On your android wear device with AutoWear, with a swipe to launch.
5) On your android wear device with AutoWear, with the shake your wrist gesture (this can also be turned on an off with wifi dependency)
I use the last four items, but did not want to force them onto users.
I'm not sure if I included the instructions in the production version of the app but they are working in beta....which I will push to production, along with the correction above, this weekend. The instructions are also listed on google plus with all the other instructions.
The reason the app is "vanishing" is because I have all screens killed when the screen turns off...I did this to prevent the app from using more resources than needed...If you do not back out of the app android will keep the app in memory (this may be another tasker limitation)...I guess this is my personal preference and I could add a setting to prevent this, but it is low priority.