871962 - [bluetooth] Page timeout is occurred when click the headset of pairing mode for connect in paired list

Status: RESOLVED WORKSFORME

(Firefox OS Graveyard :: Bluetooth, defect, P1)

Description

[leo.bugzilla.gecko]

Attachment: page_timeout_in_pairing_mode

GENERAL Defect
1. Title : Page timeout is occurred when click the headset of pairing mode for connect in paired list
2. Precondition : headset connected
3. Tester`s Action : 
  1) headset disconnected from bt setting
  2) Enter the pairing mode for headset
  3) click the headset on paired list of bt setting
4. Detailed Symptom : cannot connected
5. Expected : Connection success
7.Reproducibility: 50%

Dear Mozilla Team,

In attached hci log, After received the Create_Connection event, Page Timeout is occurred.
Please check it.

Thanks.

Comment 1

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

Hi,

Just checked the log, and I didn't see anything wrong.

The BD_Address of command CreateConnection (0x58170cecaa93) seems to be correct since it is the same as parameters in frame 449. After about 5 secs, the page timeout event returned. As you may know, establishing an ACL connection is not guaranteed to be successful. The result may be different because of surroundings or the problem of headset itself.

Please use another device to test with that headset under the same circumstances. If the fail rate of B2G devices is obviously higher that other devices, please attach more sniffer log/hcidump log to let me know.

Thank you.
Eric

Comment 2

[leo.bugzilla.gecko]

Attachment: mw600_reproduced_movie

Comment 3

[leo.bugzilla.gecko]

Dear Mozilla Team,

I have checked air log and hcidump, but I don't found the any suspect point.
And this symtom is not reproduced on android phone and frequency rate is aobut 30~40%.

So, I uploaded the reproduced video. 
If you can try like this movie, please check the connection process.

Thanks.

Comment 4

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

Hi,

I saw the video. In the video, the tester always puts MW600 into Discoverable mode, which is good, because we know that a headset would not automatically do reconnection when it's in Discoverable mode.

So, the problem is "why page timeout". It shouldn't be the problem of Bluetooth implementation under dom/bluetooth. It's more likely to be the problem of Bluetooth chipset, maybe we could try to adjust configuration or something.

To be honest, I don't think this is an urgent issue. There might be something we could do to make connection more smooth, but should not be from software.

Comment 5

[Wayne Chang [:wchang]]

Triage - consider low user impact as multiple conditions/actions required for this bug to occur. Set to tracking, please renom if reporter/anyone considers user impact is great.

Comment 6

[leo.bugzilla.gecko]

Dear Mozilla Team,

I have tested this, as a result it is headset attribute that not connected directly.
Android phone try to reconnect but d300 is not. 
So, I close this case.

Thansk.