1104407 - [FFOS2.0][Woodduck][BT] Can't call the last number via BT headset when there are two SIM cards inserted.

Status: RESOLVED DUPLICATE of bug 1021478

(Firefox OS Graveyard :: Gaia::Dialer, defect, P2)

Description

[sync-1]

DEFECT DESCRIPTION:
 >Can't call the last number via BT headset when there are two SIM cards inserted.
 
  REPRODUCING PROCEDURES:
 1.Insert two SIM cards, go to settings->SIM manager->outgoing calls, select always ask;
 2.Connect with a BT stereo hesdset, and outgoing a call via BT headset;
 3.Then call the last number in call log via BT headset, but it prompt "no  network connetct",can't call last number.--KO
 
 ps: "bt" means blueteeth.

Comment 1

[sync-1]

Attachment: picture

Comment 2

[Josh Cheng [:josh]]

Hi Norry,
qawanted for Woodduck 2.0M and Flame 2.0/2.1/2.2. Thanks!

Comment 3

[Norry.L.F(Leave from Mozilla)]

Attachment: Verify.mp4

This bug can be reproed on Woodduck 2.0M and Flame 2.0, can't repro on Flame 2.1/2.2

On Woodduck 2.0M and Flame 2.0, after redial via BT heaset, device will show "no network connetct".

See the attachments: Verify.mp4 and logcatVerify.txt
Occurrence time:16:37
Occurrence rate:5/5

Repro STR:
1. Insert two SIM cards, go to settings->SIM manager->outgoing calls, select always ask;
2. Pair and connect BT headset
3. Press Home key
4. Redial via BT headset
**There is no response.
5. Launch Phone
**Device shows "no network connetct".

Found time:

Woodduck build:
Gaia-Rev        87b23fa81c3b59f2ba24b84f7d686f4160d4e7cb
Gecko-Rev       d049d4ef127844121c9cf14d2e8ca91fd9045fcb
Build-ID        20141125050313
Version         32.0
Device-Name     jrdhz72_w_ff
FW-Release      4.4.2
FW-Incremental  1416863158
FW-Date         Tue Nov 25 05:06:35 CST 2014
------------------
Flame 2.0:
Gaia-Rev        124c2f85f1b956e9e8429dab5121de702a3bc197
Gecko-Rev       https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/fc90ac008cc1
Build-ID        20141124000201
Version         32.0
Device-Name     flame
FW-Release      4.4.2
FW-Incremental  eng.cltbld.20141124.034117
FW-Date         Mon Nov 24 03:41:27 EST 2014
Bootloader      L1TC00011880
------------------
FLame2.1 build:
Gaia-Rev        8ae086c39011bc8842b2a19bb5267906fa22345a
Gecko-Rev       https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/ebbd5c65c3c1
Build-ID        20141124094013
Version         34.0
Device-Name     flame
FW-Release      4.4.2
FW-Incremental  eng.cltbld.20141124.130744
FW-Date         Mon Nov 24 13:07:55 EST 2014
Bootloader      L1TC00011880
------------------
FLame2.2 build:
Gaia-Rev        aad40f6d6eb8f626c6a20db55b9f00d2e832f113
Gecko-Rev       https://hg.mozilla.org/mozilla-central/rev/be4ba3d5ca9a
Build-ID        20141124100136
Version         36.0a1
Device-Name     flame
FW-Release      4.4.2
FW-Incremental  eng.cltbld.20141124.132512
FW-Date         Mon Nov 24 13:25:25 EST 2014
Bootloader      L1TC00011880

Comment 4

[Norry.L.F(Leave from Mozilla)]

Attachment: logcatVerify.txt

Comment 5

[Josh Cheng [:josh]]

Hi Shawn,
Could you help to check the bug? Thanks!

Comment 6

[Shawn Huang [:shawnjohnjr][:shuang] (as a happy gecko contributor)]

I checked this problem. It seems like it's not bluetooth issue but telephony feature bug.

Comment 7

[sync-1]

Dear mozilla:
 
   May i ask how is it going on?

Comment 8

[Josh Cheng [:josh]]

Hi Shawn,
Could you please help to check the problem? Thanks!

Comment 9

[shawn ku [:sku]]

Geko ril log is not enabled.

Please make sure [1] was set to true, and re-get log for me to check.

// Log command
adb logcat -b radio -b main -v threadtime > /tmp/1104407.log

Stop logging, attach /tmp/1104407.log onto bugzilla, ni?sku then.
Thanks!


[1] - http://dxr.mozilla.org/mozilla-central/source/dom/system/gonk/ril_consts.js?from=ril_consts.js&case=true#17

Comment 10

[Peipei Cheng (needinfo if you need my action)]

Norry, could you please help get gecko ril log per comment 9? Please NI on me if you have any question.

