Could not force LE connection to a dual mode server

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

 



Hello,

I have two dual mode devices (BR/EDR & LE) and I need them to
communicate through LE transport. The server device advertises as an
LE general discoverable mode and does not specify that BR/EDR is not
supported (in the advertisement flags). Is there a way to force LE
connection ?

I have seen that BR/EDR has priority over LE since version 4.2 but I
could not find any way to force bluetoothd to use LE connection.
However, it sometimes did use LE connection (it might have something
to do with the duration threshold in select_conn_bearer function in
device.c).

If there is no way to do so, I thought that I could maybe add an
optional parameter in the Connect dbus method on org.bluez.Device1
interface. This optional parameter for the bearer type would only be
used in case BR/EDR and LE timestamps are equal (or come from the same
advertisement packet) and would default to BR/EDR so that priority
stays like before.

Thank you for your consideration,
Eric KHACH
--
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