Thanks for your help ! Obviously the culprit was the wake-on-twist. It is very handy while running, but the power draw being so high, it can be advantageously replaced by wake-on-tap. I did a short test run today and I realised 1)I don't need any backlight if running in daytime. 2) Just this might be enough to save enough energy to handle 2h30 in a row. I'll test that next week with a long run.
If it's not enough, I was thinking that the recorder app has a "time period" settings. I've set it to 1s, but do you think setting it to 2 secs would save a fair share of energy ?
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.
Thanks for your help ! Obviously the culprit was the wake-on-twist. It is very handy while running, but the power draw being so high, it can be advantageously replaced by wake-on-tap. I did a short test run today and I realised 1)I don't need any backlight if running in daytime. 2) Just this might be enough to save enough energy to handle 2h30 in a row. I'll test that next week with a long run.
If it's not enough, I was thinking that the recorder app has a "time period" settings. I've set it to 1s, but do you think setting it to 2 secs would save a fair share of energy ?