882841 - [B2G][Leo][Cellular & Data] Leo device is not receiving second call when call forwarding is disabled

Status: RESOLVED WORKSFORME

(Firefox OS Graveyard :: Gaia::Settings, defect)

Description

[Jeni]

Call forwarding is broken, which is causing second call to not be received.

Note:  Turn call forwarding on in Call Settings

Repro Steps:
1) Leo Build ID: 20130610070206
2) Call Leo Device with second device
3) Answer phone call and remain on phone
4) Have another phone call Leo
5) View what happens

Actual:
Second call is not received.  User gets no indication someone is calling device.  

Expected:
User sees second call and has option to answer or reject call

Environmental Variables
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/8e3f39363c54
Gaia: ce3b99781d182ad550a325206990c249b0dbcf0e
Platform Version: 18.0

Notes:
Repro frequency: 100% 3/3
Test Suite Name: Cellular & Data
UCID: 3535
Link to failed test case: https://moztrap.mozilla.org/runtests/run/1475/env/314/?&pagenumber=1&pagesize=100&sortfield=order&sortdirection=asc&filter-id=3535&filter-suite=158

Comment 1

[Jeni]

Attachment: Log of issue

Comment 2

[John Hammink]

If I understand correctly, isn't this the correct behavior?  Having call forwarding ON should mean that there is no interruption to the call in progress.  Please recheck this.

Comment 3

[Jeni]

Make sure call-forwarding is disabled not enabled.

Comment 4

[Jeni]

Attachment: Video of Leo Device issue

Comment 5

[Jeni]

Video Link https://www.dropbox.com/s/ohfyifxmdcuxbog/20130613_144153.mp4

Comment 6

[Hsin-Yi Tsai (she/her) [:hsinyi]]

