From what I gather, you have context-sensitive actions you want tied to an EditText
, and HTC's changes to Android are interfering with that.
First, I would reconsider using context menus in general, as they are not particularly discoverable, so most of your users will never find them.
Second, in the case of the EditText
, the odds of users discovering that a double-tap will bring up a context menu will be on par with the odds that the Earth will have an extinction-level asteroid strike today.
:: looks up in sky ::
Rather than a double-tap, one option would be to put a small ImageButton
adjacent to the EditText
, with a downward-facing arrowhead (akin to a Spinner
), and tie that ImageButton
to a PopupMenu
(ideal, but only API Level 11), a PopupWindow
, or an AlertDialog
. Or, in a pinch, have the ImageButton
display a context menu when clicked via showContextMenu()
. This too is non-standard UX, but it is at least more discoverable, as users will be used to things popping up when pressing down-arrow buttons, from both Android and other OSes.
If you are absolutely convinced that you need a double-tap, AFAIK that is not a recognized touch event, so you will need to handle the low-level touch events yourself, determine when a double-tap occurs, and do so in a way that does not interfere with the usage of the EditText
(e.g., setting cursor position).