You are reading a single comment by @user141359 and its replies.
Click here to read the full conversation.
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.
@user141359
I am on the release build, not the cutting edge build.
On the 7th of October I updated the watch to the release 2v15 build, and I also updated all installed apps to their latest release version. Before that I didn't have a problem (I think before that I was on 2.13, build but I can't remember for sure).
There is a chance that the corruption is not actually caused by the 2V15 build but by an AnDark update. I suspect it's the watch OS but I can't fully rule out other factors since I updated them at the same time.
I actually don't know how it happens, I just look at the watchface randomly to read the time and about every second day I notice it is corrupted. At first I thought it was probably because I had enabled debug output during the update process because I had a bit of a problem connecting to the watch via Blueooth at first and I thought the debug output would give me an indication why I couldn't connect to the watch. Later I realize I could connect without problems if I disabled Gadgetbridge first. Then I forgot to turn off Debug output again. But a week ago I disabled debug output and rebooted and the display corruptions keept happening even with debug output set to Hide. That's when I realized I should probably make a bug report.
Every time I enter settings and go back to the watch screen I believe that causes the watchface to redraw, and so I think that fixed it every time so far.
I am sorry I can not give more details. I haven't tested with another watchface so far.
I attached more photos. Those photos were made before I had switched off debug output, the photo in the original post was made after I had switched off debug output.
Appreciate the extensive response to find the underlying fault!
1 Attachment