Hello,
why I missed your previous post > do not know, sorry.
It is really weird because I'm aware of only two situations when track recording may be really paused "magically":
1) new, not yet perfectly working, mentioned "auto-pause" settings
2) app was killed by the system, and later started manually again (after more than 10 minutes after it was killed) and the app automatically pause the previous recording.
Otherwise, it may be paused over the widget, by intent (so over Tasker etc), in the UI (side panel or dashboard). Hmm and this is probably all ...
--
I've anyway just generated a new Beta version for tests so I've added some extra logs related to the start/stop of track recording. If you find a moment, you may try to install it, then long-click on the app main menu button and enable Setup logging > Log to file.
Then try recording as usual and after the issue happens, so after you notice an accidentally paused track recording, just stop the app and send me a log file from the Locus/logs directory. Info, when (exact time) issue happened may be useful.
why I missed your previous post > do not know, sorry.
It is really weird because I'm aware of only two situations when track recording may be really paused "magically":
1) new, not yet perfectly working, mentioned "auto-pause" settings
2) app was killed by the system, and later started manually again (after more than 10 minutes after it was killed) and the app automatically pause the previous recording.
Otherwise, it may be paused over the widget, by intent (so over Tasker etc), in the UI (side panel or dashboard). Hmm and this is probably all ...
--
I've anyway just generated a new Beta version for tests so I've added some extra logs related to the start/stop of track recording. If you find a moment, you may try to install it, then long-click on the app main menu button and enable Setup logging > Log to file.
Then try recording as usual and after the issue happens, so after you notice an accidentally paused track recording, just stop the app and send me a log file from the Locus/logs directory. Info, when (exact time) issue happened may be useful.
The following users thanked this post: michaelbechtold