Closed
Bug 1052456
Opened 10 years ago
Closed 10 years ago
[Loop] In Loop Call established, when one GSM call is receiving, the Loop call isn't put on hold while the GSM continues (ringing).
Categories
(Firefox OS Graveyard :: Gaia::Loop, defect)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: javier.deprado, Assigned: jaoo)
References
Details
(Whiteboard: [mobile app][feedback pending])
Device: Flame / FireE
Loop Version: 609ec57
STR:
1.- Device-A and Device-B are in a loop call.
2.- Device-C makes a GSM call to Device-A
ACTUAL RESULT:
While Device-A is receiving the GSM call (ringing), using long tap in home button to change to Loop App, Loop App doesn't show the hold screen. (and the loop call doesn't send or receive any sound)
EXPECTED RESULT:
The loop screen in device-A should be the "hold screen" (with stop and resume buttons).
Comment 1•10 years ago
|
||
In this case, Loop will show the 'hold' screen once the GSM call is answered (not before), which is the right behavior. The Loop call should be in 'hold' state just when the GSM call is answered. Closing as WORKSFORME.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Comment 2•10 years ago
|
||
(In reply to Borja Salguero [:borjasalguero] from comment #1)
> In this case, Loop will show the 'hold' screen once the GSM call is answered
> (not before), which is the right behavior.
Nope, the webrtc call should be on hold when the device plays the ringtone for the GSM call.
Please, could you give a try again please? This should not happen because it was fully tested. If it still happens, provide as much information as you can. Thanks.
Status: RESOLVED → REOPENED
Flags: needinfo?(javier.deprado)
Resolution: WORKSFORME → ---
Updated•10 years ago
|
Whiteboard: [mobile app] → [mobile app][feedback pending]
Assignee | ||
Updated•10 years ago
|
QA Contact: josea.olivera
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → josea.olivera
QA Contact: josea.olivera
Assignee | ||
Comment 3•10 years ago
|
||
Tested with flame-kk.user.v2.0.gecko-6cc9a4d.gaia-31434a3 and still working fine for me. Javier, could you give it a try please. Thanks!
Reporter | ||
Comment 4•10 years ago
|
||
Tested with flame-KK.eng.v2.0.B-11.Gecko-9362b48.Gaia-263e3b2, loop version: 041ff17, and it works fine now.
In a loop call between Device-A and Device-B, When device-A is receiving GSM call from Device-C, I can see "on hold" in Device-B, and I can change in Device-A to loop app and check than Loop call is on hold.
Flags: needinfo?(javier.deprado)
Assignee | ||
Comment 5•10 years ago
|
||
(In reply to Javier de Prado from comment #4)
> Tested with flame-KK.eng.v2.0.B-11.Gecko-9362b48.Gaia-263e3b2, loop version:
> 041ff17, and it works fine now.
Oops, I didn't see this comments. Resolving then.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 6•10 years ago
|
||
Verified again on:
Dev: Flame / Gecko-8f91e4c.Gaia-31a49c7
Loop client version: 83b17d9
RAM: 512Mb
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•