Don't start a new file when already logging to a file #FeatureRequest

[kevjs1982]

Currently¹ when starting GPSLogger logging (e.g. through the widget, Samsung Modes & Routines, or calling the Intent (e.g. via Home Assistant)) a new track is always created even if it's already recording one.

What would be really useful is for it to be allowed to continue the existing log if a recording is started while already in progress - e.g. when the trigger is being connected to Android Auto any drop outs cause a new log to be started when it reconnects. This would allow one file per journey to be created rather than multiple files, or being limited to one file per day with long gaps between them.

e.g.

• GPS Logger isn't logging anything
• Android Intent immediatestart:true called
• New file is created, GPS Logger starts logging
• Some time passes (GPS Logger continues logging to a file)
• Android Intent immediatestart:true called
• GPS Logger ignores this request and continues to logs to the existing file.
• GPS Logger is stopped
• Some time passes (GPS Logger is no longer logging)
• Android Intent immediatestart:true called
• New file is created, GPS Logger starts logging

I envisage this to be an additional option underneath Logging details only enabled when "New file creation" is set to "Every time I start"

• "When already logging, continue logging to the previous file"

Default would be off to match the existing behaviour.

Footnotes

1. If you have the new file creation option set to "Every Time I start" ↩

[mendhak]

I was able to recreate this bug when I selected "Every time I start" under New file creation. When I sent a Llama Automate 'immediatestart' I got a new file even though logging had already started. This sounds like a bug to me so I've added a check for it in this pull request.