This can happen if there's a ctrl-c character sent to the watch, which should only happen when Gadgetbridge connects to the watch (it uses the character to clear the input line) and not afterwards. Do you think that's the case, or does it happen during connection as well?
Ctrl-C doesn't itself break out of the interval if it finished executing reasonably quickly, but if it takes more than ~1/2 a second then it will break execution - so it could be the clock face takes longer than that to draw?
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
This can happen if there's a ctrl-c character sent to the watch, which should only happen when Gadgetbridge connects to the watch (it uses the character to clear the input line) and not afterwards. Do you think that's the case, or does it happen during connection as well?
Ctrl-C doesn't itself break out of the interval if it finished executing reasonably quickly, but if it takes more than ~1/2 a second then it will break execution - so it could be the clock face takes longer than that to draw?