If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

[MediaRecord] MediaRecording status is wrong while another app acquire microphone

RESOLVED DUPLICATE of bug 904025

Status

()

Core
Audio/Video: Recording
RESOLVED DUPLICATE of bug 904025
4 years ago
4 years ago

People

(Reporter: cjku, Assigned: rlin)

Tracking

Trunk
ARM
Gonk (Firefox OS)
Points:
---

Firefox Tracking Flags

(blocking-b2g:koi+)

Details

(Whiteboard: [MR 1.2] [FT: Media Recording, Sprint])

(Reporter)

Description

4 years ago
Scenario 
1. User start recording in an recording app
2. An incoming call. Phone app acquire microphone. 
3. Media recorder instance in recording app goes into an unknown state. No ondataavailable callback; requestData out of work.

Basically, app has no idea that media stream is broken since HW contention.

Expect behaviour:
1. media recorder switch to inactive mode.
2. trigger onerror on callback
Assignee: nobody → rlin

Updated

4 years ago
blocking-b2g: --- → koi+
Whiteboard: [MR 1.2] → [MR 1.2] [FT: Media Recording, Sprint]
Test with B2G
1. recording
2. answer MO call, remote side can't hear the uplink sound, but the recording still works.
Telephony channel should be threat at the first priorty.
I think should be hooked in gUM module because gUM would hold the mic audio path.
Set it to be duplicate and let gUM module to handle the problem.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 904025

Updated

4 years ago
No longer blocks: 896935
Component: Video/Audio → Video/Audio: Recording
You need to log in before you can comment on or make changes to this bug.