Closed Bug 1021175 Opened 10 years ago Closed 10 years ago

Incorrect version of wallpaper shows the first time you use dialer

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:2.0+, b2g-v1.4 unaffected, b2g-v2.0 verified, b2g-v2.1 verified)

VERIFIED FIXED
2.0 S5 (4july)
blocking-b2g 2.0+
Tracking Status
b2g-v1.4 --- unaffected
b2g-v2.0 --- verified
b2g-v2.1 --- verified

People

(Reporter: marcia, Assigned: drs)

References

Details

(Keywords: regression, Whiteboard: [planned-sprint])

User Story

.

Attachments

(3 files)

Flame, while running: Gaia d2cfef555dabab415085e548ed44c48a99be5c32 SourceStamp 51b428be6213 BuildID 20140605040202 Version 32.0a1 Base image: 10G STR: 1. Flash a Flame device. 2. Change the default homescreen to another picture, either from Gallery or from Wallpapers 3. Make a call from Dialer. Observe the attached screenshots. The first time you make a call using dialer the old wallpaper still shows. In the sequence the green wallpaper was initially selected and changed to a different one- the strawberry.
User Story: (updated)
Attached image First launch of dialer
A video of the bug here could help clarify the impact a bit better.
Keywords: qawanted
(In reply to Jason Smith [:jsmith] from comment #3) > A video of the bug here could help clarify the impact a bit better. Flame 2.0 Video example = https://www.youtube.com/watch?v=VSt28YcLelc
Keywords: qawanted
QA Contact: mclemmons
(In reply to mclemmons from comment #4) > (In reply to Jason Smith [:jsmith] from comment #3) > > A video of the bug here could help clarify the impact a bit better. > > Flame 2.0 Video example = https://www.youtube.com/watch?v=VSt28YcLelc We need a video here that focuses on the bug here & keeps out irrelevant information that's not part of the bug.
Keywords: qawanted
Let's not make a video, we have enough information with the STRs. Could it be a regression of bug 1009596?
Flags: needinfo?(drs+bugzilla)
Keywords: qawanted
(In reply to Anthony Ricaud (:rik) from comment #7) > Let's not make a video, we have enough information with the STRs. Could it > be a regression of bug 1009596? We need a video because I can't make a triage call off of the given information.
Keywords: qawanted
Here's the new video: http://youtu.be/VSt28YcLelc?t=52s I'll look into this.
Assignee: nobody → drs+bugzilla
Status: NEW → ASSIGNED
Flags: needinfo?(drs+bugzilla)
Keywords: qawanted
I backed out bug 1009596 locally and it's still broken.
Assignee: drs+bugzilla → nobody
Status: ASSIGNED → NEW
Keywords: qawanted
UX - If the wallpaper is wrong when you first dial a phone call, then is this a blocker? Note - this is a regression.
Flags: needinfo?(firefoxos-ux-bugzilla)
Keywords: qawanted
Component: Gaia::Wallpaper → Gaia::Dialer
Defer to Victoria but my inclination is to say: not a blocker (up to Vicky though), but believe it is a regression.
Flags: needinfo?(firefoxos-ux-bugzilla) → needinfo?(vpg)
Even if it's not a blocker, I'd like to keep it as a feature-b2g: 2.0 since such regressions are not acceptable imho.
blocking-b2g: --- → 2.0?
triage: regression
blocking-b2g: 2.0? → 2.0+
(In reply to Stephany Wilkes from comment #12) > Defer to Victoria but my inclination is to say: not a blocker (up to Vicky > though), but believe it is a regression. It looks like a decision has already been made around the priority. I agree. This looks really odd and if it's a regression, we should fix it. Thanks.
Flags: needinfo?(vpg)
I'd like a regression range for this.
Whiteboard: qawanted
I think I used the wrong tag for comment 16.
Whiteboard: qawanted
Switching to qawanted to first branch check this on 1.4.
Not able to reproduce it in latest 1.4 version on a buri device Build info ------------ hamachi-v1.4 B-101 Gecko-15e6ea6 Gaia-3419a1f BuildID:20140622204229 Platform version:30.0
Assignee: nobody → drs+bugzilla
Target Milestone: --- → 2.0 S5 (4july)
I believe this is a regression from the landing of the callscreen (thanks Etienne). I have a patch for this, but I've discovered a somewhat bad problem with Blobs which I need to hack a workaround for. I have described this further in bug 1029064.
Status: NEW → ASSIGNED
Keywords: qawanted
See Also: → 1029064
(In reply to Doug Sherk (:drs) from comment #21) > I believe this is a regression from the landing of the callscreen (thanks > Etienne). I have a patch for this, but I've discovered a somewhat bad > problem with Blobs which I need to hack a workaround for. I have described > this further in bug 1029064. So that means this is a regression from bug 990003, right?
(In reply to Jason Smith [:jsmith] from comment #22) > (In reply to Doug Sherk (:drs) from comment #21) > > I believe this is a regression from the landing of the callscreen (thanks > > Etienne). I have a patch for this, but I've discovered a somewhat bad > > problem with Blobs which I need to hack a workaround for. I have described > > this further in bug 1029064. > > So that means this is a regression from bug 990003, right? I believe so, but I didn't bisect it or confirm that, I just jumped straight to fixing it. Based on my fix, I think it's safe to say so.
Depends on: 990003
PR: https://github.com/mozilla-b2g/gaia/pull/20942 I was wrong about the fix required in bug 1029064. Unfortunately I implemented a really complicated blob comparison in attachment 8445567 [details] [diff] [review], and then when I was done, I realized I could just listen for the wallpaper.image setting. Fortunately, it's really simple now.
Attachment #8445619 - Flags: review?(etienne)
Comment on attachment 8445619 [details] [diff] [review] Fix incorrect wallpaper shown if the user changes it. Review of attachment 8445619 [details] [diff] [review]: ----------------------------------------------------------------- 2 questions: - What's you plan for the emergency wallpaper? (it won't be handle by a settings change) - Isn't SettingsListener.observe triggering the callback a first time with |null| and thus calling _onWallpaperReady too early?
Attachment #8445619 - Flags: review?(etienne)
(In reply to Etienne Segonzac (:etienne) from comment #25) > Comment on attachment 8445619 [details] [diff] [review] > Fix incorrect wallpaper shown if the user changes it. > > Review of attachment 8445619 [details] [diff] [review]: > ----------------------------------------------------------------- > > 2 questions: > - What's you plan for the emergency wallpaper? (it won't be handle by a > settings change) I figured we'd cross that bridge when we come to it. I don't think there's any value in leaving a stub function that does nothing. Roughly, I think we could store the wallpaper whenever it's set, and when an emergency call ends, restore that old wallpaper. > - Isn't SettingsListener.observe triggering the callback a first time with > |null| and thus calling _onWallpaperReady too early? I just checked and it's always called with a blob passed in if the pref is set. I think the default value is only used if the pref doesn't exist.
Flags: needinfo?(etienne)
Comment on attachment 8445619 [details] [diff] [review] Fix incorrect wallpaper shown if the user changes it. Review of attachment 8445619 [details] [diff] [review]: ----------------------------------------------------------------- Cool. Thanks for the answers. Let's needinfo German since he's the one asking for the setEmergencyWallpaper to be kept in. It's not a big deal, but I think it's fair to remove it if we know the assets won't come in time for this sprint or the next one.
Attachment #8445619 - Flags: review+
See below :)
Flags: needinfo?(etienne) → needinfo?(gtorodelvalle)
I thought about this some more, and I came up with a better strategy. Now that we have better contact photos code, we handle the emergency call wallpaper there. The contact photos code can store the emergency wallpaper blob, and when it detects that a call is an emergency call, it returns that as the contact photo for that call to CallScreen. This allows us to leverage the wallpaper/photo teardown logic of the contact photos code. I'll still wait for Germán to answer before I push this, though.
Whiteboard: [planned-sprint]
Ups, I mislaid this need-info :O Sorry! Totally fine with removing the mentioned non-really-functional functions ;-) Thanks for asking!
Flags: needinfo?(gtorodelvalle)
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
v2.1 on the left, v2.0 on the right(build 2014/07/07) https://www.youtube.com/watch?v=udOaXTScZjo Hi Vicky, Just want to make sure this is the expected behavior, thanks.
Flags: needinfo?(vpg)
(In reply to Eric Chang [:ericcc] [:echang] from comment #33) > v2.1 on the left, v2.0 on the right(build 2014/07/07) > https://www.youtube.com/watch?v=udOaXTScZjo > Hi Vicky, Just want to make sure this is the expected behavior, thanks. Sorry, what should I look at? If you have a picture assigned to a contact, that's what you should see. if there's no picture associated to a contact, the current wallpaper would be shown. I am asking because I just see examples of contacts with pictures here.
Flags: needinfo?(vpg)
Wallpaper shown at first, then it gets replaced by Contact photos, so we see both, one follows the other, just not sure if that is what we expected or intended to implement for transition like that.
Hi Vicky, so the transition is okay, thanks.. Works okay with these 2 builds. Flame Aurora v2.0 Gaia 1dd043857399c713e3b509c0ed31bdf20326f08b Gecko https://hg.mozilla.org/releases/mozilla-aurora/rev/3f9d7a3a0b7b BuildID 20140707160206 Version 32.0a2 ro.build.version.incremental=109 ro.build.date=Mon Jun 16 16:51:29 CST 2014 B1TC00011220 Flame Master v2.1 Gaia e935f4ff190b76c70d9b2af8856c542a6e4a7546 Gecko https://hg.mozilla.org/releases/mozilla-aurora/rev/3f9d7a3a0b7b BuildID 20140707160206 Version 32.0a2 ro.build.version.incremental=109 ro.build.date=Mon Jun 16 16:51:29 CST 2014 B1TC00011220
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: