in an application and with some watches, WatchUi.KEY_CLOCK doesn't work correctly

I have an old application: APP4TRAIL when the application runs, when I press KEY_CLOCK, the application opens a new screen.

Work correctly on my F6X and    in the simulator too

A user tells me with his F5 PLUS, when he presses  KEY_CLOCK,  he displays Audio reader  screen , not the screen of my application

Return is set to true.

When I check on simulator for F5 PLUS, all is good and my new screen appears.

He receives a new EPIX2 , and same issue, he displays audio reader. His watch is just unboxed and only my application.

Why this event key isn't tracked by the watch.

  • What is the sequence you use for KEY_CLOCK?  For example, long press of down is often the music player on devices, or something else can be assigned to long press down on devices with hot keys.  These are things you won't see in the sim, and no way to simulate or override it.

    The f5+ and epix2 both have on device music, while the f6x doesn't, which would explain what you are seeing.

  • In my F6X in hot key I set Watch face.  And on F6X music is avalable too.  In this case why I don't display my watch face when I press KEY_CLOCK.

    I think with an application all keys was available for the application, but some other internal applications are prioritarry of the third application. 

  • In the API documentation, it is indicated that in an application, we had all the functions of the watch available.
    The KEY_CLOCK key is one of the 24 keys available
    If this key cannot be called when an application is running, why put this key in the documentation.

    And why on my F6X it works and display my function and not for an F5 plus nor an EPIX gen 2 it displays MUsic screen

  • The KEY_CLOCK is not always tied to a specific physical button. On devices like the Epix2 and fenix it is a hot key. Before music watches, the KEY_CLOCK used to default to a long press of the down button (Hold DOWN), but it seems Garmin wanted to standardise that to bring up the music player for all music devices so they bound "Music Controls" to Hold DOWN by default.

    So, you need to find what the user has configured for the action "Watch Face" in their hot key configuration. If this is not assigned then KEY_CLOCK will not be available to them.

    Personally, I stick with "Music Controls" for Hold DOWN since I want consistency with other Garmin watches I own which do not have hot keys where cannot be changed. But, I like the ability to be able to return to the watch face from within activities etc, so I define a "Watch Face" hot key as Hold BACK instead.

    Therefore, for me, when I long press the back button, I get KEY_CLOCK in my apps.

    Short summary, for a new Epix2 out of the box, "Music Controls" will be the default for Hold DOWN. The user can change this to "Watch Face" if they want KEY_CLOCK from this button, or can assign "Watch Face" to some other hot key and then KEY_CLOCK will be generated from that one instead.