Closed Bug 1200571 Opened 9 years ago Closed 9 years ago

Unable to end call

Categories

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

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1126260

People

(Reporter: wilsonpage, Unassigned)

Details

(Keywords: foxfood, Whiteboard: [bzlite])

Attachments

(5 files)

User-Agent: Mozilla/5.0 (Mobile; rv:43.0) Gecko/43.0 Firefox/43.0

Callscreen unresponsive and strange white notification when returning to homescreen.
Attached file dev-log-main.log
Attached file properties.log
Attached image screenshot.png
Attached image screenshot.png
[Blocking Requested - why for this release]:Broken Functionality. Nominated to block 2.5
blocking-b2g: --- → 2.5?
Component: Gaia::Feedback → Gaia::Dialer
Keywords: qawanted
I cannot reproduce this issue on latest Flame central and Aries. Callscreen acted normal and I was able to end call on multiple attempts. Also tried stressing the phone by doing other tasks while in a call and couldn't reproduce the white callscreen/notification completely unresponsive issue.

Note: I think I have seen this issue on Flame 2.2 once before, where the active call notification is white and can't be tapped on to get to callscreen. I wasn't able to reproduce at that time, and wasn't able to reproduce now.

Device: Aries 2.5
BuildID: 20150902124951
Gaia: e2fab8f6ac345ecde10a1350e699be9ceb6987d6
Gecko: 1b687fcb5213153855c7ac0f8392ce0a4a7e3382
Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd
Version: 43.0a1 (2.5) 
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:43.0) Gecko/43.0 Firefox/43.0

Device: Flame 2.5
BuildID: 20150902030203
Gaia: b75979ec8862bd5799a7c42e938d3f67be38d6ae
Gecko: fb720c90eb49590ba55bf52a8a4826ffff9f528b
Gonk: c4779d6da0f85894b1f78f0351b43f2949e8decd
Version: 43.0a1 (2.5) 
Firmware Version: v18Dv4
User Agent: Mozilla/5.0 (Mobile; rv:43.0) Gecko/43.0 Firefox/43.0

Changing this to steps wanted and let others attempt.
Flags: needinfo?(jmercado)
Keywords: qawantedsteps-wanted
Flags: needinfo?(jmercado)
Sorry, I have no idea how it got into this broken state. I was hoping the attached logs might give some clue...?
I am also unable to reproduce this issue on both the latest Flame and Aries builds as well as an 8/12 build (near the reporter’s build). I was successfully able to accept, end, and reject calls when both making and receiving phone calls. I tried this multiple times with no apps open, multiple apps open, running on a low memory (319MB) Flame device, and testing on a device that had been idle for several hours.

I was always able to end the call at the call screen, and never received broken or blank notifications.  Both Voicemail and Missed Call notifications behaved and functioned properly.

Environmental Variables:
Device: Aries 2.5
BuildID: 20150902124951
Gaia: e2fab8f6ac345ecde10a1350e699be9ceb6987d6
Gecko: 1b687fcb5213153855c7ac0f8392ce0a4a7e3382
Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd
Version: 43.0a1 (2.5)
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:43.0) Gecko/43.0 Firefox/43.0

Environmental Variables:
Device: Flame 2.5
BuildID: 20150902030203
Gaia: b75979ec8862bd5799a7c42e938d3f67be38d6ae
Gecko: fb720c90eb49590ba55bf52a8a4826ffff9f528b
Gonk: c4779d6da0f85894b1f78f0351b43f2949e8decd
Version: 43.0a1 (2.5)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:43.0) Gecko/43.0 Firefox/43.0

Environmental Variables:
Device: Aries 2.5
BuildID: 20150812224407
Gaia: 52f3ea58df38e5427f6afeb636bc6ad01d24022f
Gecko: cf932fc931dcd19f425934db79bec641ebe2a8a9
Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd
Version: 43.0a1 (2.5)
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:43.0) Gecko/43.0 Firefox/43.0

Leaving steps-wanted for another tester to attempt.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmercado)
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmercado)
Comms triage: QA was unable to reproduce the problem. That might be something related to the country or the carrier. Wilson, could you enable the RIL debugging on[1] and send us some new logs to see how we could repro/fix the problem?

[1] https://wiki.mozilla.org/B2G/QA/Tips_And_Tricks#RIL_Debugging
Flags: needinfo?(wilsonpage)
(In reply to Johan Lorenzo [:jlorenzo] (QA) from comment #10)
> Comms triage: QA was unable to reproduce the problem. That might be
> something related to the country or the carrier. Wilson, could you enable
> the RIL debugging on[1] and send us some new logs to see how we could
> repro/fix the problem?
> 
> [1] https://wiki.mozilla.org/B2G/QA/Tips_And_Tricks#RIL_Debugging

I'm afraid I have no way of reproducing the problem myself. I only saw it once and that was when I filed this bug.
Flags: needinfo?(wilsonpage)
Comms triage: This issue only reproduces in some conditions. We currently no way to know what might have failed. Removing the nomination until we have more information.
blocking-b2g: 2.5? → ---
You've most likely hit bug 1126260, but that should be fixed already. I'm dup'ing against that one if nobody can reproduce but please reopen this if you hit it again.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Flags: needinfo?(jmercado)
Keywords: steps-wanted
QA Whiteboard: [QAnalyst-Triage+]
Flags: needinfo?(jmercado)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: