Bug: automatic time zone set not correct

Correct. Some networks do not support time from there towers. There is a protocol for this but alas can't remember its name.

@slava: How would a successful answer look like? I get an empty array:

    [nemo@Jolla ~]$ dbus-send --system --print-reply --type=method_call --dest=org.ofono /ril_0 org.ofono.NetworkTime.GetNetworkTime
method return sender=:1.14 -> dest=:1.868 reply_serial=2
   array [
   ]

It means that Jolla never received the NITZ (Network Identity and Time Zone) message from your operator (MTS?) so it has no idea what the real timezone is. MCC (250) only tells you which country you are in. Most Russian people live in the Moscow time zone, so it's the best bet :) The good answer would look like this (MTS/St.Petersburg):

[nemo@Jolla ~]$ dbus-send --system --print-reply --type=method_call --dest=org.ofono /ril_0 org.ofono.NetworkTime.GetNetworkTime
method return sender=:1.13 -> dest=:1.1816 reply_serial=2
   array [
      dict entry(
         string "UTC"
         variant             int64 1420621143
      )
      dict entry(
         string "DST"
         variant             uint32 0
      )
      dict entry(
         string "Received"
         variant             int64 79556
      )
      dict entry(
         string "Timezone"
         variant             int32 10800
      )
      dict entry(
         string "MobileCountryCode"
         variant             string "250"
      )
      dict entry(
         string "MobileNetworkCode"
         variant             string "01"
      )
   ]

My operator (Beeline/Ufa) also doesn't sent NITZ message. The array is empty. Android phones have option for timezone in settings and it can be customized even when automatic time update enabled.

Thanks, @slava! I am currently in Germany, on Vodafone's network. It seems operators do not take care of any feature not generating any profit.

My operator Motiv in Yekaterinburg sends NITZ messages. I have this:

   array [
  dict entry(
     string "UTC"
     variant             int64 1425716124
  )
  dict entry(
     string "DST"
     variant             uint32 0
  )
  dict entry(
     string "Received"
     variant             int64 3026405
  )
  dict entry(
     string "Timezone"
     variant             int32 18000
  )
  dict entry(
     string "MobileCountryCode"
     variant             string "250"
  )
  dict entry(
     string "MobileNetworkCode"
     variant             string "35"
  )

]

But there are a some questions: 1) What is the time format? "UTC" value is 1425716124. If it is Unix time that it is Sat, 07 Mar 2015 08:15:24 GMT. But now the time is Mon, 09 Mar 2015 14:04:00 GMT. 2) What is "Received" value? (3026405). 3) The "Timezone" value is 18000. I have UTC+5 (MSK+2, RTZ 4). How to convert that value?))

It will be good if somebody has information about NITZ protocol.

My Jolla also selects US Eastern time when connected to T-Mobile in US Mountain time. Here is the output from GetNetworkTime:

[nemo@Jolla ~]$ dbus-send --system --print-reply --type=method_call --dest=org.ofono /ril_0 org. ofono.NetworkTime.GetNetworkTime method return sender=:1.9 -> dest=:1.29339 reply _serial=2 array [ dict entry( string "UTC" variant int64 1455489508 ) dict entry( string "DST" [nemo@Jolla ~]$ ) dict entry( string "Received" variant int64 712255 ) dict entry( string "Timezone" variant int32 -25200 ) dict entry( string "MobileCountryCode" variant string "310" ) dict entry( string "MobileNetworkCode" variant string "260" )

Later in Germany, as expected as T-Mobile.DE is not supporting this, and also 6310i has nothing to react on:

[nemo@Jolla ~]$ dbus-send --system --print-reply --type=method_call --dest=org.ofono /ril_0 org.ofono.NetworkTime.GetNetworkTime
method return sender=:1.7 -> dest=:1.906 reply_serial=2
   array [
   ]

At wikipedia dot org there is an article about whether various mobile provider supporting Network Identity and Time Zone (NITZ) , In addition there at reference '5' it is stated that the time feature is about a kind of license to buy from Mobile System Supplier.