Public intent to start recording sometimes doesn't enable GPS
This is a bit special problem and I can't reproduce it, but it's kinda severe:
For travel, I defined some tasks that automatically enable the phone's GPS and then start Locus recording, using the public intent locus.api.android.ACTION_TRACK_RECORD_START (I wanted to link to the manual page here, but http://docs.locusmap.eu/doku.php?id=manual:locus_api:public_intents gives an error...).
This worked quite well - most of the time. But in a few cases I later realized that GPS was turned on, Locus was in recording mode, but within Locus, GPS wasn't enabled - so nothing was being recorded effectively.
That was quite a blow, as I lost my track until then. Unfortunately, when I tried to reproduce it, it always worked.
Is there some condition under which the intent doesn't enable GPS within Locus, or is this a bug?