Closed
Bug 948982
Opened 12 years ago
Closed 12 years ago
[Unagi_1.2][Pre-IOT] Call waiting freeze when adding a third party
Categories
(Firefox OS Graveyard :: Gaia::Dialer, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: dpalomino, Unassigned)
References
Details
Attachments
(1 file)
|
335.95 KB,
text/plain
|
Details |
Issue seen during pre-iot for 1.2.
device: unagi
Gecko: d77ba08
Gaia: 1b67b55
AU: AU_LINUX_GECKO_B2G_ICS_1.2.01.02.00.019.120
STR:
1. Establish voice call #1
2. Establish a second voice call #2 (call #1 will be on hold). We DON'T join these calls.
3. Try to establish a third voice call #3
Result:
- Third voice call is not established
- No error message shown
- It is not possible to change between the two previously established calls, or to join the calls
Expected:
- Third voice call established (if device/network support this?)
- In case not allowed, error message shown
- It should not affect to previously established calls
Nonminated for koi?
Comment 1•12 years ago
|
||
David,
Please take a look.
blocking-b2g: koi? → koi+
Flags: needinfo?(dscravaglieri)
Comment 2•12 years ago
|
||
n? to rik and etienne to take a look at this bug.
Flags: needinfo?(etienne)
Flags: needinfo?(dscravaglieri)
Flags: needinfo?(anthony)
Comment 3•12 years ago
|
||
We don't support more than 2 open lines.
I agree an error message would be nice, let's file a bug for this add, but definitely not koi+.
Now for this part:
> It should not affect to previously established calls
Can we get a logcat?
Flags: needinfo?(etienne)
Keywords: qawanted
Updated•12 years ago
|
Flags: needinfo?(anthony)
Updated•12 years ago
|
QA Contact: sparsons
Comment 4•12 years ago
|
||
I am unable to reproduce this issue on the Buri 1.2 Build ID: 20131212004004
BuildID: 20131212004004
Gaia: 6d02039072a2ae5cf9225a6f4c78ed49decfab5c
Gecko: 8bae10bb0aed
Version: 26.0
Base: V1.2_20131209
Also, I can not reproduce this issue on the Buri 1.3 Build ID: 20131212004003
BuildID: 20131212004003
Gaia: 588a3e02c4ace3b3341ba1f6bb7274120b53b2b3
Gecko: 031270be3702
Version: 28.0a2
Base: V1.2_20131209
Keywords: qawanted
Comment 6•12 years ago
|
||
Sarah: Did you try with Commercial RIL or Moz RIL?
Hsin-yi: ccing you in case this turns out to be RIL related.
Flags: needinfo?(sparsons)
Comment 7•12 years ago
|
||
Moz RIL
(In reply to Anthony Ricaud (:rik) [out until Jan 7] from comment #6)
> Sarah: Did you try with Commercial RIL or Moz RIL?
>
> Hsin-yi: ccing you in case this turns out to be RIL related.
Flags: needinfo?(sparsons)
Comment 10•12 years ago
|
||
(In reply to Sarah Parsons from comment #7)
> Moz RIL
>
> (In reply to Anthony Ricaud (:rik) [out until Jan 7] from comment #6)
> > Sarah: Did you try with Commercial RIL or Moz RIL?
> >
> > Hsin-yi: ccing you in case this turns out to be RIL related.
are you sure you used Moz RIL? In comment 2, you mentioned the base image is : Base: V1.2_20131209. Did you flash gecko and gaia only over this base? Because if you did, then you're on a Com RIL.
If you did a full Flash, then its likely you were testing Moz RIL.
Please reconfirm.
Updated•12 years ago
|
Flags: needinfo?(sparsons)
Comment 11•12 years ago
|
||
Hi Tony, what I'm on the seeing on the latest Buri 1.2 COM Ril is that the user cannot have more than 2 calls on the line, when the user attempts to add a 3rd, an error message appears, no freezing is present and the user can hang up both already connected calls.
On the Moz RIL, the user can connect no more than 2 calls, when the user attempts to connect a third an error will prompt and when they try to disconnect the already two connecting calls, the user will remain on the connected call screen (bug 937773)
FYI: I'm using the old base 20131115. If you'd like I can check on a newer base.
Gaia fcf1c2fe020c29da4755621cbffdc1a333a43be9
SourceStamp 129ad3c335a5
BuildID 20131216004002
Version 26.0
(In reply to Tony Chung [:tchung] from comment #10)
> (In reply to Sarah Parsons from comment #7)
> > Moz RIL
> >
> > (In reply to Anthony Ricaud (:rik) [out until Jan 7] from comment #6)
> > > Sarah: Did you try with Commercial RIL or Moz RIL?
> > >
> > > Hsin-yi: ccing you in case this turns out to be RIL related.
>
> are you sure you used Moz RIL? In comment 2, you mentioned the base image
> is : Base: V1.2_20131209. Did you flash gecko and gaia only over this
> base? Because if you did, then you're on a Com RIL.
>
> If you did a full Flash, then its likely you were testing Moz RIL.
>
> Please reconfirm.
Flags: needinfo?(sparsons)
Keywords: qawanted
Comment 12•12 years ago
|
||
Using the updated base 20131209, I cannot reproduce this issue on either Com or Moz Ril on the latest 1.2 Buri Build ID: 20131216004002
Gaia fcf1c2fe020c29da4755621cbffdc1a333a43be9
SourceStamp 129ad3c335a5
BuildID 20131216004002
Version 26.0
Comment 13•12 years ago
|
||
Moz QA cannot reproduce this issue. Sarah has spent a handful of different scenarios using various base images, Com RIL, and Moz RIL. The latest base image in comment 12 does not freeze this problem.
Going to renom this bug since its not reproducible.
blocking-b2g: koi+ → koi?
Comment 14•12 years ago
|
||
Could this failure depend on whether or not we're on 3G?
Comment 15•12 years ago
|
||
Comment 16•12 years ago
|
||
Hi,
Attached you could find the logs of the bug reported with the build used then, just in case they are useful to see where the problem could be and avoid it for the future.
I also tried with latest v1.2 build both with MOZ and Com RIL and not able to reproduce the problem.
12/17 v1.2 build:
Gecko-f6f325b
Gaia-4f53ba8
It apperas a message when trying to call to the third number: 'Unable to make a phone call now' Cannot make a call. If you are already dialing, please hang up firs. And 'Ok' option.
| Reporter | ||
Comment 17•12 years ago
|
||
Thanks a lot Sarah, Isabel, for retesting this. So, as it's not present anymore with the recent builds, I guess we can move it to WFM.
Thanks!
David
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Updated•12 years ago
|
blocking-b2g: koi? → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•