Closed Bug 1183620 Opened 7 years ago Closed 6 years ago

With a connected call and an incoming one hanging up the first call prevents the second one from being answered

Categories

(Firefox OS Graveyard :: Emulator, defect, P3)

All
Gonk (Firefox OS)
defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: gsvelto, Unassigned)

Details

(Whiteboard: [EMU] [CI])

STR:

1. Launch the emulator
2. Connect to it via telnet
3. In the telnet prompt create a first call: gsm call 456
4. In the phone UI answer the first call
5. In the telnet prompt create a second call: gsm call 789
6. In the phone UI press the red button to hangup the first call and answer the incoming one

Expected result:

The first call is hung up and the second call is answered

Actual result:

The first call is hung up and the second one remains in the waiting state. Calling TelephonyCall.answer() on it doesn't seem to do anything even though the resulting promise resolves correctly.

I've encountered this issue on the x86 KitKat emulator so I'm not sure if it affects the regular one too. I'll try and see if it happens there too when I have some time.
Priority: -- → P3
Blocks: emu-x86-kk-tests
No longer blocks: emulator-kk
No longer blocks: b2g-emulator-x86-KK
Whiteboard: [EMU] [CI]
This is a feature request to emulation capability but not a blocker against enabling emu-x86-kk tests. Removing the dependency to reflect the fact.
No longer blocks: emu-x86-kk-tests
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.