Hey Gareth, It might have something to do with the flash script and the time function not setting the time correctly initially. Do you sync the time automatically via NTP and have a wifi or SIM card in the device? (i.e. automatically set time/date in the settings).
I think the bugs revolve somewhere around those items. I have been having a hard time replicating consistently. Regards, Naoki On Dec 29, 2014, at 11:36 AM, Gareth Aye <gareth....@gmail.com> wrote: > Difficult to diagnose currently since flashing latest mozilla-central gaia + > gecko makes the regions and cities disappear from the settings selector. > Currently, my flame says it's 6:56pm which isn't correct in any timezone > (it's 2:35 EST right now) and toggling the set automatically radio button to > try to coerce time sync into triggering isn't working :/ > > On Mon, Dec 29, 2014 at 1:40 PM, Gareth Aye <gareth....@gmail.com> wrote: > Just to add a little bit more information, the only ways that gaia interacts > with the platforms' timing facilities are through the standard Date api and > then also via mozTime in the ftu and settings apps to call > navigator.mozTime.set. Nothing looks particularly sketchy in gaia. > > On Mon, Dec 29, 2014 at 1:20 PM, Gareth Aye <gareth....@gmail.com> wrote: > I think this issue still exists. My sms messages are often scrambled like > Julien mentioned, notifications fire at the wrong time, and hacking on > calendar can be a PITA. It seems like no one is actively working on it. This > seems like the root cause behind a whole host of issues across a number of > apps (I am currently investigating a few issues related to timezone and alarm > issues for calendar). As far as I can tell from some of the comments in the > bugs that :whsu collected, this is also happening across multiple devices. > Does this perhaps qualify as a DOM bug? > > On Mon, Jun 30, 2014 at 5:53 AM, Greg Weng <snowma...@gmail.com> wrote: > Thanks William! > > 2014-06-30 17:29 GMT+08:00 William Hsu <w...@mozilla.com>: > > The other devices seemed to have the same problem. > > - https://bugzilla.mozilla.org/show_bug.cgi?id=1011592 > > - https://bugzilla.mozilla.org/show_bug.cgi?id=1022877 > > - https://bugzilla.mozilla.org/show_bug.cgi?id=1031573 > > - https://bugzilla.mozilla.org/show_bug.cgi?id=1002399 > > > > I have helped nominate this bug. > > Have a nice day! > > > > > > Cheers, > > William > > > > On Mon, 2014-06-30 at 01:51 -0700, Greg Weng wrote: > > > > Well, one of the problems is that I don't know which component this bug > > belongs to. The only thing I'm sure is this seems not like a Gaia issue. > > > > ----- 原始郵件 ----- > > 寄件者: "Marco Zehe" <mz...@mozilla.com> > > 收件者: "Greg Weng" <snowma...@gmail.com>, "dev-gaia" > > <dev-g...@lists.mozilla.org>, "dev-b2g" <dev-b2g@lists.mozilla.org> > > 寄件備份: 2014 6 月 30 星期一 下午 3:42:06 > > 主旨: Re: Has anyone notice that sometime the clock would be incorrect on > > Flame? > > > > Hi Greg, > > > > I've seen this for weeks and thought this is so obvious that this has > > been long reported. I'm in Germany, CEST timezone, and while the > > timezone is correct, my Flame is sometimes an hour, sometimes three, > > sometimes only 30 minutes ahead. But almost never at the correct time. > > > > I also don't have STR, but couldn't imagine this was solely happening on > > my device, so didn't bother reporting a bug. So feel free to file a bug > > on this, I can definitely confirm. > > > > Marco > > > > On 30.06.2014 09:25, Greg Weng wrote: > >> Hi all, > >> > >> I use Flame daily and sometime the clock (not the app) would be > >> incorrect. For example, I've got alarmed at 6:00 AM while the phone > >> shows it's 8:00 AM (because I set a alarm at 8:00 AM). I'm pretty sure > >> this is not caused by time zone issue because after I cancel the alarm > >> and try to figure the time in Settings panel, the clock suddenly jump > >> to about 10:00 AM and it's still incorrect. I've experienced this at > >> least twice, although in the later case it's only faster about 20 mins > >> than the real time. > >> > >> I send this mail rather than report bug because I (unfortunately) > >> can't give a STR, although I suspect that it seems related to NTP then > >> charing the phone (I did these steps at the first case). And today one > >> of my colleague also noticed me about this bug, so I can make sure > >> that this is not my own failure. In my opinion, this is a really > >> serious bug because when you can only rely on your phone to get the > >> current date time (just like the modern people usually do), it may > >> cause serious trouble when you miss some date just because the alarm > >> (and the date tome) doesn't work correctly. > >> > > > > _______________________________________________ > > dev-gaia mailing list > > dev-g...@lists.mozilla.org > > https://lists.mozilla.org/listinfo/dev-gaia > > _______________________________________________ > > dev-b2g mailing list > > dev-b2g@lists.mozilla.org > > https://lists.mozilla.org/listinfo/dev-b2g > > > > > > > > -- > Greg Weng > > http://about.me/snowmantw > > Understand y f = f [ y f ] ; lose last remaining non-major friend > -- Anonymous > _______________________________________________ > dev-gaia mailing list > dev-g...@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-gaia > > > > -- > Best, > Gareth > > > > > -- > Best, > Gareth > > > > > -- > Best, > Gareth > > _______________________________________________ > dev-gaia mailing list > dev-g...@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-gaia
_______________________________________________ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
