Thank you for clarifying this.
However, I didn’t notice until after several years of use. My impression is that before the offline MLS stuff was introduced, I was able to enable Flight mode without killing GPS. So it could be that the implementation hasn’t always matched design intention.
Also, it’s a bit difficult to understand the design:
- Expectation when coming from other systems is for GPS to be unaffected by Flight mode
- Documentation only mentions Flight mode in the context of networking and telephony, not in the context of GPS or location
- The
Position toggle
in theTop menu
stays in theOn
state when enablingFlight mode
- Jolla added this bug to their internal tracker in March 2023
Unfortunately, these ingredients form a recipe for getting many useless bug reports…
To improve the situation, I think there are a couple of options:
- Follow through with the design
- Ensure proper UI feedback (e.g.
Location
indicator inTop menu
should reflect actual state) - Update documentation (several pages) to make the design intention clear, to people coming from other systems can set their expectations correctly
- Ensure proper UI feedback (e.g.
- Adapt to the way of other systems
- Ensure that
Flight mode
does not affectLocation
- Ensure that
- Keep everything as is
I would certainly prefer option 2, since I frequently use offline navigation.
Option 1 is probably more work, but the community could help working on the docs.
I think option 3 is the worst, as it would keep wasting resources on useless bug reports - both the resources of Jolla and those of the community.
Do you have any thought on this?