![]() |
2008-02-02
, 09:15
|
Posts: 251 |
Thanked: 22 times |
Joined on Dec 2007
@ Houston, Texas
|
#2
|
![]() |
2008-02-02
, 09:17
|
Posts: 164 |
Thanked: 132 times |
Joined on Dec 2007
|
#3
|
![]() |
2008-02-02
, 09:20
|
Posts: 164 |
Thanked: 132 times |
Joined on Dec 2007
|
#4
|
Are the timestamps UTC (GMT) time? Is the difference between the timestamp and your local time, the difference in timezones?
If so...not an error.
![]() |
2008-02-02
, 10:38
|
|
Posts: 739 |
Thanked: 159 times |
Joined on Sep 2007
@ Germany - Munich
|
#5
|
![]() |
2008-02-02
, 11:12
|
|
Posts: 2,142 |
Thanked: 2,054 times |
Joined on Dec 2006
@ Sicily
|
#6
|
![]() |
2008-02-02
, 19:30
|
Posts: 164 |
Thanked: 132 times |
Joined on Dec 2007
|
#7
|
how do you monitor? I tried dbus-monitor --system but the time value seems to be shown in exponential format so that I lose several least significan digits.
![]() |
2008-02-02
, 19:57
|
Posts: 164 |
Thanked: 132 times |
Joined on Dec 2007
|
#8
|
![]() |
2008-02-02
, 21:52
|
|
Posts: 716 |
Thanked: 236 times |
Joined on Dec 2007
|
#9
|
![]() |
2008-02-02
, 23:14
|
Posts: 139 |
Thanked: 24 times |
Joined on Sep 2005
|
#10
|
If you need exact timestamps, you can write your own signal listener (only a few lines of Python) or download the source of dbus-monitor and hack it to print doubles with %f instead of %g.
Right now it is 1 am on February 2nd. The timestamps coming from GPS are around 1202027650, which ctime tells me is
Sun Feb 3 00:39:11 2008
If there is indeed an off-by-one error, this could explain the poor GPS performance in acquiring satellites (since the almanac data would be invalid). Perhaps there is a simple fix that could make the GPS in our tablets significantly better.
I hope I am onto something. Anyone know of a legitimate reason for the time difference?
See my collection of maemo apps: http://nitapps.com