Many here have complained about the lack of a menu key on the One and many have defended HTC's curious omission stating HTC was doing what Google wanted.
Now comes word straight from Google that the as yet unannounced "Google One" will need either a dedicated menu button or a remapping.
Can we please end this debate now?
From the AC home page:
"The existence of a Google Edition HTC One raises several questions, however. The current two-buttoned HTC One relies on an unsightly on-screen bar for legacy menu key support, so how would this work on a vanilla Android variant? It's unlikely that menu key functionality could be re-mapped to, say, a long-press of the back key, as it's previously been confirmed that Google doesn't want HTC hiding the menu button. The most direct (but unlikely) solution would be a change to the hardware key layout, assuming Google and HTC want to avoid losing screen space to an on-screen menu bar."
Now comes word straight from Google that the as yet unannounced "Google One" will need either a dedicated menu button or a remapping.
Can we please end this debate now?
From the AC home page:
"The existence of a Google Edition HTC One raises several questions, however. The current two-buttoned HTC One relies on an unsightly on-screen bar for legacy menu key support, so how would this work on a vanilla Android variant? It's unlikely that menu key functionality could be re-mapped to, say, a long-press of the back key, as it's previously been confirmed that Google doesn't want HTC hiding the menu button. The most direct (but unlikely) solution would be a change to the hardware key layout, assuming Google and HTC want to avoid losing screen space to an on-screen menu bar."