Closed Bug 1179321 Opened 11 years ago Closed 11 years ago

auto setting in FTE - Displayed date in first time set up does not match selector date when automatic time adjusts date after setup

Categories

(Firefox OS Graveyard :: Gaia::First Time Experience, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: scabral, Unassigned)

Details

(Keywords: foxfood)

Attachments

(2 files)

quoting from e-mail: related to bug 1081862 ; I'm not sure if NTP is being used for FTE.  I believe it kicks in afterwards.  We need a bug in regards to the automatic setting in FTE.
Component: General → Gaia::First Time Experience
QA Whiteboard: [foxfood-triage]
Also experiencing this. Setting date & time to automatic throws incorrect details. Forcing it with manual and then going to automatic once set, throws it to incorrect setting again. Around UTC +11 hours. Reboot also throws to incorrect setting despite now being in manual mode. Now shows 15 Sep 2014 04:36 whilst in manual. Changing to automatic heads to correct local UK time. Reboot again to reproduce, this time in automatic mode and time has thrown ahead 9 hours and 10 minutes to 16:14 with correct date. Toggle to manual, then back to automatic, sets time correctly. July 12 V3 nightly base image, 20150729 gaia & gecko.
Just done a shallow flash with 2.5 nightly (20150821) and time again sets to 7 hours ahead of UTC. Toggled the 'set automatically' switch and it jumps ahead further to 11:15 hours ahead of UTC. Switched to manual. Corrected time. Toggle to 'set automatically' and it resets back to +11:15 hrs. Adding logcat whilst I was performing these actions.
Attached file logcat —
Is this a duplicate of bug 1172609 ?
(In reply to David Ross from comment #2) > Just done a shallow flash with 2.5 nightly (20150821) and time again sets to > 7 hours ahead of UTC. Toggled the 'set automatically' switch and it jumps > ahead further to 11:15 hours ahead of UTC. Switched to manual. Corrected > time. Toggle to 'set automatically' and it resets back to +11:15 hrs. The 'set automatically' switch is in Settings, not FTE. So I'm no longer sure where this bug is occurring. Settings and FTE share some code but are distinct apps. Flagging for qawanted to see if bug 1172609 landing has changed or fixed any of this - can we re-verify that the time is set correctly from Date/Time screen in FTE for the selected timezone, and subsequently in Settings when toggling 'set automatically'.
Keywords: qawanted
Hi Sam, This bug can't be repro on latest Flame KK v2.5 and Aries KK v2.5 by the STR in comment 5. It seems this bug is fixed. Upload the video for your double check, thanks. Actual results: After selected timezone, the time is set correctly and consistent with status bar on 'Date/Time' screen in FTE, and the time is also set correctly and consistent with status bar in Settings when toggling 'set automatically'. See attachment: FlameKK_v2.5.3gp Reproduce rate: 0/10 ---------------------------------------------------------------------------------------- Device: Flame KK 2.5 (unaffected) Build ID 20150906150206 Gaia Revision d5e1a4414cb99c36cfe2da9949e52dbfa6fce963 Gaia Date 2015-09-05 20:22:53 Gecko Revision https://hg.mozilla.org/mozilla-central/rev/56f5ffd44b7f13d5db5bd497018f428dcbb28fc4 Gecko Version 43.0a1 Device Name flame Firmware(Release) 4.4.2 Firmware(Incremental) eng.cltbld.20150906.183003 Firmware Date Sun Sep 6 18:30:19 EDT 2015 Firmware Version v18D v4 Bootloader L1TC000118D0 Device: Aries KK 2.5 (unaffected) Build ID 20150906042207 Gaia Revision d5e1a4414cb99c36cfe2da9949e52dbfa6fce963 Gaia Date 2015-09-05 20:22:53 Gecko Revision https://hg.mozilla.org/mozilla-central/rev/56f5ffd44b7f13d5db5bd497018f428dcbb28fc4 Gecko Version 43.0a1 Device Name aries Firmware(Release) 4.4.2 Firmware(Incremental) eng.worker.20150906.034325 Firmware Date Sun Sep 6 03:43:33 UTC 2015 Bootloader s1
QA Whiteboard: [foxfood-triage] → [foxfood-triage][MGSEI-Triage+]
Flags: needinfo?(sfoster)
Keywords: qawanted
That looks good to me. Lets resolve this and keep an eye out for any reports of similar issues.
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(sfoster)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: