[oobe] Initialize the system date and time

[Mika Meskanen]

Expected result: Greeter shows actual and local time and date.

Actual result: Apparently clock starts ticking from 1/1/2000 12:00 AM every time phone is flashed.

[Bill Filler (bfiller)]

So in 11-29-12 build, the time and date are live for me. They update correctly. The only problem is the timezone is wrong and it's showing UK time even though I'm in the US.

Is there some locale/timezone setting that we need to set that could be read in?

@mika
Your phone might not have the date set properly on it that's why you might be seeing it reset. Type "date" after shelling into the phone to see what the system date is set to.

[Florian Boucault (fboucault)]

Any way to have the date set automatically with ntp?

[Ricardo Salveti (rsalveti)]

On Sat, Dec 1, 2012 at 11:34 AM, Florian Boucault
<email address hidden> wrote:
> Any way to have the date set automatically with ntp?

Probably, and I believe it'd be our best option here (but it would
require the user to connect to a valid network).

The phone has a default date of 01/01/2000 00:00, so until you set the
time by hand (or calling ntp), it'll still show the wrong values. Once
I get at London I'll give it a shot to see how it works with our setup
(aka see if it also sets up the clock for the android side, so it can
stay between reboots).

[Bill Filler (bfiller)]

@rsalveti
I this fixed comitted? I know it will be manual for user to setup correct timezone via dpkg-reconfigure tzdata, but will your phones make phones come up with correct date now?

[Ricardo Salveti (rsalveti)]

ntpdate should be working fine now once the user connects phone at a valid network. The only piece that will still need manual interaction is the timezone settings.

I believe what we can do, until we can set timezones at the indicator-time, is to automatically set it to CES's timezone at build time.

[Ricardo Salveti (rsalveti)]

ntpdate is already working once connected, but for the default timezone we have the following MR: https://code.launchpad.net/~manhattan-team/manhattan/manhattan-quantal-armhf_setting_default_timezone/+merge/140937

[Bill Filler (bfiller)]

this won't get fixed till we have an first boot wizard to allow the user to set the proper timezone.

[Pat McGowan (pat-mcgowan)]

This is also related to NITZ support