-
Notifications
You must be signed in to change notification settings - Fork 295
Description
RunnerUp worked fine for me for at least 8 runs/walks before I experienced this problem, but now it seems to be happening about half the time.
I start the app, Hit the 'start GPS' button and wait for GPS signal/heartrate monitor connection. Then hit 'start activity'. within a second or so the 'Resume' button appears above the 'STOP' button. When I move no distance is recorded. I have lost the data for a couple of runs due to this problem, so I messed some more today.
After a couple of km I tried repeatedly hitting 'Resume' (nothing happens), and starting again with 'Start GPS' and 'start activity'. A couple of times it got as far as the audio announcement 'Lap starting', but several times it didn't even get that far. But it reliably always went to 'Resume' button showing within a couple of seconds.
The only way to make the app work was to quit it and restart it. After that the activity started and stayed started, as expected.
I'm not sure what's going on here, but presumably something is erroring and it is going into 'paused/stopped' mode.
Is there some debug info I can look at or log to see if we can work out what's going wrong here, because an unreliable run-timer is very frustrating!
The fact that it sometimes says 'Lap started' means you can't rely on that as a check for successful startup. And then you don't notice for 500m (with announcements on), or the end of the run (with announcements off), that in fact nothing is being recorded.
I have had this issue both with and without a bluetooth HRM.
I 'save'd 4 of the failed-start runs today and 3 are 0m 0:00 time. One is 1m, 0:01 time
I can't find any logging data to check.