bug: device discovered when turned off

[Garth]

I seem to have found a bug. It occurs by doing the following:

1. Start a device inquiry
2. Find device.
3. Inquiry is completed
4. Attempt to form an L2CAPConnection. connection opening times out
with a BluetoothConnectionException: Connection timeout (this is ok)
5. Start device inquiry again. Now we have the bug: We will find the
the previously found device regardless of whether or not it is even
turned on.

I'm not sure what is happening, but it seems that bluecove is somehow
remembering the device that it previously tried to connect to, and is
reporting it as a found device, regardless of whether or not the
device is there. It is possible that the exception is triggering this,
as I have only seen it happen with devices that I have tried to
connect to but timed out on.

It's probably not relevant, but in all cases it was also the 3rd
device being connected to (I have the persistent problem that I can
connect to the 1st and 2nd devices quickly, but the 3rd one sometimes
times out. That is a different problem though).

WinXP bluecove 2.0.2 WIDCOMM

Thanks,
Garth

[Vlad Skarzhevskyy]

Nothing like this. Tested on WIDCOMM stack version:BWT 5.0.1.2800,  I tried to connect to non existing service to create Connection timeout.

Bluecove is not remembering the device it asks native stack for devices every time.
Also I tested the Bluecove and it can connect up to 7 devices at the same time -> no problems!

[Garth]

Ack, I looked at my code so carefully before writing, but it was my
bug. I am sorry for wasting your time.

(timeouts are still a problem with many devices, but I have worked
around it)

Garth

On Feb 11, 5:32 pm, "Vlad Skarzhevskyy" <skarzhevs...@gmail.com>
wrote: