Closed GoogleCodeExporter closed 9 years ago
Finally I've managed to code a workaround for this bug.
Here I relate all the details because it may help when trying to isolate and
reproduce the bug effectively.
It only takes place the very first time that a search is done. So this means
that to reproduce it I had to restart
the system every time.
It also worked to unplug/plug in the bluetooth dongle that I use. But this
would eventually affect every usb
device connected to the computer, this could be caused by so many things (as
winxp itself, my motherboard,
the usb controller) but it actually happened in my system).
If the computer is left for a considerable amount of time (few hours) with no
bluetooth activity whatsoever, the
exception may also be obtained.
So basically, I tried the "loop" trick that alvmoriles suggests, but that
wouldn't avoid the bug. But I have found
something that will surely reproduce the bug. Which is to obtain the device
friendly name immediately after it
has been discovered.
For instance, this means that if you check for the device friendly name in the
"deviceDiscovered()" method of
the "discoveryListener" the program will always crash, no matter how many
times you have gone in the loop.
What my program used to do is to inform the user about the device friendly name
right after it had been
found, this would end up with the JVM exception every time that the application
was run for the first time.
Now I search for every device and I don't retrieve the friendly names at all.
Once the "inquiryCompleted" has
been fired and I start looking for services on each device, then I am able to
show the friendly names.
However, from time to time, these names will be returned as a empty strings.
Hope this helps. Anyway don't hesitate to ask if I haven't really made myself
clear, because I am probably one
of the most interested in seeing this bug fixed :)
If it can be helpful I could try all this stuff with the avetana stack, to see
if there's something inherent to
microsoft's driver, as the empty strings instead of actual names.
Good luck with it.
Jaume
Original comment by jaumedej...@gmail.com
on 19 Aug 2006 at 9:23
Fixed the problem in dll would be avalable in version 1.2.1
Original comment by skarzhev...@gmail.com
on 16 Dec 2006 at 6:59
Original comment by skarzhev...@gmail.com
on 16 Mar 2007 at 6:39
Original issue reported on code.google.com by
paul.tot...@gmail.com
on 19 Aug 2006 at 1:35