Menu button handling on Q5

Just a general inquiry at this stage.
Is there anything logged about the Q5 menu handling (that I have missed)?
The latest release of my app is responding incorrectly to the menu button : it brings up the watch's System menu, not my app's menu.
I don't have a device to test on but have a cooperating user, but the testing turnaround is a bit slow.

It works as expected in the simulator.

It was working OK in my previous release, and I have made quite a lot of changes, so it's probably my code, but I'm wondering what to look for that could cause the System Menu to be invoked from within my app?

jim_m_58 over 8 years ago

See https://forums.garmin.com/forum/developers/connect-iq/1241457-avoiding-the-menu-when-holding-menu-button

The Q5 and F5 are basically the same, and it sounds like the extra step is still in the Q% firmware.

Alan.raceQs over 8 years ago

Thanks, Jim,
3 questions:

What is "the extra step"? The linked threads were multi-page and I lost focus when ploughing through them.
Why did my previous release not raise the System Menu?
Is it a bug (maybe gets fixed) or do I have to code around it? (if so, how?)

jim_m_58 over 8 years ago

Ok, here's a summary. The "Extra Step" came about a while back. When running a CIQ app on the the device, long press of "Up" brought up a System menu, but the first item on it was the CIQ app, and you had to select it to get to "onMenu" in your app. The "Extra step" is gone on the f5/f5s/f5x/935, but it seems it's still on the Q5. Look at AlphaMonkeyC's posts in that thread (he's the "Big Banana" of CIQ - Sorry AM - I couldn't resist!)

Sounds like the first FW used was before the "extra step", the one now still has the "extra step", and you just need to wait for FW where the "extra step" was removed. Nothing to change in your code.

But do check you are doing a proper return with the proper value from onMenu(), as a few folks have run into that bit.

Alan.raceQs over 8 years ago

Hmmm, my user is reporting a menu with two options: "History or Settings" that doesn't appear consistent with what you're describing. I'll press for more test details

jim_m_58 over 8 years ago

I bet the user thinks the first selection is the title of the menu or something. Ask for a picture.

Alan.raceQs over 8 years ago

This is a screenshot of what he's getting. I don't think he's confused? I don't see a "first selection".
My user is reporting that sometimes he's getting the app menu, and sometimes this System menu.

Looking more and more like a bug to me.
community.garmin.com/.../1260443.jpg

jim_m_58 over 8 years ago

That's odd for sure. I think you'll want to submit a bug report.

Brandon.ConnectIQ over 8 years ago

This is a known bug that I believe had already been fixed on F5 but either hasn't made it to a release or wasn't included on the Q5 (though it should have been). I'll make sure it gets attention.

UPDATE: the fix has been made, but it's not in a public release yet. I'd expect it in the next public firmware release.

Alan.raceQs over 8 years ago

This is a known bug that I believe had already been fixed on F5 but either hasn't made it to a release or wasn't included on the Q5 (though it should have been). I'll make sure it gets attention.

Can you please confirm if it affects the F5?

UPDATE: the fix has been made, but it's not in a public release yet. I'd expect it in the next public firmware release.

Please, Brandon, the fix has NOT "been made" till it's released. And as ever, there's no schedule.

So it seems my app may run on the F5 but not the Q5 and so I should I remove the Q5 from supported platforms. But how? I believe the "fenix5" is the iq:product code for both Q5 and F5 . (love that : p with no space appears as a smiley in the Forum!)

Alan.raceQs over 8 years ago

I am receiving similar menu button misbehavior from F 935 users. Is it possible that the F5 fix missed that platform too?