LKML Archive on
help / color / mirror / Atom feed
From: Tony Lindgren <>
To: Pavel Machek <>
Cc:, kernel list <>,
	linux-arm-kernel <>,,,,,
Subject: Re: Incoming sms problem on Motorola Droid 4
Date: Tue, 8 May 2018 18:03:24 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20180508215102.GA5253@amd>

* Pavel Machek <> [180508 21:53]:
> Hi!
> I have problems with incoming SMS. ofono tries to use +CNMI=1,2,2,1,0
> > AT+CNMI=?
> < +CNMI: (0,1,2),(0,1,2,3),(0,2),(0,1,2),(0,1)
> < OK
> ofonod[3070]: drivers/atmodem/sms.c:build_cnmi_string()
> ofonod[3070]: drivers/atmodem/sms.c:construct_ack_pdu()
> > AT+CNMI=1,2,2,1,0
> < OK
> ofonod[3070]: src/network.c:__ofono_netreg_add_status_watch() 0x5bbbf0
> ... unfortunately, with that configuration no messages are comming to
> ofono and the other phone sees them as "delievery failed".
> I had some luck with unicsy_demo using AT+CNMI=1,2 with text mode (not
> PDU) messages. That works well enough for me.
> Unfortunately, if I force ofono to pass "AT+CNMI=1,2", it does not
> work well, either.
> Any ideas how to debug this / what to try?

Well you can try to see what Android is doing for SMS with:

# echo 0x7fffffff > /sys/module/ts27010mux/parameters/debug_level
# dmesg | grep ts27010 | grep AT

To send SMS, looks like Android RIL first does:

2 AT+CMGS=327 where 327 seems to be the size of the whatever
encoded message. Then the next packet to dlci 2 contains the
encoded message that is of size 327.

When receiving, mdm6600 sends these on dlci 1:

Then mdm6600 sends this on dlci 9:

And that's probably the incoming SMS size. But I don't see
anything for what actually reads the incoming SMS.



      reply	other threads:[~2018-05-09  1:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-08 21:51 Pavel Machek
2018-05-09  1:03 ` Tony Lindgren [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \
    --subject='Re: Incoming sms problem on Motorola Droid 4' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).