jonasoreland
stability issues when uploading long activities
Somewhere between 8 and 10 hours, uploading becomes problematic.
Runkeeper works RunningAhead works if selected by itself Endomondo works if selected by itself
Ugh... Mobile
Strava and Garmin do not work at all.
I'm currently on a bike tour and am limited to a phone.
my guess is that it's out of memory... and a db dump sounds good.
my guess would be a solution where we don't upload every gps location, but every third or so...depending on how long the acvtivity is...
/Jonas
On Sun, Jun 21, 2015 at 8:56 AM, David Hilton [email protected] wrote:
I could probably send a db dump of it would help?
— Reply to this email directly or view it on GitHub https://github.com/jonasoreland/runnerup/issues/277#issuecomment-113870155 .
Either that or try to come up with a good interpolation to throw out some points (ideally the "not so important" ones). I'm planning to have a look at the graph views, so I might put some thought into this as well....
Both of my 10 hour activities included some sections where I forgot to pause, so auto-collapsing those sections(or me enabling auto-pause) might help.
I generated tcx files and they were about 8MB, so perhaps the uploaded could be made to be more memory-efficient? On Jun 21, 2015 3:38 AM, "Tobias Nett" [email protected] wrote:
Either that or try to come up with a good interpolation to throw out some points (ideally the "not so important" ones). I'm planning to have a look at the graph views, so I might put some thought into this as well....
— Reply to this email directly or view it on GitHub https://github.com/jonasoreland/runnerup/issues/277#issuecomment-113882412 .
https://www.dropbox.com/s/xia3x7sesjjtbqg/runnerup.db.export?dl=0 On Jun 21, 2015 6:58 AM, "David Hilton" [email protected] wrote:
Both of my 10 hour activities included some sections where I forgot to pause, so auto-collapsing those sections(or me enabling auto-pause) might help.
I generated tcx files and they were about 8MB, so perhaps the uploaded could be made to be more memory-efficient? On Jun 21, 2015 3:38 AM, "Tobias Nett" [email protected] wrote:
Either that or try to come up with a good interpolation to throw out some points (ideally the "not so important" ones). I'm planning to have a look at the graph views, so I might put some thought into this as well....
— Reply to this email directly or view it on GitHub https://github.com/jonasoreland/runnerup/issues/277#issuecomment-113882412 .
By the way if you are using default settings (eg GPS update distance frequency: 0 meter), pull request #291 should reduce drastically size of the track and save a lot of battery as well. If you are running into unlimited GPS refresh rate, you can end up with pretty big files!
why not instead simply change the value in the preferences ?
/Jonas
On Sat, Jul 18, 2015 at 11:24 PM, Gautier Pelloux-Prayer < [email protected]> wrote:
By the way if you are using default settings (eg GPS update distance frequency: 0 meter), pull request #291 https://github.com/jonasoreland/runnerup/pull/291 should reduce drastically size of the track and save a lot of battery as well. If you are running into unlimited GPS refresh rate, you can end up with pretty big files!
— Reply to this email directly or view it on GitHub https://github.com/jonasoreland/runnerup/issues/277#issuecomment-122597838 .
Yes you can do it but there is a bug when using default parameters values which could explain the issue.
