linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [Bluez-devel] rfcomm disconnects + hcid dying
@ 2006-05-28  4:09 Lasse Kärkkäinen
  2006-05-29 13:05 ` Marcel Holtmann
  0 siblings, 1 reply; 4+ messages in thread
From: Lasse Kärkkäinen @ 2006-05-28  4:09 UTC (permalink / raw)
  To: bluez-devel


[-- Attachment #1.1: Type: text/plain, Size: 1076 bytes --]

Who is responsible for these parts? Why am I getting no replies to this
mail? Are any developers reading this list? Where should I send this, to
developers' private addresses or something?

Reposting, third time:


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 -



[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

^ permalink raw reply	[flat|nested] 4+ messages in thread
* [Bluez-devel] rfcomm disconnects + hcid dying
@ 2006-05-22 12:58 Lasse Kärkkäinen
  0 siblings, 0 replies; 4+ messages in thread
From: Lasse Kärkkäinen @ 2006-05-22 12:58 UTC (permalink / raw)
  To: bluez-devel

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

^ permalink raw reply	[flat|nested] 4+ messages in thread
* [Bluez-devel] rfcomm disconnects + hcid dying
@ 2006-05-17 12:59 Lasse Kärkkäinen
  0 siblings, 0 replies; 4+ messages in thread
From: Lasse Kärkkäinen @ 2006-05-17 12:59 UTC (permalink / raw)
  To: bluez-devel

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2006-05-29 13:05 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-05-28  4:09 [Bluez-devel] rfcomm disconnects + hcid dying Lasse Kärkkäinen
2006-05-29 13:05 ` Marcel Holtmann
  -- strict thread matches above, loose matches on Subject: below --
2006-05-22 12:58 Lasse Kärkkäinen
2006-05-17 12:59 Lasse Kärkkäinen

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).