HTC Desire keyboard problem

by Michael Rueger » Sat, 17 Apr 2010 15:46:35 GMT


Sponsored Links
 Hi all,

a day away from deployment...
Our application which we had tested on a G1 with 1.6 and a Nexus with 
2.1 suddenly has unexpected problems on a HTC desire (German version) 
with 2.1.


It seems that the keyboard behaves differently:

- event.getAction() == KeyEvent.ACTION_UP
doesn't work/fire

- android:imeOptions="actionNext"
doesn't seem to be honored by the keyboard (it keeps the return button)

Unfortunately I don't have access to the phone (a user did some testing) 
so I can't debug.


Any ideas?

Michael

--



HTC Desire keyboard problem

by jamesc » Sun, 18 Apr 2010 21:43:52 GMT


 Hi Michael

It'll be the Sense UI's IME which has different behaviour to the stock
Android IME. Sadly, I'd suggest that you get your hands on a Sense UI-
equipped device (even a Hero, which whilst it has 1.5 on it, may help
you track that issues).

When you say that ACTION_UP doesn't work, is this for all key presses,
or just some in particular?  A bit more information on what you're
attempting to capture with ACTION_UP would be helpful in order to
allow to to get some useful debug prints out.



>


Sponsored Links


HTC Desire keyboard problem

by Michael Rueger » Mon, 19 Apr 2010 16:15:38 GMT


 

Hi Michael It'll be the Sense UI's IME which has different behaviour to the stock Android IME. Sadly, I'd suggest that you get your hands on a Sense UI-
Thanks for the hint, I found this issue for the problem: http://code.google.com/p/android/issues/detail?id=2882& ;q=htc%20ime&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars
equipped device (even a Hero, which whilst it has 1.5 on it, may help you track that issues).
I'm afraid so...
When you say that ACTION_UP doesn't work, is this for all key presses, or just some in particular? A bit more information on what you're attempting to capture with ACTION_UP would be helpful in order to allow to to get some useful debug prints out.
See code below, very simple one digit entry fields. (any tips for achieving that more elegantly appreciated :-) ). On the HTC the focus doesn't move to the next field on a key press (the user tells me), so I'm assuming somehow the key event doesn't make it. Michael digit2.setOnKeyListener(new View.OnKeyListener() { @Override public boolean onKey(View v, int keyCode, KeyEvent event) { if (event.getAction() == KeyEvent.ACTION_UP) { if (event.getKeyCode() == KeyEvent.KEYCODE_DEL) { digit1.requestFocus(); } else { digit3.requestFocus(); } } return false; } }); --



HTC Desire keyboard problem

by jamesc » Tue, 20 Apr 2010 04:52:32 GMT


 Perhaps your 'digit2' View doesn't have focus at the point where input
is being requested?






>



HTC Desire keyboard problem

by jamesc » Wed, 21 Apr 2010 13:31:29 GMT


 The solution is that you shouldn't use onKey() but implement an
InputConnection to handle key presses:





HTC Desire keyboard problem

by Michael Rueger » Wed, 21 Apr 2010 14:35:45 GMT


 

The solution is that you shouldn't use onKey() but implement an InputConnection to handle key presses:



Other Threads

1. Overwriting data in EditTexts

If you are talking about the gray text in the edittext that disappears
when the first letter is typed, in the xml properties for the edittext
there is a setting for Hint, just type in what you want it to say.




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

2. Translators needed for Czech, Dutch, and Polish

OpenIntents is looking for native speakers who would like to help to
translate our open source applications, like OI Notepad or OI Shopping
list ( www.openintents.org ).

We urgently look for translations in:
* Czech
* Dutch
* Polish
but translations into other languages are also welcome!

If you happen to be a native speaker of one of these languages, or
have a friend living in one of these countries, who might be
interested in helping us to translate our applications, please let us
know!

Answer to the following thread,

3. Google please give us 'su -' was:Am I root?

4. Background resource doesnt scroll when viewgroup is scrolled

5. Changing General UI

6. Unable to set permissions on sdcard correctly

7. applications that require money