View Single Post
gnuite's Avatar
Posts: 1,245 | Thanked: 421 times | Joined on Dec 2005
#152
Originally Posted by RussNelson
Yes. rfcomm bind doesn't survive a reboot.

BTW, I discovered a problem with opening /dev/rfcomm*. If the bluetooth GPS receiver is not turned on, the user interfce hangs while the kernel is attemting to bind to the device. Makes the user interface pause for the timeout period between every UI event. Click .... timeout .... click .... timeout .... click. I usually just turn off "Enable GPS" if I'm going to leave the GPS receiver off.
I have noticed this, too, but have no idea why this occurs. I thought that bluetooth connection occurred during the open() call, but it's possible that it's occurring during the read() call. I have no idea how to handle this, though, since I am already setting the non-blocking flag.