on exit of the settings menu (caling load()) the GPS power is turned back off
Yes, that's expected. I think I'd mentioned before about this in another post, but between apps everything gets returned to power-on state. The recent changes are there just to stop widgets calling Bangle.setGPSPower(0) and breaking other apps.
However, I believe you're saving the GPS config? Even though it is saved to nonvolatile RAM on the GPS, turning the GPS 'off' shouldn't lose any of that state - it's more like 'standby' than 'off.'.
I am not yet convinced switching the GPS on / off all the time is a great idea
It's not ideal, that's for sure. I think I mentioned before but it's something that could be fixed with a firmware update later on - so I wouldn't try and add stuff to hack around it just yet.
However once the GPS has a lock, if it's turned off for a few seconds I don't think it should take that long to reacquire. If you've got your low power 120s fix stuff added I doubt you'd even notice.
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.
Yes, that's expected. I think I'd mentioned before about this in another post, but between apps everything gets returned to power-on state. The recent changes are there just to stop widgets calling
Bangle.setGPSPower(0)
and breaking other apps.However, I believe you're saving the GPS config? Even though it is saved to nonvolatile RAM on the GPS, turning the GPS 'off' shouldn't lose any of that state - it's more like 'standby' than 'off.'.
It's not ideal, that's for sure. I think I mentioned before but it's something that could be fixed with a firmware update later on - so I wouldn't try and add stuff to hack around it just yet.
However once the GPS has a lock, if it's turned off for a few seconds I don't think it should take that long to reacquire. If you've got your low power 120s fix stuff added I doubt you'd even notice.