Closed
Bug 1209536
Opened 10 years ago
Closed 10 years ago
[Dialer] Callscreen can't be dismissed in some situations
Categories
(Firefox OS Graveyard :: Gaia::System::Window Mgmt, defect)
Tracking
(blocking-b2g:2.5+)
RESOLVED
FIXED
| blocking-b2g | 2.5+ |
People
(Reporter: julienw, Assigned: etienne)
References
()
Details
Attachments
(1 file)
STR:
1. Calling somebody who doesn't answer.
2. Press the "hang up" button.
3. Very quickly, before the callscreen disappear, you have the time to press home, show the utility tray, and press the "callscreen" notification line.
=> what happened to me is that the callscreen panel would then never disappear: I could see it in the utility tray, I could display it, I could press home to dismiss it but then I would see the blue glowing indicator at the top of the screen and the notification would be back.
I reproduce really easily on Sony, not so easily on my Flame (but my utility tray is slow there because I don't have bug 1178162 yet :) ).
Comment 1•10 years ago
|
||
[Tracking Requested - why for this release]:
Removing nomination for 2.5. Not usual STR.
blocking-b2g: 2.5? → ---
tracking-b2g:
--- → backlog
Comment 2•10 years ago
|
||
Looking at your STR this smells a lot like an issue in the system app's window management or somewhere else rather than in the callscreen. I wonder if this is related to bug 1078448.
| Reporter | ||
Comment 3•10 years ago
|
||
[Blocking Requested - why for this release]:
Renominating.
Reason: I got the issue without especially looking for it. And then we're pretty much stuck and need to reboot. (Maybe it's possible to recover by having or receiving a call too, I haven't tried).
blocking-b2g: --- → 2.5?
Comment 4•10 years ago
|
||
Comms triage: Race condition that puts the dialer in bad state that is hard to recover from.
blocking-b2g: 2.5? → 2.5+
tracking-b2g:
backlog → ---
Comment 5•10 years ago
|
||
BTW I doubt this is a dialer bug, it's far more likely to be related to window management in the system app. The dialer will always eventually close itself after the last call has been hung up, see the code here:
https://github.com/mozilla-b2g/gaia/blob/master/apps/callscreen/js/calls_handler.js#L346
Comment 6•10 years ago
|
||
Etienne, could you have a look and check what happens in the window manager / callscren agent when we hit this bug? I'd do it myself but I'm still grappling other blockers for now.
Flags: needinfo?(etienne)
| Assignee | ||
Comment 7•10 years ago
|
||
I can only test on a flame, but I can't reproduce the issue on mater.
That said, I was able to follow the STR and make the re-opening of the callscreen race the window.close() and it still got removed properly.
It's possible that bug 1202909 fixed it so it's worth re-testing on master is somebody can.
Flags: needinfo?(etienne) → needinfo?(jlorenzo)
Comment 8•10 years ago
|
||
Thanks for testing:
(In reply to Etienne Segonzac (:etienne) from comment #7)
> It's possible that bug 1202909 fixed it so it's worth re-testing on master
> is somebody can.
Good point, I hadn't thought about that.
| Reporter | ||
Comment 9•10 years ago
|
||
mmm I'm quite sure I had a build older than bug 1202909 and I reproduced. I'll try again :)
Comment 10•10 years ago
|
||
I repro'd on the laster master[1]. See this video for the steps and the effects of it: https://goo.gl/g30o9P . One tricky part of the STR is: you have to bring back the call screen right when the end call banner is displayed. Otherwise the correct call screen will re-appear, and will correctly be dismissed.
[1] Build ID 20151006110347
Gaia Revision 60cdaa3d3424db3432dc903e7f9c6c8fa099c06d
Gaia Date 2015-10-06 04:50:53
Gecko Revision https://hg.mozilla.org/mozilla-central/rev/89732fcdb0baca70e8b7a25a2725117113f0db80
Gecko Version 44.0a1
Device Name aries
Firmware(Release) 4.4.2
Firmware(Incremental) eng.worker.20151006.102229
Firmware Date Tue Oct 6 10:22:38 UTC 2015
Bootloader s1
Flags: needinfo?(jlorenzo)
| Reporter | ||
Comment 11•10 years ago
|
||
Just reproduced on the first try on a Sony with a build from Oct 06th.
| Assignee | ||
Comment 12•10 years ago
|
||
I'm fairly confident this is a WindowManager issue, Johan if you can lend me a z3c-sized test sim card sometime this week I'll take a look.
Component: Gaia::Dialer → Gaia::System::Window Mgmt
Comment 14•10 years ago
|
||
| Assignee | ||
Comment 15•10 years ago
|
||
Comment on attachment 8674222 [details] [review]
[gaia] etiennesegonzac:bug-1209536-lingering-attention-screen > mozilla-b2g:master
Flagging Julien for feedback since he has the magic touch when it comes to reproducing this bug :)
But the review is all yours Alberto!
Attachment #8674222 -
Flags: review?(apastor)
Attachment #8674222 -
Flags: feedback?(felash)
| Reporter | ||
Comment 16•10 years ago
|
||
Comment on attachment 8674222 [details] [review]
[gaia] etiennesegonzac:bug-1209536-lingering-attention-screen > mozilla-b2g:master
I don't seem to reproduce it :)
Great job !
Attachment #8674222 -
Flags: feedback?(felash) → feedback+
| Reporter | ||
Comment 17•10 years ago
|
||
I think the behavior could be improved in the future though:
When the user presses "home" and the call already ended, maybe the callscreen could be closed instead of minimized. We can assume the intent of the user pressing "home" at that moment is to close the callscreen completely anyway.
Comment 18•10 years ago
|
||
Comment on attachment 8674222 [details] [review]
[gaia] etiennesegonzac:bug-1209536-lingering-attention-screen > mozilla-b2g:master
Nice! Thanks
Attachment #8674222 -
Flags: review?(apastor) → review+
| Assignee | ||
Comment 19•10 years ago
|
||
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•