To have your FreeRunner display time appropriate to your local timezone, update the /etc/localtime symlink to point to the file in /usr/share/zoneinfo that represents your timezone. For example, in an SSH session to the phone, or in a terminal running on the phone:

(Based on [http://n2.nabble.com/Date-%2B-NTP-tp675145p675163.html this post on the support mailing list])

+

+

You may want to try this if the above returns something like "file exists".

+

# ln -sf /usr/share/zoneinfo/CST6CDT /etc/localtime

+

the -f (--force) removes existing destination files. (CQ).

== Setting the date/time automatically with NTP ==

== Setting the date/time automatically with NTP ==

−

If your Freerunner is connected to the internet, you can instead set the time automatically:

+

If your FreeRunner is connected to the internet, you can instead set the time automatically:

−

opkg install ntpclient

+

opkg install ntpclient

−

ntpclient -s -h pool.ntp.org

+

ntpclient -s -h pool.ntp.org

−

If your Freerunner is connecting to the internet through a USB host, make sure you allow UDP traffic to pass through on port 123 (NTP) on your host machine or you may get a "no route to host" error from ntpclient.

+

If your FreeRunner is connecting to the internet through a USB host, make sure you allow UDP traffic to pass through on port 123 (NTP) on your host machine or you may get a "no route to host" error from ntpclient.

+

+

Have a look over [https://wiki.muc.ccc.de/openmoko#freerunner1 over here] where this process is automated whilst udhcpc is started, which happens automatically for wifi connections initiated by Mofi and friends.

== Syncing the hardware clock ==

== Syncing the hardware clock ==

Line 34:

Line 78:

hwclock --systohc

hwclock --systohc

−

Note: if you run the [[ASU]] image, hwclock will not work. Instead you can use:

+

Note:

+

If you run the [[ASU]] or [[Qtopia / Qt Extended on FreeRunner|Qtopia]] image, hwclock will not work. The missing /dev/misc/rtc could be establish with

+

+

mkdir /dev/misc

+

ln -s /dev/rtc /dev/misc/rtc

+

+

but the device is usually busy due to the atd daemon.

+

Instead you can use this command causing atd to write the current time into the rtc:

−

echo "W\n" > /var/spool/at/trigger

+

echo -e "W\n" > /var/spool/at/trigger

−

Here is a link from the community mailing list for using hwclock with the [[ASU]] image

+

Here is a link from the community mailing list for using hwclock with the [[ASU]] image:

−

:http://lists.openmoko.org/pipermail/community/2008-July/023849.html

+

:http://lists.openmoko.org/nabble.html#nabble-td584362

== Setting the date/time automatically with gps ==

== Setting the date/time automatically with gps ==

Line 45:

Line 96:

[http://projects.openmoko.org/projects/gpv/ GPS Sight] has a button to sync the hardware clock to the gps clock.

[http://projects.openmoko.org/projects/gpv/ GPS Sight] has a button to sync the hardware clock to the gps clock.

−

First you have to make sure gps works on you neo. You can do that by following the steps in the [[Getting_Started_with_your_Neo_FreeRunner#Use_the_GPS]].

+

First you have to make sure gps works on you neo. You can do that by following the steps in the [[Howto_Test_Your_GPS_with_agpsui]].

The last step is the actual syncing of the clock. For this, simply run the GPS Sight program from the main menu, wait for it to find the gps time and click the button labeled "Sync clock".

The last step is the actual syncing of the clock. For this, simply run the GPS Sight program from the main menu, wait for it to find the gps time and click the button labeled "Sync clock".

Line 57:

Line 108:

Presumably it might also be possible to use gpspipe (or something else) to set the date once you have a gps fix automatically? In addition, the phone stack should set the date, time, and timezone once connected to a network.

Presumably it might also be possible to use gpspipe (or something else) to set the date once you have a gps fix automatically? In addition, the phone stack should set the date, time, and timezone once connected to a network.

−

[[Category:Documentation|Date and Time]]

+

[[Category:Middleware settings]]

−

[[Category:Guides|Date and Time]]

+

−

[[Category:Preferences|Date and Time]]

+

Latest revision as of 05:24, 7 August 2012

Linux systems (such as the FreeRunner) prefer that the system clock be set to universal time (UTC). Then, you will need to configure the timezone to display the time adjusted to local time.

To have your FreeRunner display time appropriate to your local timezone, update the /etc/localtime symlink to point to the file in /usr/share/zoneinfo that represents your timezone. For example, in an SSH session to the phone, or in a terminal running on the phone:

If your FreeRunner is connected to the internet, you can instead set the time automatically:

opkg install ntpclient
ntpclient -s -h pool.ntp.org

If your FreeRunner is connecting to the internet through a USB host, make sure you allow UDP traffic to pass through on port 123 (NTP) on your host machine or you may get a "no route to host" error from ntpclient.

Have a look over over here where this process is automated whilst udhcpc is started, which happens automatically for wifi connections initiated by Mofi and friends.

Presumably it might also be possible to use gpspipe (or something else) to set the date once you have a gps fix automatically? In addition, the phone stack should set the date, time, and timezone once connected to a network.

For more information on Linux timekeeping, see Linux, Clocks, and Time. (But ignore mentions of /etc/sysconfig/clock. That doesn't apply to the Openmoko environment.)

Setting the date/time using "date"

To change the date on your Freerunner, issue one of the following commands:

date -s MMDDhhmm
date -s MMDDhhmmYYYY
date -s MMDDhhmmYYYY.ss

where MM is the month, 01-12; DD is the day, 01-31; hhmm is the time, 0000-2359; YYYY is the optional year, and .ss is the optional seconds.

Setting date/time from your linux box

ssh root@openmoko "date -s `date --utc +%m%d%H%M%Y.%S`"

Setting the date/time automatically with NTP

If your Freerunner is connected to the internet, you can instead set the time automatically:

opkg install ntpclient
ntpclient -s -h pool.ntp.org

If your Freerunner is connecting to the internet through a USB host, make sure you allow UDP traffic to pass through on port 123 (NTP) on your host machine or you may get a "no route to host" error from ntpclient.

Syncing the hardware clock

No matter which method you used above, sync the hardware clock with the system time to make your change persist over reboots:

hwclock --systohc

Note: if you run the ASU image, hwclock will not work. Instead you can use:

echo "W\n" > /var/spool/at/trigger

Here is a link from the community mailing list for using hwclock with the ASU image

The last step is the actual syncing of the clock. For this, simply run the GPS Sight program from the main menu, wait for it to find the gps time and click the button labeled "Sync clock".

Future Work

Presumably it might also be possible to use gpspipe (or something else) to set the date once you have a gps fix automatically? In addition, the phone stack should set the date, time, and timezone once connected to a network.