Wow, thanks for tracking that down! And yes, I can confirm it's the same here too
I bet that destroys battery life as well. I've just put a fix in if you update the widget app now.
This actually exposed a few issues which I've now fixed:
Bangle.isBarometerOn was broken in cutting edge builds, which is what caused this in the first place
The widget needn't have been checking isBarometerOn though - so just removing the check fixed it
The widget also kept adding handlers for the barometer data, so every 15 minutes it'd just use more and more memory and get slower and slower - so I've fixed that now too
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.
Wow, thanks for tracking that down! And yes, I can confirm it's the same here too
I bet that destroys battery life as well. I've just put a fix in if you update the widget app now.
This actually exposed a few issues which I've now fixed:
Bangle.isBarometerOn
was broken in cutting edge builds, which is what caused this in the first place