Meaning the the SD card was mounted, which will cause Run.GPS to terminate because Run.GPS needs the SD card to operate.
In the log you sent yesterday there was only information about Run.GPS being started, but nothing about it's termination.
If possible, we'll improve this behaviour in the coming 2.3.9 release. If you still get some log containing information about the app's termination, that would be nice to have.
If you want you can use the "Log Collector" app (free on Android Market) to lookup the reason why Run.GPS is terminated (just search for "esymetric" or "rungps" in the log).
There must be a glitch with the software or the Android. RunGPS shuts off when a phone call occurs. Yesterday it shut off after receiving a text message. I have over 12 GB of memory. I couldn't have been low in memory.
There must be a glitch with the software or the Android. RunGPS shuts off when a phone call occurs. Yesterday it shut off after receiving a text message. I have over 12 GB of memory. I couldn't have been low in memory.
Sounds a little strange as the Galaxy S has quite a large amount of memory?!
Would that be dependent of the distance gone when the call occured? (i.e. when tracklog was large, think it was after 12 km, 1:30 hrs) or could i just start a training and call myself up to try and log?
This probably happened because you were low on memory. When the operating systems thinks it does not have enough memory left, it will shut down background applications when you open new ones (Phone app in this case). You could install the "Log Collector" (Market) and see what happens after such an incident. The log is normally pretty clear about it. Just search for "esymetric" (manufacturer) in the log.