From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH] hfpmodem: Handle repeated held call indicator
Date: Mon, 11 Jan 2016 12:04:37 -0600 [thread overview]
Message-ID: <5693EEB5.8070000@gmail.com> (raw)
In-Reply-To: <1452532775-8557-1-git-send-email-kubax.t.pawlak@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2426 bytes --]
Hi Kuba,
On 01/11/2016 11:19 AM, Kuba Pawlak wrote:
> An issue with iPhone 5C iOS 9.2 triggers desynchronization in call
> states. When an active call is put on hold and another call arrives,
> it is in WAITING state. It should be possible to answer it by issuing
> AT+CHLD=2 but the phone changes its state to INCOMING so ATA should be
> used. This change is advertised by sending callheld:2 event, but it is
> not handled. This event can be used to trigger CLCC poll to synchronize
> call states.
>
> +CIEV: 3,1 <- first call arrives
> AT+CLCC
> +CLCC: 1,1,4,0,0,"01234567890",129
> OK
> RING
> +CLIP: "01234567890",129
> ATA
> OK
> +CIEV: 2,1
> +CIEV: 3,0.
> AT+CHLD=2.$ <- first call is put on hold
> OK
> +CIEV: 7,2 <- notification confirming that call #1 is on hold
> +CCWA: "09876543210",129,1 <- second call arrives
> +CIEV: 7,2
> +CIEV: 3,1
> AT+CLCC
> +CLCC: 1,1,1,0,0,"01234567890",129
> +CLCC: 2,1,5,0,0,"09876543210",129 <- new call is still in WAITING state
> OK
> +CIEV: 7,2 <- phone iternally promotes WAITING call to INCOMING
So looks like the iPhone should be sending us a callheld=0 instead of
callheld=2.
> AT+CHLD=2 <- there is no WAITING call anymore, ATA should be used
> +CME ERROR:3
> ---
> drivers/hfpmodem/voicecall.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/drivers/hfpmodem/voicecall.c b/drivers/hfpmodem/voicecall.c
> index d0e9353796c335a1fc876779345eedeb6556345d..2b7524e9cccbbdb9d8ce1e47a91d2e32ccfbb6a8 100644
> --- a/drivers/hfpmodem/voicecall.c
> +++ b/drivers/hfpmodem/voicecall.c
> @@ -1111,6 +1111,18 @@ static void ciev_callheld_notify(struct ofono_voicecall *vc,
> vd->clcc_source = g_timeout_add(POLL_CLCC_DELAY,
> poll_clcc, vc);
> }
> + else {
Can you make sure this follows our coding style? else should be on the
same line as the previous }
> + if (vd->clcc_source)
> + g_source_remove(vd->clcc_source);
> +
> + /* We got a notification that there is a held call
> + * and no active call but we already are in such state.
> + * Let's schedule a poll to see what happened.
> + */
This comment is also not according to our coding style. Item M2.
> + vd->clcc_source = g_timeout_add(POLL_CLCC_DELAY,
> + poll_clcc, vc);
> + }
> +
> }
>
> vd->cind_val[HFP_INDICATOR_CALLHELD] = value;
>
Regards,
-Denis
prev parent reply other threads:[~2016-01-11 18:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 17:19 [PATCH] hfpmodem: Handle repeated held call indicator Kuba Pawlak
2016-01-11 18:04 ` Denis Kenzior [this message]
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=5693EEB5.8070000@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