New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rtl8723au bluetooth device found, lescan finds one result and stops? #43
Comments
I'm not sure either. I do not have an RTL8723AU device, but I have a number of other Realtek devices with associated BT hardware. All of them find all the BT devices that I have here as long as I use "scan" in the hcitool command. When I try the lescan, nothing responds. I'm not sure why, but LE connections appear not to be possible. For what it is worth, the same is true for an Intel BT device as well. |
hw correction: RTL8723BU device. Strange that the le scan wouldn't work. |
I do have a BU device. Same situation - scan works, but LE scan does not. |
updated bluez doesn't seem to make a difference in this case. |
'new' branch on kernel 3.1.8.7+ seems to scan a few more devices.
scan from rtl8723bu:
Interestingly, if i leave it scanning for a while, it only ever returns unique bluetooth device IDs. Never a duplicate. Sounds like a bug somewhere in there. |
'new' branch works for LE advertising on kernel 3.18.7+ |
'test' branch works for LE advertising on kernel 4.1.7+ |
Summary
I'm able to build the kernel branch on a raspberry pi b+ (jessie), install the drivers, view the devices and start an LE scan. However, the LE scan only returns 1 result for the rtl8723bu device, whereas it returns dozens of results for a CSR bluetooth device.
Hardware summary
Building the drivers
Installing drivers
Device details via bluez post driver install
LEScan attempt for rtl8723bu device returns one result and stops
LEScan attempt for CSR bluetooth device returns results quickly and continues forever
I tried all the other branches, but the kernel branch had the best results. I don't see any errors. Not sure what's going on.
The text was updated successfully, but these errors were encountered: