Closed Bug 970477 Opened 10 years ago Closed 10 years ago

[B2G][Settings]Changing city within Date & Time section to city in a different Time Zone doesn't alter Time field in Settings App

Categories

(Firefox OS Graveyard :: Gaia::Settings, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:1.3+, b2g-v1.2 unaffected, b2g-v1.3 affected)

RESOLVED DUPLICATE of bug 965912
blocking-b2g 1.3+
Tracking Status
b2g-v1.2 --- unaffected
b2g-v1.3 --- affected

People

(Reporter: mclemmons, Unassigned)

References

()

Details

(Keywords: regression, Whiteboard: burirun1.3-3)

User change of the city in the Settings App's Date & Time section to a different city in a different time zone updates the time in the status bar but does not change the time in the time field of the device screen display

Repro Steps:
1) Updated Buri to BuildID: 20140210004002
2) Tap Settings App and select Date & Time and verify set automatically is set to off
3) Tap City field and select city in a different time zone than default (i.e. change from Chicago (Central Time) to Denver (Mountain Time))

Actual:
Time changes in status bar but doesn't change in Time field of Date & Time section of Settings App

Expected:
Time changes in both status bar and Time field of Date & Time section of Settings App

Environmental Variables:
Device: Buri 1.3 MOZ
BuildID: 20140210004002
Gaia: 5c8416fb1ea4a27f172ee6386ab3c19135448506
Gecko: 9c9382f433c0
Version: 28.0
RIL Version: 01.02.00.019.102
Firmware Version: V1.2-device.cfg

Notes:
1. Repro frequency: (5/5, 100%)
2. Link to failed test case: https://moztrap.mozilla.org/manage/case/4000/
3. See attached: (video clip)
4. Intermittently, waiting about a minute after making the city change to a city of a different time zone, the time field updates accordingly on Buri 1.3. (success rate witnessed 2 out of 5 times)
This issue does not reproduce on Buri 1.2 Following the STR in Comment 0 displays the correct time in both the status bar as well as the Time field in the Date & Time section of the Settings App immediately.


Environmental Variables:
Device: Buri 1.2 MOZ
BuildID: 20140210004002
Gaia: 539a25e1887b902b8b25038c547048e691bd97f6
Gecko: 2673f348598c
Version: 26.0
Firmware Version: v1.2-device.cfg
blocking-b2g: --- → 1.3?
QA Contact: mvaughan
In followup to Comment 0, these are the updated Environmental 1.3 variables

Environmental Variables:
Device: Buri 1.3 MOZ
BuildID: 20140210004002
Gaia: 5c8416fb1ea4a27f172ee6386ab3c19135448506
Gecko: 9c9382f433c0
Version: 28.0
Firmware Version: V1.2-device.cfg
This issue started reproducing on the 02/08/14 1.3 build. 

The following regression window was found using tinderbox builds...

- Works -
Device: Buri ENG v1.3 MOZ RIL
BuildID: 20140207172403
Gaia: dd94a5ba3f56ce1e8b378feeecc8a2d7a0b30fc7
Gecko: 44838b3b9bf7
Version: 28.0
Firmware Version: V1.2-device.cfg

- Broken -
Device: Buri ENG v1.3 MOZ RIL
BuildID: 20140208084104
Gaia: dd94a5ba3f56ce1e8b378feeecc8a2d7a0b30fc7
Gecko: edc84cd72067
Version: 28.0
Firmware Version: V1.2-device.cfg
There's tinderbox builds in that range - can you bisect this deeper?
Sorry about that. There is one more tinderbox build that is in between the builds given in the window. Here is the updated regression window...

- Works -
Device: Buri ENG v1.3 MOZ RIL
BuildID: 20140207172403
Gaia: dd94a5ba3f56ce1e8b378feeecc8a2d7a0b30fc7
Gecko: 44838b3b9bf7
Version: 28.0
Firmware Version: V1.2-device.cfg

- Broken -
Device: Buri ENG v1.3 MOZ RIL
BuildID: 20140208031408
Gaia: dd94a5ba3f56ce1e8b378feeecc8a2d7a0b30fc7
Gecko: 06be79299149
Version: 28.0
Firmware Version: V1.2-device.cfg
blocking-b2g: 1.3? → 1.3+
Cervantes - Is this a dupe of bug 965912 by any chance? The problem here seems similar to that bug, except bug 965912 deals with the FTE app where as this bug deals with the Settings app.
Flags: needinfo?(cyu)
I think this is a dupe. The code dealing with timezone is in the shared gaia library.
Flags: needinfo?(cyu)
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.