Closed Bug 833268 Opened 11 years ago Closed 6 years ago

When a voice call is connected, the caller side can't hear DTMF tone.

Categories

(Firefox OS Graveyard :: General, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: vliu, Unassigned)

References

Details

STR for this issue:

1. Activate dialer app and make a call.
2. When call is connected, press key in Dialpad.

Expected:
DTMF tone should hear in caller side.

Actual:
I can't hear any DTMF tone.
When I pressed a key after a call is established, TonePlayer.start was called in dialer app. Based on above, I think it is a platform issue.
Component: Gaia::Music → General
QA Contact: mozillamarcia.knous
After issue tracking, I got the behavior below.

1. When a dialer.js was launched, created a HTMLAudioElement object with channel type "ringer". When I pressed a key tone, HTMLAudioElement created nsNativeAudioStream object to write tone sampling data.
2. When a call was established, another HTMLAudioElement object with channel type "ringer" and nsNativeAudioStream were also created in oncall.js. In this second object I could see tone sampling data in array and also been written by nsNativeAudioStream::write(). But even so, I still can't hear tone sound.
3. After running sysdump in adb, the sound seems been muted in AudioFlinger. 
4. With Macro's suggestion, changing the Audio channel type in first AudioElement object to 'normal' can fixed this issue.
5. Changing to 'normal' is not a solution because the volume level can't be adjusted any more. A Bug 832170 is dedicated for creating a dtmf tone channel type for all dtmf event. I will block this issue until Bug 832170 is done.
Blocks: 832170
No longer blocks: 832170
Depends on: 832170
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.