GPS disabled itself twice today
This seems related to this earlier question.
Today, GPS disabled itself twice on a three hour hike, and each time Locus Map stopped recording the track until I found out.
Only in the first case, ~1.5 km after recording stopped, the app finally complained about some setting that may be causing GPS getting lost while the app is running in background. (I tapped "Show me what to do" but nothing happened, possibly because there was no mobile internet connection, something a hiking app should not really expect to be there IMHO...)
In both cases, GPS was off when I noticed something was wrong, and I had to manually turn it on again.
This is Locus Map 4.3.3 on Android 11 (LineageOS 18.1) on an FxTec Pro1 phone, and I never had this before with either Locus Map 3 Pro or Locus Map 4, at least not after properly setting the necessary system options.
What I find a bit strange now, though, is that when I looked whether battery optimisation really was disabled, the settings page reported for both Locus Map 3 Pro and Locus Map 4 "Battery optimisation not available", and there was nothing I could configure. I could swear the last time I looked it showed either "optimised" or "not optimised".
I don't think this could be a case for the "Memory Locker" app (the device has 6 GB RAM and I don't see too much else going on in the background), but I might try "GPS locker" if this happens again.
Oh, and there was one possibly related Locus Maps setting disabled, which I did enable right now – "GPS ON for track recording", but I don't remember changing anything there ever before.
And just on a side note, could it be that the app's behaviour on losing GPS is somehow different when there's no mobile connection (in my case not even GPRS)?