Maxdamantus | Applying a screen protector to my N9: https://maxdamantus.eu.org/n9sp.jpg | 02:28 |
---|---|---|
Maxdamantus | Realised it doesn't like the curved glass on the edges, so trying to hold it down with plastic/tape for a while. | 02:29 |
brolin_empey | sunshavi: OK although Windows XP changed a lot between the RTM in 2001 and the final Service Pack 3 in 2008. | 06:37 |
brolin_empey | I meant to check if my Maemo 5 installation has a normal fstab file whilst I was at home but I forgot until I am back at my office again. Does Maemo have a normal fstab file located at /etc/fstab ? | 06:41 |
sunshavi | brolin_empey: yes | 06:42 |
brolin_empey | sunshavi: OK, thank you. Now I do not have to try to remember to check when I am back at home. | 06:43 |
akossh | Hi everyone! | 13:26 |
akossh | Do you know a fix for the problem, that the N900 GPS time and date is off by almost 20 years? | 13:27 |
akossh | it displays summer of 2000 | 13:28 |
sicelo | i don't know. you're seeing it through GPS recorder? or how else are you seeing it? | 13:29 |
akossh | yes, through GPS recorder | 13:31 |
akossh | the system time is correct, but the GPS time displayed and recorded in track logs is back in the past | 13:32 |
akossh | strangely this does not occure immediately after the GPS week number rollover | 13:33 |
sicelo | maybe someobe needs to work on its source and fix/update something. else, you can use one of the other gps loggers | 13:33 |
akossh | I will try | 13:35 |
akossh | I did not check for updates for a long time. | 13:35 |
sicelo | no, the latest version in repositories has that problem ... i tested it. | 13:37 |
akossh | It must be related to the GPS week number rollover | 13:37 |
sicelo | i meant that someone needs to fix the source and rebuild ... that's if someone knows why the problem exists :) | 13:37 |
akossh | because the error seems to be 1024 weeks | 13:38 |
sicelo | sounds like easiy fix then | 13:38 |
akossh | I do not hope for a firmware fix in the GPS chipset, but might be somebody implement a workaround in the "gpsd" daemon | 13:40 |
sicelo | that's closed source (liblocation). i was thinking of a fix in GPS Recorder actually | 13:41 |
akossh | that should work, but then it will only fix a single application | 13:43 |
sicelo | nearly all other applications don't use gps time afaik | 13:45 |
sicelo | or I'm missing something? | 13:45 |
akossh | GPSJinni has the same problem | 13:47 |
sicelo | ah, I don't use it. But yeah, liblocation & modem are unfixable .... so, probably fixing affected foss apps is best bet | 13:48 |
akossh | Either that, or a wrapper library | 13:50 |
brolin_empey | I am not familiar with the specifics involved with this question but are you certain that the date returned by the navigation satellites is still correct? Have you confirmed with another receiver that you are certain is using only GPS, not GLONASS nor any other GNSS, that the date returned by the navigation satellites is still correct? I ask because the format sent by the GPS satellites was briefly changed a few years ago, which affected a customer of my | 15:23 |
brolin_empey | company because the embedded computer my company provides to the customer was not able to handle the change, at least not fully. The USA government (I think? I mean whoever controls that aspect of the GPS.) ended up reverting/undoing the change because the change caused unexpected issues for some receivers. This issue received at least a little media coverage but seemed to be mostly not covered by the media. | 15:23 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!