Package: mtkbabel Version: 0.8.3.1-1.1 Severity: normal Tags: patch Dear Maintainer,
When I download GPS data from an i-Blue 747 device, Model ID 001B, all the timestamps are now in the past by 7168 days. As an example, a track recorded in data 2019-10-10, have all timestamps with date 2000-02-24. The time is indeed correct. The device has worked perfectly until some months ago. Searching for "GPS Weeks Rollover Bug" on the net, I discovered that many GPS devices are affected by an overflow on weeks count, this means that timestamps will overflow after 1024 weeks (10 bits), starting back from device hard-coded EPOCH (begin of the time). The upstream mantainer (i.e. me) has made a patch in mtkbabel: if you use the -W -1 option, the program will try to guess if a rollover is happening, and it will add 1024 weeks to the timestamp. You can also pass the exact count of rollover weeks, e.g. with -W 1024. New upstream version is downloadable here: https://sourceforge.net/projects/mtkbabel/files/mtkbabel/0.8.4/ -- System Information: Debian Release: 9.9 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-9-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mtkbabel depends on: ii libdevice-serialport-perl 1.04-3+b3 ii libtimedate-perl 2.3000-2 ii perl 5.24.1-3+deb9u5 mtkbabel recommends no packages. mtkbabel suggests no packages. -- no debconf information
