QWERTY USB keyboard - keystrokes problem

by Jerry Johns » Thu, 30 Apr 2009 08:28:19 GMT


Sponsored Links
 I managed to successfully port the android 2.6.23 kernel changes over
to a TI Davinci TMS320DM6446 EVM Board - its an arm926ejs core with a
DSP processor as well in the die.
The changes were patched over the davinci-git kernel (2.6.23 as well).

The board boots up fine over NFS - i get the red blob moving around,
and then the final UI comes up fine with no error messages on the
console.

I connected a QWERTY keyboard as a USB HID, and it worked absolutely
fine the first time i connected it to the board; on subsequent boots
however, a single keystroke started getting mis-interpreted as
multiple keystrokes - typing "H" would result in 3 Hs for example;
navigating the UI was really hard as it would skip over many of the
icons.
On further boots, this became even more problematic as it would
duplicate them 5 times.

A "getevent" showed that in addition to the event0 device being
registered, some other weird .nfs0020932092302 device in the /dev/
input/ folder was being registered as well. If i deleted that device
(an "ls" in the folder didn't show it), i would get
newer .nfsxxxxxxxxx keystrokes being logged.

Any ideas why this is happening? I'm using the ramdisk provided in the
m5-rc14 SDK version.

Thank you kindly,

Jerry
--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



Other Threads

1. adb install gives Failure [-12] when deploying an application to phone

the error code are defined in the android.content.pm.PackageManager class.
See here: 
http://android.git.kernel.org/?p=platform/frameworks/base.git;a=blob;f=core/java/android/content/pm/PackageManager.java;h=53a966d3db126eb6bce3b7878a4876db27ab4402;hb=eclair#l367

-12 seems to be INSTALL_FAILED_OLDER_SDK meaning that your app
requires a more recent build that your device is running.

This is confirmed by the info you provided, as your device runs
"Firware Version: 1.0", but you compiled your app for 1.1 and 1.5

1.0 is quite obsolete. I would flash something newer on the phone to
test your app. You can see the distribution of the different version
of android at 
http://developer.android.com/resources/dashboard/platform-versions.html

Regarding signed application, all applications must be signed to run
on Android. See more information at
http://developer.android.com/guide/publishing/app-signing.html

Xav




> 

2. After entry/selection is complete, how do I make the virtual qwerty keyboard go away?

Not sure about how changing focus will work w/the soft-keyboard, but
you can set the following as an OnKeyListener for your
AutoCompleteTextView to hide it whenever you want....

@Override public boolean onKey(View v, int keyCode, KeyEvent event) {

        // .. or whatever key you want to use to trigger this
        if(keyCode==KeyEvent.KEYCODE_ENTER) {

                final InputMethodManager mgr =
                        (InputMethodManager)<YourActivity>.this.getSystemService
(Context.INPUT_METHOD_SERVICE);

                mgr.hideSoftInputFromWindow(
                        <YourAutoCompleteTextView>.getWindowToken(),
                        InputMethodManager.HIDE_NOT_ALWAYS
                );

                // indicate that you've handled this event
                return true;
        }

        // allow default handling of this event
        return false;
}



-- 

3. "Force clearing orientation change". bug in G2?

4. How to display unicode text received from a web API

5. Cara pisahkan gmail

6. Service - Need Info

7. Need Suggestion on running Service