Closed
Bug 1071535
Opened 10 years ago
Closed 10 years ago
[Loop] The call is always an audio call
Categories
(Firefox OS Graveyard :: Gaia::Loop, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: mbarone976, Assigned: frsela)
References
Details
(Whiteboard: [mobile app][tef-triage])
Attachments
(1 file)
Device: Flame, v.2.0 (KK v180)
Gecko-d87b9af.Gaia-0658006
Loop Id: c56785f
STR
1. Make sure that Loop Setting is configured as "Default call mode: Video"
2. In the call log of device A you need to have at least one missed call
3. Click on the missed call in order to call the user of Device B
4. Answer the call on Device B
ACTUAL RESULT
The call log on device A shows a new entry. The entry is a new outgoing call, but the icon is an audio call instead of a video call.
Comment 1•10 years ago
|
||
> ACTUAL RESULT
> The call log on device A shows a new entry. The entry is a new outgoing
> call, but the icon is an audio call instead of a video call.
Just one question, apart of the icon shown in the call log (you say it's an audio icon) is really an audio call or a video call the one initiated by device A in step 3. ?
Flags: needinfo?(mbarone976)
Updated•10 years ago
|
Severity: normal → major
OS: Mac OS X → Gonk (Firefox OS)
Hardware: x86 → ARM
Whiteboard: [mobile app] → [mobile app][tef-triage]
Updated•10 years ago
|
Assignee: nobody → borja.bugzilla
Updated•10 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Updated•10 years ago
|
Assignee: borja.bugzilla → frsela
Comment 3•10 years ago
|
||
Just adding more info about the issue and the agreed solution:
According to the ACs in bug 1007924 and bug 1010196, the "Default Call mode" setting in Loop only applies when the call is initiated through the contact picker inside the Loop application.
When Calling Back to an ID based on a Call Log entry, the type of call used for that entry will be used. (bug 1007937) so the "Default call mode" setting will not be taken into account.
When QA opened this bug, we realized that when user A receives a missed call in his Call log, as we have not ever answered it, we have never chosen between Audio or video call, so when calling back to B we don't have the call mode info to launch the Loop call. In that case we have agreed with QA team that it'd better to check the "Default Call mode" setting as we do for Loop calls launched though the contact picker.
I'll update the Acs of the corresponding User Stories to clarify this special case for calling back from a missed call entry on the Call history of Loop application.
Assignee | ||
Comment 4•10 years ago
|
||
Attachment #8504612 -
Flags: review?(borja.bugzilla)
Comment 5•10 years ago
|
||
Comment on attachment 8504612 [details]
Proposed patch
Small comment in the PR. Please address it and let me know when ready, we are quite close to land this! Thanks!
Attachment #8504612 -
Flags: review?(borja.bugzilla) → feedback+
Assignee | ||
Updated•10 years ago
|
Attachment #8504612 -
Flags: review?(borja.bugzilla)
Comment 6•10 years ago
|
||
Comment on attachment 8504612 [details]
Proposed patch
Thanks for the modifications! Ready to go! :)
Attachment #8504612 -
Flags: review?(borja.bugzilla) → review+
Assignee | ||
Comment 7•10 years ago
|
||
Landed: https://github.com/mozilla-b2g/firefoxos-loop-client/commit/63be03eb7d8ae3805bf202e46f93f19e4f694c48
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 8•10 years ago
|
||
Verified onfireE (firee-kk-v2.0-SW2E3-1)
Loop version: 1.1 , 2168965
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•