* Description: This bug happened on v1.3T build, and cannot reproduce it on other branches. Using keypad of dialer app to make a phone call. After receiver answer the phone call, caller and receiver cannot hear any voice. If you use call log to make a phone call, you cannot reproduce this bug. * Reproduction steps: 1. Launch the dialer app 2. Using keypad of dialer app to make a phone call 3. Receiver answers the phone 4. Checking the voice of caller * Expected result: 1. The caller and receiver can hear any voice * Actual result: The caller and receiver cannot hear any voice * Build info.:(Tarako Build) - Gaia d8ff994bd96c37ba9a93c343932a5441a78a0eec - Gecko 6db37b3f76b4fe2aa6f8fb5ae9e036ed99344772 - BuildID 20140327060053 - Version 28.1 Thanks!

Which side did you use the tarako device on? Is this a dup of 982531?

No, it is not a duplicate case of Bug 982531 because I cannot catch the same log of bug 982531 Comment 7 mentioned. By the way, the symptom is similar to Bug 982531 Comment 28 mentioned. Attaching the log I collected. (Radio_log_20140328)

Given thi is device specific, it most likely looks like a POVB issue. NI :sam to help here and confirm the same.

ni? sku as well

Hi Sam: It looks like this is modem memory shrink issue. Please help update when can SPRD provide flash pac tool for linux. We can have Mozilla QA to verify it then. Thanks!! Shawn

Gabriele according to Comment 6 you might help on this. Thanks

(In reply to shawn ku [:sku] from comment #6) > It looks like this is modem memory shrink issue. Could you elaborate on this? I'm not really familiar with the modem output so I can't really tell if there's something wrong with the attached log.

(In reply to shawn ku [:sku] from comment #6) > Hi Sam: > It looks like this is modem memory shrink issue. > Please help update when can SPRD provide flash pac tool for linux. > > We can have Mozilla QA to verify it then. > > Thanks!! > Shawn Steven, is this something you can help? Thank you.

ni? James

Add Sam here.

Add Sam here.

Hi, from the log: I found twice call. the second call log. 03-28 14:47:03.131 93 4959 D AT : Channel1: AT> ATD777; //make call 03-28 14:47:03.151 93 257 D AT : Channel0: AT< ^DSCI: 1,0,2,0,0,777,129 //in dialing state //gecko use CLCC to get current call status, it is still in dialing process 03-28 14:47:03.151 93 4959 D AT : Channel1: AT> AT+CLCC 03-28 14:47:03.151 93 257 D AT : Channel1: AT< +CLCC: 1,0,2,0,0,"777",129 03-28 14:47:03.151 93 257 D AT : Channel1: AT< OK //and it is hanged.. 03-28 14:47:06.131 93 4959 D RILC : [0118]> HANGUP (1) 03-28 14:47:06.261 93 4959 D AT : Channel1: AT> AT+CHLD=71 //and no call now 03-28 14:47:06.561 93 257 D AT : Channel0: AT< ^DSCI: 1,0,6,0,0,777,129,,255 So it is no problem for second call, it shouldn't have any voice. and for first call, i can't find the atd //Call is active now 03-28 14:44:57.591 93 4959 D AT : Channel1: AT> AT+CLCC 03-28 14:44:57.601 93 257 D AT : Channel1: AT< +CLCC: 1,0,2,0,0,"777",129 03-28 14:44:57.601 93 257 D AT : Channel1: AT< OK //hangup it. 03-28 14:45:01.711 93 4959 D AT : Channel1: AT> AT+CHLD=71 03-28 14:45:02.001 93 257 D AT : Channel0: AT< ^DSCI: 1,0,6,0,0,777,129,,255 03-28 14:45:02.001 93 257 D RILC : [UNSL]< UNSOL_RESPONSE_CALL_STATE_CHANGED 03-28 14:45:02.001 93 257 D AT : Channel0: AT< *SPCSC: 1,21,,"777",129,1 03-28 14:45:02.001 93 257 D AT : Channel0: AT< ^CEND: 1,,21

Hi whsu@mozilla.com, Which the caller which can't hear any voice ? the first or the second? and, please update the pac and try to reproduce it. please log with: adb logcat -b radio -b main Thanks! Sam

(In reply to sam.hua from comment #14) > Hi whsu@mozilla.com, > > Which the caller which can't hear any voice ? the first or the second? [William] Sorry! I cannot understand what you mean. Do you mean who cannot hear any voice? Both of the caller and receiver cannot hear the voice after the receiver answers the call. > and, please update the pac and try to reproduce it. > please log with: > adb logcat -b radio -b main [William] I cannot reproduce this bug after I update the PAC file. Marked this bug as "WORKFORME" Also, attach the logs. FYI. You can download it if you think it is worth to debug it. 1. Dialer-PAC_0121 -> Test with old PAC file and can always reproduce this bug 2. Dialer-PAC_0402 -> Test with new PAC file and cannot reproduce this bug Thanks. > Thanks! > Sam * Test Build: - Gaia 02b97c89dec7a10a955c85b921b2a66181eebb0e - Gecko f8bca24057937f5b09d73512ba1e771011ab4203 - BuildID 20140331101634 - Version 28.1

Is there a way to include Dialer-PAC_0402 in regular pvt builds as we're using these builds for our daily smoketests and other Tarako's test runs and it still fails Dialer TCs.

Hi, Naoki-san, Could I have your help? I cannot sure if you are the right person to provide latest PAC (0402) file to Natalya. If you are not the right person, could you please help needinfo the right one? Thanks so much.

On the laster Tarako build, the dial sound cannot be heard when making a call from Dialer

The PAC file was sent, having said that the issue remains that we cannot get the flashing tool to work on any windows machine.

Weird~! Because we have installed the flashing tool (research download) on Windows 7 64 bit machines and it works as expected. I also can flash the latest PAC(0402) file into Tarako device. Did I misunderstand anything?

Issue does not occur for us today when flashing from latest PVT build Device: Tarako 1.3T BuildID: 20140408004001 Gaia: 643f3e6676cbb89c62708a9f7cbef2edc795a552 Gecko: b850e0f09e61 Version: 28.1 Firmware Version: sp8810

It may be because you have a AMD chipset? Apparantly there is a ubuntu way of flashing the PAC file now. Thanks, William. Thanks for verifying Brogan!

This is not the only issue which confirmed to be reproducible only with old PAC so I opened bug 994191 specifically to track updating PAC files issue.