LMT is a tool for Android (tested already on multiple devices - see below) that launches a command when perform single touch or multitouch gestures on the screen (In any app/screen/etc.). You can connect basic and advanced commands to any gesture LMT supports. In addition to the gestures you can activate a system-wide PieControl for navigation like the feature in the ICS stock browser (touch the side of the screen to activate it).
In the pie you’ll see the current time, date, some animating status indicators, and one or two rows of icons, depending on how you’ve set it up. You can change the colors and even the spacing and radii how ever you’d like.
First, you’ve got to have a rooted device for LMT to work. Second, the settings aren’t user-friendly — no, they’re not difficult, but if you want icons to show up you have to change the value of one particular setting from “0″ to “1″. (Don’t worry, I’ll show you where that is in the video.)
· Download the latest apk here
· Copy it to your phone
· Install it via file explorer
· After installation start LMT and set the specified input device for your phone. Then connect an action to e.g. the double swipe up gesture, start the touchservice and do the double swipe up gesture on the screen afterwards. If everything works fine, you’ll see the corresponding overlay and action.
CHANGELOG FOR 1.9:
· Redesigned UI a little bit
· New color picker
· Added support for non armv7 devices
· Fixed tasker task
· Fixed script action
· Fixed 24h clock
WHAT IS ISAS?
The ISAS (invisible swipe areas) can be used to swipe with one finger from the sides to to center of the screen (like you would bring up the pie) to trigger actions. E.g. you could use the 3 ISAS at the bottom of the screen to trigger back, home and recents with just swipes when the navbar is hidden. Those swipes are as fast and reliable as normal button presses. In order to make the ISAS work you have to do the following setup:
activate gestures via setMode (because ISAS are being recognized via the internal gesture engine)
Configure min bbox size. Actually this is the length in pixel the swipe must be long, so that the corresponding action for the ISA is being triggered.
Configure activation area size. This is the height (for bottom/top ISAS) or the width (for left/right ISAS) of the area, where the swipe must be started in. So the lower the value, the more precise you have to start the swipe at the side of the screen
Last but not least the touchscreen to screen factors: As for some devices the touchscreen uses a different coordinate system as the screen, you have to adjust here the values for x and y. For the Nexus devices I added those values already to the OP and in later versions I'll introduce a kind of auto calibrate. But for now it is a little bit of testing...
Once the setup is complete you can assign your actions to the 12 available ISAS!
If ISAS isn’t working correctly, try changing these settings:
· HTC Evo3D -> 4
· HTC Sensation -> 2/4, x=200%, y=100%
· HTC Amaze -> 4
· HTC HD2 -> 0
· HTC DesireHD -> 3
· HTC Thunderbolt -> 1
· HTC Inspire 4G -> 1
· HTC One X -> 4
· Google Galaxy Nexus -> 1, x=100%, y=100%
· Google Nexus S -> 0
· Google Nexus 4 -> 2, x=200%, y=200%
· Google Nexus 7 -> 0, x=160%, y=200%
· Samsung Galaxy S2 -> 2
· Samsung Galaxy Note -> 2
· Samsung Galaxy Note 2 -> 2
· Samsung Galaxy S -> 0/8
· Samsung Galaxy Tab 8.9 -> 4
· Sony Xperia T -> 2
· Motorola Atrix 4G -> 3/5
· Motorola RAZR -> 4
· Motorola DROID 3 -> 4
· Motorola Defy -> 3
· HP Touchpad -> 6
· Acer Iconia -> 2/4