Closed
Bug 1039844
Opened 11 years ago
Closed 11 years ago
[B2G][Dialer]Touchtones are unresponsive during phonecall
Categories
(Firefox OS Graveyard :: Gaia::Dialer, defect)
Tracking
(blocking-b2g:2.0+, b2g-v1.4 unaffected, b2g-v2.0 verified, b2g-v2.1 unaffected)
Tracking | Status | |
---|---|---|
b2g-v1.4 | --- | unaffected |
b2g-v2.0 | --- | verified |
b2g-v2.1 | --- | unaffected |
People
(Reporter: rkuhlman, Assigned: drs)
References
Details
(Keywords: smoketest, Whiteboard: [2.0-daily-testing][273MB-Flame-Support])
Attachments
(1 file)
80.65 KB,
text/plain
|
Details |
During a phone call, touchtone keypad input is not getting transmitted.
Repro Steps:
Prerequisite: Set device to 273 mb memory
1) Update a Flame to BuildID: 20140716000201
2) Launch Dialer app
3) Call a number that utilizes touchtones
(Ex: Mozilla conference line 6509030800)
4) During call, tap keypad button to display number pad
5) Tap numbers
Actual:
Number buttons flash to indicate that button has been pressed, but touchtones are not registered on the other end of the connection
Expected:
Touchtone signals are broadcast and received at the other end of the connection
v2.0 Environmental Variables:
Device: Flame v2.0 273Mb
BuildID: 20140716000201
Gaia: 5f8b1b8a2da9e3b531eee817a669f57fa4d9b9c6
Gecko: 913827496f65
Version: 32.0a2
Firmware Version: v122
Notes:
Repro frequency: 100%
See attached: logcat
Reporter | ||
Updated•11 years ago
|
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
OS: Linux → Gonk (Firefox OS)
Hardware: x86 → ARM
Whiteboard: [2.0-daily-testing][273MB-Flame-Support]
Comment 1•11 years ago
|
||
Smoketest blocker, requesting qawanted for branch checks to verify regression.
Updated•11 years ago
|
QA Contact: ddixon
Comment 2•11 years ago
|
||
If I understand description correctly, DTMF tones are not working. If this is the case, this is a cert blocker. Nominating accordingly.
Updated•11 years ago
|
blocking-b2g: --- → 2.0?
Comment 3•11 years ago
|
||
(In reply to Beatriz Rodríguez [:brg] from comment #2)
> If I understand description correctly, DTMF tones are not working. If this
> is the case, this is a cert blocker. Nominating accordingly.
you are right, the DTMF tones don't work, it should block the release
Updated•11 years ago
|
blocking-b2g: 2.0? → 2.0+
Comment 4•11 years ago
|
||
Branch Checks
(273 memory for Flame devices)
Issue DOES occur on Flame 2.0, Buri 2.0.
Actual Results: During a call the test device does not transmit Dialpad touch tones through its own speakers nor to the receiving device.
Flame 2.0 Repro? Yes
Device: Flame 2.0
Build ID: 20140717085706
Gaia: 9977a02ea62ba96425a1cc4d1bfb54a909f68905
Gecko: cc563253a046
Version: 32.0a2 (2.0)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
----------------------------------------------------------------------------------
Buri 2.0 Repro? Yes
Device: Buri 2.0
Build ID: 20140717085706
Gaia: 9977a02ea62ba96425a1cc4d1bfb54a909f68905
Gecko: cc563253a046
Version: 32.0a2 (2.0)
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
----------------------------------------------------------------------------------
----------------------------------------------------------------------------------
Issue DOES NOT occur on Flame 2.1, 1.4, Buri 2.1
Flame 2.1 Repro? No
Device: Flame Master
Build ID: 20140716172339
Gaia: Unknown
Gecko: a74600665875
Version: 33.0a1 (Master)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0
----------------------------------------------------------------------------------
Flame 1.4 Repro? No
Device: Flame 1.4
Build ID: 20140715123018
Gaia: 393d72937727ad20e82b2ff7b13e3d7ff077a9f0
Gecko: 932c37978d37
Version: 30.0 (1.4)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0
----------------------------------------------------------------------------------
Buri 2.1 Repro? No
Device: Buri Master
Build ID: 20140717070416
Gaia: Unknown
Gecko: f92e4d13b3c6
Version: 33.0a1 (Master)
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0
Updated•11 years ago
|
status-b2g-v1.4:
--- → unaffected
status-b2g-v2.1:
--- → unaffected
Updated•11 years ago
|
Comment 5•11 years ago
|
||
2.0 AURORA Regression Window
Last Working
Environmental Variables:
Device: Flame 2.0
Build ID: 20140715082614
Gaia: 391258012d09cc1dde9a6f3f9a2078739043d0d6
Gecko: 7025d37f4b06
Version: 32.0a2 (2.0)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
First Broken
Environmental Variables:
Device: Flame 2.0
Build ID: 20140715091335
Gaia: 391258012d09cc1dde9a6f3f9a2078739043d0d6
Gecko: c57fbd13b6f1
Version: 32.0a2 (2.0)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Last Working Gaia and First Broken Gecko
Issue DOES occur here.
Gaia: 391258012d09cc1dde9a6f3f9a2078739043d0d6
Gecko: c57fbd13b6f1
Last Working Gecko and First Broken Gaia
Issue DOES NOT occur here.
Gaia: 391258012d09cc1dde9a6f3f9a2078739043d0d6
Gecko: 7025d37f4b06
Gecko Pushlog:
http://hg.mozilla.org/releases/mozilla-aurora/pushloghtml?fromchange=7025d37f4b06&tochange=c57fbd13b6f1
Updated•11 years ago
|
Comment 6•11 years ago
|
||
This is a regression because bug 981519 was uplifted to 2.0 without all the Gaia dependencies. We need to uplift bug 1026081.
Comment 7•11 years ago
|
||
I just uplifted it. This should now be fixed.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Comment 8•11 years ago
|
||
Testing with Flame-2.0- Gecko-5287d8d.Gaia-8cb1a94, the DTMF tones are working fine. Thanks for fixing it.
Comment 9•11 years ago
|
||
Touch tones are now working correctly.
Environmental Variables:
Device: Flame 2.0
Build ID: 20140721000201
Gaia: 8cb1a949f2e9650bb2c5598e78a6f24a58bbaf97
Gecko: 4bd4b0ae7bbe
Version: 32.0a2 (2.0)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Status: RESOLVED → VERIFIED
Updated•11 years ago
|
Flags: in-testsuite?
Updated•11 years ago
|
Flags: in-testsuite? → in-qa-testsuite?(jlorenzo)
Updated•11 years ago
|
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][fxosqa-auto-backlog?]
Flags: in-qa-testsuite?(jlorenzo)
QA Whiteboard: [QAnalyst-Triage+][fxosqa-auto-backlog?] → [QAnalyst-Triage+][fxosqa-auto-backlog+]
Comment 10•11 years ago
|
||
Clearing the backlog tag now that bug 1112191 is created.
QA Whiteboard: [QAnalyst-Triage+][fxosqa-auto-backlog+]
You need to log in
before you can comment on or make changes to this bug.
Description
•