[OPEN C][BLUETOOTH]Coexistence issue: Sounds intermittently by bluetooth headset when searching devices or using wifi.

RESOLVED INCOMPLETE

Status

P1
major
RESOLVED INCOMPLETE
4 years ago
4 years ago

People

(Reporter: yang.xiaohong, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 years ago
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; MALC; .NET4.0C; .NET4.0E; Zune 4.7; InfoPath.2; TCO_20140909091303)

Steps to reproduce:

Listening music by bluetooth headset,
Searching other bluetooth devices,
or open wifi browsing the web.


Actual results:

Sound should be smooth.


Expected results:

Sound intermittently.
Is there any pach for this kind of coexistence issue?
(Reporter)

Updated

4 years ago
Severity: normal → major
OS: All → Gonk (Firefox OS)
Priority: -- → P1
Hardware: All → ARM
This needs to be handle inside BT/Wifi firmware. See  Bug 836516
BluetoothService::ToggleBtAck::Run()
{
  MOZ_ASSERT(NS_IsMainThread());

  // This is requested in Bug 836516. With settings this property, WLAN
  // firmware could be aware of Bluetooth has been turned on/off, so that the
  // mecahnism of handling coexistence of WIFI and Bluetooth could be started.
  //
  // In the future, we may have our own way instead of setting a system
  // property to let firmware developers be able to sense that Bluetooth has
  // been toggled.
#if defined(MOZ_WIDGET_GONK)
  if (property_set(PROP_BLUETOOTH_ENABLED, mEnabled ? "true" : "false") != 0) {
    BT_WARNING("Failed to set bluetooth enabled property");
  }
#endif
As far as I know, Gecko already wrote property for indication purpose. So Android property "bluetooth.isEnabled" had been set, so the wifi util/co-existence util shall be able to check this property value and activate the correct co-existence algorithm from firmware side.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.