Comment 11

[Sue]

Attachment: logcat

I have uploaded logcat of Flame 2.0
Found time:15:18
Please check it, thanks.

Flame 2.0 versions:
Gaia-Rev        856863962362030174bae4e03d59c3ebbc182473
Gecko-Rev       https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/2d0860bd0225
Build-ID        20141210000202
Version         32.0
Device-Name     flame
FW-Release      4.4.2
FW-Incremental  eng.cltbld.20141210.034839
FW-Date         Wed Dec 10 03:48:50 EST 2014
Bootloader      L1TC00011880

Comment 12

[Peipei Cheng (needinfo if you need my action)]

shawn, could you please take a look at the new logcat? attachment 8534841 [details]

Comment 13

[shawn ku [:sku]]

Operator report "normal call clearing" (16), need Gaia to check what to improve when receiving NormalCallClearingError.


Hi Luke:
 Could you please help check this error cause from Gaia's perspective?



12-11 15:18:10.944 I/Gecko   (  206): -*- RadioInterface[0]: Received message from worker: {"rilMessageType":"callDisconnected","call":{"state":2,"callIndex":1,"toa":129,"isMpty":false,"isMT":false,"als":0,"isVoice":true,"isVoicePrivacy":false,"number":"10010","numberPresentation":0,"name":null,"namePresentation":0,"uusInfo":null,"isOutgoing":true,"isEmergency":false,"isConference":false,"hangUpLocal":true,"failCause":"NormalCallClearingError"},"rilMessageClientId":0}

12-11 15:18:10.944 I/Gecko   (  206): TelephonyService: handleCallDisconnected: {"state":2,"callIndex":1,"toa":129,"isMpty":false,"isMT":false,"als":0,"isVoice":true,"isVoicePrivacy":false,"number":"10010","numberPresentation":0,"name":null,"namePresentation":0,"uusInfo":null,"isOutgoing":true,"isEmergency":false,"isConference":false,"hangUpLocal":true,"failCause":"NormalCallClearingError"}

Comment 14

[Luke Chang [:lchang] (inactive)]

Hi Sean,

This bug seems to be identical to bug 1094670. Since you are investigating that bug, could you also take a look at this and mark one of these bugs as a duplicate? Thanks.

Comment 16

[Sean Lee [:seanlee][:weilonge]]

Attachment: PR for v2.0m

Hi Doug,

Here is my PR. Please help to review it. Thank you.

Comment 17

[Josh Cheng [:josh]]

Hi XingMing,
Can you try patch per comment 16?

Comment 18

[xingming.yin]

(In reply to Josh Cheng [:josh] from comment #17)
> Hi XingMing,
> Can you try patch per comment 16?

Hi:
  I will check it tomorrow.

Comment 19

[Doug Sherk (:drs) (inactive)]

Comment on attachment 8539985 [details] [review]
PR for v2.0m

Instead of using this patch, we could uplift:
* bug 1061473
* bug 982163
* bug 1021478

If you choose not to uplift these, we should at the very least look at the tests here and copy some of them over.

Comment 20

[Sean Lee [:seanlee][:weilonge]]

Hi Seinlin, Josh,

Pleae help to uplift the following patch to v2.0m with the order:
1st: bug 1021478
https://github.com/mozilla-b2g/gaia/commit/5e28fb653ee50f749cf450decc9d75c2ee5a02d1

2nd: bug 982163
https://github.com/mozilla-b2g/gaia/commit/7de5f193237cf94734630a21754852daf797bd77

3rd: bug 1061473
https://github.com/mozilla-b2g/gaia/commit/faa59403d66145b6eb7ed69fa5c04d8eda7fc228

Comment 21

[Sean Lee [:seanlee][:weilonge]]

Hi Seinlin, Josh,

For further explanation, the above 3 patches are tested on Woodduck v2.0m and the test result is PASS.

Thank you.

Comment 22

[Josh Cheng [:josh]]

Hi Sean,
all 2.0M+.

Hi Kai-Zhen,
Can you help to land all of them on 2.0M? Thanks!

Comment 23

[Kai-Zhen Li [:seinlin][:kli]]

Done.

Comment 24

[Josh Cheng [:josh]]

Thank you Sean, Thank you Kai-Zhen,

I will dup this to first bug since there is nothing to fix here. Thanks!

Comment 25

[xingming.yin]

(In reply to Josh Cheng [:josh] from comment #17)
> Hi XingMing,
> Can you try patch per comment 16?

dear mozilla:
   it is pass!

Comment 26

[sync-1]

此bug为克隆bug，源bug：
 
 http://bugzilla.tcl-ta.com/show_bug.cgi?id=834560
 
 已被关闭，请wei.deng关闭此bug