Description
@naricdurmus reported in #5:
Another error occurred on a different smartwatch and phone combination, the smartwatch displayed after several minutes: 'Someone else is writing to this logging session.' Afterwards, the phone application restarted itself (while receiving the data from the Pebble) and no data was saved.
Not entirely sure why this is happening. Something similar occurred once during my longest test session on #5 while I was disconnected from my phone. Through some combination of button presses (which I do not remember) I managed to get the watch app back into the normal logging mode without exiting. I was then able to save the results and noticed no abnormalities besides a few missing minutes of data.
I suspect that this message is appearing and pausing logging due to a temporary lack of accessibility to the datalogging session on the watch. A possible fix may be retrying the write or temporarily storing readings in-RAM until the datalogging session can be accessed again.
The reported issue with the Android application is rather baffling. Unless ADB logs of the crash are available, I'll assume that it's a side-effect of the watch app error and focus on that.