Closed Bug 982007 Opened 10 years ago Closed 10 years ago

[Tarako] unable to establish the second MT call connection with headphone

Categories

(Firefox OS Graveyard :: Vendcom, defect)

Other
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:1.3T+, b2g-v1.3T verified)

RESOLVED FIXED
blocking-b2g 1.3T+
Tracking Status
b2g-v1.3T --- verified

People

(Reporter: angelc04, Assigned: sam.hua)

References

Details

(Whiteboard: [POVB])

Attachments

(3 files)

Attached video Steps to reproduce
Test build: 20140310152650

STR:
1. Restart device
2. Make a MT call to tarako device
3. Answer the call on test device, Call connection can be established
4. End the call
5. Make a MT call to Tarako device again.
   --> Incoming Call screen appears and stay forever. User cannot answer/end the call. Device need reboot to kill Phone app process.

Please see attached video for details.
(In reply to pcheng from comment #0)
> Created attachment 8389047 [details]
> Steps to reproduce

> the call. Device need reboot to kill Phone app process.

Please ignore comment "User cannot answer the call". The behavior I saw is: after user select to answer the call. The screen still shows "Incoming" screen. And there is no sound in the call connection.
Aknow, can you please analyze this bug?
Flags: needinfo?(szchen)
Hi pcheng,

I got a Taroko device w/ build id: 20140310100318 but cannot reproduce the issue. There are something need your help.
(1) Is this a regression? The build I use is older than yours.
(2) Tarako is a multisim device. Could you share your detailed setting, e.g., how many sim are inserted in the phone and which one you were used to receive the MT call.
(3) Could you provide the log with ril debugging info. You could turn on the debugging by following steps.

====
To enable debug log, you need to add one line, 'pref("ril.debugging.enabled", true);', into /system/b2g/defaults/pref/user.js in device. Then reboot device or restart b2g service.

detailed step:
adb remount
adb pull /system/b2g/defaults/pref/user.js user.js
[update user.js with adding 'pref("ril.debugging.enabled", true);']
adb push user.js /system/b2g/defaults/pref/user.js
adb shell reboot
Flags: needinfo?(szchen)
This seems to be device specific. I tried on the other device and it works. I will do more tests and update here. Thank you very much for your help!
Attached file dialer.log
This bug can be reproduced with headphone plugged in.

STR:
1. Plugin headphone
2. Make MT call to test device
3. Answer call on test device
4. Repeat 2 and 3
   --> For the second time, incoming Call screen appears and stay forever. User cannot answer/end the call. Device need reboot to kill Phone app process.


Please see attached adb log. Test starts: 03-14 11:56:46.016
Summary: [Tarako] unable to establish the second MT call connection → [Tarako] unable to establish the second MT call connection with headphone
Cool. I could reproduce the issue with headphone plugged in.
Looks like there is no response for the ATA and cause the phone hang.
D/AT      (   92): Channel1: AT> ATA
Hi Sam:
 Please help check why we did not see response for ATA request?
(There is no [0106]< ANSWER in log too)

03-14 17:32:47.400    92   336 D RILC    : [0104]> GET_CURRENT_CALLS
03-14 17:32:47.420    92   336 D RILC    : [0104]< GET_CURRENT_CALLS {[id=1,INCOMING,toa=129,norm,mt,als=0,voc,noevp,0911230714,cli=0,name='(null)',0}
03-14 17:32:47.630    92   335 D RILC    : [0105]> GET_CURRENT_CALLS
03-14 17:32:47.630    92   335 D RILC    : [0105]< GET_CURRENT_CALLS {[id=1,INCOMING,toa=129,norm,mt,als=0,voc,noevp,0911230714,cli=0,name='(null)',0}
03-14 17:32:51.140    92   334 D RILC    : [0106]> ANSWER
03-14 17:32:51.140    92   334 D AT      : Channel1: AT> ATA
Component: RIL → Vendcom
Flags: needinfo?(sam.hua)
okay,

The modem doesn't assert. from the log of modem.it still works well when I end the 2nd call in the remote. but AP can't get any response of Modem.
I think maybe the connection problem between modem and ap. There are maybe conflict between audio channel and RIL channel.
Flags: needinfo?(sam.hua)
Sam, seem like you are working on it. assign to you for now. please reassign if this is incorrect. thanks
Assignee: nobody → sam.hua
blocking-b2g: --- → 1.3T+
Whiteboard: [POVB]
Hi,
please update the newest code. it is resolved now. 
/device/sprd 
git commit id: fd4c8556e28408d73f8485c6b4e4fd21ee4a422f

Thanks!
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(pcheng)
Resolution: --- → INVALID
Resolution: INVALID → WORKSFORME
(In reply to sam.hua from comment #13)
> Hi,
> please update the newest code. it is resolved now. 
> /device/sprd 
> git commit id: fd4c8556e28408d73f8485c6b4e4fd21ee4a422f
> 
> Thanks!

Sam,is this patch already reviewed and uplift to v1.3t? If not, i think it's better to keep this bug open until uplift it.

I will test on sprd's build to see if your fix work.
Status: RESOLVED → REOPENED
Flags: needinfo?(pcheng) → needinfo?(sam.hua)
Resolution: WORKSFORME → ---
It is under the device/sprd which is maintained by us.
u could check this commit log before u build it.
Flags: needinfo?(sam.hua)
Sam and Shawn, please update status.
Flags: needinfo?(sku)
Flags: needinfo?(sam.hua)
The latest SPRD rom works for me.

Hi Peipei:
 Could you please update SPRD pac image (modem image need to be updated.), and reflash the latest ROM you have to double check if this issue was resloved?

Thanks!!
Flags: needinfo?(sku) → needinfo?(pcheng)
Flags: needinfo?(sam.hua)
tested on today's build, it works now. Thanks!

Gaia d8ff994bd96c37ba9a93c343932a5441a78a0eec
Gecko 6db37b3f76b4fe2aa6f8fb5ae9e036ed99344772
BuildID 20140327060053
Version 28.1
ro.build.version.incremental=69
ro.build.date=Thu Mar 27 06:07:07 CST 2014
Status: REOPENED → RESOLVED
Closed: 10 years ago10 years ago
Flags: needinfo?(pcheng)
Resolution: --- → FIXED
Verified that the multiple subsequent calls can be received by a Tarako running 1.3T.

1.3T Environmental Variables:
Device: Tarako 1.3T MOZ
BuildID: 20140502014001
Gaia: a8e0ff550de08e58e4bf75af3cecf175b9b71e70
Gecko: 71790bf476cb
Version: 28.1
Firmware Version: sp6821a-Gonk-4.0-4-29
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: