From: "Lasse Kärkkäinen" <tronic+bdtmwkm6@trn.iki.fi>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] rfcomm disconnects + hcid dying
Date: Sun, 28 May 2006 07:09:00 +0300 [thread overview]
Message-ID: <4479225C.9090809@trn.iki.fi> (raw)
[-- 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
next reply other threads:[~2006-05-28 4:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-28 4:09 Lasse Kärkkäinen [this message]
2006-05-29 13:05 ` [Bluez-devel] rfcomm disconnects + hcid dying 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4479225C.9090809@trn.iki.fi \
--to=tronic+bdtmwkm6@trn.iki.fi \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).