View source for Better handling of AUX/Power buttons
From Openmoko
You do not have permission to edit this page, for the following reasons:
You can view and copy the source of this page:
Return to Better handling of AUX/Power buttons.
You do not have permission to edit this page, for the following reasons:
You can view and copy the source of this page:
Return to Better handling of AUX/Power buttons.
The freerunner as only two hardware buttons: AUX and Power, here we discuss about a way to use them in the best way.
A lot of distros uses the AUX and Power button in a very poor way: simple locking, suspend the device, and some other little things.
The real problem is that the big part of software read keyboard events from FSO or by the Input Event kernel interface while in some cases buttons are grabbed by the window manager.
That makes impossible to use the buttons in application contexts.
We may simulate different key events combining short/long press of the two real buttons. For example:
and so on.
We may than use the long/combined press for global shortcuts, eg long AUX for locking, long POWER to bring up settings, etc. etc., and use the short events in application context.
Possible implementations:
A daemon that grab /dev/input/events* and provide a virtual uinput keyboard, in a trasparent manner for the system.
A daemon that grab X11 events and iniects fake events in the X server it'self