[SOLVED] onKeyDown not always called in Android app

This Question and Answer are collected from stackoverflow and tested by JTuto community, is licensed under
CC BY-SA 2.5. - CC BY-SA 3.0. - CC BY-SA 4.0.


I’ve created a simple android game, based on the Lunar Lander sample, and I’m having a problem with handling key events. When the activity starts, the only keys that onKeyDown or onKeyUp get called for are the dpad up/down/left/right keys. Neither the menu, back, or dpad_center keys trigger onKey methods. However, once I’ve pushed one of the dpad up/down/left/right buttons, pressing the menu, back, or dpad_center keys do trigger these methods. I’m not getting any errors, or any indication of what’s going wrong.

It’s possible that the focus is set wrong – the activity is started from a button on screen, so it could be in touchscreen mode. If that’s the case, shouldn’t touching the back button get me in to the right focus mode so that I can catch the event?

I’m using the emulator from SDK-1.5r3. I have not been able to try this on a real phone yet. Here’s my onKeyDown.

public boolean onKeyDown(int keyCode, KeyEvent msg)
    Log.d(TAG, "onKeyDown: " + keyCode);
    return super.onKeyDown(keyCode, msg);




Is this onKeyDown in a view or in the activity?

If setContentView is called passing in a view, and that view has setFocusable(true) called on it, all key events will bypass the activity and go straight into the view.

On the other hand, if your onKeyDown is in the view, and you haven’t called setContentView on the Activity and setFocusable(true) on the view, then your Activity will get the key events and not the View.

Look for those specific calls but I think you’re right about it being a focus issue.

Answered By – haseman

people found this article helpful. What about you?