View Single Post
Posts: 166 | Thanked: 106 times | Joined on Dec 2007 @ Finland
#8
It's been a while since I have had this problem, but now it happened again.

Originally Posted by fanoush View Post
you can also try "hciconfig hci0 reset" between stop and start but the "No rfcomm created" may be caused by something not directly related to bluetooth chip but the bluetooth software stack. Or maybe it is generic out of memory problem.
hciconfig hci0 reset did not help.

Originally Posted by fanoush View Post
Is there something interesting in kernel log (use 'dmesg') when bluetooth stops working or when you stop/start it?
As far as I can see, no there isn't.

Originally Posted by fanoush View Post
Also maybe you somehow run out of rfcomm ports by allocating new ones without releasing old ones? Try rfcomm --help (bind, release command options)
I can bind the GPS receiver to /dev/rfcomm0 and then cat -u /dev/rfcomm0 outputs the GPS sentences. I can even start gpsd by hand and it seems to work (/usr/sbin/gpsd -N -D 2 /dev/rfcomm0). Still the usage through gpsbt_start doesn't work. Really odd.