Oh likewise for WindowManagerService, which actually dispatches the events to the appropriate window.
On Tue, Nov 25, 2008 at 10:07 AM, Dianne Hackborn <[EMAIL PROTECTED]>wrote: > There is lots of debugging you can turn on an the input class (can't > remember the name) by changing a boolean at the top. > > > On Tue, Nov 25, 2008 at 12:36 AM, mvniekerk <[EMAIL PROTECTED]> wrote: > >> >> Thanks for the pointer. >> >> Left key gave this: >> V/EventHub( 1628): revents for 1 = 0x00000001 >> >> V/EventHub( 1628): /dev/input/event0 got: t0=408, t1=216528, type=1, >> code=105, v=1 >> >> V/EventHub( 1628): iev.code=105 outKeycode=21 outFlags=0x00000002 >> err=0 >> >> V/EventHub( 1628): revents for 1 = 0x00000001 >> >> V/EventHub( 1628): /dev/input/event0 got: t0=408, t1=426522, type=1, >> code=105, v=0 >> >> V/EventHub( 1628): iev.code=105 outKeycode=21 outFlags=0x00000002 >> err=0 >> >> Button 1 gives gave output: >> >> V/EventHub( 1628): revents for 1 = 0x00000001 >> >> V/EventHub( 1628): /dev/input/event0 got: t0=441, t1=426538, type=1, >> code=2, v=1 >> >> V/EventHub( 1628): iev.code=2 outKeycode=8 outFlags=0x00000000 err=0 >> >> V/EventHub( 1628): revents for 1 = 0x00000001 >> >> V/EventHub( 1628): /dev/input/event0 got: t0=441, t1=596523, type=1, >> code=2, v=0 >> >> V/EventHub( 1628): iev.code=2 outKeycode=8 outFlags=0x00000000 err=0 >> >> It is not just the Desktop and Menu that is unresponsive to this >> input, it is also the Dialer. Obviously I could not navigate (sic) to >> the applications, so I cannot test any other apps for this. The only >> difference from this is the outFlags - I take it is the difference >> between WAKE_ON_DROPPED and 0. I'm going to torture that .java file >> for debug and come back with results. >> >> >> On Nov 24, 6:55 pm, "Joe Onorato" <[EMAIL PROTECTED]> wrote: >> > If you uncomment the LOG_NDEBUG line at the top of >> > frameworks/base/libs/ui/EventHub.cpp, and rebuild, there will be some >> more >> > logging each time a key is pressed. After that, you'll need to start >> > tracing through the code. The java code that reads from EventHub is in >> > frameworks/base/services/java/com/android/server/KeyInputQueue.java. >> > >> > -joe >> > >> > On Mon, Nov 24, 2008 at 9:33 AM, mvniekerk <[EMAIL PROTECTED]> wrote: >> > >> > > For the record, all the other keys work fine. Maybe a git Android bug? >> > >> > > On Nov 24, 4:28 pm, mvniekerk <[EMAIL PROTECTED]> wrote: >> > > > If found this in logcat: >> > > > I/EventHub( 1622): New device: path=/dev/input/event0 name=mxckpd >> > > > id=0x10000 (of 0x1) index=1 fd=42 classes=0x1 >> > >> > > > I/EventHub( 1622): New keyboard: publicID=65536 device->id=65536 >> > > > devname='mxckpd propName='hw.keyboards.65536.devname' keylayout='/ >> > > > system/usr/keylayout/qwerty.kl' >> > >> > > > Yeah, that's about it. >> > >> > > > On Nov 24, 4:11 pm, "Joe Onorato" <[EMAIL PROTECTED]> wrote: >> > >> > > > > There is some logcat debugging info when the window manager starts >> up. >> > > Do >> > > > > you see any logs with the tag "EventHub?" >> > >> > > > > -joe >> > >> > > > > On Mon, Nov 24, 2008 at 9:03 AM, mvniekerk <[EMAIL PROTECTED]> >> > > wrote: >> > >> > > > > > On our custom iMX platform, when pressing the navigation keys >> (up, >> > > > > > down, left and right) it is registered by getevent, but the >> interface >> > > > > > does not respond. >> > >> > > > > > This is the output from getevent: >> > > > > > # getevent >> > >> > > > > > add device 1: /dev/input/event0 >> > >> > > > > > name: "mxckpd" >> > >> > > > > > /dev/input/event0: 0001 0069 00000001 >> > >> > > > > > /dev/input/event0: 0001 0069 00000000 >> > >> > > > > > /dev/input/event0: 0001 006a 00000001 >> > >> > > > > > /dev/input/event0: 0001 006a 00000000 >> > >> > > > > > /dev/input/event0: 0001 006c 00000001 >> > >> > > > > > /dev/input/event0: 0001 006c 00000000 >> > >> > > > > > /dev/input/event0: 0001 0067 00000001 >> > >> > > > > > /dev/input/event0: 0001 0067 00000000 >> > >> > > > > > Key 69 (105 in dec) is left >> > > > > > Key 6a (106 in dec) is right >> > > > > > Key 6c (108 in dec) is up >> > > > > > Key 67 (103 in dec) is down >> > >> > > > > > Now all this corresponds to the keylayout kl file. >> > >> > > > > > Any pointers as to what the problem is will be greatly >> appreciated. >> > >> > >> >> >> > > > -- > Dianne Hackborn > Android framework engineer > [EMAIL PROTECTED] > > 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. > > -- Dianne Hackborn Android framework engineer [EMAIL PROTECTED] 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. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "android-framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-framework?hl=en -~----------~----~----~----~------~----~------~--~---
