Hello,

I have a beagleboard rev c3 with 6 gpio buttons.  The kernel is
recognizing the buttons
but I can't seem to figure out how to get Android to recognize and
associate the
buttons with the KEY_MENU and KEY_BACK events (the other 4 are not
being used at this time).

According to http://www.kandroid.org/android_pdk/keymaps_keyboard_input.html,
I need to create a
keylayout map and a keychars map file which I have a gpio-keys.kl and
gpio-keys.kcm (although a
*.kcm.bin is created).  My problem seems to be that the qwerty.kl is
the default regardless to my
changes and I'm unsure how to go about changing...any guidance would
be great. Thanks.

log file results
I/EventHub(  788): New keyboard: publicID=65539 device->id=65539
devname='gpio-keys'
propName='hw.keyboards.65539.devname' keylayout='/system/usr/keylayout/
qwerty.kl'

results of my build in the current directory...
...
for a hardware target is generic. The result of my of my build is:
target Prebuilt:  (out/target/product/generic/system/usr/keylayout/
tuttle2.kl)
target Prebuilt:  (out/target/product/generic/system/usr/keylayout/
gpio-keys.kl)
Target buildinfo: out/target/product/generic/root/default.prop
Target buildinfo: out/target/product/generic/system/build.prop
Copy: out/target/product/generic/system/etc/apns-conf.xml
KeyCharMap: out/target/product/generic/obj/KEYCHARS/gpio-
keys.kcm_intermediates/gpio-keys.kcm.bin
Install: out/target/product/generic/system/usr/keychars/gpio-
keys.kcm.bin
KeyCharMap: out/target/product/generic/obj/KEYCHARS/
tuttle2.kcm_intermediates/tuttle2.kcm.bin
Install: out/target/product/generic/system/usr/keychars/
tuttle2.kcm.bin
Generated: (out/target/product/generic/android-info.txt)

my system.prop file is:

rild.libpath=/system/lib/libreference-ril.so
rild.libargs=-d /dev/ttyS0

android.keylayout.gpio-keys = /system/usr/keylayout/gpio-keys.kl
android.keychar.gpio-keys = /system/usr/keychars/gpio-keys.kcm

-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

Reply via email to