Closed Bug 820696 Opened 12 years ago Closed 7 years ago

FTE: Default time is not automatically/correctly set by the first-run settings.

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-basecamp:-, b2g18+, b2g-v2.0 affected, b2g-v2.2 affected)

RESOLVED WONTFIX
blocking-basecamp -
Tracking Status
b2g18 + ---
b2g-v2.0 --- affected
b2g-v2.2 --- affected

People

(Reporter: airpingu, Unassigned)

Details

(Whiteboard: Permafail)

STR: ==================== 0. 2012/12/12 build. 1. Reflash everything to simulate the first-run process. 2. *Skip* all the first-run settings. 3. The system time shown on the Home screen (or status bar) is not correct. Note: ==================== I'm not sure if the step #3 is expected or not because I didn't choose the timezone/date/time at the first-run settings. However, when you go to the "Date & Time" in the settings app later, it shows "Set automatically" is enabled. If you disable and enable it again, you will get the correct system time. Suggestions: ==================== We should disable the "Set automatically" in the settings app if users manually set the system time at the first-run settings. Also, we can provide another "Set automatically" option at the first-run settings. If users choose to use it, then the "Set automatically" in the settings app will be enabled by default.
(In reply to Gene Lian [:gene] from comment #0) > Suggestions: > ==================== > We should disable the "Set automatically" in the settings app if users > manually set the system time at the first-run settings. Also, we can provide > another "Set automatically" option at the first-run settings. If users > choose to use it, then the "Set automatically" in the settings app will be > enabled by default. Well, after some thoughts, I think disabling the "Set automatically" in the settings app is not a good idea, because users would never know to enable it again and thus wasting the feature.
blocking-basecamp: --- → ?
TRIAGE: We should modify the logic of FTU time settings screen to disable 'automatically set time' or shows a checkbox to let the user disable it because by default it's enabled. Or we should remove the FTU time settings...
(In reply to Alive Kuo [:alive] from comment #2) > TRIAGE: We should modify the logic of FTU time settings screen to disable > 'automatically set time' or shows a checkbox to let the user disable it > because by default it's enabled. Or we should remove the FTU time settings... Also, in current build, if the user changes any thing in time screen of FTU, The change would be overwritten by 'auto-set-time' setting when next time booting because the platform side is updating the time every time you boot. This is a broken feature in FTU...
Triage: Need UX input
Flags: needinfo?(jcarpenter)
related to bug 826359. if the decision in bug 826359 is to keep the timezone selection page, then this bug is to decide if automatic timeozone option should be added
(In reply to Alive Kuo [:alive] from comment #2) > TRIAGE: We should modify the logic of FTU time settings screen to disable > 'automatically set time' Let's start by doing this. > or shows a checkbox to let the user disable it because by default it's enabled. If we have time it would be great to also look at adding this, but I don't think it's must have for v1. Or we should remove the FTU time settings...
Flags: needinfo?(jcarpenter)
(In reply to Josh Carpenter [:jcarpenter] from comment #6) > (In reply to Alive Kuo [:alive] from comment #2) > > TRIAGE: We should modify the logic of FTU time settings screen to disable > > 'automatically set time' > > Let's start by doing this. > > > or shows a checkbox to let the user disable it because by default it's enabled. > > If we have time it would be great to also look at adding this, but I don't > think it's must have for v1. > > Or we should remove the FTU time settings... I vote for this. 'Auto set for you' should be enabled for most cases for the user. Or: If the user doesn't change anything in FTU, keep it as enabled. If something is changed, disable the 'automatically set'.
I think that 'Auto set for you' should be a general case for the user too.
We would take a patch for this.
blocking-basecamp: ? → -
tracking-b2g18: --- → +
Whiteboard: testrun 2
Whiteboard: testrun 2 → testrun 2, [2.0-flame-test-run-2]
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Whiteboard: testrun 2, [2.0-flame-test-run-2] → Permafail
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
QA Whiteboard: [QAnalyst-Triage+][lead-review+] → [QAnalyst-Triage?][lead-review+]
Flags: needinfo?(dharris)
QA Whiteboard: [QAnalyst-Triage?][lead-review+] → [QAnalyst-Triage+][lead-review+]
Flags: needinfo?(dharris)
Ted, can you update this bug with our current status and plans? Is this bug still valid and actionable? ISTM the flow should be something like this: 1) The time should be automatically correct for the default timezone 2) If we can get more timezone info from the network or SIM, we replace the default on the Date & Time screen 3) In FTE, we offer the user the ability to change or implictly confirm their timezone Do we actually need the time picker here? If we cant get this automatically, perhaps we should direct user to update in Settings?
Flags: needinfo?(tclancy)
Flags: needinfo?(ted.clancy)
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.