From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] rfcomm disconnects + hcid dying
Date: Mon, 29 May 2006 15:05:28 +0200 [thread overview]
Message-ID: <1148907928.31689.15.camel@localhost> (raw)
In-Reply-To: <4479225C.9090809@trn.iki.fi>
Hi Lasse,
> 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?
don't try the developers private addresses. They might ignore you or if
you send it to me, I am going to tell you to send it to the mailing
list. You need to have patience, because some of us might be busy with
other stuff that has higher priority.
> 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.
You can of course keep /dev/rfcommX open with cat for example, but it
won't reconnect if the device get out of range.
There is nothing elegant for device that come out of range and then come
back and they should automatically reconnect. The device most initiate
this at the moment, because the host behaves passiv and if nobody tells
it to connect, it simply doesn't.
> 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.
We fixed a lot of stuff in the upcoming bluez-utils-2.26 version, but
without any log messages or reports I can't tell you anything. However
you can run "hcid -n" and it will log everything in the terminal instead
of the log files.
Regards
Marcel
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-05-29 13:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-28 4:09 [Bluez-devel] rfcomm disconnects + hcid dying Lasse Kärkkäinen
2006-05-29 13:05 ` Marcel Holtmann [this message]
-- 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=1148907928.31689.15.camel@localhost \
--to=marcel@holtmann.org \
--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