From: Remy Bosch <reboli@hccnet.nl>
To: Bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Audio gaps with bcm2035 and Hama receiver
Date: Thu, 25 Oct 2007 18:46:19 +0200 [thread overview]
Message-ID: <4720C85B.1090300@hccnet.nl> (raw)
Hi,
I'd like to have my sound sent over from my laptop with a BCM2035 chip to a
Hama receiver. Though it works fine under W*ws, the sound under Linux is
broken off every minute for a second to continue afterwards. I used mplayer
and xmms2. and both have this problem.
I use bluez-libs/utils 3.2
Commands to get audio online:
dbus-send --system --print-reply --dest=org.bluez /org/bluez \
org.bluez.Manager.ActivateService string:audio
dbus-send --system --type=method_call --print-reply --dest=":1.19"
/org/bluez/audio \ org.bluez.audio.Manager.CreateDevice
string:00:10:60:9F:32:3B
For some reason sco isn't used...
Thanks!
Remy
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2007-10-25 16:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 16:46 Remy Bosch [this message]
2007-10-25 22:48 ` [Bluez-users] Audio gaps with bcm2035 and Hama receiver Marcel Holtmann
2007-10-26 12:53 ` Remy Bosch
2007-10-26 16:20 ` Remy Bosch
2007-10-26 17:35 ` Brad Midgley
2007-10-26 20:26 ` Remy Bosch
2007-10-26 21:46 ` Brad Midgley
2007-10-26 23:40 ` Remy Bosch
2007-10-30 11:29 ` Brad Midgley
2007-10-30 11:49 ` Remy Bosch
2007-10-30 6:25 ` Sumeet VERMA
2007-10-30 10:22 ` Remy Bosch
2007-10-30 10:23 ` Sumeet VERMA
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=4720C85B.1090300@hccnet.nl \
--to=reboli@hccnet.nl \
--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