838025 - [System][User Story] Call waiting with Bluetooth headset

Status: RESOLVED WORKSFORME

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

Description

[Peter Dolanjski [:pdol]]

UCID: Bluetooth-013

User Story:
As a user that is currently on a phone call using a Bluetooth headset, I want to be able to answer another incoming call from the headset, placing the first call on hold.

Comment 1

[Rob MacDonald [:robmac]]

Hi Peter - Casey checked with the developers and the support seems to be in place for:

1) Hanging up current call and answering new call
2) Holding current call and answering new call.

This is determined by the headsets button configuration.

Based on this, can we close this story / bug?

- Rob

Comment 2

[[:fabrice] Fabrice Desré]

We need QA to verify first.

Comment 3

[Marcia Knous [:marcia]]

Do we need to verify on a particular Bluetooth headset? I have a Plantronics and a Jabra headset ATM.

Comment 4

[Marcia Knous [:marcia]]

I tested the use cases in Comment 1 and I can report the following - this testing was done with the latest nightly build on unagi.

*Hanging up current call and answering new call
**Worked with Plantronics Marque 2 headset but not with Jabra headset. The Jabra headset did not give me an audible signal for the second incoming call.

*Holding current call and answering new call
**Worked with Plantronics Marque 2 headset, but not with Jabra headset. The Jabra headset did not give me an audible signal for the second incoming call.

Note that the Jabra headset is a lower end headset - http://jabra.com/Products/Bluetooth/JABRA_TALK/Jabra_TALK.
Plantronics headset: http://www.plantronics.com/us/product/m165

Comment 5

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Removing QAWanted as Marcia tested.  Thanks Marcia!

Comment 6

[Peter Dolanjski [:pdol]]

QA team, how do you want to handle closing out features like this?
It clearly works on some headsets.  
Should we close out this feature bug and allow additional bugs to be raised for specific headsets that do not work?

Comment 7

[Jason Smith [:jsmith]]

(In reply to Peter Dolanjski from comment #6)
> QA team, how do you want to handle closing out features like this?
> It clearly works on some headsets.  
> Should we close out this feature bug and allow additional bugs to be raised
> for specific headsets that do not work?

That sounds right to me.

Comment 8

[Kai-Chih Hu [:khu]]

(In reply to Peter Dolanjski [:pdol] from comment #6)
> QA team, how do you want to handle closing out features like this?
> It clearly works on some headsets.  
> Should we close out this feature bug and allow additional bugs to be raised
> for specific headsets that do not work?

Should we still include this one into the scope of v1.1.0? 
Thanks.

Comment 9

[Dietrich Ayala (:dietrich)]

Comment #6 is correct - file bugs for individual headsets confirmed to not work, and nominate those for blocking.

Product team: we need a framework for evaluating things like this. Eg: "for country X, Firefox OS should support these top 5 headsets for sale in that market, as specified by the carrier partner".

Comment 10

[Dietrich Ayala (:dietrich)]

And closing per previous comment.