Hi!
I've written a small library which uses the JNI to bring BlueZ to Java.
Upon that, I'm writing a small "Location Aware Web-Service"-Demo. So my
ClientApp has a DiscoveryThread which does non-cached inquiry and
sdp_search() all the time, and an UpdateThread which uses the
DiscoveryInfo to connect to the servers, measure RSSI and LQ and
transmit the websites via L2CAP. Everything works fine while all
devices are good in range, but if one device is at the edge of the
range, sdp_search() blocks the DiscoveryThread and also seems to
cripple/block the UpdateThread. I don't know why. I have seen that
there is a hard coded 20s timeout in sdp_read_resp(). Is there a way to
decrease this timeout or to make it a settable parameter in future
versions? Anyway, sdp should not cripple l2cap, shold it? Any
suggestions? Thanks in advance!
Kind regards
Stefan Mischke