TrekBuddy

[xvici]

Hi,

I have recently upgraded to 0.9.83 (from .81) version and get problems with new time format in GPX log. The time itself is correct but the timezone not. I guess, that in central Europe during daylight saving time we have +02:00. But there is +01:00 in GPX logs. It brings some problems when processing logs in PC.

I have searched the discussion but haven't found similar posts.

Maybe it would be great to implement option in settings menu that everybody could choose what format to log.

Phone: SE K550i
Timezone in phone settings menu: +01:00
Daylightsaving time in phone settings menu: ON
TrekBuddy tech info: Timezone GMT+01:00; true; 3600000

Thank you for developing such a great tool

[kruch]

I will add the config options: "enable GMT timestamp" and "timezone correction"

[BeardyGit]

I've just tripped over the same issue. I'm based in the UK and have the device time zone set to GMT (Dublin, London). The device applies daylight savings to the current time, but still seems to label it as GMT. That 'GMT' time is then written into TrekBuddy GPX logs as Zulu time (with a terminating 'Z'). So it seems that TB may have been doing what it was told ... but it was told to do the wrong thing by the OS?

I don't know if it would be possible to detect whether daylight saving is in effect, or even to access the time stamp from the GPS signals themselves, which is more likely to be correct than Blackberry reports, I'd have thought!

Many thanks - great tool!

[herman_p]

This is a topic kick, as I think this phenomenon still exists.
Let me give some details to illustrate this.

Living in The Netherlands we are at GMT+1, also having Daylight saving of +1 hour now.
I am using TB 1.0.11 on a Nokia 6700 classic, firmware V13.21

I tested four different time setting combinations on the handy, with the following results

GMT+1, Daylight saving +1 hour
Handy clock indicates 20:34
GPX logfile entry
<time>2011-05-05T19:34:37.686Z</time>

GMT+2, Daylight saving 0
Handy clock indicates 20:55
GPX logfile entry
<time>2011-05-05T18:55:49.611Z</time>

GMT +0, Daylight saving +2 hours
Handy clock indicates 21:14
GPX logfile entry
<time>2011-05-05T21:14:52.795Z</time>

GMT +0, Daylight saving +0 hours
Handy clock indicates 21:29
GPX logfile entry
<time>2011-05-05T21:29:32.82Z</time>


When the handy is set to GMT+1, Daylight saving +1 hours, the technical screen of TB reports the following:

Time zone
GMT+1:00; false; 3600000

It seems to me that Daylight saving time is not reflected in the logfile, but maybe I am doing something wrong?
For the time being my workaround is to set the handy to GMT+2, Daylight saving 0, which results in a logfile with correct timestamps.

Enjoy!

Herman

[kruch]

If you see GMT+1:00; false; 3600000 for GMT+1 timezone with daylight, then it means midlets get wrong information from the OS, because there should be true instead of false (meaning: this timezone uses daylight saving time), and the raw offset would then probably be 7200000.
When I select Czech Republic region in Nokia 6720c (how can I configure DST in Nokia??), it sets GMT+2 timezone, which gives correct offset of 2 hours, but strictly speaking it should be GMT+1 with DST (but I ccanot find where to configure this).

Also tried to select Netherlands, it resulted in "GMT+2 Netherlands" TZ.

[herman_p]

Hi Kruch,

Thank you for responding, for looking into this.

On my Nokia 6700c I can set DST in Settings / Date and time / Date & time settings where there are separate entries for Time zone (expressed in GMT +/- something) and Daylight saving.
AFAIK the 6700c has no options to set a country directly as the 6720c apparently has.
I wonder, if this is an OS interface issue, how to persuade Nokia to look into this?

Enjoy!

Herman

[kruch]

It looks like known issue (at the bottom of http://library.forum.nokia.com/index.jsp?topic=/Java_Developers_Library/GUID-61343D82-D041-4B59-B0F1-9923C17AB4DF.html). If the workaround (setting GMT+2 TZ) does not interfere with anything, then you will have to live with it, I'm afraid

And I think you can just forget about persuading Nokia to look into this. Unless you are friend of their CEO or some...

[herman_p]

Hi Kruch,

Once more thank you for your time!
I guess it is something I have to learn to live with

Enjoy!

Herman.

[Roland von Bremen]

On my Sonim XP5300_10.0.0 the time stamp issue is still present. On the screen, TrekBuddy reports the local time correctly 13:37, which is CET+1h daylight saving (DST). The technical info lists the TimeZone:

GMT+1:00; true; 3600000

which I assume means, time zone is GMT+1 plus one h for DST. The OS is providing the correct time zone and DST information to TrekBuddy.

The correct

[Roland von Bremen]

I changed DST to off on the phone. This was reflected in the technical info, TimeZone:

GMT+1:00; false; 3600000

The phone now displayed UTC+1. The displayed time on the TB screen changed to UTC+1 (without DST, CET) and the recorded <time> tag was 1h earlier and set correctly to UTC <time>2012-05-19T14:03:41Z</time>. The file name had UTC+1 (20120519-150250.gpx).

I then set DST on and phone time to DST+3.

The phone now displayed UTC+3. The displayed time on the TB screen was UTC+2 and the recorded <time> tag was UTC+1 <time>2012-05-19T15:48:07Z</time>. The file name had UTC+3 (20120519-174535.gpx).

This leads to the following conclusions:

1. TB is getting the time zone info from the phone correctly
2. TB is also getting the DST info from the phone correctly
3. TB uses the time on the phone to build the file name, this does not really matter. It would be better to use GPS time to avoid potential conflicts.
4. TB uses GPS (UTC) time and the time zone and DST info from the phone to build the (local) time on the display. This works as it should and is not confused by odd settings of the phone time.
5. TB uses some odd mechanism to go from GPS time to UTC and gets confused on the way with DST.