Use current time from remote server instead of handset clock

[GoogleCodeExporter]

I use Vodafone and ask my handset to sync its time with the network, which 
annoyingly is always two to three minutes slow.

Tram Hunter appears to get expected arrival times (rather than durations) for 
coming trams, and then turn this into a duration using the handset's clock.

When the handset's clock is slow, the duration comes down to 2/3 minutes, the 
tram comes and goes and that line disappears from the display before ever 
reading 1 or Now.

When the handset's clock is fast, the duration shows up as Err.

My understanding is that the SOAP response includes the current time as known 
by the server.  I feel that it may be better to use this when calculating 
offsets/durations instead of the current time as reported by the handset.

Original issue reported on code.google.com by alex.peters on 2 Sep 2010 at 7:40

[GoogleCodeExporter]

Thanks for the report. I managed to reproduce it, so I'll be working on a fix 
for this soon.

Original comment by andybott...@gmail.com on 12 Sep 2010 at 8:36

• Changed state: Accepted

[GoogleCodeExporter]

Found the bug which was caused by the current time sent in the TramTracker 
Request to silently fail to be parsed, falling back to the handset clock time.

Please test v0.6-test1 available from:

http://tramhunter.googlecode.com/files/tramhunter-v0.6-test1.apk

and reply back to this issue.

Thanks

Original comment by andybott...@gmail.com on 17 Sep 2010 at 3:51

• Changed state: Fixed

[GoogleCodeExporter]

Seems to work a treat!  Thanks for your attention.

Original comment by alex.peters on 20 Sep 2010 at 11:24