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

Status: RESOLVED WORKSFORME

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

Description

[Richard Newman [:rnewman]]

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.)

Comment 1

[Jonathan Kew [:jfkthame]]

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.

Comment 2

[Fernando Campo (:fcampo)]

Attachment: 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?

Comment 3

[Jonathan Kew [:jfkthame]]

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.

Comment 4

[Fernando Campo (:fcampo)]

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.

Comment 5

[John Karahalis [:openjck]]

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?

Comment 6

[Ian Tommins ('thelem')]

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.

Comment 7

[Henrik Skupin [:whimboo][⌚️UTC+1]]

(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.

Comment 8

[Ian Tommins ('thelem')]

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.

Comment 9

[Henrik Skupin [:whimboo][⌚️UTC+1]]

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?

Comment 10

[Sam Foster [:sfoster] (he/him)]

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