Description: While user is in call, opening dial pad and pressing any number results in two numbers (e.g. pressing the number '5' results in '55'). Two tones are heard on the other end indicating that two numbers have been pressed. This prevents user from using any phone system that uses DTMF touch tones including conference call lines and voicemail. This only happens with dialer pad in call, this issue cannot be seen while dialing to initiate call or dialing to initate conference call. Repro Steps: 1) Update a Tarako to BuildID: 20140416004007 2) Launch Dialer 3) Call a valid number 4) Open number pad in call (not initiating conference call) 5) Press any number Actual: Two numbers are dialed for every one number pressed on dialer pad during call. Expected: One number is are dialed for every one number pressed on dialer pad during call. 1.3T Environmental Variables: Device: Tarako 1.3T BuildID: 20140416004007 Gaia: 718a06816327fcb6a18095f677cfff4b86adc292 Gecko: 9ef12c19ddc9 Version: 28.1 Firmware Version: sp6821a Notes: Repro frequency: 3/3, 100% See attached: Youtube video clip & logcat

Youtube video clip: http://youtu.be/YVxoBhn8dOE

NI :eitenne to help here.

Gabriele, could this be related to the latest keypad optimizations?

Never mind. We're calling telephony.startTone only once and get 2 tones. I think this is lower level than gaia.

the event from driver looks normal when issue happened when I press once, the event also report once which is same as our expect

(In reply to Etienne Segonzac (:etienne) from comment #4) > Never mind. We're calling telephony.startTone only once and get 2 tones. > I think this is lower level than gaia. Yes, I've actually encountered this issue already, maybe we have another bug filed for it? It's definitely a device-specific issue as I've experienced it on the Tarako only. It seems that telephony.startTone() makes the lower levels play a sound. You can try two scenarios: if you have keypad tones enabled you'll hear two sounds, the one we play ourselves and another one; if you disable keypad tones the phone does play a tone on his own. I had dug a bit into this and this didn't look like a Gecko problem either: what the telephony stack does is just hand out a message to the RIL to play the DTMF tone so I think that the RIL's at fault here.

Hi! Ken, Could your team help to check this case? Thanks -- Keven

Aknow, can you please look into this bug?

Gabriele, Have you check the video in Comment 1. In video, pressing once on keypad results in two characters showing on the screen. I check the log on gecko layer. We indeed sent out two messages to RIL; thus there will be two DTMF tone. Could you check how many times that dialer calls mozTelephony.startTone() api? I suspect that keypad trigger two click event so it generate two chars on screen and also two api calling.

(In reply to Szu-Yu Chen [:aknow] from comment #9) > Have you check the video in Comment 1. In video, pressing once on keypad > results in two characters showing on the screen. I hadn't see the video so I didn't realize that we're seeing two keys, I thought this was only about two DTMF tones being heard. I'll check on my Tarako and report back.

The main cause maybe function callSetup() in callscreen app is double executed in index.js and calls_handler.js. Disabled the loading of index.js, the DTMF dialing became nomal. I want to know What the role of this document(index.js) is,because it is the same as last part of calls_handler.js.

hi Gabriele, looks like you are looking at this bug, do you mind taking? Thanks

Yes, I'm actively working on this, taken!

This looks like the same issue as bug 998044 which already has a patch. I'll check when reviewing bug 998044.

Confirmed, this is a dup of bug 998044 and Etienne's patch fixes the problem we're seeing here too.

Verified it. * Build information: - Gaia b5adc5a943d3abbd6ab070a47c847f2c24891cc5 - Gecko https://hg.mozilla.org/releases/mozilla-b2g28_v1_3t/rev/e9890f5d4709 - BuildID 20140429014002 - Version 28.1 * Result: - Cannot reproduce