[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190116230602.GA3131@amd>
Date: Thu, 17 Jan 2019 00:06:02 +0100
From: Pavel Machek <pavel@....cz>
To: Tony Lindgren <tony@...mide.com>
Cc: linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-omap@...r.kernel.org,
Jarkko Nikula <jarkko.nikula@...mer.com>,
Johan Hovold <johan@...nel.org>,
Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>,
Marcel Partap <mpartap@....net>,
Merlijn Wajer <merlijn@...zup.org>,
Michael Scott <hashcode0f@...il.com>,
NeKit <nekit1000@...il.com>, omerlle@...il.com,
Sebastian Reichel <sre@...nel.org>,
Peter Ujfalusi <peter.ujfalusi@...com>,
Rob Herring <robh@...nel.org>
Subject: Re: WIP Droid 4 voice calls, GNSS & PM with a TS 27.010 serdev driver
Hi!
> Yeah the scripts in droid4-sms-tools git repo work for me for sending
> and receiving. They do not work with cdma currently as the format is
> different.
>
> Maybe you've managed to change the mode of the modem to queue the
> messages with the at commands to the usb port?
I did not have ttyUSB open during that boot. I hope this kind of
settings does not survive across reboots.
> You are reading and writing to /dev/motmdm9 for incoming sms right?
Yes, I think so. Same one where hex-coded PDU comes.
> > > My logs show that Android uses two different commands for ack.
> > > Either AT+GCNMA=1 or AT+CNMA=0,0 gets used depending on something
> > > that I have no idea of.. Maybe the network connected?
>
> I think AT+GCNMA=1 works 3g and AT+CNMA=0,0 with cdma. Or it could be
> that one of them is just a delayed ack, I don't know.
Strange. It does not seem to be recognized at all.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)
Powered by blists - more mailing lists