Hi Ravi, Thanks for your help. After changing permissions of system/usr/keychars/qwerty.kcm.bin Every thing worked fine and now I can map any keyboard key.
Also after changing permissions of /dev/input/event1, I can use USB optical mouse also. Regards, Shivdas Gujare On Mon, Dec 1, 2008 at 5:46 PM, R K <[EMAIL PROTECTED]> wrote: > Hi Shivdas, > > http://beagleboard.googlecode.com/files/evtest.c run following test case, > will help you to see the keyboard events. > > Regards, > Ravi > > > On Sun, Nov 30, 2008 at 8:06 PM, Shivdas Gujare <[EMAIL PROTECTED]> > wrote: >> >> Hi All, >> >> I am porting android on omap3 platform. I can boot android on it, >> and able to see GUI. I connected "Qwerty USB Keyboard(Dell Keyboard)" >> to my board. >> >> From kernel configuration, I selected "Event interface" under "Device >> Drivers -> Input device support -> Generic input layer" and associated >> USB support >> and I can see events generated on /dev/input/event0. >> >> I compared events generated by my Dell Keyboard on target and emulator >> keyboard using "getevent". and looks like it all are similar. >> I verified file "/system/usr/keylayout/qwerty.kl" for both emulator >> and my target. and are both same. >> >> Now my target detects only events from "ENTER", and android GUI works >> properly. But not a single key other than "ENTER" gets detected >> by Android. >> >> Do I am missing any further verification/modification? >> Do I needs to do anything else setup to make keyboard working? >> How can I correlate scan keycodes genetared by my Dell keyboard and >> expected by android. >> >> Thanks for any help. >> >> Thanks and Regards, >> Shivdas Gujare >> >> > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [EMAIL PROTECTED] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