(In reply to Jeni from comment #1)
> Created attachment 762330 [details]
> Log of issue

Thanks for the log, but sadly it isn't much help since it doesn't provide any RIL information. Please help attach the log with RIL debug enabled. 

Also, I am guessing this is a duplicate of Bug 861896. If you ever see similar debug messages as [1], then I'm pretty sure that's the cause.

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=880726#c9

Comment 7

[Tony Chung [:tchung]]

(In reply to Hsin-Yi Tsai [:hsinyi] from comment #6)
> (In reply to Jeni from comment #1)
> > Created attachment 762330 [details]
> > Log of issue
> 
> Thanks for the log, but sadly it isn't much help since it doesn't provide
> any RIL information. Please help attach the log with RIL debug enabled. 
> 
> Also, I am guessing this is a duplicate of Bug 861896. If you ever see
> similar debug messages as [1], then I'm pretty sure that's the cause.
> 
> [1] https://bugzilla.mozilla.org/show_bug.cgi?id=880726#c9

Hi Hsin-Yi, how do we enable RIL debug on the production build?

Comment 8

[Hsin-Yi Tsai (she/her) [:hsinyi]]

(In reply to Tony Chung [:tchung] from comment #7)
> (In reply to Hsin-Yi Tsai [:hsinyi] from comment #6)
> > (In reply to Jeni from comment #1)
> > > Created attachment 762330 [details]
> > > Log of issue
> > 
> > Thanks for the log, but sadly it isn't much help since it doesn't provide
> > any RIL information. Please help attach the log with RIL debug enabled. 
> > 
> > Also, I am guessing this is a duplicate of Bug 861896. If you ever see
> > similar debug messages as [1], then I'm pretty sure that's the cause.
> > 
> > [1] https://bugzilla.mozilla.org/show_bug.cgi?id=880726#c9
> 
> Hi Hsin-Yi, how do we enable RIL debug on the production build?
Hi Tony, please refer to https://bugzilla.mozilla.org/show_bug.cgi?id=811605#c5. Thank you!

Comment 9

[leo.bugzilla.gecko]

Could you check the call forwarding / barring/ waiting options?
You can disable the all CFs using MMI code.

Comment 10

[leo.bugzilla.gecko]

Could you check the call forwarding / barring/ waiting options?
You can disable the all CFs using MMI code.
(Deactivation - all CF : #002#, all conditional CF : #004#)

Comment 11

[Hsin-Yi Tsai (she/her) [:hsinyi]]

I cannot reproduce this issue with
gecko: git mozillaorg/gecko-18, 856e2024ea06f2f92a6b931f7fef41a6ebac0b62
gaia: git mozillaorg/v1-train, aea6834efc2b291971c3065eca7bdfe74a319be8

Comment 12

[cbarker]

jcouassi and all qanalydocs members are QA and perform primarily Blackbox Testing.  If you can give some steps to perform the request in Comment 9, we can get you the information you are requesting, however most code related tasks are best handled by in house QA.

Comment 13

[leo.bugzilla.gecko]

Precondition 
1. Deactivation unconditional CF
  - Dialer > #002# > SEND
2. Deactivation conditional CFs
  - Dialer > #004# > SEND
3. Deactivation incoming Call Barring
  - Dialer > #35*0000# > SEND
    or you can check CB status (*#35#)
3. Check Call Waiting ON
  - Settings > Call settings > Call Waiting is ON

If CF/CB is activated or CW is deactivated, 2nd call will be rejected automatically.

Comment 14

[Jeni]

After doing all preconditions still was unable to receive second call.  Tested with call waiting off as well as on just in case.  

Note: Step 2 received a GenericFailure error and with Call Barring received message saying Call_Barring_Not_Supported_Via_MMI

Comment 15

[Sarah Parsons]

This issue is reproduced on the Buri 1.0.1 Build ID: 20130621070204

Gecko: http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/9c62297d11b0
Gaia: 93241eb6c5d6c110710fad8da3ccd4423312b0c9
Platform Version: 18.0

User is unable to receive a second call with call waiting both enabled and disabled.

Comment 16

[leo.bugzilla.gecko]

We cannot reproduce this issue.

It might depends on your sim card.
Please make sure android device can receive second call with the same sim card you used.

If android device could get second call but FFOS's not, please attach the ril log.

How to get ril log is stated comment 8.

Thanks!

Comment 17

[Sarah Parsons]

We do not have an unlocked android or an android at&t phone to check this issue since we only have at&t SIMs.


(In reply to leo.bugzilla.gecko from comment #16)
> We cannot reproduce this issue.
> 
> It might depends on your sim card.
> Please make sure android device can receive second call with the same sim
> card you used.
> 
> If android device could get second call but FFOS's not, please attach the
> ril log.
> 
> How to get ril log is stated comment 8.
> 
> Thanks!

Comment 18

[leo.bugzilla.gecko]

Then, do you have an Unagi device? Can you test with the same sim?

If not, please use another sim which haven't had black box test.

We don't have any RIL log so it's very hard to investigate but guessing.

We hope your understanding.

Thanks!

Comment 19

[Sarah Parsons]

I was able to check on today's Unagi build, build ID: 20130625070217 and the issue did not occur. I used the same SIM as before. 

Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/29933d1937db
Gaia: 1436e2778b90bd74635b0b94d1cf8ccb0d71b60c
Platform Version: 18.1

Comment 20

[leo.bugzilla.gecko]

How about now?
Is it still reproduced on Leo with the same SIM?
Please check once again all call forwarding options are disabled, call waiting option is enabled. (When call waiting is disabled, 

Settings->Call Settings -> all call forwardings are disabled
Settings->Call waiting -> enabled.

We've never reported this issue before, so please upload ril log when it reproduced on Leo.

Thanks!

Comment 21

[leo.bugzilla.gecko]

I missed some message.

When call waiting is disabled, as you know, cannot receiving second call is normal behavior.

Comment 22

[leo.bugzilla.gecko]

Any updates?

Comment 23

[Sarah Parsons]

This issue is still reproducing on today's Leo Build ID: 20130702070214

Environmental Variables
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/01eacfdb4793
Gaia: 0d5a9a7577f16b6a72a982148c6f509ee1714ea2
Platform Version: 18.1
RIL Version: 01.01.00.019.148 

Second call is not received when call forwarding is enabled. See Ril log attached.

Comment 24

[Sarah Parsons]

Correction: When call waiting is enabled.


(In reply to Sarah Parsons from comment #23)
> This issue is still reproducing on today's Leo Build ID: 20130702070214
> 
> Environmental Variables
> Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/01eacfdb4793
> Gaia: 0d5a9a7577f16b6a72a982148c6f509ee1714ea2
> Platform Version: 18.1
> RIL Version: 01.01.00.019.148 
> 
> Second call is not received when call forwarding is enabled. See Ril log
> attached.

Comment 25

[Sarah Parsons]

Attachment: Ril Log

Comment 26

[Hsin-Yi Tsai (she/her) [:hsinyi]]

(In reply to Sarah Parsons from comment #25)
> Created attachment 770228 [details]
> Ril Log

According to the log, the root cause looks like the same one as Bug 861896, which addresses gecko part only. To fully make it work, you will need to update full_leo.mk. Please make sure your 'device-leo project' is up-to-date. Please make sure you have the quirk "ro.moz.ril.extra_int_2nd_call=true" in full_leo.mk (see bug 880726). Then, remove B2G/out/target/product/leo/system/build.prop, and ./build.sh and ./flash.sh.

Comment 27

[Sarah Parsons]

The issue in comment 15 is no longer reproducing on Leo Build ID: 20130703070210

Environmental Variables
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/a078412b1671
Gaia: b12b6f8895427708fad4e25af180266085bd2e74
Platform Version: 18.1
RIL Version: 01.01.00.019.148 

Call waiting is now working properly.

Comment 28

[Hsin-Yi Tsai (she/her) [:hsinyi]]

I'll close this bug per comment #27.