1096712 - [Loop] While connected with another device, if one device makes a call, then the loop app is closed, the other call will stay on hold for a few minutes

Status: RESOLVED WONTFIX

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

Description

[Robert Mead [:RobertM]]

Attachment: Flame2.1logcat.txt

Description:
While on a Loop call with another device, if Device A makes a call to a third device, Device B's loop call will be put on hold. If device A then force quits the loop app, Device B won't register the lost signal and remain on hold for several minutes before ending.
   
Prereq:
Have the loop app installed on 2 devices and have a 3rd device too

Repro Steps:
1) Update a Flame device to BuildID: 20141107001205
2) Establish a loop call between the 2 devices
3) Use Device A's 'Dialer' app and call the 3rd device(Device B should be put on hold)
4) On Device A, go into card view and force close the loop call

Actual:
The call Ends on Device A, but Device B continues to remain on hold for several minutes

Expected: 
The loop call should end on Device A and Device B


Flame 2.1(319mb)(KitKat)(Shallow Flash)

Device: Flame 2.1 (319mb)(Kitkat Base)(Shallow Flash)
BuildID: 20141110001201
Gaia: 0ec1925fc37b7c71d129ae44e42516a0cfb013c4
Gecko: 97487a2d1ee6
Version: 34.0 (2.1)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
  

Notes: Due to a Bug 1095706, sometimes it can be difficult to force close the Loop app

Repro frequency: 100%
See attached: logcat, video - http://youtu.be/evguWlyh-wk

Comment 1

[Robert Mead [:RobertM]]

This issue also occur in Flame 2.2(319mb) and Flame 2.0(319mb)

While on a loop call, if one device calls a 3rd device via the dialer, Device B's loop call will be put on hold. If Device A's loop call is force closed, it won't be recognized on Device B and it will remain on hold for several minutes.

Flame 2.2

Device: Flame 2.2 Master (319mb)(Kitkat Base)(Shallow Flash)
BuildID: 20141110040206
Gaia: 5f8206bab97cdd7b547cc2c8953cadb2a80a7e11
Gecko: d380166816dd
Version: 36.0a1 (2.2 Master)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0


Flame 2.0

Device: Flame 2.0 (319mb)(Kitkat Base)(Shallow Flash)
BuildID: 20141110000204
Gaia: d3e4da377ee448f9c25f908159480e867dfb13f3
Gecko: 7198906837e7
Version: 32.0 (2.0)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Comment 2

[KTucker [:KTucker][Inactive 3/4/2016]]

Massimo, can you weigh in on whether or not this is a blocker? The call seems to remain on hold for a while after the call has ended.

Comment 3

[Loli (:lolimartinezcr)]

flame
v2.0
188based
Gecko-aaf47aa
Gaia-28991b2

Loop version:1.1, 38eadf0

I can't reproduce this bug, because with a Loop call established I can't close Loop application. 

Also, when user clicks in "home" button with GSM call established, this call is positioned in header and I can't do drag and drop in "utility try".

Comment 4

[BMO Automation]

Firefox OS is not being worked on