Closed Bug 928019 Opened 11 years ago Closed 7 years ago

If the low memory killer kills an active process using the microphone, give the user an explicit notification that the microphone has been released

Categories

(Firefox OS Graveyard :: Gaia::System, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: jsmith, Unassigned)

References

Details

It's currently possible that the low memory killer can kill an active process using the micorphone in the background. When this happens, a user silently finds out if they closely watch the recording indicator disappear, which I think is too silent of a notification that the microphone is no longer active. Instead, if the low memory killer kills the process using the microphone, we should be more explicit to indicate that the microphone is no longer active.
Need info to UX to discuss what we should do here.
Flags: needinfo?(firefoxos-ux-bugzilla)
We'll get to this when we've cleared koi+ and koi?, which are taking all of our time right now.
(In reply to Stephany Wilkes from comment #2) > We'll get to this when we've cleared koi+ and koi?, which are taking all of > our time right now. Thinking about this again, this is low priority, so don't worry about putting this on your backlog to look into right now. If we start getting user complaints around this, then I'll reflag to get someone to look into this.
Flags: needinfo?(firefoxos-ux-bugzilla)
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.