[Flame][Settings]The time zone will change automatically after you turn on "Set automatically" in time setting view.



Firefox OS
3 years ago
3 years ago


(Reporter: Lance(leave from Mozilla), Unassigned)


Gonk (Firefox OS)

Firefox Tracking Flags

(b2g-v2.1 affected, b2g-v2.2 affected)



(2 attachments)



3 years ago
Created attachment 8523731 [details]

[Flame][v2.1][Settings]After you turn on "Set automatically", the time will change to a time in another timezone.
Found time:11:24
See attachment: logcat_1124.txt and 1124.mp4

[2.Testing Steps]: 
Premise: You have connected to local wifi, and turn on "Geolocation".
1.Launch Settings.
2.Tap  "Date & Time".
3.Change "Region" to Asia, "City" to "Chongqing", then change the date and time.
4.Turn on the "Set automatically".

[3.Expected Result]: 
4. The time should display timezone you choose

[4.Actual Result]: 
4. The time will change  to another timezone time automatically,.

[5.Reproduction build]: 
Gaia-Rev        81160ad79e5b4c21967418dd63f1a1d08d77924e
Gecko-Rev       https://hg.mozilla.org/releases/mozilla-

Build-ID        20141116001201
Version         34.0
Device-Name     flame
FW-Release      4.4.2
FW-Incremental  eng.cltbld.20141116.035450
FW-Date         Sun Nov 16 03:55:01 EST 2014
Bootloader      L1TC00011880

[6.Reproduction Frequency]: 
Always Recurrence,5/5


3 years ago
status-b2g-v2.1: --- → affected

Comment 1

3 years ago
Created attachment 8523752 [details]

Comment 2

3 years ago
Same problem on, i.e. the latest default OTA update.

I'm in the Canary Islands. At the moment, i.e. in Winter, the islands are in the timezone WET (UTC+0). When "Set automatically" is selected, then the timezone updates itself to CET (UTC+1). The consequence is that displayed time is one hour off.

It should be possible to select the timezone manually even when date and time are retrieved automatically.
This issue can be repro on Flame 2.2

Flame 2.2 build:
Gaia-Rev        cb1dad4881533bff9f06d47e34983c7b10c04a8c
Gecko-Rev       https://hg.mozilla.org/mozilla-central/rev/b17e7747d3fb
Build-ID        20141224010204
Version         37.0a1
status-b2g-v2.2: --- → affected
Hi Jenny, Could you comment on this, thanks.
Flags: needinfo?(jelee)

Comment 5

3 years ago

Hi Fred,

I believe we've discussed about how "set automatically" should work properly before? When user tap on "set automatically", we should be able to show time correctly.

Maybe you can comment on this :) ?
Flags: needinfo?(jelee) → needinfo?(gasolin)
Currently we have one 'Set Automatically' toggle to auto change both date and time.
So for current version it's a design decision to not let user choose timezone when 'Set Automatically' toggle is enabled.

For future version, I saw in Android there are 2 toggles 'Set Date and time Automatically' and 'Set Timezone Automatically' to control data/time & timezone separately. So they allow user to choose their timezone when 'Set Timezone Automatically' toggle is disabled.

Maybe we could provide similar option for user if its a highly demand function?
Flags: needinfo?(gasolin) → needinfo?(jelee)

Comment 7

3 years ago
Hi Fred,

I think the problem here is that the timezone user chose is not aligned with the timezone system picked. I'm assuming normally they should be the same?
Flags: needinfo?(jelee)
The timezone user chose will be overwritten when we toggle `set Automatically` on.

So if europe user pick america timezone manually then toggle `set Automatically` on, the time will be shifted to europe timezone automatically. The comment 2 report is about the auto timezone did not handle some cases well. 

As described on comment 6, it's a expect behavior in current version and we can consider if we want separate data/time and timezone toggle, or change the behaviors as comment 1 (and maybe we have to deal with first time use to guess a proper timezone) in future version.
Flags: needinfo?(jelee)

Comment 9

3 years ago
I see, thanks Fred!

Hi Lance,

To address the issue you brought up here, design needs to be updated as Fred pointed out. However, given the major changes in plans for 2.2 (i.e. that most of UX changes will not be included in scope) and subsequent near-term releases, the UX team will evaluate all feature and UI requests after v3 planning, which will have a strong impact on future versions of FXOS. Thanks for understanding!
Flags: needinfo?(jelee)


3 years ago
Blocks: 1141258


3 years ago
No longer blocks: 1141258
See Also: → bug 1141258
Duplicate of this bug: 1066329
You need to log in before you can comment on or make changes to this bug.