Android assumes the sysfs interface for backlight adjustment is at "/
sys/class/leds/lcd-backlight/brightness", which is not true for EeePC.
EeePC uses "/sys/class/backlight/eeepc/brightness". And other
platforms may use "/sys/class/backlight/acpi_video0/brightness".
Also Android assuems the back
How does Android process the "touch event" from the linux kernel /dev/
input/eventX ?
Does it use the tslib like Qtopia?
There are some "touch" related info in "MotionEvent" in the
documents...
Well, I don't know how it get the "raw" touch data, or how it perform
the calibration to the touch devic
WindowManagerService start the thread that reads events, implemented in
KeyInputQueue. There are debug log statements you can turn on in
KeyInputQueue.
On Thu, Feb 5, 2009 at 4:14 PM, 常青 wrote:
> Hi All,
>
> The problem I have is that after *updaing system.img* with the latest
> changes from Go
Hi All,
The problem I have is that after *updaing system.img* with the latest
changes from Google, while *without changing anything in keypad kernel
driver*, some keypad events can not be handled by user space applications
anymore.
After checking with *"/system/bin/getevent /dev/input/event0"*, I