Hi, Try checking your logcat log, in case loading the expected keylayout fails and we fallback to the generic layout there should be a print that shows the error and the expected name.
Also, To easily get the input device name, you can try "getevent -c 1" to get a listing of the available devices. On May 31, 3:11 pm, nirmaalu <nirm...@gmail.com> wrote: > Hi, > > We were using a product specific KeyLayout(.kl) and > KeyCharacterMap(.kcm) files for the Android 2.3 based product. Input > Keys are captured from IR and written to the /dev/uinput device. > When we ported to the Android Honey Comb(3.1) we are facing issues > with the kl and kcm files. Android is always using Generic.kl and > Generic.kcm files. Can any one help to change this default kl and kcm > file and load our product specific key map files? > > Warm Regards, > Nirmal -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
