Re: [Bluez-devel] Reading RSSI of non-connected devices

["Andreas Färber" <afaerber@rumms.uni-mannheim.de>]

Hi Marcel,

>the ioctl() is very old and number updated it to support Inquiry with
>RSSI or Extended Inquiry. The main reason for this is, because you can't
>update it without breaking backward-compatibility with older versions of
>the library and the tools.
>
>However you can program the HCI socket interface directly and read the
>inquiry result directly. Example code for this is already available in
>the mailing list archives.
>  
>
Some posts say ioctl was bad because it's old, some posts say raw HCI 
sockets were bad because the messed with BlueZ. Your hcitool apparently 
is using ioctl for "hcitool scan" in its most recent version 
downloadable from your site...
Our software is a Java framework that shall continuously check the RSSI 
of devices around in a background thread (test code for this is in C). 
Another thread might be continuously using GPS data via BT and apart 
from that we don't want to keep the user from using the BlueZ stack in a 
"normal" way while our software is running. In this context is it safe 
to use HCI sockets in the way you have suggested?

I'm having a hard time finding the example you're mentioning over and 
over... Do you have any search words for me?
Not having found it I would assume you mean hci_open_dev and 
hci_send_cmd? Examples for the latter would be in the kernel driver 
which I already have.

Regards,

Andreas



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel