Open Source Telephony
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: ofono@ofono.org
Subject: Re: Incoming sms problem on Motorola Droid 4
Date: Wed, 09 May 2018 08:50:34 +0200	[thread overview]
Message-ID: <20180509065033.GB10423@amd> (raw)
In-Reply-To: <bb8c59dd-db99-f86d-2ca1-ed746809327d@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2214 bytes --]

On Tue 2018-05-08 17:08:25, Denis Kenzior wrote:
> Hi Pavel,
> 
> On 05/08/2018 04:51 PM, Pavel Machek wrote:
> >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".
> 
> So you're saying the modem firmware is lying about supporting all these
> modes :)

I'm saying this modem is broken in more than one way, yes. I tried
CNMI=1,1, but that did not work too well:

ofonod[2935]: drivers/atmodem/sim.c:at_crsm_read_cb() crsm_read_cb:
90, 00, 30
> AT+CNMI=1,1
< OK
ofonod[2935]: src/network.c:__ofono_netreg_add_status_watch() 0x53bbf0
...
ofonod[2935]: src/modem.c:get_modem_property() modem 0x53b000 property
SystemPath
ofonod[2935]: plugins/upower.c:battery_props_changed()
< +CMTI: "ME",-1
ofonod[2935]: Unable to parse CMTI notification
< +CIEV: 7,1

I'm getting the +CMTI: "ME",-1 indication in other cases, too :-(.

> >I had some luck with unicsy_demo using AT+CNMI=1,2 with text mode (not
> >PDU) messages. That works well enough for me.
> 
> oFono doesn't support text mode...
> 
> >
> >Unfortunately, if I force ofono to pass "AT+CNMI=1,2", it does not
> >work well, either.
> 
> You could try using value of '1' for the <mt> parameter and see if the modem
> will route messages to memory first and send a +CMTI indication..

Invalid SMTI indication, AFAICT :-(. Let me play some more...

> >Any ideas how to debug this / what to try?
> >
> 
> I think you have to play with some combinations, not really sure what to
> tell you. Refer to 3GPP 27.005 for details on the SMS related AT commands.

Thanks for the pointer.

									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  parent reply	other threads:[~2018-05-09  6:50 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-08 21:51 Incoming sms problem on Motorola Droid 4 Pavel Machek
2018-05-08 22:08 ` Denis Kenzior
2018-05-09  4:31   ` Marcel Holtmann
2018-05-09  8:18     ` Pavel Machek
2018-05-09 13:03       ` Denis Kenzior
2018-05-09 15:11         ` Pavel Machek
2018-05-09 15:41           ` Denis Kenzior
2018-05-09 18:57             ` Pavel Machek
2018-05-09 19:33               ` Denis Kenzior
2018-05-10  6:50                 ` Marcel Holtmann
2018-05-10  6:58                   ` Pavel Machek
2018-05-10  7:11                     ` Marcel Holtmann
2018-05-11 23:18                       ` Voice calls over qmi was " Pavel Machek
2018-05-12  0:47                         ` Denis Kenzior
2018-05-12  3:09                           ` Joey Hewitt
2018-05-12 11:02                             ` Pavel Machek
2018-05-12 14:19                             ` Alexander Couzens
2018-05-13 10:33                               ` Marcel Holtmann
2018-05-14  6:45                               ` Pavel Machek
2018-05-14 16:19                               ` Denis Kenzior
2018-05-12  1:02                         ` Denis Kenzior
2018-05-12  7:37                           ` Harald Welte
2018-05-16 15:10                             ` Bob Ham
2018-05-16 16:12                               ` Harald Welte
2018-05-14 13:02                       ` [rfc] Fix incoming sms on Droid 4 " Pavel Machek
2018-05-09  6:50   ` Pavel Machek [this message]
     [not found] <20180509010324.GA98604@atomide.com>
2018-05-09  8:48 ` Pavel Machek
     [not found] <20180509133506.GX77069@atomide.com>
2018-05-09 13:38 ` Pavel Machek
2018-05-11 12:34 ` Pavel Machek
     [not found] <20180511123926.GK77069@atomide.com>
2018-05-14  9:01 ` Pavel Machek

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=20180509065033.GB10423@amd \
    --to=pavel@ucw.cz \
    --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