You are reading a single comment by @jerryn and its replies.
Click here to read the full conversation.
-
I am hoping that this has been narrowed down to an issue with the IOS messaging. That seems to be the App the starts things going badly.
I had mine in a really bad state a few weeks ago, but eventually was able to get in via the WEB IDE and delete the corrupted files. It took many tries to get connected, but eventually I think it was just that I had to clear the BLE device from my Mac in order to reconnect. It is nice to be able to recover no matter how confused it gets!
jerryn
Hi,
I also had a "spontaneous factory reset" once. It was in the beginning of my development of Anton clock. I started with copying it into a new app but garbled the app.json entry. My "antwsclk" overwrote the "antonclk" files on the Bangle as I did not change the file names. After some back and forth, I removed my app and therefore (parts of) Anton clock - which was still the default clock at that moment (I had not understood the concept of "default clock" at that time...).
However, I locked up the Bangle.js severely and the boot screen talked about "corrupted boot data" or did simply nothing. I left the Bangle alone for some 30 minutes and when I looked at it again, it obviously had performed a factory reset. Stock Anton clock etc.
I did not see this behaviour again once I corrected my app.json entries. There was another factory reset lateron, but for that I can absolutly not say any suspicious circumstances - it just happened.
Perhaps this helps more than it sounds...
Regards,
Dirk