On Thu, May 26, 2011 at 7:56 AM, David Turner di...@android.com wrote:
The no keyboard for id 0 message probably means that your event kernel
driver is reporting a name that doesn't have a corresponding .kcm / .kl file
combination, i.e. you're likely missing some configuration files, or your
This is not related to the NDK, you should try android-porting instead.
Briefly speaking, getevent() returns the events sent from the kernel to the
framework. Since everything seems good here, you can forget about a
driver/hardware failure.
It looks like the framework input handling code is
