Closed Bug 941584 Opened 12 years ago Closed 12 years ago

[bluedroid] Assertion failure: !mController, dom/bluetooth/bluedroid/BluetoothHfpManager.cpp:1243

Categories

(Firefox OS Graveyard :: Bluetooth, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:-)

RESOLVED WORKSFORME
1.3 C1/1.4 S1(20dec)
blocking-b2g -

People

(Reporter: shawnjohnjr, Assigned: shawnjohnjr)

Details

STR: 1. Connect HFP/A2DP headset 2. Force to turn off bluetooth BluetoothHfpManager::Disconnect(BluetoothProfileController* aController) { MOZ_ASSERT(NS_IsMainThread()); NS_ENSURE_TRUE_VOID(sBluetoothHfpInterface); bt_bdaddr_t deviceBdAddress; StringToBdAddressType(mDeviceAddress, &deviceBdAddress); NS_ENSURE_TRUE_VOID(BT_STATUS_SUCCESS == sBluetoothHfpInterface->disconnect(&deviceBdAddress)); MOZ_ASSERT(!mController); mController = aController; }
I've tested HFP for several days but I have never run into this issue. Since I couldn't reproduce, I'm going to remove this blocker in order to not affect the time line of HFP porting on bluedroid. ni? Shawn for more investigation.
No longer blocks: 911943
Flags: needinfo?(shuang)
(In reply to Eric Chou [:ericchou] [:echou] from comment #1) > I've tested HFP for several days but I have never run into this issue. Since > I couldn't reproduce, I'm going to remove this blocker in order to not > affect the time line of HFP porting on bluedroid. > > ni? Shawn for more investigation. Here is the more accurate STR: 1. Connect HFP/A2DP headset 2. Play music via A2DP 3. Force to turn off bluetooth It looks like this will be easier to hit the problem.
Flags: needinfo?(shuang)
OS: Linux → Gonk (Firefox OS)
Hardware: x86_64 → ARM
Target Milestone: --- → 1.3 C1/1.4 S1(20dec)
blocking-b2g: --- → 1.3?
triage: not blocking release. please fix in on trunk and ask for approval to uplift. thanks
blocking-b2g: 1.3? → -
I cannot reproduce this bug on the latest build, strange :( 3 weeks ago, I can hit the bug.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.