Hi,
I did a 30k run today. I am having to problem syncing.
Firstly, it seems to always drop out so I cannot sync the whole run
Secondly, when it drops out, it saves the date that has been loaded, fine so far, but next time it duplicates the run. It would be better if it remembered that it was the same run and best if it continued from the last point
We're seeing this issue as well -- hoping to be able to address it in either a F/W (quick) or App (longer) update.
Hi guys,
Don't know if it's OK for me to add to this, but I ran a half marathon this AM and I cannot get it to get a complete sync to the phone either. I've retried 4 times and gotten runs of 0, 10.84, 11.29 and 11.37. It just stops and says the runScribe has suddenly disconnected.
I have tried shaking the pod every 30 sec or so to keep it awake, but it doesn't seem to matter.
Steve
I tried the 'shanking every few seconds' thing too. For now I have lowered the timeout rate. I have to stop to cross roads every now and again and hopefully I will be able to upload the smaller sections. With the new stitching function ( which I tried yesterday) I will still get the full run.
I believe it's a known issue and the team is working on fixing it. There are couple of posts in the Beta Testing forums
My longest run has been 17 miles and it took several tries before I was finally able to get a good sync and data transfer.
I experienced similar problem. Due to some traffic light stops, my long run (12.5 mi) was cut into three piece. It took three attempts to synch it but it worked in the end. Also stitching the three chunks together once uploaded worked fine! :-)