It failed for me - N810 / OS2008 latest release. I'm in Pacific time zone in the U.S. It's possible that the unit was off at 2 am but I can't be sure.

I have submitted this as Bug 3843 with a pointer back to this thread.

I wish it would take the hour from a server, like my PC.

Your server might not have the right time. But there are sources for the accurate time, including Internet time servers or GPS.

None of that will help it adjust for the right time zone or Daylight Savings though.

Worked fine here... I wasn't monitoring it at 0200, but it was right yesterday and is right now.

Elia, there's a couple or three NTP clients available that will keep it synced to an NTP server; there's also one to sync from a GPS whenever the GPS is running (particularly slick for N810s, but also for N800s with BT/USB GPS).

Time changed OK but the software knocked my alarm back by an hour. That made no sense.

I'll look into the NTP clients, any reccomendations? About the GPS, I've been meaning to get a BT one, but the keyboard experience hasn't left me too eager to try ebay accesory shopping again. I may be convinced if the dollar goes back down. Shtoopid crisis thingy, now I can't buy any electronics ¬¬ .

Not really; haven't used any of them.

Actually now that you mention it.. I notice that too now. (good thing I would've woken up early for my class for no reason).

NTP client is the most used method. I believe openntpd is the package you want. Like other Linux systems, the Nokia OS honors daylight savings changes based on yuor hardware clock. Accuracy of the clock setting isn't considered.

I added the following to my /etc/init.d/gpsclockd

# Added 23 Oct 08 to automatically get good time hack at bootup.
sleep 30 #needed to get wireless networking time to connect
rdate -nv 192.168.1.114 >> /home/user/time_hack.log # Get hack from tubuntu2
adjust-clock -1.500 >> /home/user/time_hack.log # Calibrate system clock
/mnt/initfs/usr/bin/retutime -I # Set hardware clock
echo Hardware clock updated to system time. >> /home/user/time_hack.log
date >> /home/user/time_hack.log
echo ------ >> /home/user/time_hack.log

# Back to our regularly scheduled programming

You need to install gpsclockd, adjust-clock, and rdate.

It grabs the correct time from a desktop machine that has ntpd running. It shaves the clock 1.5 seconds/day. It seems new quartz clocks run fast to counter crystal aging. Then saves the corrected system time to the hardware clock.

The time hacks get dumped to a log file so you can correct your time shave.

Log file looks like:

~ $ cat time_hack.log
#Super cheesy time keeping log file


Hardware clock updated to system time
Hardware clock updated to system time.
Current clock adjustment: -1.000 sec/day
Hardware clock updated to system time.
Thu Oct 23 15:21:15 PDT 2008
------
Thu Oct 23 15:29:35 PDT 2008
rdate: adjust local clock by 2.625423 seconds
Current clock adjustment: -1.000 sec/day
Hardware clock updated to system time.
Thu Oct 23 15:29:36 PDT 2008
------
Tue Oct 28 16:50:38 PDT 2008
rdate: adjust local clock by -4.928068 seconds
Current clock adjustment: -1.000 sec/day
Hardware clock updated to system time.
Tue Oct 28 16:50:39 PDT 2008
------
Sat Nov 1 07:57:22 PDT 2008
rdate: adjust local clock by -3.460317 seconds
Current clock adjustment: -1.000 sec/day
Hardware clock updated to system time.
Sat Nov 1 07:57:23 PDT 2008
------
Sun Nov 2 18:52:43 PST 2008
rdate: adjust local clock by -1.302905 seconds
Current clock adjustment: -1.000 sec/day
Hardware clock updated to system time.
Sun Nov 2 18:52:44 PST 2008
------


Works using OS2008 on an n800.