Re: [Bluez-devel] Bluez libs 3.22 & hci_read_remote_name

[Manuel Naranjo <naranjo.manuel@gmail.com>]

I had seen the same problem, but by doing "hcitool scan". I have a piece
of code in C that does scanning (based on the web site example) and it
doesn't seem to be having the same problem.

Maybe hci_* functions had started failing? And it's time to move to D-BUS?

D-BUS is a great solution, I really like it, I had my first experience
with it during the weekend, and it's much better than calling libbluez
directly, but AFAIK there's no way to open an rfcomm channel and wait
for connections. So moving to D-BUS is not 100% applicable yet.

Thanks
Manuel
> I have big problems making "hci_read_remote_name" work using libs 3.22, it 
> is very long or blocking.
> I had to roll back to 3.20 which is working fine.
> I have 4 dongles on my computer, maybe has there been a change on 
> multi-devices in 3.22 ?
> If you need me to investigate further just ask me what to do and I'll 
> provide you with more details.
>   


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel