I've written a small utility to calibrate the software clock on my N810. With this utility, the clock is accurate to about 0.01 sec / day. Previously the clock lost 1.5 seconds / day.

http://olya.com/maemo

Unfortunately, the calibration is lost on reboot.

Excellent idea. Now that you bring it up, I'm actually somewhat surprised that there isn't already some kind of clock sync feature included standard. Wouldn't it be quite easy since it already has GPS receiver build in? Seems like it would to me. Even it it wasn't an automatic service, they should as least have a "sync clock" option in the control panel or something.

Sure you can synchronize to an external source. NTP would be even easier.

The point of this utility is to make the clock intrinsically accurate, so that the need for synchronization is minimized.

You can just installed ntpd and be done with it. I installed it on my N810 and it works fine.

There is no good way to demonstrate that the ntpd frpm the openntp package is actually doing anything.

It needs ntpdate and nptdc added to the package to be of any real value.

In my case, ntpd does not appear to be working at all on the n810. The clock is 2 minutes behind my other systems ...

Yep, I have exactly the same problem with ntpd & openntp. It is reading the defined time servers but not updating the system clock. If I run ntpd with debug in foreground it tells me theres a 166 sec offset but whatever the option is, it never updates the clock.

Better hv a look at how I can submit a bug on that.....