Hi! Today I tested the new version of the Java application. After I recorded this track the following information was displayed on the phone:

The following split times were displayed on the phone:

These are different from what I can see on the web interface (which seems correct). I will repeat the test soon…

Hi Zsolt,
It seems that on the software’s track summary page, some information is not filtering through correctly on some devices which use an external Bluetooth GPS. We are looking into this now and it will be fixed in the next release.

Thanks for highlighting the split time discrepancy with the website. Distance is calculated differently on the mobile phone compared to the website which uses the Google maps polyline API. This causes the split times to be slightly different. We are working to unify the calculation so that the phone and website both report the same splits.

Thanks for the feedback and I hope you are enjoying using the system,
Rob

Hi Rob,
Only the last line was strange for me in the split times. The 1 second difference is not a problem at all.
I actually tried to test it again this morning but the application (or the phone) crashed after a few minutes. Maybe it was due to the simultaneous mp3 playback or something else. I am using a SonyEricsson W800i with a Bluetooth GPS receiver.
Regards,
Zsolt

Hi again!

I have just tested v1.0.2 and it was almost perfect. I am not listing the split times here, they were within 1 second on the phone compared to the web application, except for the first one where the difference was 4 seconds. However, the last entry on the phone was a bit still strange:

6.0 to 6.14: -2:-24

The only major difference between track data on the phone and on the web was the total time (and the average speed that is calculated from it). On the phone it was 17:34 while on the web it is 20:49.

Can you tell me what “fastest pace per km” means on the phone? I can see it is not one of the split times. Is it the top speed converted to minutes/km or is it the fastest full kilometer covered?

Finally a minor remark. On the web application at the “Pace” data it is the slowest km displayed as “max”. I think it would be more interesting to see the fastest one. :)

Best regards, Zsolt

Hi Zsolt,
Yes, the split time breakdown still needs a bit of work and should be fixed soon. It’s all down to a synchronization issue with incoming GPS points and the clock timer. “Fastest pace per km” should match up with the quickest split time, and will do once the issue is fixed.
I agree, the fastest split time would be more useful on the website! We’ll change it over soon.

Thanks again for the great feedback,
Rob

Hi,

I had very similar results with version 1.1 of the application when making this track.

The last entry in the split times was this: 10.0 to 10.62: -7:-35

The total time on the phone was 00:44:22 while it was 00:54:50 on the web. Unfortunately, the longer time is realistic for me. :) I noticed that the average pace (04:10) was calculated from the shorter time while average speed (11.6 kph) was based on the longer time. I have not really checked this, it is just my estimation.

I do not think all this is a major problem. I am really satisfied with the accuracy of the track.

Best regards, Zsolt