When I connected to the apps page, it reported that the firmware was 2v11 when I have been running 2v16 since it came out
Are you 100% sure? Maybe you could screenshot and show me where you say 2v11 being reported? I guess it could be the bootloader version it showed?
Because going from 2v16 to 2v11 on its own is basically impossible - while the JS apps themselves can be 'factory reset' from flash, once you overwrite the watch firmware it stays overwritten (there's no hidden copy of the original firmware in the watch).
I think likely the watch is fine though, and it just encountered some corruption in its filesystem. This is getting super rare now - especially with 2v16 - but it's actually possible the corruption got in with an earlier firmware, and then your Bangle has only just used up enough flash that it hit it now :( Hopefully you won't see this again at all
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.
Argh, sorry to hear that.
Are you 100% sure? Maybe you could screenshot and show me where you say 2v11 being reported? I guess it could be the bootloader version it showed?
Because going from 2v16 to 2v11 on its own is basically impossible - while the JS apps themselves can be 'factory reset' from flash, once you overwrite the watch firmware it stays overwritten (there's no hidden copy of the original firmware in the watch).
I think likely the watch is fine though, and it just encountered some corruption in its filesystem. This is getting super rare now - especially with 2v16 - but it's actually possible the corruption got in with an earlier firmware, and then your Bangle has only just used up enough flash that it hit it now :( Hopefully you won't see this again at all