search

ayoola-solomon / mytracks

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

export to GPX: save next day date instead the real one date when it was saved #764

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?

1.Export a track to GPX to SD or storage.
2.The dates saved in GPX file are the next day (in someway it adds a day to the 
time correct time on time's mark).

What is the expected output? What do you see instead?

The date of the track (and track's name) is OK but when it is exported the date 
saved in GPX file data is the next day date instead the date when the track was 
saved.

What version of MyTracks are you using? On what version of Android? On what
phone?
MyTracks 1.1.13.
Android 4.0.3
Phone: Nexus S

Original issue reported on code.google.com by fjherra...@gmail.com on 26 Jan 2012 at 12:02

GoogleCodeExporter commented 9 years ago 
I can confirm this appears on my LG Optimus P990 as well.  It should be noted 
that this is a somewhat big deal, as this makes MyTracks unusable for linking 
gpx files to photos taken with an external camera (some apps can't shift time 
24 hours)

Original comment by thefirel...@gmail.com on 26 Jan 2012 at 7:17

GoogleCodeExporter commented 9 years ago 
I also confirm this happening (Nexus S)

Original comment by abor...@gmail.com on 4 Mar 2012 at 4:47

GoogleCodeExporter commented 9 years ago

Original comment by jshih@google.com on 5 Mar 2012 at 10:16

GoogleCodeExporter commented 9 years ago 
Can one of you include the gpx file or a snippet of the gpx <time> tag.
Can you also tell me which time zone you are in? What is the time zone set on 
your phone? And around what time you were recording your track.

Thank you
Jimmy

Original comment by jshih@google.com on 5 Mar 2012 at 10:26

GoogleCodeExporter commented 9 years ago 
Hi,  I have version 1.1.15, on an LG Optimus Speed and still see this 
occurring.  Here is a recent recording.  It is from 03.03.12  The file name is 
correct: 03_03_2012 09_52.gpx  This was recorded in the Central European 
Timezone.

Note that the time in each trackpoint lists the date as the 4th...

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<?xml-stylesheet type="text/xsl" href="details.xsl"?>
<gpx
 version="1.1"
 creator="My Tracks running on Optimus 2X"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns="http://www.topografix.com/GPX/1/1"
 xmlns:topografix="http://www.topografix.com/GPX/Private/TopoGrafix/0/1" xsi:schemaLocation="http://www.topografix.com/GPX/1/1 http://www.topografix.com/GPX/1/1/gpx.xsd http://www.topografix.com/GPX/Private/TopoGrafix/0/1 http://www.topografix.com/GPX/Private/TopoGrafix/0/1/topografix.xsd">
<trk>
<name><![CDATA[03/03/2012 09:52]]></name>
<desc><![CDATA[]]></desc>
<number>27</number>
<extensions><topografix:color>c0c0c0</topografix:color></extensions>
<trkseg>
<trkpt lat="47.41936" lon="12.35777">
<ele>1542</ele>
<time>2012-03-04T09:06:41Z</time>
</trkpt>
<trkpt lat="47.41928" lon="12.35803">
<ele>1669</ele>
<time>2012-03-04T09:06:48Z</time>
</trkpt>
<trkpt lat="47.41935" lon="12.35802">
<ele>1587</ele>
<time>2012-03-04T09:06:52Z</time>
</trkpt>
<trkpt lat="47.4194" lon="12.35801">
<ele>1571</ele>
<time>2012-03-04T09:06:54Z</time>
</trkpt>

Original comment by thefirel...@gmail.com on 11 Mar 2012 at 3:18

GoogleCodeExporter commented 9 years ago 
Also, I believe the correct start time for the above file is 9:52

Original comment by thefirel...@gmail.com on 11 Mar 2012 at 3:43

GoogleCodeExporter commented 9 years ago 
The time portion seems right. The GPX timestamp is in UTC time zone. So your 
first timestamp 2012-03-04T09:06:41Z is 10:06:41am in Central European 
timezone. This is about 14 minutes after the track has started at 9:52am.

I cannot explain the difference on the date, between 3/3/12 and 3/4/12. Under 
your phone's settings for "Date & time", can you share your settings?
Do you have "Automatic date & time" and "Automatic time zone" checked? Or do 
you manually set these values?

Thanks
Jimmy

Original comment by jshih@google.com on 13 Mar 2012 at 12:57

GoogleCodeExporter commented 9 years ago 
Hi,
   I have "automatic" checked, with 24 hour format, and date format of 31/12/2012

I believe I saw the issue initially with a track that was recorded without 
automatic time values, but the track I posted here was made with that set.

Original comment by thefirel...@gmail.com on 13 Mar 2012 at 9:46

GoogleCodeExporter commented 9 years ago 
Hi,
For add more information I have had "Automatic date & time" before this issue 
began (it worked fine before 1.1.13 version). I have so 24 hour format and 
dd/mm/yyyy for date.

Original comment by fjherra...@gmail.com on 13 Mar 2012 at 10:00

GoogleCodeExporter commented 9 years ago 
I'm having this problem, too--I just discovered it after some problems 
geotagging photos. The GPX timestamps are exactly 24 hours ahead of reality. I 
just did a test with my three phones: Nexus One, Nexus S, Galaxy Nexus. Only 
the Nexus S showed the problem.

I'm using automatic date and time (network-provided). (My time zone is GMT+1 
CET). All the phones have their time set correctly, within a few minutes at 
least.

I'm attaching the track logs from each of the phones.

My Tracks version numbers as follows:
Nexus One: 1.1.15
Nexus S: 1.1.15
Galaxy Nexus: Nexus One: 1.1.16

Here's the top of the log for the Nexus S:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<?xml-stylesheet type="text/xsl" href="details.xsl"?>
<gpx
 version="1.1"
 creator="My Tracks running on Nexus S"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns="http://www.topografix.com/GPX/1/1"
 xmlns:topografix="http://www.topografix.com/GPX/Private/TopoGrafix/0/1" xsi:schemaLocation="http://www.topografix.com/GPX/1/1 http://www.topografix.com/GPX/1/1/gpx.xsd http://www.topografix.com/GPX/Private/TopoGrafix/0/1 http://www.topografix.com/GPX/Private/TopoGrafix/0/1/topografix.xsd">
<trk>
<name><![CDATA[2012/03/18 22:49 Nexus S]]></name>
<desc><![CDATA[]]></desc>
<number>26</number>
<extensions><topografix:color>c0c0c0</topografix:color></extensions>
<trkseg>
<trkpt lat="48.84766" lon="2.26223">
<ele>159</ele>
<time>2012-03-19T22:00:58Z</time>
</trkpt>

Original comment by stsh...@gmail.com on 18 Mar 2012 at 10:33

Attachments:

GoogleCodeExporter commented 9 years ago 
The cause seems to be a bad firmware affecting several phones. Please see

http://code.google.com/p/android/issues/detail?id=23937

Original comment by jshih@google.com on 19 Mar 2012 at 9:04

GoogleCodeExporter commented 9 years ago 
I'm also experiencing this problem.
I have a Nexus S, and for me it didn't matter whether I use 24 or 12 hour 
format and the issue was present both in Canada (time zone set correctly) and 
in Europe (time zone set correctly).

Original comment by christia...@gmail.com on 6 Apr 2012 at 7:54

GoogleCodeExporter commented 9 years ago 
Looks like it is a firmware bug affecting all applications.

See http://code.google.com/p/android/issues/detail?id=23937

Original comment by jshih@google.com on 16 May 2012 at 10:23

GoogleCodeExporter commented 9 years ago 
I have the same problem. I am in tokyo, UTC+9, My tracks set the time zone to 
be UTC+0. So the time stamps in .gpx file are incorrect.

To geo-tag my photos, I use Picasa to change the date and time of my photos, 
geo-tag and then change date and time back. It works, but it is really 
annoying. 

I hope someone can fix this soon.

Original comment by vivozhang on 21 Nov 2012 at 1:13

GoogleCodeExporter commented 9 years ago 
>I hope someone can fix this soon.

This will not be fixed, it is a problem with the phone itself, to this 
application

Original comment by thefirel...@gmail.com on 21 Nov 2012 at 1:18