Re: Error setting UUIDs discovery filter on big endian systems

[Luiz Augusto von Dentz <luiz.dentz@gmail.com>]

Hi Matt,
On Mon, Dec 3, 2018 at 3:59 PM Matt <mwtaylor@gmail.com> wrote:
>
> Hi,
>
> When setting a UUIDs discovery filter I am receiving
> "org.bluez.Error.InProgress" on starting a scan (which isn't in progress
> and will not start unless the discovery filter is cleared).
>
> I am using bluez 5.50 (on openWRT). The problem seems to only appear on
> big endian hardware (tested a couple of recent kernel and bluez
> versions), the same software compiled for and tested on little endian
> hardware works as expected. The issue can be reproduced in the following
> way using bluetoothctl:
>
> # /etc/init.d/bluetoothd restart
> # bluetoothctl
> [bluetooth]# power on
> Changing power on succeeded
> [CHG] Controller 00:1A:7D:DA:71:13 Powered: yes
> [bluetooth]# menu scan
> [bluetooth]# uuids 0000180f-0000-1000-8000-00805f9b34fb
> [bluetooth]# back
> [bluetooth]# scan on
> SetDiscoveryFilter success
> Failed to start discovery: org.bluez.Error.InProgress
>
> Setting an rssi filter does work as expected on my big endian hardware,
> it is only the uuids filter that appears to show this problem. The issue
> appears whether set using bluetoothctl or directly using DBus.

Do you have the bluetoothd logs when that happens? I wonder if it is
something with our string to UUID conversion.


-- 
Luiz Augusto von Dentz