[pulseaudio-discuss] Porting pulseaudio to Android

Vikram Gupta vikram.exe at gmail.com
Wed Jul 6 07:04:20 PDT 2011

Thanks Colin for the quick reply.

After referring to your instructions from
for the nice explanation :) ), and giving the below mentioned args
to configure, I have compiled the source code and its working fine with the
compiled "paplay".

*../configure --prefix=$(pwd) --disable-x11 --disable-samplerate
--disable-oss-output --disable-oss-wrapper --disable-coreaudio-output
--disable-solaris --disable-jack --disable-openssl --disable-nls
--disable-waveout --disable-glib2 --disable-gtk2 --disable-gconf
--disable-avahi --disable-asyncns --disable-tcpwrap --disable-lirc
--disable-hal --disable-udev --disable-bluez --disable-dbus
--disable-hal-compat --disable-ipv6 --disable-manpages

export PULSE_SERVER=<ip>
however, when I am playing some thing using default "aplay", the sound is
played locally and not on the remote machine. I think that should be because
of some configuration issue and I am looking in to it.
My question is, do we have some doc which can give a list of files that are
essential for pulse audio to work (without any optional components), which I
can directly use in my Android Makefile or will I have to look for the
compilation logs to figure that out?


On Wed, Jul 6, 2011 at 5:46 PM, Colin Guthrie <gmane at colin.guthr.ie> wrote:

> 'Twas brillig, and Vikram Gupta at 06/07/11 12:09 did gyre and gimble:
> > Hi,
> >
> > I have been using pulse audio on Ubuntu to remote my sound to a network
> > Windows-7 machine. Now I am trying to port pulse audio to Android.
> > Looking at the dependencies, I think, I will have to port a lot of
> > libraries before I can start compiling pulse audio code. Also the
> > default configure option brings in a lot of things which are not
> > available on android by default. I have used a few options (like
> > --disable-x11 etc) to remove the optional support, but still a lot of
> > libs are required on android. Has anybody tried porting pulseaudio to
> > Android, or can help (with a web link maybe) getting me started.
> I'm not sure how many people have tried this before.
> A lot of the various bits and bobs are indeed optional, although highly
> desirable. e.g. dbus is needed for bluetooth support, but then I really
> don't know how the bluetooth stack on android works - it could be a far
> cry from the bluez stuff used on desktops.
> But certainly initally, I'd disable dbus, bluez, consolekit etc. and
> really cut things down to a bare minimum, so you can check to make sure
> the basics work well enough before going crazy on the optional stuff.
> If there is anything in particular lib wise that you think is a problem?
> If so just shout and we can maybe advise as to how really useful it is!
> Col
> --
> Colin Guthrie
> gmane(at)colin.guthr.ie
> http://colin.guthr.ie/
> Day Job:
>  Tribalogic Limited [http://www.tribalogic.net/]
> Open Source:
>  Mageia Contributor [http://www.mageia.org/]
>  PulseAudio Hacker [http://www.pulseaudio.org/]
>  Trac Hacker [http://trac.edgewall.org/]
> _______________________________________________
> pulseaudio-discuss mailing list
> pulseaudio-discuss at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20110706/f4653c65/attachment.html>

More information about the pulseaudio-discuss mailing list