Closed Bug 894848 Opened 12 years ago Closed 12 years ago

[User Story] [Media Recording] Microphone API

Categories

(Firefox OS Graveyard :: General, defect, P1)

ARM
Gonk (Firefox OS)
defect

Tracking

(blocking-b2g:koi+, firefox26 fixed)

RESOLVED FIXED
blocking-b2g koi+
Tracking Status
firefox26 --- fixed

People

(Reporter: ITsay, Unassigned)

References

Details

(Keywords: dev-doc-needed, Whiteboard: [ucid:audio1, FT:Media-Recording, koi:p1])

No description provided.
Depends on: 856361
No longer depends on: 56361
What is this bug about? I'm trying to understand why it depends on bug 856361.
(In reply to :Ehsan Akhgari (needinfo? me!) from comment #1) > What is this bug about? I'm trying to understand why it depends on bug > 856361. It's a tracker bug to track completion of the 1st 1.2 user story for Media Recording - https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AtVT90hlMtdSdEd4TVVjWXNfU3ctMlVhWFRrWkpweVE#gid=25. The notes in the user story indicate that Roc identified that we need bug 856361 for collecting/processing raw audio samples to meet this user story's requirements.
Cool. Please let me know if there is anything specific that I need to be aware of. Thanks!
Depends on: 853356
Summary: [User Story] [Media Recording] Microphone and recording API → [User Story] [Media Recording] Microphone API
No longer depends on: 856361
No longer depends on: 803414
blocking-b2g: --- → koi+
No longer depends on: MediaRecording
No longer depends on: 834513
No longer depends on: 842243
No longer depends on: 855990
Whiteboard: [ucid: audio 1, koi:1] → [ucid: audio 1, FT: Media Recording, koi-p1]
QA Contact: jsmith
Depends on: 904025
Adjust white board keyword to compile with the format agreed in EPM discussion.
Whiteboard: [ucid: audio 1, FT: Media Recording, koi-p1] → [ucid:audio1, FT:Media-Recording, koi:p1]
Flags: in-moztrap?(jsmith)
Depends on: 913896
Ivan, what is the acceptance criteria of audio-capture? Do we need to support multiple audio-capture source before 9/16?
Flags: needinfo?(itsay)
Fred, what audio types are we capturing with current implementation? We are primarily trying to enabler some third parties to capture audio, so we can check with our partner engg if the current formats supported would cover what they need.
cc alfredo since I'm not familiar with that audio types detail
Flags: needinfo?(ayang)
When you are saying audio types, are you referring to internal mic vs. other available input devices such as bluetooth?
(In reply to Fred Lin [:gasolin] from comment #8) > cc alfredo since I'm not familiar with that audio types detail I don't know what "audio type" means here. If my recall is correct, the audio stream (raw data) retrieved via gUM is passed from Android layer and Android layer (audio policy, audio HAL) will do others when input device changed. Upper layer doesn't need to pay special attention.
Flags: needinfo?(ayang)
(In reply to Fred Lin [:gasolin] from comment #6) > Ivan, what is the acceptance criteria of audio-capture? > Do we need to support multiple audio-capture source before 9/16? Hi Fred, No, since it is not supported yet in gecko now, we don't need it before 9/16. It's also need to be discussed if the requirement is necessary.
Flags: needinfo?(itsay)
Depends on: 915705
No longer depends on: 853356
Depends on: 914494
Depends on: 898986
In terms of what's needed for feature complete - bug 898986 is still needed to be able to call this user story feature complete. bug 914494 is a followup issue, but not needed for feature complete.
The two open bugs are the follow up bug and we can fix it during the bug fixing period.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
(In reply to Ivan Tsay (:ITsay) from comment #13) > The two open bugs are the follow up bug and we can fix it during the bug > fixing period. bug 898986 isn't a bug - it's part of the feature landing, so I don't agree with that. I'm not granting a FC signoff without that fixed. Reopening.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Hi Jason, The bug 901559 and 913896 are the bugs to resolve the feature of 898986. That's why I think it is completed.
Flags: needinfo?(jsmith)
No longer depends on: 898986
Looks like the bug in question was already fixed then per Ivan's comments, so this is FC.
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Flags: needinfo?(jsmith)
Resolution: --- → FIXED
Depends on: 917359
Depends on: 917367
Depends on: 828600
Depends on: 917544
Depends on: 918054
Depends on: 918056
Depends on: 918059
Depends on: 918061
Depends on: 918133
Depends on: 918139
Depends on: 918523
No longer depends on: 904025
No longer depends on: 828600
No longer depends on: 914494
No longer depends on: 917359
No longer depends on: 917367
No longer depends on: 917544
No longer depends on: 918054
No longer depends on: 918056
No longer depends on: 918059
No longer depends on: 918061
No longer depends on: 918133
No longer depends on: 918139
No longer depends on: 918523
No longer depends on: 944584
You need to log in before you can comment on or make changes to this bug.