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, 常青 <cha...@gmail.com> wrote: > 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'm sure > that correct key codes have been sent out from keypad driver. > > Other information that I have, > > - system_server is the only user of /dev/input/event0 > - /system/usr/keylayout is not changed > - /system/usr/keychars is not changed > > > So to debug this issue, I will have to know the exact application (child of > system_server???) which is polling/handling keypad events. Or that program > is in HAL layer? > > Could someone have a chance to know this? > > Thanks, > Stephen > > > > -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel -~----------~----~----~----~------~----~------~--~---
