fenix series BehaviorDelegate oddities

Never heard about button related problems on 5 button devices. How is the relevant code?

Really nothing exceptional, and confirmed it works in the relevant simulators... and I would share the code if the forum wouldn't consider it abusive 

pastebin.com slash WBR2zrjM

In your delegates for things like onKey, onMenu, onSelect, do you always return true of false? I imagine for all keys you handle in your app you want to return true.

I confirmed that all code paths return a boolean, and returns true if I need to capture the input (not that it seems to do much good for system hotkeys).

You're not trying to catch your own long presses, are you? Mentioning hotkeys makes me ask.  You don't want to do that. 

In one case I need to do something while the user is holding a button. The other case is totally vanilla though (with BehaviorDelegate overrides instead of lower-level InputDelegate). And in both cases, other devices seem fine with the setup.

Trying to detect the long press can be very problematic, especially on devices with hot keys.  I would look at doing things a different way

I'm not trying to detect long-press as such. In one case I'm maintaining state awareness of buttons being down, and in the other case it's just regular button presses. But yeah, fenix devices appear to be behaving oddly.

onKeyPressed and onKeyReleased have been known to be flaky on some devices for years.  Just search this forum.

One of the reasons I never use them and just have always just stuck with the basics.

Hotkeys may or may not be involved.