search

CompanyGateways / mytracks

Automatically exported from code.google.com/p/mytracks
1 stars 0 forks source link

Timestamp error in GPX export #402

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Use android phone with time zone set to UTC +10h
2. Records a track
3. Export track to GPX

What is the expected output? What do you see instead?
Timestamps for points are recorded in the GPX file as UTC time zone (indicated 
by a "Z" prefix in the GPX timestamps). I expect that timestamp to be 10 hours 
behind my local time, but it is actually recorded as 20 hours behind local time.

Eg a point that I recorded at 2011-03-12 10:46am local time is exported to a 
GPX file as "<time>2011-03-11T14:46:28Z</time>".

What version of MyTracks are you using? On what version of Android? On what 
phone?
MyTracks ver 1.1.4
Android 2.3 (Cyanogen mod)
Samsung i5700 Spica

If possible please provide a log.  Either upload here or send to mytracks-
support@google.com.
Detailed instructions can be found here:
http://code.google.com/p/mytracks/wiki/HowToReportErrors

Please provide any additional information here:

Original issue reported on code.google.com by dcarte...@gmail.com on 22 Mar 2011 at 11:34

GoogleCodeExporter commented 9 years ago 
Correction to Android version: Using Android version 2.2.1 (CyanogenMod 
6.1.1-Spica-alpha8.3, Kernel 2.6.29.6)

Original comment by dcarte...@gmail.com on 22 Mar 2011 at 11:42

GoogleCodeExporter commented 9 years ago 
I am inclined to say this is a bug in Cyanogen as I have never seen this on a 
std android build.

Original comment by sandordo...@google.com on 8 Apr 2011 at 11:52

GoogleCodeExporter commented 9 years ago 
I have cyanogen mod and I'm having the same problem, it must be a cyanogen mod 
bug.
(Android Version 2.3.3, Kernel version 2.6.35.7-g1d030a7 android-build@apa28 
#1, Mod version Cyanogenmod-7.0.0-RC4-NS, Build number GRI40)

Original comment by mohammad...@gmail.com on 25 Apr 2011 at 7:10

GoogleCodeExporter commented 9 years ago 
Can you please file the bug with cyanogen instead?

Original comment by rdama...@google.com on 30 Apr 2011 at 10:00

GoogleCodeExporter commented 9 years ago 
I have reported it as a Cyanogenmod issue 
(http://code.google.com/p/cyanogenmod/issues/detail?id=3660). We'll see what 
happens.

Original comment by dcarte...@gmail.com on 4 May 2011 at 7:12