The 'MOVEMENT' tab has three functional areas. One which sensor are currently being tracked. FlickStart only monitors sensors on a device when it's sensor state is green. The second area provides sliders to control the levels FlickStart expects before a sensor can trigger a command. The last area provides feedback if you want to practice movements. All possible moves are listed and the last move result.
The colour of the button indicates whether FlickStart is watching the microphone or not.
A greenish colour indicates FlickStart is watching the microphone on the phone and will start the speech recognizer when it hears a loud enough sound.
When the speech recognizer is started it will try to turn your speech into text and hand the text to FlickStart for matching against speech-based commands. After a longish pause the recognizer stops and FlickStart goes back to monitoring the microphone till the next loud noise.
'Loud' is determined by the slider next to the button.
Tapping the button will flip the state.
When the button is reddish in colour Flickstart will ignore input from the microphone on the phone.
The colour of the button indicates whether FlickStart is using the motion sensor on the phone or ignoring the sensor.
A greenish colour indicates FlickStart is watching the motion sensor on the phone and will try to match motion of the phone to one of the 9 movements the app can recognize.
Tapping the button will flip the state.
When the button is reddish in colour Flickstart will ignore movement of the phone.
The colour of the button indicates whether FlickStart is using the motion sensor on the watch or ignoring the sensor.
A greenish colour indicates FlickStart is watching the motion sensor and will try to match motion of the watch to one of the 9 movements the app can recognize.
Motion sensing on the watch is independent of motion sensing on the phone. In fact the part of FlickStart on the watch can trigger actions there even when the phone and watch are not connected to each other or the phone has lost connectivity with a service provider.
Tapping the button will flip the state.
When the button is reddish in colour Flickstart will ignore movement of the watch.
When the speech tracking button is green, FlickStart monitors the microphone waiting for a loud noise before calling in the Google speech recognizer.
The volume level required to trigger the recognizer is determined by the slider.
If you move the slider too far to the left almost any noise or bump will be enough to make FlickStart start the recognizer. If the environment is noisy enough you will hear the beep of the recognizer being started and double beep when the recognizer gives up happening frequently.
On the other and if you move the slider too far to the right you won't be able to shout loud enough to start the recognizer at all.
You will almost certainly need to adjust the slider when going from an environment like a quiet room to a noisy one like a car.
The speed slider selects the time frame for a complete movement. Initially the slider starts in the middle position and FlickStart will expects moves to complete in 1/2 to 2 seconds. Faster moves or slower moves are rejected.
You might want to move the slider for one of two reasons:
The required speed of movement is uncomfortable.
The speed setting allows too many spurious movements to trigger commands.
Also, the speed setting is something you might change for different usage scenarios (eg. sitting, running, driving, etc.).
The strength slider determines how much acceleration is required during a move before FlickStart will recognize a move.
You might move the slider for one of two reasons:
The required acceleration is uncomfortable.
The strength setting allows too many spurious movements to trigger commands.
Weaker strength settings will make it easier to accidentally trigger commands.
When FlickStart is open at the 'MOVEMENT' tab and one or more sensor is enabled a successful move (or something close to a successful move) will cause a picture to pop up showing which move Flickstart has recognized. If the picture has a greenish background, the move is considered successful and any commands that belong to active tags and match the move will be triggered. If the picture has a reddish background, the move is considered to be unsuccessful and FlickStart will indicate what it thought the move was and also indicate why it wasn't close enough to be successful.
Unsuccessful moves should be regarded as normal as FlickStart would be constantly triggering commands if all movements were classified as successful.
However, if you find moves seem to be more difficult to do successfully than they should be, consider adjusting the sliders for strength and/or speed.
Leave FlickStart open on the 'MOVEMENT' tab and pictures will pop up as you practice movements. You don't need to have any active tags in order to do practice.
Yes.
On the handheld, tapping on the tag name in the list of tags will produce a panel where you can view the list of commands. If you longpress a command, the command will be run. If you tap on the command there is a 'Start Command' button in the panel which pops up.
On the wearable, if you have FlickStart app visible and scroll down to any tag and then scroll right to look at the commands in a tag, tapping on a command will cause the command to be run.
You create a new tag and command or change one of the existing commands.
If you just want to start an app with a movement, you can find the app in the 'Handheld' tab (if the app you want to start is on the phone), or in the 'Wearable' tab. Then tap on the line showing the app and fill in a few details (such as which movement should be used to start the app).
If you want to send a more complex message to an app, create a tag in the 'Tags' tab and then create a command. When you create a command from the 'Tags' tab you have many more choices in the type of message you can send to an app. However, creating commands this way is quite complex and requires knowledge of the 'Android Intents' system and detailed information on the workings of the target app.
You can find Help for those tags by choosing the 'Current tab help' entry from the menu bar when you have the 'TAGS' tab visible.