Thanks - yes, it's actually due to a change in the settings/bootloader that re-enabled the error logging to the LCD (because previously some apps were silently making errors and nobody knew).
It's this issue here: https://github.com/espruino/BangleApps/issues/102
I'd be interested to know what you think would be a good solution (there are some options on that issue)
Thanks for the update @Gordon. Can we have a "Debug To" settings in the settings app, can we use it to toggle the logging on to Console/LCD/None?
I see uses for log being written to the LCD when I am coding, for example currently my watch is looping "Unable to open file" and previously it was showing "File too big" [Different issue again, I'll report it separately] :-).
The UI of the watch face seems to get corrupted ever so often after I installed this version.
I am using a modified
Looks like everytime I connect to console or disconnect from console it logs something to the screen pushing the buffer up. This results in the next paint (on
lcdPower) picking up the wrong corrupted buffer and keeps repainting it until the next corruption happens. As seen in the next image, the time is actually
Initially I thought I wasn't repainting the widgets on
lcdpowerevent hence it looked corrupted. Now after repainting the widget area, the widgets show up correctly but as you can see there is a bit of corruption above the widget as well.
My code is here
It is based off the beta version of
mclockwith some modifications. I've updated how the widgets are loaded and painted as per latest version of
Reloading the app by long-pressing button 3 temporarily resolves this. (I have also lost Button 2 click so can't get to settings, but that's a different issue I believe, still digging into that).