Created attachment 8516960 [details] bluetoothlog.txt Description: If the user recieves an incoming call, while in the process of pairing a bluetooth headset, the bluetooth device will automatically answer the incoming call as soon as it finishes pairing. Repro Steps: 1) Update a Flame device to BuildID: 20141104001202 2) Open settings 3) Open Bluetooth page 4) Enable "bluetooth" and "visible to all" 5) Set a bluetooth headset to pairing mode 6) Confirm that bluetooth device is visible under "Devices in the area" section 7) Initiate an incoming call from a different device 8) Tap on the icon for the bluetooth headset BEFORE incoming call is recieved Actual: When the bluetooth headset finishes pairing the call will be automatically answered. Expected: Call should not be answered/ignored without user input. Environmental Variables: Device: Flame 2.1 (319mb)(Kitkat Base)(Shallow Flash) BuildID: 20141104001202 Gaia: 8b0cf889ae0d48a9eb7ecdcb9b67590de45cc5e5 Gecko: 388b03efe92d Version: 34.0 (2.1) Firmware: v188-1 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Repro frequency: 100% See attached: Youtube video, logcat Youtube Link: https://www.youtube.com/watch?v=0wJ9xlFfI74
Issue DOES occur on Flame 2.2(319mb)(KitKat)(Shallow Flash) and Flame 2.0(319mb)(KitKat)(Shallow Flash) Flame 2.2 Device: Flame 2.2(319mb)(KitKat)(Shallow Flash) Build ID: 20141104040207 Gaia: 3c50520982560ccba301474d1ac43706138fc851 Gecko: 54d05732f29b Version: 36.0a1 (2.2) Firmware Version: v188-1 User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0 Flame 2.0 Device: Flame 2.0(319mb)(KitKat)(Shallow Flash) BuildID: 20141104000201 Gaia: fe2167fa5314c7e71c143a590914cbf3771905a8 Gecko: 241e51806687 Version: 32.0 (2.0) Firmware: V188-1 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 Actual Result: When the bluetooth headset finishes pairing the call will be automatically answered.
[Blocking Requested - why for this release]: The device should not be answered unless the user does manual input. This is poor UX and flow.
blocking-b2g: --- → 2.0?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
This issue can also be reproduced by Nexus 4 with native android image. Probably this issue is related to the underlying bluetooth stack.
[Triage] push to 2.2 given current phase and timing of 2.0 and 2.1.
blocking-b2g: 2.0? → 2.2?
Created attachment 8522633 [details] hcidump.log The bug can be reproduced on Flame/Nexus 4 + JAMBOX by Jawbone. Attached hcidump shows it's bluetooth headset that commands phone to answer the incoming call after connection is established. -- Hcidump log shows phone received command (ATA) from bluetooth headset to answer the incoming call, and then responded OK. > ACL data: handle 4 flags 0x02 dlen 12 L2CAP(d): cid 0x0043 len 8 [psm 3] RFCOMM(d): UIH: cr 0 dlci 4 pf 0 ilen 4 fcs 0xbf A T A . < ACL data: handle 4 flags 0x02 dlen 15 L2CAP(d): cid 0x0140 len 11 [psm 3] RFCOMM(d): UIH: cr 1 dlci 4 pf 1 ilen 6 fcs 0x79 credits 1 . . O K . .
The bug can NOT be reproduced with Flame/Nexus 4 + Plantronics bluetooth headset. Per comment 5, the bug occurrence depends on bluetooth headset behaviour and phone can only answer incoming call if headset commands. Mark this bug as WONTFIX. Please reopen it for any concern. Also still good to know, cinnes, which bluetooth headset do you use?
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WONTFIX
This is by headset design. Auto answer incoming call, is to resolve if user is turning on bluetooth headset at the moment call is ringing, call will be answered and audio will be routed to bluetooth automatically.
The headset I used was the GoGroove Airband Bluetooth Headset. Product link:http://www.gogroove.com/AirBand-Bluetooth-Wireless-Stereo-Headphones-with-Handsfree-Microphone-pid8857#tab-attribute
I was also able to reproduce this issue on todays Flame 2.1 kk (319mb)(Shallow Flash) build using the P253 BT Bluetooth Stereo Headset by Arctic. Product link:http://www.arctic.ac/us_en/p253bt.html
You need to log in before you can comment on or make changes to this bug.