Re: LE ControllerMode fails with Google Chrome

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Francois,

> When setting "ControllerMode = le" in /etc/bluetooth/main.conf file,
> starting a dual scan from Google Chrome fails as you can see below.
> 
> Run ./chrome --enable-web-bluetooth
> Go to https://googlechrome.github.io/samples/web-bluetooth/automatic-reconnect.html
> Click "Scan button"
> Bluetooth chooser should show nearby Bluetooth devices. Sadly it only
> returns the ones in cache.with "ControllerMode = dual"

if you tell bluetoothd to configure a dual mode controller as it is a single mode controller, then only LE side will work. The kernel will block any attempt to use dual mode or BR/EDR functionality. However this might be a simple bug somewhere in the code that accidentally tries to use dual mode on a single mode controller.

Should be rather easy to fix if you can pin-point down the line of code that does this wrong. In general this should not be exposed to the D-Bus interface as an error. It should do the right thing depending on what controller is used or how it is configured.

Regards

Marcel

--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux