Problem with bluetooth output

[ghostop14]

Problem with bluetooth output

[alphafox02]

I’m having what seems to be a similar issue. I can see there’s some interaction with hci when running the sparrow WiFi Bluetooth scan (with standard adapter) as dmesg shows some activity. How’d you locate the failing output you show above? Did you ever resolve the issue?

What’s interesting is that on my raspberry pi running 20.04 as well, nearly all the same software that I can tell except it’l has a 5.4 kernel instead of a 5.15 like my laptop I do in fact get normal Bluetooth scan output with sparrow WiFi on it.

Also on the laptop all other tools can generate Bluetooth scan results.

[alphafox02]

@ghostop14 i have two laptops, both have internal Bluetooth. I now confirmed with the same exact image booted and ran live on each laptop I get the following results.

1. Runs sparrow WiFi and normal Bluetooth scan yields results, this is with 20.04 and the latest hwe 5.15 kernel.

2. Second laptop, same software/image Sparrow WiFi does not yield normal Bluetooth scan results, yet hci and blue hydra both generate scan results.

I would love to provide more info, only thing I see I think different on second laptop is that each time I try to do a scan it shows this in dmesg

Bluetooth: hci0: MSFT filter_enable is already on.

I don’t know where else to debug this but it seems like maybe a way the Bluetooth scan is being conducted it is not liked in some cases.

[alphafox02]

It just occurred to me. If this even makes sense, maybe the Bluetooth in the one laptop isn’t standard and thus the normal scan sparrow is doing (without ubertooth) is not compatible?

[alphafox02]

I was wrong, I to get a failure as mentioned above with sudo hcitool lescan, however blue hydra works. It appears after further research it may be associated to the kernel and people are saying bluetoothctl should maybe be used instead of hci.

[alphafox02]

“bluetoothctl scan on” ran in terminal appears to be a replacement for hci for btle 5.x devices and works great where hci fails.

Maybe it could be an optional means of scanning. However maybe this would require some extensive changes to the scanning mechanism.