From: Colin Murphy <lists@spudulike.me.uk>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] Understanding /etc/bluetooth/audio.conf
Date: Tue, 1 Jan 2008 20:20:08 +0000 [thread overview]
Message-ID: <200801012020.08991.lists@spudulike.me.uk> (raw)
I am fighting to get a workable link between stereo headsets and a USB
dongel. My current set-up has been configured with the Blueman gui. When I
go to play some audio from XMMS which is set up for Bluetooth, I can see that
a connection is made, I get half a second of audio and 8 seconds of silence,
after which the connection is dropped. This is on my Ubuntu 7.10 system.
There is much I don't understand about this subject and I will need to chip
away at the problems a piece at a time.
My first query is with audio.conf. I can see the following
in /var/log/syslog :-
Jan 1 19:34:09 colin-desktop hcid[29890]: Bluetooth HCI daemon
Jan 1 19:34:09 colin-desktop hcid[29890]: HCI dev 0 registered
Jan 1 19:34:09 colin-desktop hcid[29890]: HCI dev 0 already up
Jan 1 19:34:09 colin-desktop hcid[29890]: Device hci0 has been added
Jan 1 19:34:09 colin-desktop hcid[29890]: Starting security manager 0
Jan 1 19:34:09 colin-desktop hcid[29890]: Device hci0 has been activated
Jan 1 19:34:09 colin-desktop hcid[29890]: Starting SDP server
Jan 1 19:34:09 colin-desktop hcid[29890]: Created local server at
unix:abstract=/var/run/dbus-3kjjteaAME,guid=d6d35f0826ae92b0ea7f9100477a95b1
Jan 1 19:34:09 colin-desktop audio[29898]: Bluetooth Audio daemon
Jan 1 19:34:09 colin-desktop audio[29898]: /etc/bluetooth/audio.conf: Key
file does not have key 'SCORouting'
Jan 1 19:34:09 colin-desktop audio[29898]: /etc/bluetooth/audio.conf: Key
file does not have key 'Enable'
Jan 1 19:34:09 colin-desktop audio[29898]: /etc/bluetooth/audio.conf: Key
file does not have key 'Disable'
Jan 1 19:34:09 colin-desktop audio[29898]: /etc/bluetooth/audio.conf: Key
file does not have group 'A2DP'
Jan 1 19:34:09 colin-desktop audio[29898]: Config options: DisableHFP=true,
SCORouting=HCI, SourceCount=1
Jan 1 19:34:09 colin-desktop audio[29898]: Unix socket created: 5
The entries 'Key file does not have *' bother me, they look like error
messages. The audio.conf file has not been edited by me by hand, though my
tinkering may have upset something.
Do these lines look suspicious? Since I don't understand what they are I need
to ask your advice on the current config options, do they look correct?
--
Colin@spudulike.me.uk
Gotta' go, things to be, people to do, stuff to, err, stuff.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
reply other threads:[~2008-01-01 20:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200801012020.08991.lists@spudulike.me.uk \
--to=lists@spudulike.me.uk \
--cc=bluez-users@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