[FSO M5] - Answering a Call
scottrcarlson at gmail.com
Wed Feb 18 14:21:46 CET 2009
Thanks, I will apply/test the patch and also file a ticket tonight. (eastern
On Tue, Feb 17, 2009 at 7:41 PM, Michael 'Mickey' Lauer (via Nabble) <
ml-user+1966-127261563 at n2.nabble.com<ml-user%2B1966-127261563 at n2.nabble.com>
> Am Tuesday 17 February 2009 20:46:20 schrieb SCarlson:
> > Does anyone know a good fix for the answer call "delay".. When I get a
> > call, I hit the answer button, and it takes approx. 3-5 seconds for the
> > phone to actually pick the call up??? What the heck is it doing? heh...
> > anyone tweaked around with this yet?
> This is a (temporary) result of fixing bug FSO #205 as described in
> At the moment, we serialize all dbus signals initiated by oeventsd, meaning
> wait until the result has been parsed, before we send the next one. In
> particular, this means we probably wait until the ring tone has stopped
> before actually taking the call and switching the audio scenario. "Thanks"
> gstreamer and its audio buffers, this can take up to 3 seconds.
> This behaviour is slightly suboptimal for calls to different subsystems,
> do not need to be serialized.
> Please open a ticket with this mail, so we do not forget the issue and I'll
> try to come up with a speed-up.
> In the meantime, please check whether applying the attached patch improves
> for you.
> [attachment removed]
> Openmoko community mailing list
> community at ...<http://n2.nabble.com/user/SendEmail.jtp?type=node&node=2344225&i=0>
> This email is a reply to your post @
> You can reply by email or by visting the link above.
View this message in context: http://n2.nabble.com/-FSO-M5----Answering-a-Call-tp2342862p2346805.html
Sent from the Openmoko Community mailing list archive at Nabble.com.
More information about the community