regarding the (double)tap_to_unlock thing:
I suggest to implement this separately in a generic way to have a system wide gesture detection daemon that has
-- configurable *attention*-triggers
. double-tap detected by accelerometer being one of them,
. various elementary gestures like e.g. face-down position or strong shaking another,
. and obviously some users would want button-press as trigger source.
-- Then the gesture-daemon needs some state awareness:
. state_is-locked,
. state_custom-script-returns-zero...
-- and needs to know which programs are in list of running processes aka started (ps ax) and also
-- which program is upfront and visible (or *would* be visible if the current program [lockscreen] vanished, i.e. second on window stack).

Depending on all these conditions met the daemon then starts to watch for certain gestures and does the configured action when sensing one of those gestures (e.g. send a dbus cmd to lockscreen app ::{ activation-trigger+=doubletap(X,1500,50);; conditions: triggerd-by=doubletap, gesture_to_detect=none, program_on_top=lockscreen;; action: cmd=dbus-send lockscreen "unlock"} )


I'd like to discuss the design rationales and architecture more in depth with anybody willing to give this a go

/j

[edit] would integrate like siamese twins with pocketsphinx voice detection as suggested in and PoC provided in another thread here on tmo (sorry can't find the link right now) - voice input is "just another gesture" to detect

[edit2] this post spawns a new thread: http://talk.maemo.org/showthread.php...10#post1038610 - PLEASE answer there, not here (unless it's about the integration of that suggested daemon with the lockscreen)