Hi Andrei, The creation and destruction of the effect as well as their configuration are done in AudioFlinger, however the call to the process and process_reverse function is done in the HAL. For the Galaxy Nexus: /device/samsung/tuna/audio/audio_hw.c: push_echo_reference for process_reverse.
What might happens as well is that you did not enable the effect in configuration file: /system/etc/audio_effects.conf For which use case do you want to enable WebRTC? VoiP?... Best regards, Thomas Le vendredi 6 avril 2012 08:45:53 UTC-7, Andreï Fomitchev a écrit : > > Dear all, > > I noted that during a VoIP call using "default" SIP Client of Android, if > output device is speaker, in AudioGroup.cpp, an aec is activated. This aec > is done through PreProcessing library by WebRTC. I added some logs in code > and I think that EchoCancellationImpl::ProcessCaptureAudio function (which > call WebRtcAec_Process) is never called, so algorithm/effect does not > process, i.e. aec is created and is configured (I think by AudioFlinger) > but is not used/did not process the stream... > > So, if somebody could indicate me where (for example, which thread of > AudioFlinger should call this process_reverse function of aec effect, > stored in effect_interface_s structure) in Android code it is possible to > really activate this aec... > > Thank you. > > Best regards, > -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
