Bug 104387 - Android OpenSL ES sink
Summary: Android OpenSL ES sink
Status: RESOLVED MOVED
Alias: None
Product: PulseAudio
Classification: Unclassified
Component: modules (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: medium enhancement
Assignee: pulseaudio-bugs
QA Contact: pulseaudio-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-26 20:57 UTC by Bohdan
Modified: 2018-07-30 09:41 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Bohdan 2017-12-26 20:57:07 UTC
Hello! I wrote an Android OpenSL ES sink module for Pulseaudio and two other guy reported that it works well. But I think it needs to be improved. Also I think it can be integrated into upstream Pulseaudio. Sources are placed here: https://github.com/twaik/pulseaudio-sles-ndk . The build.sh script inside repo downloads external prerequisites and builds all this stuff for Android using NDK.
The module only source is placed here: https://gist.github.com/twaik/0eaee765c712ddd03fc9dc4eaac09cfc
Comment 1 Arun Raghavan 2018-05-31 12:19:50 UTC
Nice! Do you think this should maybe move to AAudio, or do you need to be pre-Oreo compatible?
Comment 2 Bohdan 2018-06-02 14:21:33 UTC
That module does not use any Android parts except OpenSL ES. Android supports OpenSL ES since Android 2.3 (API level 9), so it should be Oreo-compatible.
Comment 3 Bohdan 2018-06-02 14:41:33 UTC
It does not replace Audioflinger (like the one noticed there: https://arunraghavan.net/2012/01/pulseaudio-vs-audioflinger-fight/ ). It uses Audioflinger as output platform.
Comment 4 GitLab Migration User 2018-07-30 09:41:11 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/93.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.