From: "Saul A. Peebsen" <jaglover@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Bluez Documentation
Date: Sun, 24 Jun 2018 08:28:07 -0500 [thread overview]
Message-ID: <20180624082807.07b87b33@zeus.asclinux.com> (raw)
Hello everyone.
I'm an end user totally stuck setting up my BT devices. My google-fu is
failing on me. Usually I read the documentation and tutorials and
that's all I need. Not with Bluez. Is there documentation for an end
user somewhere?
My current problem: I paired and connected to my BT headphones
successfully using bluetoothctl. However, every time the headphones are
powered off and on I have to connect manually again. Is there a way to
auto-connect?
Using Gentoo, no PulseAudio, no systemd, Intel NUC built-in BT. I set
the trusted flag. What else is needed?
--
Cheers, Saul
next reply other threads:[~2018-06-24 13:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-24 13:28 Saul A. Peebsen [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-10-17 10:00 Bluez documentation sathish
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=20180624082807.07b87b33@zeus.asclinux.com \
--to=jaglover@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
/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).