860684 - [Buri][BT][regression]BT headset disconnected itself when the second call coming

Status: RESOLVED FIXED

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

Description

[sync-1]

+++ This bug was initially created as a clone of Bug #438078 +++
 
 Created an attachment (id=386883)
 log
 
 DEFECT DESCRIPTION:
 BT headset disconnected itself when the second call coming
 
  REPRODUCING PROCEDURES:
 1.Connected a BT headset(Vondafone A2201)
 2.Dial up a call such as 10086,then a another call coming
 3.Find 10086 have no sound output,back to seting ,BT headset has disconnected itself
 PS:Even hang up and black screen one time
 
  EXPECTED BEHAVIOUR:
 For KO,BT headset should not disconnected itself
 
  ASSOCIATE SPECIFICATION:
 
  TEST PLAN REFERENCE:
 
  TOOLS AND PLATFORMS USED:
 
  USER IMPACT:
 
  REPRODUCING RATE:
 5/5
  For FT PR, Please list reference mobile's behavior:
 
 ++++++++++ end of initial bug #438078 description ++++++++++

Comment 1

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

Gina, would you please take a look? Thanks.

Comment 2

[Alex Keybl [:akeybl]]

Blocking, assuming that this reproduces.

Comment 3

[Gina Yeh [:gyeh] [:ginayeh]]

Followed the reproduce procedures but had no luck to reproduce. Can anyone help to reproduce it?

Comment 4

[Shawn Huang [:shawnjohnjr][:shuang] (as a happy gecko contributor)]

I think this could be IOP problem, could you provide air sniffer trace? Since there are many reason to cause bluetooth disconnection. We need air sniffer trace to identify problem. Otherwise, we cannot proceed this bug.

Comment 5

[Gina Yeh [:gyeh] [:ginayeh]]

I tried with two different Bluetooth headset: Jabra wave+ and Plantronics discovery 975. There's no problem with both of them. In details, the established connection is still existed, we can either "release the current call and answer the new call" or "put current call on hold and answer the new call".

Please also tell us your version number of Gecko. Thanks.

Comment 6

[Kai-Chih Hu [:khu]]

Suggest to talk with the reporter face to face this week.

Comment 7

[Kai-Chih Hu [:khu]]

If you don't know who they are, ping me.

Comment 8

[Jason Smith [:jsmith]]

Based on Kevin's comments, I'm removing qawanted and suggesting that Gina and the reporter talk to each other to figure this out to avoid QA testing churn.

Comment 9

[sync-1]

Gecko version:
 AU_LINUX_GECKO_ICS_STRAWBERRY_V1.01.00.01.19.059

Comment 10

[zhiming.tang]

Attachment: logcat_dmesg_log

Logcat+dmesg
hcidump will arrive later...

Comment 11

[Gina Yeh [:gyeh] [:ginayeh]]

Thanks, zhiming. I've checked the attachment. But I cannot get any hint from either logcat or dmesg.

Will come back and check it soon once if hcidump or sniffer trace is attached.

Comment 12

[Gina Yeh [:gyeh] [:ginayeh]]

n-i for hcidump or sniffer trace.

Comment 13

[sync-1]

Can not verify this PR on sw123 or sw123-1 becasuce PR:437756
 Summary:  [REG][CW]No incoming call interface when one call established block.
 Call waiting have no effect!
 Thanks!

Comment 14

[Cheng-An, XIONG]

(In reply to sync-1 from comment #13)
> Can not verify this PR on sw123 or sw123-1 becasuce PR:437756
>  Summary:  [REG][CW]No incoming call interface when one call established
> block.
>  Call waiting have no effect!
>  Thanks!

on latest sw, it's blocked by https://bugzilla.mozilla.org/show_bug.cgi?id=863145

Comment 15

[Kai-Chih Hu [:khu]]

The reporter can't reproduce this issue anymore with latest build. Close this issue for now. Thanks!

Comment 16

[zhiming.tang]

(In reply to sync-1 from comment #13)
> Can not verify this PR on sw123 or sw123-1 becasuce PR:437756
>  Summary:  [REG][CW]No incoming call interface when one call established
> block.
>  Call waiting have no effect!
>  Thanks!

Hi Gina,

We can not reproduce the bug on Buri with latest SW release since the process is broken by another issue:

https://bugzilla.mozilla.org/show_bug.cgi?id=855577

In addition we realized the bug also not re-producible on the old build, maybe it was linked with some special condition. What a about we downgrade the priority of this issue, at least remove tef+ for the moment

Comment 17

[Gina Yeh [:gyeh] [:ginayeh]]

Hi Zhiming,

Kevin helped to close this issue since it can't be re-producible now. Feel free to re-open it if needed.

Comment 18

[Wayne Chang [:wchang]]

Removing tef+ per comment 16

> 
> In addition we realized the bug also not re-producible on the old build,
> maybe it was linked with some special condition. What a about we downgrade
> the priority of this issue, at least remove tef+ for the moment

Please reopen and renom if issue reappears.