From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 1/2] sms: Option HSO modem can't really do CNMA
Date: Mon, 24 Nov 2014 12:29:03 -0600 [thread overview]
Message-ID: <547378EF.8050704@gmail.com> (raw)
In-Reply-To: <87wq6pwbu2.fsf@ossau.homelinux.net>
[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]
Hi Neil,
>
> oFono chooses 2 for the "mt" value, rather than 1, if it thinks that the
> modem can do "CNMA", which I think means acknowledging each SMS after it
> is transferred from the modem to the containing OS. But:
Yes, oFono prefers using +CMT indication instead of +CMTI. That is
because we actually need 2 extra AT commands to process the incoming
message instead of just 1 with +CMT.
>
> - in practice the modem never generates the +CMT indications that are
> supposed to go with this mode of operation
>
Your modem is just weird then.
> - there are other places in the source code nearby where CNMA acking is
> skipped for OFONO_VENDOR_OPTION_HSO.
>
Not really. We only skip the generation of the ackpdu. Acknowledging
via AT+CNMA still works with the 'safe' AT+CNMA=0 option. This works on
every HSO device I have :) Admittedly I never played with the GTA04.
> It seems this adds up to an indication that the modem doesn't really do
> CNMA, and the patch that I've submitted does the trick and allows
> incoming SMSes to be received successfully.
You might need to rework the hso driver to detect/handle the GTM601
separately. Adding another vendor quirk to do so.
Regards,
-Denis
next prev parent reply other threads:[~2014-11-24 18:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 1:48 [PATCH 1/2] sms: Option HSO modem can't really do CNMA Neil Jerram
2014-11-21 1:48 ` [PATCH 2/2] receive-sms: Support printing received SMS with non-ASCII characters Neil Jerram
2014-11-24 18:31 ` Denis Kenzior
2014-11-21 2:01 ` [PATCH 1/2] sms: Option HSO modem can't really do CNMA Neil Jerram
2014-11-24 18:29 ` Denis Kenzior [this message]
2014-11-26 10:37 ` Neil Jerram
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=547378EF.8050704@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.