[Dialer][Touch Tones] Touch tones in dialer seem to have echo and static sounding effects when dialing

NEW
Unassigned

Status

()

Core
Web Audio
P4
normal
Rank:
10
3 years ago
2 months ago

People

(Reporter: DerekH, Unassigned)

Tracking

(Depends on: 1 bug, {qawanted})

unspecified
ARM
Gonk (Firefox OS)
qawanted
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(blocking-b2g:-, b2g-master affected)

Details

(Whiteboard: [3.0-Daily-Testing][spark][platform], URL)

Description:
The touch tones in dialer exhibit static and echo sounds when dialed. This will happen across all buttons dialed on the dial pad


Repro Steps:
1) Update a Xperia Z3 Compact (B2G) to 20150526104521
2) Open Dialer
3) Type on the Dial Pad
4) Listen to the Dial tones


Actual:
Dial tones sound echoy and staticy


Expected:
Dial tone sounds are played without any disruption


Environmental Variables:
Device: Xperia Z3 Compact (B2G) 3.0
Build ID: 20150526104521
Gaia: 0359bf81f96a5356dacfc07e12ca72df61cbd638
Gecko: e537a1ba501b
Version: 41.0a1 (3.0)
Firmware Version:
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0


Repro frequency: 10/10
See attached: Logcat, Video - https://youtu.be/tn1bsDrmQ98
This issue does NOT occur on Flame 3.0

Dial tone sounds are played without any disruption

