[ekidd]

Whilst using my Nexus S, it rings. I pull it out of my pocket, only to discover I can't answer it because there's a keyboard over the Answer/Decline buttons.

Huh? I'm running Android Gingerbread on a Nexus One, and when the phone rings, I see the usual "unlock" screen, with one option for answering, and one for ignoring the call. There's no way to get a keyboard, no matter which buttons I press.

Is your phone fully awake and unlocked in your pocket? Is there something weird about Gingerbread (or the buttons) on the Nexus S?

[nuclear_eclipse]

On any version of Android, dating back to the introduction of the virtual keyboard in version 1.6, long-pressing on the menu button will pop up the keyboard, which allows you to, for instance, bring up the keyboard in applications without needing a specific textbox to select. This allows you to have applications like ConnectBot, where the entire screen is a terminal emulator, and you can pop up the keyboard at any point and start typing without having to type into a textbox and then "send" the text to the terminal. On the home screen, you can bring up the keyboard and just start typing a search query without needing to press (or even have) the search button or widget.

And for the record, when the virtual keyboard is shown, pressing the back button will always dismiss it without sending the back action to the current activity, so in your case you could have pressed back to dismiss the keyboard, and then pressed the button to receive the call.

[refulgentis]

Exactly, completely understand where this is coming from - but why in the world is this a default!?

[pkulak]

This has happened to me. I'm a geek, so I knew that hitting the back button would get rid of it, but come on. Anyone else in the world would have missed the call while starting at their phone and listening to it ring.

[refulgentis]

Couldn't tell ya. :/ I'll have to test it and get back to you.