1110605 - [FFOS2.0][Woodduck][Call]MS always display incoming call screen and ringing even the remore party already hang up the call.

Status: RESOLVED DUPLICATE of bug 1108520

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

Description

[sync-1]

Created an attachment (id=1064854)
 mtklog
 
 DEFECT DESCRIPTION:
 MS always display incoming call screen and ringing even the remore party already hang up the call.
 
  REPRODUCING PROCEDURES:
 1. Call DUT by a work telephone
 2. Before connected， hung up at MO side
 >DUT would stay at callscreen and ringing
 This issue doesn't occur when dial DUT via a cellphone.
 It is ok on sw7G1A+Zz.not ok on sw7G1b+zz
 
  EXPECTED BEHAVIOUR:
 MS will hang up immediately when the remote party hangup the call.
 >TEL:[phone](61945)
 
  ASSOCIATE SPECIFICATION:
 
  TEST PLAN REFERENCE:
 
  TOOLS AND PLATFORMS USED:
 
  USER IMPACT:
 
  REPRODUCING RATE:
 
  For FT PR, Please list reference mobile's behavior:

Comment 1

[sync-1]

Attachment: screenshot

Comment 2

[sync-1]

Attachment: mtklog

Comment 3

[sync-1]

this issue occurs after we merged patch MTK v1.1 patch3, maybe the change in dom/system/gonk/ril_worker.js caused this problem. After we reverted modifications here, this issue doesn't occur any more. 
 
 -  _processClassifiedCalls: function(removedCalls, remainedCalls, addedCalls,
 -                                    failCause) {
 +  _processCalls: function(newCalls, failCause) {
 +    // Let's get the failCause first if there are removed calls. Otherwise, we
 +    // need to trigger another async request when removing call and it cause
 +    // the order of callDisconnected and conferenceCallStateChanged
 +    // unpredictable.
 +    if (failCause === undefined) {
 +      for each (let currentCall in this.currentCalls) {
 +        if (!newCalls[currentCall.callIndex] && !currentCall.hangUpLocal) {
 +          this.getFailCauseCode((function(newCalls, failCause) {
 +            this._processCalls(newCalls, failCause);
 +          }).bind(this, newCalls));
 +          return;
 +        }
 +      }
 +    }

Comment 4

[sync-1]

The devices would ask fail cause forever when this issue happens.

Comment 5

[Johan Lorenzo [:jlorenzo] - On PTO - Back on July 28th]

QA wanted for a branch check on Woodduck and Flame.

Comment 6

[Joshua Mitchell (Inactive)]

Kirkland office does not have a land-line; leaving QA-Wanted tag for other offices/labs

Comment 8

[sync-1]

Hi Mozilla,
   would you please make 1108520 public or add [e-mail] to its CC list? 
   'You are not authorized to access bug #1108520'..

Comment 9

[Josh Cheng [:josh]]

(In reply to sync-1 from comment #8)
> Hi Mozilla,
>    would you please make 1108520 public or add [e-mail] to its
> CC list? 
>    'You are not authorized to access bug #1108520'..

Done.

Comment 10

[Shally Li（leave from Mozilla）]

Per Comment 7 (DUPLICATE BUG),clear "qawanted".