> -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Kalle Lampila > Sent: Tuesday, March 01, 2011 5:38 PM > To: Carsten Munk; Arjan van de Ven > Cc: [email protected] > Subject: Re: [MeeGo-dev] How to pair my device with the BT headset by command > and test audio on it > > On Mon, Feb 28, 2011 at 18:12, Carsten Munk <[email protected]> wrote: > > 2011/2/28 Arjan van de Ven <[email protected]>: > >> On 2/28/2011 7:50 AM, Kevron Rees wrote: > >>> > >>> On Mon, 2011-02-28 at 17:46 +0200, Kalle Lampila wrote: > >>>> > >>>> On Wed, Feb 23, 2011 at 08:08, jms yang<[email protected]> wrote: > >>>>> > >>>>> Hi there.. > >>>>> I've got it paired and workable. > >>>>> I can heard an audio from my BT earpiece without the "test-audio" > >>>>> action. > >>>>> BTW, there is also needed to append some more code in the file .asoundrc > >>>>> or > >>>>> the /etc/alsa/default.conf for bluetooth, > >>>>> then I can test audio playback from BT by command below. > >>>>> #gst-launch audiotestsrc ! alsasink device=bluetooth > >>>>> More question, can I route bluez audio data to pulseaudio sound server > >>>>> for > >>>>> audio mixing? > >>>>> I am fail to test audio playback by "pulsesink" element. > >>>> > >>>> Resource policy fw is capable to route also audio to BT and that is > >>>> what should to use audio routing. > >>>> > >>>> - Kalle > >>> > >>> Do we have this working in meego? I had to manually route audio to use > >>> the bt sink last time I tried. > >> > >> the whole resource policy stuff is very underimplemented in MeeGo that > we're > >> currently discussion what to do; > >> for 1.2, removing it (or replacing it with a very simple shell script) is > >> not out of the question at this point in time.
Hi, Arjan, can you elaborate why you stated that the FW was underimplemented? Unfortunately, Nokia policy guys don't seem to be so present on the ML to give formal details... As I've been deeply involved with them on handset audio integration on Intel platform, I confirm everything is in place at least regarding "audio" policy (The FW handling much more than audio by the way). All basic rules have been delivered, and need customizations/adaptation. Now, it's a matter of integration with the Intel specific changes made in pulseaudio and pulseaudio enforcement point. Known limitation with the current ruleset is that there is only one logical output active at a time. AFAIK, multiple output logical model was in progress on Nokia side, and was going to be delivered. Don't know what is the plan now, after the Nokia "announcement". Anyways, can you please put me in the loop if you hear about topics around replacing the policy FW by "scripts". The policy logic in a phone is generally a very complex part, which would be highly risky to be implemented from scratch now. On my side, I don't see any chance to have a script based policy to remain simple when addressing telephony policy decisions. Also, please note that the pulseaudio architecture we are maintaining in handset is very dependent on the availability of the current policy framework in Meego. > All common components of resource policy fw was released to trunk in > December-January. I think that there is nothing underimplemented in > fw. I know that resource policy aware is not implement most of > applications. But at least new release 0.1.18 of dialer include > resource policy support. > https://bugs.meego.com/show_bug.cgi?id=13156 > https://bugs.meego.com/show_bug.cgi?id=13154 > > Even without resource policy aware support in applications we get > basic audio routing working to headset, BT, etc. I am quite sure that > we don't get any better solution with some script even we totally > missing all applications aware. Fully agree with this... FYI, we developed a OHM plugin to trigger a fact change via dbus. This would allow to override any upfront rule, and directly change the routing decision from command line, for testing purpose. We're still having troubles to deliver (OBS, licence, etc...) , but it should come soon, hopefully... Can you confirm my understanding : Regarding applications, apart from the dialer, which has some policy related specifics, other multimedia apps would use directly the Multimedia FW, intended to abstract the resource management, right? And camera, for example implements the also the libresource calls in cameraBin if I remember correctly. What I'm still missing in the picture, is how any policy framework will interact with the contextKit to get/update the various context variables. (I thought this was the only way for apps to register on accessory state changes for example (and update the accessory icons, etc...). Anyone can confirm this too? Regards, Sylvain --------------------------------------------------------------------- Intel Corporation SAS (French simplified joint stock company) Registered headquarters: "Les Montalets"- 2, rue de Paris, 92196 Meudon Cedex, France Registration Number: 302 456 199 R.C.S. NANTERRE Capital: 4,572,000 Euros This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
