Select button on Edge 520 Plus not being recognized

Is anyone with Edge 520 Plus users getting reports of issues with the Select button (the top-right one) not triggering the action that it should?

I'm troubleshooting this in our routeCourse app, where it is definitely not working the way it is supposed to on the physical Edge 520 Plus. We are not getting an onKey, onKeyPressed or onKeyReleased event for it. All is well in the simulator (and on every other physical device).

I've asked a related question over in the Edge 520 Plus forum, since one user mentioned that he had seen it not work in one of the built-in apps too.

Thanks.

jim_m_58 over 6 years ago

In the sim for both the 520 and 520+, the upper right button is KEY_ENTER, and the right one on the bottom is KEY_START. And a long press of the upper right is KEY_MENU. In onKey() are you seeing something but not what you expect, or is onKey() not called at all?

If it's seen with a native app too, that sounds like a FW bug - what FW are people seeing this on? By "built-in app", does the 520+ come with any pre-loaded CIQ apps? You may what to see what "native app" the user saw this in, as I seem to recall that something is pre-loaded on the 520+.

mappicus over 6 years ago

The native app mentioned was within routing during an activity -- the user was unable to answer a question about rerouting since the Select button was unresponsive.

Coleman.Apps over 6 years ago

Okay. I've been testing this today. It appears that it's not working for your app, but it is working on hardware using our Input sample in the SDK so I don't think it's a low level integration issue on the device. However, it is isolated to this device from what I can tell. Can you give us any more information about how your delegate is set up? Maybe there is something unique about the way that behavior is getting triggered that is unique to the 520 Plus? It appears that the integration is the same so I'm not sure why it's doing this.

mappicus over 6 years ago

Sorry for the delay in reply, but I've gathering logs from Edge 520 Plus device owners. I have the skeleton of the code to share, although this forum site is not letting me include or upload, will try again...

mappicus over 6 years ago

// This is the main delegate set in getInitialView()
// and the main view contains a set of Selectables.

class dwInputDelegate extends Ui.BehaviorDelegate {
    function onKey(key) {
        // When Select is pressed, on the simulator Edge 520 Plus this is called with KEY_ENTER.
        // However on the real hardware Edge 520 Plus, this is NOT called.
    }

    function onSelectable(event) {
        // When Select is pressed, this gets called with :stateSelected, on both hardware and simulator
        // HOWEVER this only gets called once, even if one pressed the Select button twice, unless one
        // moves off and back onto the selectable.  This does not work well when the button is a "page down"
        // that you want to press several times in a row.
    }
}

class dwRoutesDelegate extends dwInputDelegate {
    function onSelect() {
        // This never seems to be called on either simulator or hardware.
    }
}

mappicus over 6 years ago

There we go. In summary:
- using onSelectable() with :stateSelected nearly works, but one has to move off the selectable button and back onto it if one wants to press it more than once. Is there perhaps a workaround for that?
- using onKey() in the past has been most reliable across devices, so is there some reason why this might not be working and giving an KEY_ENTER on the Edge 520 Plus hardware?

Thanks!

Coleman.Apps over 6 years ago

Perfect. That's what I needed to crack it. It's definitely a firmware bug on the 520 Plus. I'm reporting it to the device team right now. Thanks as always!

- Coleman

mappicus over 6 years ago

Perfect. That's what I needed to crack it. It's definitely a firmware bug on the 520 Plus. I'm reporting it to the device team right now. Thanks as always!

- Coleman

Ok cool thanks, glad I was able to supply actionable info, and thanks for moving on to the device team. I'll ask the Edge 520 Plus users that I've been working with to be on the lookout for a future firmware update.