Environmental Variables:
Device: Flame 3.0 (319mb)(Kitkat)(Full Flash)
Build ID: 20150526104742
Gaia: 0d67eb545b2f4342525d14e1a10e80c91c87ada0
Gecko: e537a1ba501b
Gonk: 040bb1e9ac8a5b6dd756fdd696aa37a8868b5c67
Version: 41.0a1 (3.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Summary: [Dialer][Touch Tones] Touch tones in dialer seem to have echo and static sounding affects when dialing → [Dialer][Touch Tones] Touch tones in dialer seem to have echo and static sounding effects when dialing
[Blocking Requested - why for this release]: Regression from the Flame.
blocking-b2g: --- → spark?

Comment 3

3 years ago
[Blocking Requested - why for this release]:

Spark triage team decided that this bug is not a Spark blocker: moving this to 3.0?
blocking-b2g: spark? → 3.0?
Flags: needinfo?(pbylenga) → needinfo?(padenot)
This is very likely to be underruns cause by the fact that the latency is too low and Web Audio API is too expensive for now.

I think we trigger the opensl fastpath in cubeb with this device (z3c), and not in the flame.
Flags: needinfo?(padenot)
Comms triage: Will break the experience on Z3C.
blocking-b2g: 3.0? → 3.0+
Component: Gaia::Dialer → Web Audio
Product: Firefox OS → Core
I think it makes sense to re-test this since a lot of changes have landed since May.

Moving this one back to Dialer since this problem doesn't occur on Flame 3.0.
Component: Web Audio → Gaia::Dialer
Product: Core → Firefox OS
[Blocking Requested - why for this release]: Nominating for 2.5 as it needs to be re-verified.
blocking-b2g: 2.5+ → 2.5?
Keywords: qawanted
Checking this issue is blocked by bug 1201133.  Once that is resolved we can check this issue again.
QA Whiteboard: [QAnalyst-Triage?]
Comms triage: Even with bug 1201133 being here, you can here some static noise at the first dial tone.
blocking-b2g: 2.5? → 2.5+
This issue is still occurring on the latest Spark Aries 2.5 build.
Static can be heard in the dialer touch tones.

Environmental Variables:
Device: Aries 2.5
Build ID: 20150908152248
Gaia: b81185d30e548f782770b852473ffb53c641a490
Gecko: b23b2fa33a9dcda59dbbca1d157eca3c32c5b862
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
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmercado)
Keywords: qawanted
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmercado)
Priority: -- → P2
I am unable to reproduce this because I'm encountering another problem: only the first touchtone is audible, all following ones are muted. I seem to have seen a similar bug but I can't find it anywhere, Alastor can you help me out finding it?
Flags: needinfo?(alwu)
We have a similar issue that the built-in keyboard only has first audible sound (bug1183033), but this issue seems not equal to bug1183033. 
After applying the patch of bug1183033, this issue still exists.
Flags: needinfo?(alwu)
Ah, we had the bug1201133 before, and the bug1183033 can fix it at that time (but can't fix it now).
Thanks Alastor, I'll try running a bisection to figure out what broke this since it used to work just a few weeks ago.
[Blocking Requested - why for this release]: I'd like to de-nom this bug because it's impossible for me to reproduce it because of bug 1211105. BTW this is most likely not a dialer bug since the relevant code hasn't been touched in months but rather an issue somewhere within gecko.
blocking-b2g: 2.5+ → 2.5?
I tested it again on [1] and even though you have 1 dial tone, you can hear static in there.

Comms triage: Regression from 2.2. Agreed with the fact that it's more a gecko related issue.


[1] Build ID               20151004181256
Gaia Revision          f3d9981dccfa4dfdfcb865d95fdcfb85e4077e1e
Gaia Date              2015-10-02 13:52:20
Gecko Revision         https://hg.mozilla.org/mozilla-central/rev/3d7532ce81ac571962abc3b99582fe7f5d685192
Gecko Version          44.0a1
Device Name            aries
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.worker.20151004.173222
Firmware Date          Sun Oct  4 17:32:29 UTC 2015
Bootloader             s1
blocking-b2g: 2.5? → 2.5+
(In reply to Johan Lorenzo [:jlorenzo] (QA) from comment #16)
> I tested it again on [1] and even though you have 1 dial tone, you can hear
> static in there.

Not a dialer issue though, not sure if this should be moved to Core::Web Audio or Firefox OS::Audio Channel.
Component: Gaia::Dialer → Web Audio
Product: Firefox OS → Core
Moved to Core::Web Audio, please reassign if this is not the right component.
Paul -- can you look at this?  Thanks.
Assignee: nobody → padenot
Rank: 10
Priority: P2 → P1
The z3c has issues at the gonk level that we need to fix first. For example bug 1166758. Lollipop might solve it, so we're blocked on that.
Reading over Bug 1166758, it looks like the root cause of this bug may be identical to the root cause for Bug 1166758.  Rather than dup'ing this bug to Bug 1166758, I'm marking this as blocked by it so that we come back to this bug and re-test once Bug 1166758 is resolved.

I'm marking QA-wanted to ask QA to re-test this once Bug 1166758 is resolved.  If it's not, we'll take another look.
Depends on: 1166758
Keywords: qawanted
Depends on: 1214195
New info: Paul Adenot retested this today because he observed bug 1166758 seems to have been fixed by the latest the last OTA update (see bug 1166758 for that discussion).  However, during his retest, he discovered a new regression and opened bug 1214195 (Dialer only makes one tone when dialing a number).  I've made that new bug a P1 and nominated it as a 2.5 blocker.  It's possible that this bug was resolved by the OTA update (like bug 1166758), but we won't know until bug 1214195 is resolved.
(In reply to Maire Reavy [:mreavy] (Plz needinfo me) from comment #22)
> However, during his retest, he discovered a new regression and opened bug 1214195
> (Dialer only makes one tone when dialing a number).

It's not new. Comment 8 already had the bug number for that issue.
Depends on: 1183033

Updated

2 years ago
Whiteboard: [3.0-Daily-Testing][spark] → [3.0-Daily-Testing][spark][platform]
Reviewing the B2G priority (P1, P2, P3) definitions, this bug is a "P3" bug.  This doesn't impact dogfooding or prevent using the phone.  It's simply glitchy, and we want to fix it.
Priority: P1 → P3

Updated

2 years ago
Whiteboard: [3.0-Daily-Testing][spark][platform] → [3.0-Daily-Testing][spark]

Updated

2 years ago
Whiteboard: [3.0-Daily-Testing][spark] → [3.0-Daily-Testing][spark][platform]
triage: unblocking this for 2.5, there is no effect on usage.
blocking-b2g: 2.5+ → -
I not planning on working on this, but ping me if you need to chat.
Assignee: padenot → nobody
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
You need to log in before you can comment on or make changes to this bug.