Closed
Bug 1046113
Opened 10 years ago
Closed 10 years ago
[Loop] Loop client doesn't ring
Categories
(Firefox OS Graveyard :: Gaia::Loop, defect)
Tracking
(b2g-v2.0 affected)
VERIFIED
FIXED
Tracking | Status | |
---|---|---|
b2g-v2.0 | --- | affected |
People
(Reporter: mbarone976, Unassigned)
References
Details
(Whiteboard: [mobile app])
STR
1. Make a call from Device A to device B. The device B answer with only audio
2. After few seconds, the device B ends the call
3. Skip the feedback
4. Make a call again from device A to device B
ACTUAL RESULT
In the device B the user can see the incoming call, but the device doesn't ring. Sometimes this behavior happens the third call, sometimes in the second call.
EXPECTED RESULT
The device should be ring at any incoming call
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.0:
--- → affected
Comment 1•10 years ago
|
||
This issue no longer occurs on the latest 2.0 build with the v165 KK base. There is a delay of about 2 seconds before the ringer will start on subsequent calls but the device always begins to ring eventually.
Environmental Variables:
Device: Flame 2.0
BuildID: 20140820030000
Gaia: 806d37a264743e04a3e1493136486f3e00124e1e
Gecko: 6329352ca531b977979451e77e5862af485388b2
Version: 32.0 (2.0)
Firmware Version: v165
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Loop version: 8c71431
Comment 2•10 years ago
|
||
This was fixed after adding the new set of sounds.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Tested with Flame v2.0 (kk v180) and gecko-ef26d06.gaia-ddec117 and Loop version: eb3a712 and works fine.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•