Closed Bug 812690 Opened 12 years ago Closed 6 years ago

Mute call when volume buttons are pressed during incoming call. Dialer.

Categories

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

ARM
Gonk (Firefox OS)
defect

Tracking

(blocking-basecamp:-)

RESOLVED WONTFIX
blocking-basecamp -

People

(Reporter: sicking, Assigned: alive)

References

Details

(Whiteboard: interaction)

+++ This bug was initially created as a clone of Bug #810780 +++

From bug 810780 comment 7:

Incoming calls:
- When there is a incoming call (ringing), pressing the volume rocker should reject the call.

I'm not sure if this is best done through modifications to the system app or the the telephony app.

The telephony app right now does not have access to the keypress events that are fired when the volume buttons are pressed.

Potentially this can be fixed by having the system app call navigator.telephony.calls[0].hangUp() but I'm not sure how well the telephony app deals with that.
c.c. Dialer app man, Etienne.
Mmmmhh... not sure how we're going to do this...

Can we make the "ring" audio channel go to 0 on the first key press?

+ the "stop ringing but don't let people know I'm hanging up on them" is a great feature :)
Is possible to stop play the ringtone when user press the volume key?
(In reply to Etienne Segonzac (:etienne) from comment #2)
> Mmmmhh... not sure how we're going to do this...
> 
> Can we make the "ring" audio channel go to 0 on the first key press?

The problem here should be: What's the volume of ring when the next call coming? Go to 0 means to set mozSettings, so the setting would be overwritten.
Then, mute always from the user presses the first volume key? But the user will be hard to recognize that he needs to goto settings app to bring the volume greater than 0...
Exactly. Setting the volume to 0 through the settings API would "work", but would mean that we risk the volume getting stuck at 0 if the phone is shut down or crashes between when we set it to 0 and we set it back to its previous volume. It would also potentially result in some weird interactions if you go to the settings app and look at the volume there before the call is hung up and we reset the volume to the previous value.

Possibly all of these problems are ones we can live with for v1 though. Might be better than living with that you can't silence an incoming call without using the touch screen.
We should mute the call, not reject it. Am updating the summary thusly. This is a strong nice-to-have for v1, IMO. cc'ing CLee for a product call on blocking+.
Summary: Reject call when volume buttons are pressed during incoming call → Mute call when volume buttons are pressed during incoming call
Flags: needinfo?(clee)
Summary: Mute call when volume buttons are pressed during incoming call → Mute call when volume buttons are pressed during incoming call. Dialer.
Whiteboard: interaction
Assignee: nobody → alive
Chris, please renominate if needed.
blocking-basecamp: ? → -
I agree that the call should not be rejected, but wouldn't block on this.
Bumping down to P4 as a nice to have.
Flags: needinfo?(clee)
Priority: P1 → P4
Depends on: 820706
Firefox OS is not being worked on
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.