Thanks for the response. What situation would you want to turn on the gps and have something else turn it off? This is why I wondered if app id was legacy and was always being injected anyway. It means a widget could turn the gps off for my app without me knowing (not sure why they would...but they could).
I also feel like widgets should be restricted to showing information and not changing any.
If a boot app is managing power and says "no sorry you can't have gps on at moment" it can't switch it off until my app exits?
When you power on the GPS there is a tag argument that registers your app wanting the gps to stay on. At that point only your app can turn off the gps.
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 the response. What situation would you want to turn on the gps and have something else turn it off? This is why I wondered if app id was legacy and was always being injected anyway. It means a widget could turn the gps off for my app without me knowing (not sure why they would...but they could).
I also feel like widgets should be restricted to showing information and not changing any.
If a boot app is managing power and says "no sorry you can't have gps on at moment" it can't switch it off until my app exits?