[hafqa] [hafqa] [Bug 2877] Incorrect GPS timestamps reported over D-BUS

[From: bugzilla-daemon at lists.maemo.org]

https://bugs.maemo.org/show_bug.cgi?id=2877





------- Comment #6 from jukka.rissanen at nokia.com  2008-02-05 13:53 GMT+3 -------
This is same as internal bug #79009

The leap year problem only affects the dates that are sent to GPS clients that
use the C library interface or dbus interface, it does not affect raw interface
(NMEA data) that the Map program is using.

The analysis that the leap year bug would affect fix times is wrong. If you are
seeing improvements in fix times after patching gpsd, then the reason is
something else. For example osso-gpsd 1.0-25 fixes serious performance bug
found in original gpsd (it reads only one sentence / sec from gps device), the
fixed version reads all possible sentences from gps device in one go (normally
this is only visible when gpsd fixes are used in voice navigation, before the
correction the fixes where coming 1-2 seconds too late).

There is some rumours circulating that the osso-gpsd is based on very ancient
gpsd version. That is not correct, the osso-gpsd is based on 2.32 which is not
so ancient (released 2006). Perhaps the mixup is caused by version number of
osso-gpsd which is currently 1.0-27, unfortunatly the original 2.32 is not
shown in version string (the upstream version is mentioned in changelog thou).

The leap year bug is fixed in osso-gpsd 1.0-26 that is only released in diablo.
Currently there are no plans to release it in chinook, fortunately the leap
year problem goes away at the end of february.

The slow fix times from internal gps chip cannot really be affected by leap
year bug because the gpsdriver is before gpsd in the GPS data pipeline. The
NMEA date data is correct (year is set correctly) but only the GPS data that
gpsd provides to clients gets incorrect date. The wrong date is never fed back
to gpsdriver and internal chip.


-- 
Configure bugmail: https://bugs.maemo.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.