Closed Bug 1139310 Opened 10 years ago Closed 7 years ago

[Nexus 5][Dialer]The control button in call out view does not work.

Categories

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

ARM
Gonk (Firefox OS)

Tracking

(tracking-b2g:backlog, b2g-v2.2 affected, b2g-master unaffected)

RESOLVED WONTFIX
tracking-b2g backlog
Tracking Status
b2g-v2.2 --- affected
b2g-master --- unaffected

People

(Reporter: huayu.li, Unassigned)

Details

(Whiteboard: [2.2-nexus-5-l][flame-l-testing-needed] )

Attachments

(7 files)

Attached file logcat3.txt
[1.Description]: [Nexus 5][Dialer]The control button on call out page cannot work normally. This issue also exist while headset is plugged in or device is connected with BT headset. Found at:15:15 See attachments: logcat3.txt.calloutpage.3gp [2.Testing Steps]: 1.Plug in headset, and you have save some contacts. 2.Launch dialer. 3.Call out a contact number in keyboard view. 4.Receive the call in another device. 5.Tap the control button as mute, keyboard, add call, speaker, pause, endcall. 6.End call and repeat step 3-5 for 1-3 times. [3.Expected Result]: 5&6.The related function should work correctly. [4.Actual Result]: 5.Maybe the functions are normal, but sometimes they do not work. 6.These buttons do not work. [5.Reproduction build]: N5: Build ID 20150303002527 Gaia Revision 3d188c414e30acc392253d5389a42352fcfbc183 Gaia Date 2015-03-03 00:53:42 Gecko Revision https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/c89aad487aa5 Gecko Version 37.0 Device Name hammerhead Firmware(Release) 5.0 Firmware(Incremental) eng.cltbld.20150303.040940 Firmware Date Tue Mar 3 04:09:55 EST 2015 Bootloader HHZ12d Flame 2.2 build: Build ID 20150303002527 Gaia Revision 3d188c414e30acc392253d5389a42352fcfbc183 Gaia Date 2015-03-03 00:53:42 Gecko Revision https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/c89aad487aa5 Gecko Version 37.0 Device Name flame Firmware(Release) 4.4.2 Firmware(Incremental) eng.cltbld.20150303.034757 Firmware Date Tue Mar 3 03:48:06 EST 2015 Bootloader L1TC000118D0 Flame 3.0: Build ID 20150303010233 Gaia Revision c8ed1085a67490a1ecd7f275e5de9487e1b93b1d Gaia Date 2015-03-02 20:14:21 Gecko Revision https://hg.mozilla.org/mozilla-central/rev/0b3c520002ad Gecko Version 39.0a1 Device Name flame Firmware(Release) 4.4.2 Firmware(Incremental) eng.cltbld.20150303.044015 Firmware Date Tue Mar 3 04:40:27 EST 2015 Bootloader L1TC000118D0 [6.Reproduction Frequency]: occasionally Recurrence,3/5 [7.TCID]: 2096 [8.Note]: The issue do not exist on Flame 2.2.
Attached video calloutpage.3gp
[Blocking Requested - why for this release]: Functionality broken on the 2.2/Android L reference device.
blocking-b2g: --- → 2.2?
ni myself to follow up
Flags: needinfo?(hcheng)
Hermes, please clarify if this is issue is on GAIA or not. We won't block if this is GAIA bug and Nexus5 only.
Whiteboard: [2.2-nexus-5-l]
I cannot really reproduce this problem. I used other phone to call Nexus 5 several times (more than 10), and got a similar issue. Nexus 5 cannot answer or reject the phone. The answer or reject button do not work, and the background is black like this screenshot.
Flags: needinfo?(hcheng)
Attached file dialer.log
Here is the RIL log. Could you take a look if it is a RIL bug?
Flags: needinfo?(htsai)
Hi Ben, please help comment 6, thank you.
Flags: needinfo?(htsai) → needinfo?(bhsu)
Attached file dialer-bt-headset.log
Another log, following the original STR more than 5 times to get the same issue.
Hi, Hsinyi and Hermes I've traced the logs, and I didn't find any hangUpCall request within the interval of the call being active and disconnected. To judge whether this bug is a RIL bug, I think we need some support from Gaia. Besides, I suggest using |adb logcat -v threadtime| than solely using |adb logcat|, since we can record more information with the extra parameter.
Flags: needinfo?(bhsu)
Hi Doug, Did dialer app actually call telephony API? Can you tell from the dialer log?
Flags: needinfo?(drs.bugzilla)
I don't have a Nexus 5 to test with, and it seems that this only repros on it. I asked around and nobody on the Dialer team has a Nexus 5, either. I tried reproing this on a 2.2 Flame and was unable to. I'm guessing that the Callscreen is indeed not calling any of the telephony API functions. But the background being solid black shows that there's something else wrong before the Callscreen is even invoked. Though I have no proof, I'm guessing that this is a RIL or otherwise platform issue. This doesn't happen on any other device, so the only possibility is that the Nexus 5 is exposing some kind of race or other problem that for some reason doesn't appear elsewhere. Since the only thing I can help with is what I see, my only suggestion is to break here and check why we're getting no contact image: https://github.com/mozilla-b2g/gaia/blob/master/apps/callscreen/js/handled_call.js#L211 You can needinfo me if there's any other info I can provide.
Flags: needinfo?(drs.bugzilla)
triage: non-blocking for below reasons: 1. this bug happens only on Nexus5 which isn't the target device to ship 2. already put much efforts to investigate but without finding any evidence that this is relevant to Lollipo
blocking-b2g: 2.2? → ---
Attached file logcat1.txt
Hi all, In today's testing, while I call out a number, the same issue appeared, the screen is black and all the control button is disabled,but it just appear once, there is no special step, just call out.Upload the log and video. Nexus5 2.2 Build ID 20150409002503 Gaia Revision ea735c21bfb0d78333213ff0376fce1eac89ead6 Gaia Date 2015-04-07 20:58:15 Gecko Revision https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/0efd5cdbe224 Gecko Version 37.0 Device Name hammerhead Firmware(Release) 5.0 Firmware(Incremental) eng.cltbld.20150409.040813 Firmware Date Thu Apr 9 04:08:30 EDT 2015 Bootloader HHZ12d
Attached video VIDEO0509.3gp
Hi Eric, could you help to check this issue? I test more 20 times, issue appeared once agian.
Flags: needinfo?(echang)
Need to check in FLAME-L later. whiteboard: [flame-l-testing-needed]
Flags: needinfo?(echang)
Whiteboard: [2.2-nexus-5-l] → [2.2-nexus-5-l][flame-l-testing-needed]
[Tracking Requested - why for this release]: backlog it first. will wait for further test input.
Comms triage: P1 if it happens on the Flame under Android L.
Priority: -- → P1
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: