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. On Apr 17, 8:46 am, Michael Rueger <[email protected]> wrote: > 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 > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group > athttp://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
