From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Niklas Claesson <nicke.claesson@gmail.com>
Cc: Lucas De Marchi <lucas.demarchi@profusion.mobi>,
linux-bluetooth@vger.kernel.org
Subject: Re: Setting up an A2DP server
Date: Sun, 09 Sep 2012 04:38:30 +0300 [thread overview]
Message-ID: <1347154710.26623.3.camel@maxim-laptop> (raw)
In-Reply-To: <CAAHv3KF8Vnz+iT0_OviJqUYUrNH=2ygMNH-GAxhc5H=H89euTw@mail.gmail.com>
On Tue, 2012-08-21 at 17:13 +0200, Niklas Claesson wrote:
> 2012/8/20 Lucas De Marchi <lucas.demarchi@profusion.mobi>:
> > On Fri, Aug 17, 2012 at 6:50 PM, Niklas Claesson
> > <nicke.claesson@gmail.com> wrote:
> >> I've actually solved the issue myself by writing an Agent that accepts
> >
> > You could mark the device as trusted, so you don't have to do this.
>
> I don't know which devices will connect, perhaps I could mark all
> nearby devices as trusted. But I don't know how I would do that.
>
> >
> >
> >> all incoming requests, and another python script that polls 'pacmd
> >> list-sources' every 2 seconds for new bluetooth sources. And third and
> >
> > Why do you need this?
>
> I have to set the bluetooth device as current source in Pulseaudio
I am also affected by this exact issue.
I also want to make my system be a 'A2DP' headset.
I managed to do so, but only when I initiate the connection from the
system, and using awkward dbus command.
When however I try to connect to it from my tablet nothing happens.
Any pointers will be welcome.
Best regards,
Maxim Levitsky
prev parent reply other threads:[~2012-09-09 1:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 11:30 Setting up an A2DP server Niklas Claesson
2012-08-17 21:50 ` Niklas Claesson
2012-08-20 17:44 ` Lucas De Marchi
2012-08-21 15:13 ` Niklas Claesson
2012-09-09 1:38 ` Maxim Levitsky [this message]
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=1347154710.26623.3.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=lucas.demarchi@profusion.mobi \
--cc=nicke.claesson@gmail.com \
/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