Hi,

On 25 nov, 16:26, "Sangsu Park" <[EMAIL PROTECTED]> wrote:
> I had same problem with you.
> But after clean build, audiofligner use the libaudio.
> I think that android build system have some weakness.

That makes sense. I will try from a clean build.

> But I have another problem.
> When AudioHardwareOmap::openOutputStream() is called,
> snd_pcm_open() is failed. Error message is like 'no device file'.
> (I didn't remember exactly....)
> I think that this is caused by no device file that time.
> Who can you explain this situation? or solve?

Maybe check your /dev/pcm* and /dev/control* device node permissions ?
Just a wild guess.

- Maxime

>
> On 11/25/08, Maxime Petazzoni <[EMAIL PROTECTED]> wrote:
>
>
>
> > I managed to make Android build the libaudio shared library (taken
> > from omapzoom.org), which was then put where it should be in /system/
> > lib/. I also have BOARD_USE_GENERIC_AUDIO set to false, which should
> > make audioflinger use this libaudio instead of the generic
> > libaudiointerface, but I still get the error message:
>
> > W/AudioHardwareInterface(  665): Using stubbed audio hardware. No
> > sound will be produced.
>
> > Any idea what I could be missing here?
>
> > Thanks in advance,
> > - Maxime
>
> > On 12 nov, 06:23, "Misael Lopez" <[EMAIL PROTECTED]> wrote:
> > > I have been working in that audio interface for ALSA in OMAP
> > > processor, you can find our tree at:
>
> > >http://git.omapzoom.org/?p=android/hardware/ti/omap3.git;a=summary
>
> > > We have been successfully played and capture audio using TWL4030 chip
> > > in OmapZoom board with that current version of the interface.
> > > I'm working on bringing the control part, probably we can have that
> > > part ready soon. It will be great if the community collaborates to
> > > correct/improve current code.
> > > You can find more information atwww.omapzoom.org, particularly about
> > > Android if you go to Projects->Android on OMAPZoom.
>
> > > Misa
>
> > > 2008/11/11 Sean McNeil <[EMAIL PROTECTED]>:
>
> > > > Hi Maxime,
>
> > > > Wind River is in the process of submitting an ALSA audio implementation.
> > > > That is what I use on the Openmoko Freerunner and what has been
> > > > successfully used on the TI OMAP Zoom reference platform.
>
> > > > Maxime Petazzoni wrote:
> > > >> Hi,
>
> > > >> I believe most of the porting efforts on the various hardware platform
> > > >> will soon get to the point (if not already) of a running system ; the
> > > >> next step being making sure all the basic functionality is there.
> > > >> Audio being one of the most important one, since telephony also
> > > >> depends on it.
>
> > > >> Without anything done on that front, we're facing the "using stubbed
> > > >> audio hardware, no sound will be produced" warning message when Dalvik
> > > >> starts.
>
> > > >> From what I've read, Android relies on an hardware glue library
> > > >> libaudio, providing AudioFlinger with the appropriate AudioInterface
> > > >> implementation to output sound to whatever sound driver the hardware
> > > >> uses. For example, on the HTC G1/MSM72xx hardware platform, Google
> > > >> useshttp://android.git.kernel.org/?p=platform/hardware/msm7k.git;a=summary
>
> > > >> But I think most of the Androids ports are made on hardware that have
> > > >> ALSA device drivers (OMAP for example). And before 20 different people
> > > >> start implementing their own libaudio bridging to ALSA, maybe we
> > > >> should coordinate this community effort. Starting by knowing if
> > > >> anything has already been started by someone, somewhere :)
>
> > > >> If not, I will most likely start working on one, and I foresee that
> > > >> it's going to be tough, as the only real documentation is the msm7k
> > > >> libaudio source code itself.
>
> > > >> Ideas, comments, suggestions ... and help are most welcome!
> > > >> - Maxime
>
> > > >> PS: of course, if you got audio working without going through this
> > > >> libaudio stuff, please share your discoveries !
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [EMAIL PROTECTED]
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---

Reply via email to