188.86 KB, application/octet-stream
150.92 KB, application/octet-stream
8.00 MB, application/octet-stream
8.00 MB, application/octet-stream
3.50 MB, application/x-rar
Description: 1. receive MT call which number is "+48696798509". 2. connect MT call 3. make a mo call which number is "*511002" 4. the second call was disconnected by application ---> K.O From the qxdm log we can confirm that "*511002" was already connect. But application disconnected this call: 06-03 13:03:53.908 I/GeckoDump( 1108): zmm:evt.call.state=connected 06-03 13:03:53.908 I/GeckoDump( 1108): zmm:updateCallsDisplay 06-03 13:03:58.488 I/GeckoDump( 1108): telephony.active.hangUp() Please help to check why application hanpup this call.
This is kind of call transfer service provide by Poland network. Below is description from customer: I think that the easiest way to explain what is happening will be to describe the service T-Mobile is offering. You may have a set of phones. One will work as a “gateway” to all the rest. Imagine that you have a secretary and some people in the office. All of them have T-Mo mobile phones. You give outside only the secretary number, so everybody are calling her. She answers the calls, talk to someone to say hello and check to whom she should connect, then – using *XXXXX codes forwards the call to one of the colleagues from the office. In the picture attached you see the “secretary phone”, with incoming call from number +48696798509, and attempt to use *511002 code which should forward this call to Nokia lying on the desk next to our phone. The issue is that this functionality works fine for couple of times, then you can’t use it because green button doesn’t respond.
blocking-b2g: --- → 1.3?
Summary: [Sora][HOMO][TMO PL 57680] can't make another call while one call connected → [Sora][IOT-PL]can't make another call while one call connected
This is a cert blocker. ni? David. Hi David, could you help to find someone to check this one? Thanks Vance
Assignee: nobody → etienne
Target Milestone: --- → 2.0 S4 (20june)
I wasn't able to reproduce the issue on a buri 1.3 from today. Might be because it's highly dependent of the operator, but there's also a fair change the issue is already fixed, so requesting qawanted to confirm. The log from the Description mentions calling telephony.active.hangUp(), I took a look at the current 1.3 code base and we're only calling telephony.active.hangUp() in code paths triggered by user actions in the call screen (button press, headset/bluetooth command etc...), which doesn't match the STR (where the only user action is pressing the call button is the dialer app). PS: can't untar the attached video, looks like we're missing part 3.
Hi Jason, this is a 1.3 certification blocker, can we get someone to verify if the bug is happening? Also, in comment 7, Etienne is commenting that cannot uncompress the attachment. Thanks!
Joshua - Can you get someone assigned to this?
Flags: needinfo?(jsmith) → needinfo?(jmitchell)
I am unable to reproduce this on the latest 1.3 Buri build. In comment 5 it is mentioned that this might be related to a Polish T-mobile service. I do not have access to a Polish SIM in order to verify that. Environmental Variables: Device: Buri 1.3 Build ID: 20140613084813 Gaia: 8d6bd6c484557c5322bf14798a4273d2a8f4300f Gecko: 634b8bb42eea Version: 28.0 (1.3) Firmware Version: v1.2device.cfg
QA Whiteboard: [QAnalyst-Triage?]
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Hei folks, do we have resources in Poland that can try to reproduce this? @vchen, is this a blocker for certification? Looks like a really specific use case.
Hi Francisco - As Jack mentioned in Comment#5, this is a common feature in Poland T-Mobile, so yes it is a cert blocker. However, let me discuss with our partner to see if we can waive this one for 1.3. keep my ni? Thanks
(In reply to Francisco Jordano [:arcturus] [:francisco] from comment #8) > Hi Jason, this is a 1.3 certification blocker, can we get someone to verify > if the bug is happening? > > Also, in comment 7, Etienne is commenting that cannot uncompress the > attachment. > > Thanks! Hi Francisco, our partner just update the last part of the zip file, you can now download and unzip to see the reproduce video Thanks
Flags: needinfo?(vchen) → needinfo?(francisco)
Thanks Vance! Looking forward for the conversations with partner to clarify if we can waive this for 1.3 Cheers.
To my understanding, QA doesn't have anyone working out of Poland. However, Stas from the localization team does work there. So I'd ask him for help to see if he has cycles to try to test this.
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
Target Milestone: 2.0 S4 (20june) → 2.0 S5 (4july)
Change to vendcom since our partner just find a workaround solution for this issue. Pull the 1.3+ flag as well Thanks
blocking-b2g: 1.3+ → ---
Component: Gaia::Dialer → Vendcom
Target Milestone: 2.0 S5 (4july) → ---
link all Fire C (codename: Sora) bugs to a meta one.
You need to log in before you can comment on or make changes to this bug.