Why do custom watch faces ALL cause serious lag on button presses

Marc over 2 years ago

Default watch faces - no lag

any custom face- 1+ second lag when pressing activity start button or the menu buttons

Top Replies

brian.reiter over 2 years ago +2

I think it has to do with the overhead of ejecting the MonkeyC VM used by ConnectIQ from memory. The native watch faces seem to be fully compiled and linked into the OS while custom faces are running in…
5963464 over 2 years ago in reply to Dr Phil +1

therealminzii already answered you to this.

every watchface has the same issue even the litest and simplest.

if the problem is for every face, it leads to think its not a face problem.

every watchface…

All Replies

0 5963464 over 2 years ago in reply to Dr Phil

therealminzii already answered you to this.

every watchface has the same issue even the litest and simplest.

if the problem is for every face, it leads to think its not a face problem.

every watchface developper would already noticed the problem when testing their own watchface, so if it was possible they already fix it. no one of them has done it.

in your opinion, why?

0 Dr Phil over 2 years ago in reply to 5963464

Ask them why. They’re the ones developing the watch face. They’re the ones who’ll be able to explain where the problem is.

5963464 said:
every watchface developper would already noticed the problem when testing their own watchface

Assuming that is developers don't simply port their watch face from one watch to another without testing. How robust is their testing? Do they test on every watch type the face is supposed to work on?

5963464 said:
every watchface has the same issue even the litest and simplest

And you know this how? Has anyone tested every single watch face that purports to work with the Enduro? Is this another assumption? Another extrapolation from the few that have been tried?

Why is it so difficult to ask the developer? Just because something is assumed to be one thing does not mean it can’t be something else.