From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: Missing CallRemoved signals
Date: Wed, 17 Aug 2011 10:43:23 -0500 [thread overview]
Message-ID: <4E4BE19B.3080003@gmail.com> (raw)
In-Reply-To: <4E4B90DA.2060706@bmw-carit.de>
[-- Attachment #1: Type: text/plain, Size: 1455 bytes --]
Hi Mikel,
On 08/17/2011 04:58 AM, Mikel Astiz wrote:
> Hi all,
>
> I'm doing further tests with oFono with a simple UI that handles the
> calls of a certain modem (bluetooth modem in this case).
>
> I keep track of the existing calls by listening to 'VoiceCallManager'
> signals, 'CallAdded' and 'CallRemoved'. The list is initialized using
> 'VoiceCallManager.GetCalls()' at startup.
>
> The problem I have found is that some 'CallRemoved' signals are
> apparently never emitted. It is in fact quite easy to reproduce, if a
> modem is powered down while a call is in progress.
By convention oFono interfaces do not emit any signals when they're
being removed (e.g. when the modem is powered down). In most cases
there isn't a meaningful value we can emit anyway, or doing so would
result in too many redundant signals.
>
> Having a look at oFono's source code (src/voicecall.c), my feeling is
> that some calls to 'voicecall_dbus_unregister' are not accompanied by a
> call to 'voicecalls_emit_call_removed', inside the function
> 'voicecall_unregister'.
>
> Could anyone confirm if this is a bug in oFono or suggest any workaround
> for the client app?
The application can track the 'Interfaces' property on the modem object
to figure out when an interface goes live / ceases to exist. If
VoiceCallManager goes away, you can mark all relevant calls accordingly.
>
> Regards,
> Mikel
Regards,
-Denis
next prev parent reply other threads:[~2011-08-17 15:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-17 9:58 Missing CallRemoved signals Mikel Astiz
2011-08-17 15:43 ` Denis Kenzior [this message]
2011-08-18 6:29 ` Mikel Astiz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E4BE19B.3080003@gmail.com \
--to=denkenz@gmail.com \
--cc=ofono@ofono.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox