It's not a problem with Beebclock, Morphing shows the same problem. And after one start of the launcher Beebclock works also for some time. It looks some parameters get lost/corrupt in RAM and a start with IDE and bluetooth reintializes something - just an idea, but how to debug?
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.
It's not a problem with Beebclock, Morphing shows the same problem. And after one start of the launcher Beebclock works also for some time. It looks some parameters get lost/corrupt in RAM and a start with IDE and bluetooth reintializes something - just an idea, but how to debug?