Closed Bug 851692 Opened 11 years ago Closed 11 years ago

clock on homescreen is out of date from when screen turned on until next minute ticks (or a little sooner)

Categories

(Firefox OS Graveyard :: Gaia::Homescreen, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:tef+, b2g18 verified, b2g18-v1.0.1 verified)

VERIFIED FIXED
blocking-b2g tef+
Tracking Status
b2g18 --- verified
b2g18-v1.0.1 --- verified

People

(Reporter: dbaron, Assigned: crdlc)

References

Details

(Keywords: regression)

Attachments

(4 files)

When I press the power button on the phone and unlock it, the clock on the homescreen shows an out-of-date time until the next change in minute.  This is really bad; one of the common things people the clock on the homescreen for is to check what time it is.

Steps to reproduce:
 1. don't use the phone for a few minutes
 2. press the power button
 3. unlock the phone
 4. look at the clock on the homescreen

I'm seeing this on a self-built user build of v1-train for Otoro, built from earlier today.

I'll attach a screenshot shortly.
Attached image screenshot
The clock in the upper left (3:27PM) is correct.  The big clock in the middle (3:05PM) is wrong.
I'd note, however, that the lockscreen is correct when this happens; it's the clock on the homescreen *after* unlocking that's wrong.
And I'm reasonably confident this regressed within the past few weeks.
Keywords: regression
I cannot reproduce after uplifting this one

https://github.com/mozilla-b2g/gaia/commit/95d5b5125a81f14b985fd8b2d919718fb35e8933

Please reopen if you find the same problem, thanks
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
I am sure that it was the problem because if you see the screenshot there is not orange bar on the top :)
blocking-b2g: tef? → ---
Should that also be uplifted to v1.0.1, or is it not a problem there?
Yes, and it was uplifted as well. See

https://bugzilla.mozilla.org/show_bug.cgi?id=837062#c22
Attached image new screenshot
Although I hadn't seen it for a few days (though I hadn't been using my phone much because of bug 850175), I'm seeing this again on v1-train, specifically with:
  gaia a78ebf426840b5ef08c0cc3e437ad30aba3e2528
  gecko 115b32b8f8fc435a0ddc31a0f7dc755ab5f609ca
That said, I've also seen cases where it gets better sooner than the next minute tick.
Status: RESOLVED → REOPENED
blocking-b2g: --- → tef?
Resolution: WORKSFORME → ---
Summary: clock on homescreen is out of date from when screen turned on until next minute ticks → clock on homescreen is out of date from when screen turned on until next minute ticks (or a little sooner)
Please STR. E.g. I stay in landing page, the phone goes away and after unlocking the date is wrong.
The steps to reproduce in comment 0 show the bug more often than not for me.  (I'm guessing when they don't it's because the phone has been active.)

In case it makes a difference:
 * I do have a lock code enabled
 * When I lock the phone, it's typically on the "Home" screen (i.e., the screen I get after pressing the home button, which is the one with the clock)
Assignee: nobody → crdlc
I am going to try to reproduce the bug with current v1-train, thanks
Hi David, I cannot reproduce the problem but I've created a patch in order to force always the update of the time when the homescreen goes to background to foreground. Could you test this patch?
Attachment #728901 - Flags: feedback?(dbaron)
I think the patch helps.  I've checked my phone three or four times over the course of the afternoon, with the patch applied, and haven't seen the bug yet.
ok, if you cannot reproduce the problem with this patch we could land this one as solution for our bug, are you agree? thanks
Comment on attachment 728901 [details] [diff] [review]
This patch forces to update the time when homescreen goes from background to foreground

Sounds good to me -- assuming the patch gets appropriate reviews (and if needed, approvals), of course.
Attachment #728901 - Flags: feedback?(dbaron) → feedback+
Given this problem has been only reproduced in v1-train I suggest we land this in master (after r+) and request approval or leo nomination. If someone can reproduce it in v1.0.1 we will request uplift for 1.0.1.
blocking-b2g: tef? → leo?
Attached file Patch v1
Patch to the rescue
Attachment #730103 - Flags: review?(21)
blocking-b2g: leo? → leo+
https://github.com/mozilla-b2g/gaia/commit/45506a722460094cd69e8fa419874cf2eb73fa2e
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
Uplifted commit 45506a722460094cd69e8fa419874cf2eb73fa2e as:
v1-train: bba9a840a261e2503b95482e6cce2927e1f9f398
It seems that is has been reproduced in v1.0.1 too (see bug 859790) marking tef+ and affected.
blocking-b2g: leo+ → tef?
blocking-b2g: tef? → tef+
Tested on an Inari using the following build :

Gecko  http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/c3ee6b445cf5
Gaia   393a946b9d60294697838c5ef7e0548d47c3281a
BuildID 20130419070202
Version 18.0

Could not reproduce it.
Can't uplift directly to v1.0.1 because of conflicts... please needinfo me if you need help uplifting.
Flags: needinfo?(crdlc)
v1.0.1: 07b934544bcb2ec953bafd5c4ffced721d9ec4df
Flags: needinfo?(crdlc)
This issue has been verified fixed on Leo Build ID: 20130426070204

Environmental  Variables:
Kernel Date: Mar 15
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/6c2493de1441
Gaia: c9046a7acef33328977840176ff5574720d2c74c

This issue has also been verified fixed on Inari Build ID: 20130429070204

Kernel Date: Feb 21
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/45aa5ba0ed53
Gaia: cf2d4136f0ebc66039637fdbeb72ed184dfbc0f2
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: