Hi, Thanks for pointing this out. Actually, this hack is already included in CSipSimple as "webRTC hack" in media settings (I included that one month ago when I saw this source code ;) ). Unfortunately, in most cases where there is actual problems (not already solved by other hacks), it does not help. It just confirms that samsung does weird things and that even google engineers get hard to workaround stuff for these devices ;). For info, csipsimple also had two implementation of the pjsip dev glue : one that works with opensl-es and one with legacy java api. After having webRTC AEC, AEC mobile and webRTC codecs working, I'm now trying to wrap the webrtc device api for pjsip. That's not so easy cause for now the project is not yet very documented. However, I think it would be a great thing to be able to rely on their stuff for maintainability, and may allow to address other platforms when supported by webRTC. I don't think it will help too much with problems there is on android cause webRTC guys announced that android support is not official yet, and besides, regarding code there is many thing not manage yet. -BTW, the android source code of the stock sip application is by far more interesting on that stuff-. So for now, just like the OpenSL-ES implementation it would be just to get prepared and wait for improvements on these projects. (OpenSL-ES does not bring yet any improvement cause manufacturers keep pluging that to the android media system). I'm also trying to play with noise suppressor of webRTC - I'll keep the mailing list in touch with this point too :) Regards, R?gis Le 14/08/2011 17:17, atik a ?crit : > I am no Android expert, but found some links while browsing WebRTC > project.. WebRTC has Android Sound Driver for both Pre-2.3, using Java > API, and 2.3 using OpenSles.. > > http://code.google.com/p/webrtc/source/browse/trunk/src/modules/audio_device/main/source/android/ > > and following file has some hack to support samsung device.. line > 484-490, Audio route between earpiece line 409-426, hope this helps to > pjsip mailing list for android developers.. > > http://code.google.com/p/webrtc/source/browse/trunk/src/modules/audio_device/main/source/android/org/webrtc/voiceengine/AudioDeviceAndroid.java > > Regards > Atik > > On Wed, Jul 27, 2011 at 6:56 PM, Benny Prijono <bennylp at teluu.com > <mailto:bennylp at teluu.com>> wrote: > > On Wed, Jul 27, 2011 at 5:02 PM, I?aki Baz Castillo <ibc at aliax.net > <mailto:ibc at aliax.net>> wrote: > >> So... in this case you can just like me cry to samsung... ;) > and then hope > >> they will release 2.3 updates on these devices (and support > fully 2.3.... > >> cause actually, now even many HTC devices does not support > properly all VoIP > >> new things... :S ) > > > > Really great to have all this information. I appreciate it. > > > > +1. We plan to support Android after 2.0 (it may even be as early as > 2.1), so these things are very interesting to us. It helps to get us > prepared, at least mentally (now that we know what to expect from the > sound device...) > > Benny > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip at lists.pjsip.org <mailto:pjsip at lists.pjsip.org> > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > > > > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip at lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20110814/897dc5c8/attachment.html>
