If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Date & Time picker starts in 1980, doesn't use NTP

RESOLVED WORKSFORME

Status

Firefox OS
Gaia::First Time Experience
RESOLVED WORKSFORME
5 years ago
3 years ago

People

(Reporter: rnewman, Unassigned)

Tracking

unspecified
ARM
Gonk (Firefox OS)

Firefox Tracking Flags

(b2g18? affected)

Details

Attachments

(1 attachment)

(Reporter)

Description

5 years ago
Setting up a new phone on Mozilla wifi. I'm going to leave it in March 1980, because this is agonizing!

Can we get a saner starting year, and maybe NTP support? And possibly a better date picker that allows direct entry?

(Feel free to morph/split/dupe this bug.)
I was just going to file this, having paged through from 1980 to 2012, month by month... ugh! Some kind of direct year entry, at least, is sorely needed for a reasonable date-picker interface.
Created attachment 700422 [details]
current date picker

I'm kinda lost here... are we talking about the same date picker?
I don't see too much trouble on changing year on the one used in First Time Experience. Maybe we are using different builds, or the tags are wrong?
In the build that was preinstalled on a Unagi phone I just received, I was presented with a "picker" that showed a calendar-like page for the month, and needed to page through from 1980 to 2013 one month at a time. However, after applying the latest update, I see the new picker as in your screenshot. So I think this has been addressed; it's just that devices currently going out to devs/testers arrive (naturally) with an older build.
Sorry about the delay of the answer, I was focusing on other bugs.

So, after your comments, I'm taking the liberty of closing this bug down, as it was fixed on latest builds.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
I also noticed the date defaulting to 1980 when I was setting up my Geeksphone Peak. Was this corrected in the latest builds as well?
This was just mentioned in a conference keynote as poor UI! https://prague2013.drupal.org/keynote/aral-balkan

I can't test this myself, but if the user is presented with attachment 700422 [details] on first use then this only solves one of the three things mentioned in the summary (forcing to go month by month).

1980 is still a silly default and means users need to scroll past 30+ years to find the current year. Even just hard coding 2013 as the default would be much better.

I've reopened and updated the summary to reflect this.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Summary: Date & Time picker starts in 1980, doesn't use NTP, forces me to scroll month by month → Date & Time picker starts in 1980, doesn't use NTP
(In reply to Jonathan Kew (:jfkthame) from comment #3)
> and needed to page through from 1980 to 2013 one month at a time. However,
> after applying the latest update, I see the new picker as in your
> screenshot. So I think this has been addressed; it's just that devices
> currently going out to devs/testers arrive (naturally) with an older build.

Jonathan, which build have you flashed? I assume it is not 1.1 because there I still see the problem. Also I think I have seen the problem on my Keon with a 1.2 nightly a couple of days ago. Please let us know where is should have been fixed and most likely the bug number too.
Status: REOPENED → NEW
status-b2g18: --- → affected
tracking-b2g18: --- → ?
Henrik: This bug as opened is to have a sensible default date.

Jonathan (and comments 2 and 4) was talking about a different bug, to improve the date picker. That has been fixed somewhere else.
Right, so it's not only this date&time picker which doesn't have a good initial state but also the FTE pane for selecting the timezone and date&time. It would be great if we could use NTP for that too, given that a mobile connection or even WiFi should be available at this time (if configured). Or shall I create a new bug for that issue?
I've not seen this or come across recent reports of this issue. Closing as works-for-me. I think the suggestions in comment #9 fall under bug #820696
Status: NEW → RESOLVED
Last Resolved: 5 years ago3 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.