I know having to do a long press reboot is not something that is mean't to be needed but I have had to do this quite a lot on 2v16.x firmware. I am currently homing in on a reproducable way of repeating hangs I have observed.
The only negative effective of a reboot is that you lose the step count which is reset to 0. That means you lose your steps for the day.
Would there be a mechanism where by when a long press is requested that step count is somehow pushed to storage ? Or maybe that is a better scheme, some sneaky bit of hardware where it could be pushed and recovered on a reboot ?
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.
I know having to do a long press reboot is not something that is mean't to be needed but I have had to do this quite a lot on 2v16.x firmware. I am currently homing in on a reproducable way of repeating hangs I have observed.
The only negative effective of a reboot is that you lose the step count which is reset to 0. That means you lose your steps for the day.
Would there be a mechanism where by when a long press is requested that step count is somehow pushed to storage ? Or maybe that is a better scheme, some sneaky bit of hardware where it could be pushed and recovered on a reboot ?