Just an unrelated hint: If you only want the "OK" button to dispose of the dialog, you don't need that no-op DialogInterface.OnClickListener -- just write alertDialog.setButton("OK", null). AlertDialog automatically disposes dialogs after button pushes.
–
Philipp ReichartSep 2 '11 at 21:47

I figured it out.. My target Sdk was: android:targetSdkVersion="11" Changed to:android:targetSdkVersion="10" Menu button doesn't work on 11 and up. My app is a webapp and I don't think the ActionBar will work in a webapp. Someone correct me if I'm wrong.
–
user899641Sep 2 '11 at 22:14

@user899641: "Menu button doesn't work on 11 and up." -- sure it does. It is in the action bar, not the system bar. "My app is a webapp and I don't think the ActionBar will work in a webapp" -- if you are writing Java code, you can have an action bar.
–
CommonsWareSep 2 '11 at 23:34

2 Answers
2

The menu key shown on the system bar in Android 3.0+ is a compatibility feature for running older apps. Setting targetSdkVersion="10" means you are not developing an app that targets Android 3.0+ and the system will adjust compatibility behavior for your app accordingly.

If you are truly writing an app to run on Android 3.0+ tablets you will not have a menu key on the system bar. Forget about it. Put it out of your mind. :) Abusing compatibility features in this way explicitly breaks Android UI design guidelines. The action bar will present your activity's options menu if present. If you do not have an action bar in your activity you should present options using some other on-screen affordance.