Detect long-press of Back on 735XT?

I know that we're not supposed to try to detect any long-presses at all, but I was wondering if anyone had any success detecting long-press of Back on 735XT, in an app or widget.

I know it works on 935 and in the simulator for every watch that has a back button. I also know it won't work on a real VAHR, since long-press of Back already does something. But based on reading some older threads, I thought it should work on 230/235/630/735XT.

Anyway, I had a 735XT user report that it doesn't work for my app, so I'm wondering if anyone else has had the same experience.

Also, has anyone had any luck detecting long-press of back on the original Vivoactive?

Thanks!

EDIT: Hmm, I'm revisiting and I see this from 2016:

The onKeyPressed/onKeyReleased functions do not get called at all on the following devices.

fr920xt
fr735xt
fr630
edge_1000

I found that the vivoactive does correctly call onKeyPressed/onKeyReleased for the physical enter button as well as the virtual back and and menu buttons. It does not work at all for the light/power button.

I could've sworn that a later thread claimed long press work for the 230/235/630/735, though.

peterdedecker over 6 years ago

Onkeydown/up detection doesnt work on the 735xt, there's a few bug reports floating around about that. As this fix likely requires a change at the side of the device i think it's unlikely that this will be fixed.

FlowState over 6 years ago

peterdedecker thanks. Do you know if the same applies to FR920XT and FR630? And how about FR230 and FR 235.

Appreciate it!

(This is where I have to go update my device-specific input handling and onscreen prompts >_>)

FlowState over 6 years ago

Also, I sort of wish there was a comprehensive known issues/wontfix database that devs could access. I have to question why onKeyPressed and onKeyReleased are even in the documentation (without notes), when they apparently don't work for most of the older devices.

Again I also have to question why the only way to discover certain device-specific things is to:
- ask someone
- search the forums and read possibly outdated info
- release a broken app

ekutter-dnu over 6 years ago

Seems really unlikely that the 630,230, 235, or 920 would get a fix for something like this. But I do use long presses and do remember on the 630 running into those issues a couple years ago. Hopefully all devices moving forward will handle this. At least now there are apps in the wild that rely on this so the issues would hopefully come up before release, or at least during the period where there is still active development on new devices.

FlowState over 6 years ago

ekutter agreed. Thanks for the response!

It's frustrating that we can only build the "ultimate" app of our dreams in newer devices, but it's in Garmin's interest (and in some ways, ours) not to fix older devices....

Oh well, this really only affects 230, 235, 735 and 920 for me....

As usual I should've listened to Travis and Jim.