923743 - [B2G][Bluetooth] Rocketfish headset cannot put a call on hold to answer call waiting

Status: RESOLVED INVALID

(Firefox OS Graveyard :: Bluetooth, defect)

Description

[Matthew Vaughan]

Attachment: LogCat for answering a call waiting while still on the line with another call.

Description:
When a user takes a call waiting, the bluetooth headset cannot put the call on hold to answer the call waiting. Instead, the first call is terminated and the user has to push the BT headset's answer button a second time to answer the call waiting.

Repro Steps:
1) Update Buri to Build ID: 20131004004003
2) Connect a Rocketfish BT headset to your phone
3) Have another phone call your phone
4) Answer the first call with BT headset
5) Have a second phone call your phone
6) Attempt to answer the call waiting with BT headset

Actual:
The first call is terminated.

Expected:
The first call is put on hold.

Environmental Variables
Device: Buri
Build ID: 20131004004003
Gecko: http://hg.mozilla.org/releases/mozilla-aurora/rev/a4b7282df517
Gaia: 9e21b6bea92fdafcb6787120a8cde0eb25a50495
Platform Version: 26.0a2

Notes:
Repro frequency: 100%
Test Suite Name: Bluetooth
UCID: (bluetooth-013)
Link to failed test case: https://moztrap.mozilla.org/manage/cases/?filter-id=6697#caseversion-id-50168
See attached: logcat.txt
Notes: Rocketfish model:RF-QX4

Comment 1

[Jason Smith [:jsmith]]

Is this reproduce on 1.1?

Comment 2

[Matthew Vaughan]

This bug does reproduce on the latest 1.1 build.

Environmental Variables
Build ID: 20131007041201
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/c630289d6388
Gaia: e5adcf3c23b6709a51087539bc4cdb67683ca4a0
Platform Version: 18.1
RIL Version: 01.01.00.019.246

Comment 3

[Eric Chou [:ericchou] [:echou]]

Hi Matthew,

Rocketfish RF-QX4 seems to be a low-end device. I just checked its user manual and the record of its certification, and it doesn't support feature "Call waiting notification" and "Three way calling". We need hcidump log to investigate more. Please follow instructions on https://wiki.mozilla.org/B2G/Bluetooth#Helpful_Debugging_Information, generate the hcidump log and attach the log to this bug.

Please feel free to ask if you have any questions. Thank you.

Comment 4

[Matthew Vaughan]

Attachment: hcidump for Rocketfish bluetooth headset.

Comment 5

[Matthew Vaughan]

Hey Eric,

Attached is the hcidump for the Rocketfish headset. If you need anything else, please let me know.

Comment 6

[Eric Chou [:ericchou] [:echou]]

Hi Matthew,

Thanks for your help. I've checked the log and it met my expectation. Since the headset doesn't support three way calling, it sent command "AT+CHUP (Call HangUP)" to the mobile phone. According to Bluetooth Handsfree Profile spec, under this circumstances (an active call + an incoming call), we only know that the currently active call should be terminated ("Execution command causes the AG to terminate the currently active call.", retrieved from 4.33.2 HFP spec 1.6). On the other hand, there is no definition to describe how the incoming call should be handled.

To clarify, I took HTC Sensation XL(Android), Samsung Galaxy Nexus(Android) and iPhone 4(iOS 6) as testing devices separately. Both Android devices did pick up the call but iPhone didn't, which means users need to press twice to answer the phone call, just like our behaviour.

I think this is not really a bug, but more like a small feature. It depends on how Dialer deals with AT+CHUP in different situations and what experience are we willing to give users. I'm going to mark this bug as resolved invalid, and please feel free to ask if you have any questions or suggestions.

Thank you.