Hi Claw,

Check for "What is WAKE_DROPED in qwerty.kl?" subject mail on Feb26th. It
might be helpful for you.

Regards,
MS

On Wed, Apr 1, 2009 at 1:46 PM, Claw <[email protected]>wrote:

>
> Hello All,
>
> I have read this forum for the keyboard porting requirements followed
> all of them but with no success.
>
> I have done the following:
> 1. I tried using the http://beagleboard.googlecode.com/files/evtest.c
> when the android is running. It returns proper values of the events
> being generated.
> 2. I have checked the qwerty.kl in /system/usr/keylayout which is
> proper for my keypad.
> 3. I have all the permissions provided for /system/usr/keychars set. I
> have not changed any *kcm.bin files either.
> 4. I have made sure that the pxafb.c file which is the frame buffer
> file for me is updated according to Reed. Infact, I have pulled his
> file into my build environment.
> 5. I have checked that the display resolutions shown by pxafb are what
> my device screen supports which is 240X320. The virtual values of xres
> and yres are also 240 and 640 as needed for double buffering.
> 5. Even getevent reports proper scan codes like this:
> Enter key pressed and released:
> /dev/input/event0: 0001 001c 00000001
> /dev/input/event0: 0000 0000 00000000
> /dev/input/event0: 0001 001c 00000000
> /dev/input/event0: 0000 0000 00000000
>
> arrow keys pressed and released:
> /dev/input/event0: 0001 0069 00000001
> /dev/input/event0: 0000 0000 00000000
> /dev/input/event0: 0001 0069 00000000
> /dev/input/event0: 0000 0000 00000000
> /dev/input/event0: 0001 0067 00000001
> /dev/input/event0: 0000 0000 00000000
> /dev/input/event0: 0001 0067 00000000
> /dev/input/event0: 0000 0000 00000000
> /dev/input/event0: 0001 006c 00000001
> /dev/input/event0: 0000 0000 00000000
> /dev/input/event0: 0001 006c 00000000
> /dev/input/event0: 0000 0000 00000000
> /dev/input/event0: 0001 006a 00000001
> /dev/input/event0: 0000 0000 00000000
> /dev/input/event0: 0001 006a 00000000
> /dev/input/event0: 0000 0000 00000000
>
> But still I find that nothing other than Enter key and other QWERTY
> keys work. I am not able to use the navigation keys at all. I have
> even configured the MENU and BACK key which show up properly in
> getevent and evtest.c as well but not on the Android GUI. I am using
> android with 2.6.25 version of kernel.
> The keypad works perfectly well in the linux environment but not when
> it enters into the android space.
>
> Any help would be great, I am stuck at this stage for days now.
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---

Reply via email to