I don't think it'll make any difference, but try the latest SVN version.
Got a reply from the BlueZ folks, I think we may have found the problem,
although fixing it may be another matter.
Aha - progress!
I actually commented 2 parts, now lets uncomment one of them and see what
happens.
Donnie
Index: libcwiid/bluetooth.c
===
--- libcwiid/bluetooth.c(revision 83)
+++ libcwiid/bluetooth.c(working copy)
@@
Hthis is a tricky one.
One other idea to try (attached). Make sure you have no other bluetooth
devices around.
I've posted the question to the BlueZ-devel mailing list, hopefully someone
has come across something similar.
Donnie
Index: libcwiid/bluetooth.c
===
Try this one. I added an error message if the device socket doesn't close,
and added a pause before the connect. I'm thinking perhaps the device
hasn't closed and cleaned up by the time wiimote_connect tries to connect to
it.
The addresses print out the same, so I'm thinking it might be the blue
First thing I want to see is the bluetooth address that it finds: in
cwiid/wiimote/connect.c (assuming 0.5.02), declare a char bd_str[18] in
wiimote_connect, then after line 85, add:
ba2str(&bdaddr, bd_str);
printf("found wiimote at %s\n", bd_str);
The output should match the address you get from
Hello again, Petter.
This is a currently unsolved mystery experienced by a lot of people, and
unfortunately, I'm unable to duplicate it. I'd be much obliged if you could
help me debug it.
Thanks,
Donnie
6 matches
Mail list logo
