1088145 - Can't access menu on tablet with hardware menu button Android

Status: RESOLVED INVALID

(Firefox for Android Graveyard :: General, defect)

Description

[piotr.halasiewicz]

Attachment: The Firefox Window when I press hardware menu button.

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:33.0) Gecko/20100101 Firefox/33.0
Build ID: 20141013200257

Steps to reproduce:

I installed newest version of Firefox for Android on my Galaxy Tab Pro 8.4 wifi tablet (mondrianwifi) with Cyanogenmod 11M11 (Android 4.4.4). Immediately after first installation I pressed tablet hardware menu button, but no menu is shown. 


Actual results:

Button lights up, but no menu is shown. The three dots menu icon is not visible either. The menu button works with other apps.


Expected results:

The menu button should bring up the menu with, among others, tools and settings.

Comment 1

[piotr.halasiewicz]

This is this tablet: http://wiki.cyanogenmod.org/w/Mondrianwifi_Info

Comment 2

[Aaron Train [:aaronmt]]

Can you run
  
  $ adb shell input keyevent KEYCODE_MENU

Does the menu show up if you run the above on command line (if you are familiar with ADB)? 

Jim, is there any keyevent or related logging the reporter can use?

Comment 3

[piotr.halasiewicz]

Thank you, Aaron, for taking look at it.

No, there is no reaction for this adb command - menu does not show. 

Just to make sure I run it with other application and there were reactions characteristic for tapping menu button.

Comment 4

[(inactive) Jim Chen [:jchen] [:darchons]]

Can you install the Play Store app "KeyEvent / Keyboard Debugger"? When you are in the app, can you press the Menu button, and post the output from the app? Thanks!

For reference, when I press the Menu button on my Galaxy Note 2, I see,

> *** Key Event Detected ***
> Key Code: 82
> Action: 0
> Meta State: 0
> Flags: 8
> Source: 257
> Keyboard Type: 1
> Device ID: 6

Comment 5

[piotr.halasiewicz]

Date: Sat Oct 25 00:48:59 CEST 2014
Device Manufacturer: samsung
Device Model: SM-T320
Device Board: MSM8974
Device Bootloader: T320XXU1ANAI
Android Version: REL 4.4.4 (sdk:19)

*** Key Event Detected ***
Key Code: 82
Action: 0
Meta State: 0
Flags: 8
Source: 257
Keyboard Type: 2
Device ID: -1

*** Key Event Detected ***
Key Code: 82
Action: 1
Meta State: 0
Flags: 8
Source: 257
Keyboard Type: 2
Device ID: -1

Comment 6

[piotr.halasiewicz]

And,Jim, for reference, this is the output from Keyevent app when tapping hardware menu button on my Galaxy S2 Plus device (where everything works fine and firefox menu shows up when the hardware menu button is tapped). As you see, it is the same:

Date: Sat Oct 25 02:29:42 CEST 2014
Device Manufacturer: samsung
Device Model: GT-I9105P
Device Board: capri
Device Bootloader: unknown
Android Version: REL 4.4.4 (sdk:19)

*** Key Event Detected ***
Key Code: 82
Action: 0
Meta State: 0
Flags: 8
Source: 257
Keyboard Type: 2
Device ID: -1

*** Key Event Detected ***
Key Code: 82
Action: 1
Meta State: 0
Flags: 8
Source: 257
Keyboard Type: 2
Device ID: -1

Comment 8

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

According to bug 1097970 comment 1, this worked in some version before 33.1.

Comment 9

[piotr.halasiewicz]

Well, I did try to install 30.0  and 32.03 - the problem existed with both of them, just as with the newest version.
I downloaded apks from here: http://firefox.en.uptodown.com/android

When I downloaded 33.0 apk, somehow it didn't start at all.

Comment 10

[Kevin Brosnan [Ex-Mozilla]]

Official builds are available directly from Mozilla. No need to go through a 3rd party site, http://ftp.mozilla.org/pub/mozilla.org/mobile/releases/

Comment 11

[piotr.halasiewicz]

Thanks - that's what I thought, but somehow couldn't find this source. I will use it in the future.

Comment 12

[Hong Xu]

I am the bug reporter who reported it works before version 33.1.

I now see why it happened -- I just switched over to the same ROM as the bug reporter here AND upgraded my firefox at the same time. Which means, Firefox works on the stock rom correctly, but not on this particular rom.

I tested more other apps, and some of them just does not work for menu button, some does. I guess this is either the bug of the rom, or a common change in Android that most apps have not been able to follow, including firefox.

Comment 13

[piotr.halasiewicz]

Can you mention some of the other apps that don't work with menu button on cyanogenmod?

Comment 14

[Hong Xu]

for example Yelp, GitHub, VLC

Comment 15

[Hong Xu]

You can follow the discussion I opened on Cyanogenmod forums to see additional info http://forum.cyanogenmod.org/topic/102028-menu-button-not-working-in-most-apps/

Comment 16

[Aaron Train [:aaronmt]]

I don't think we could or should go around chasing around every ROM's changes. Unless there's a workaround I suggest WONTFIX on this.

Comment 17

[Richard Newman [:rnewman]]

Concur.

Hong Xu, Piotr: if you get a response from Cyanogen along the lines of "simple, just handle this event instead", then we can reopen this bug and see about a workaround.

Most likely this is a pure Cyanogen bug, and they'll need to fix it to maintain compatibility with the rest of Android.

My wild speculation, based on nothing more than a hunch, is that they're sending two menu keypress events, so we're immediately hiding the menu again.

Resolving this as INVALID, which is Bugzilla-speak for "this is not a Firefox bug".