Messages

Thank you for quick response. Yes, this seems to be a hardware issue. Another track, recorded by Trekbuddy, shows the same wrong datetime.

I only can record a track if I set the time interval to 0 sec. The reason is a wrong datetime. See this snippet from today's track 20110517_195143.gpx :
------------------------------------------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="ISO-8859-1"
standalone="yes"?>
<?xml-stylesheet type="text/xsl" href="details.xsl"?>
<gpx version="1.0"
 creator="Android"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns="http://www.topografix.com/GPX/1/0"
 xmlns:topografix="http://www.topografix.com/GPX/Private/TopoGrafix/0/1" xsi:schemaLocation="http://www.topografix.com/GPX/1/0 http://www.topografix.com/GPX/1/0/gpx.xsd http://www.topografix.com/GPX/Private/TopoGrafix/0/1 http://www.topografix.com/GPX/Private/T ... grafix.xsd">
<trk>
<name><![CDATA[2011-05-17 19:51:43]]></name>
<desc><![CDATA[0h:0m:0s | 348m

Distanz - 348m
Punkte // POI - 50
Erstellt - 1970-01-16 03:40:51
Max. Geschwindigkeit - 5.2km/h
Min. Meereshöhe - 212m
Max. Meereshöhe - 215m
]]></desc>
<topografix:color>c0c0c0</topografix:color>
<trkseg>
<trkpt lat="47.89708468231547" lon="7.624402073782538">
<ele>214.50244140625</ele>
<time>1970-01-16T02:40:51Z</time>
</trkpt>
<trkpt lat="47.89764907256435" lon="7.625193801052845">
<ele>213.28555297851563</ele>
<time>1970-01-16T02:40:51Z</time>
</trkpt>
<trkpt lat="47.897690790552275" lon="7.625242539606226">
<ele>213.1326904296875</ele>
<time>1970-01-16T02:40:51Z</time>
</trkpt>
---------------------------------------------------------------------------------------------------------------------------
Because <time> is a constant value, I get only one trackpoint, if I set the time interval to > 0 sec.
How to get the correct time information ?
By the way, this is a smart app. Congratulations !