On Sat, 2 May 2009, Dominic Fandrey wrote: > # hccontrol -n ubt0hci inquiry > Inquiry complete. Status: No error [00] > > is pretty lame compared to what should appear according to the > handbook: > > % hccontrol -n ubt0hci inquiry > Inquiry result, num_responses=1 > Inquiry result #0 > BD_ADDR: 00:80:37:29:19:a4 > Page Scan Rep. Mode: 0x1 > Page Scan Period Mode: 00 > Page Scan Mode: 00 > Class: 52:02:04 > Clock offset: 0x78ef > Inquiry complete. Status: No error [00]
Depends what's in range.
Your command indicates to me that there are no _discoverable_ BT modules
in range. (Note the discoverable part :)
BTW the '-n ubt0hci' is optional if you only have one BT controller.
If it isn't discoverable you can do something like..
sdpcontrol -a pda browse
(I entered pda into /etc/bluetooth/hosts).
If it doesn't show anything (like my phone) you need to bruteforce
search for services (I don't understand the rationale of that but
that's the way it is), eg..
sh -c 'for i in \
CIP CTP DUN FAX FTRN GN HID HSET LAN NAP OPUSH SP; do \
sdpcontrol -a pda search $i; done'
There's a command in Bluez which does this for you but the above would
tell you a reasonable amount.
--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
signature.asc
Description: This is a digitally signed message part.
