[Bluez-devel] rfcomm disconnects + hcid dying

["Lasse Kärkkäinen" <tronic+bdtmwkm6@trn.iki.fi>]

Received no replies the last time, reposting.


PROBLEM 1:

Whenever /dev/rfcomm0 (or rfcomm1) is closed, the corresponding Bluetooth
device gets disconnected and I have to run hcitool cc xx:xx:xx:xx:xx:xx to
get it working again. How can I have the devices automatically connected
at all times whenever they are within reach and the USB BT dongle is
plugged in?

My current workaround is an endless while loop that runs hcitool cc all
the time, but this is obviously quite ugly. It works, but I'd really want
to have something more elegant.


PROBLEM 2:

My hcid keeps dying occassionally. I don't know why, but it just does
that. My current workaround is to have the init system restart it whenever
it dies, but this, too, is somewhat ugly. Haven't found any messages about
that in the logs yet, but that is partly because my log was flooded with
other stuff.


- Tronic -




-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel