Closed Bug 1181264 Opened 4 years ago Closed 2 years ago
[Aries][Sound][Call Screen] Long touch tones stutter heavily when held down in a call
Description: If the user has Long touch tones, and they hold down the keypad in the call screen during the call, they will hear heavy stuttering static sound in the audio of the touch tone. Prerequisites: Must have Audible touch tones set to Long in Settings>Sound (Currently Default) Repro Steps: 1) Update a Aries to 20150707033152 2) Make an outbound call or accept an inbound call. 3) At the callscreen, bring up the keypad 4) Hold down a number on the keypad, listen to the touch tone sound. Actual: Touch tones stutters as it is held down. Expected: Touch tone does not stutter, sounds smooth. Environmental Variables: Device: Aries 2.5 (Full Flash) Build ID: 20150707033152 Gaia: e6506d68e01489b57616f8b74e8773f938ce62b3 Gecko: e271ef4c49ae Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd Version: 42.0a1 (2.5) Firmware Version: D5803_23.1.A.1.28_NCB.ftf User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0 Repro frequency: 10/10 See attached: Logcat, Video (URL)
This issue does NOT occur on Flame 2.5 builds. Touch tone does not stutter, sounds smooth. Environmental Variables: Device: Flame 2.5 (Full Flash) Build ID: 20150707010204 Gaia: e6506d68e01489b57616f8b74e8773f938ce62b3 Gecko: e7e69cc8c07b Gonk: a4f6f31d1fe213ac935ca8ede7d05e47324101a4 Version: 42.0a1 (2.5) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0
QA Whiteboard: [QAnalyst-Triage?]
[Blocking Requested - why for this release]: Regression from flame behavior, poor ux.
blocking-b2g: --- → 2.5?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Comms triage: The Flame is still the only reference device, so this issue won't block certification. However, for a high-end phone, this sounds cheap. This might be related to the integration with the audio hardware. What do you think, Gabriele?
Smells like bug 1166758, my take is that this must be a driver issue of some sort. Note that I've previously checked if this was related to excessive CPU usage in a low power state while playing MP3s but this was disproved in bug 1166758 comment 15 and in this bug there's no decoding involved so it can't be that either.
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.