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 15:38:21 +0200	[thread overview]
Message-ID: <20180509133821.GA23230@amd> (raw)
In-Reply-To: <20180509133506.GX77069@atomide.com>

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

Hi!

> > > > > AT+CNMI=1,2,2,1,0
> > > > < OK
> > 
> > > 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.
> > 
> > Sending SMSes seems to work with ofono.
> 
> OK is this over ttyUSB or ngsm port?

ttyUSB. ngsm port behaves too strangely for me.

> > > When receiving, mdm6600 sends these on dlci 1:
> > > ~+WAKEUP
> > > ~+WAKEUP
> > > ~+WAKEUP
> > > 
> > > Then mdm6600 sends this on dlci 9:
> > > ~+CMT=372
> > > 
> > > And that's probably the incoming SMS size. But I don't see
> > > anything for what actually reads the incoming SMS.
> 
> Hmm it occured to me that maybe the incoming messages are read
> using QMI over USB.
> 
> > That seems to be standard message
> > ftp://www.3gpp.org/tsg_t/TSG_T/TSGT_04/Docs/PDFs/TP-99129.pdf .
> > 
> > Do you see AT+CNMI during boot and AT+CNMA after message is received?
> 
> I'm only seeing AT+CNMA=0,0 on dlci 9 after resume. I think that is
> used to query for new messages.
> 
> No CNMI in my logs it seems. But if QMI over USB is used to read
> the messages that would explain it only checks for new SMS.

Thanks for info. No real leads there :-(.
									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 --]

       reply	other threads:[~2018-05-09 13:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180509133506.GX77069@atomide.com>
2018-05-09 13:38 ` Pavel Machek [this message]
2018-05-11 12:34 ` Incoming sms problem on Motorola Droid 4 Pavel Machek
     [not found] <20180511123926.GK77069@atomide.com>
2018-05-14  9:01 ` Pavel Machek
     [not found] <20180509010324.GA98604@atomide.com>
2018-05-09  8:48 ` Pavel Machek
2018-05-08 21:51 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-09  6:50   ` 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=20180509133821.GA23230@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