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" <[email protected]> > 收件者: "Greg Weng" <[email protected]>, "dev-gaia" > <[email protected]>, "dev-b2g" <[email protected]> > 寄件備份: 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 > [email protected] > https://lists.mozilla.org/listinfo/dev-gaia > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
