From: =?unknown-8bit?q?Andr=C3=A9?= Draszik <git@andred.net>
To: ofono@ofono.org
Subject: Re: telit modem NW DETACH
Date: Tue, 21 Feb 2017 08:56:12 +0000 [thread overview]
Message-ID: <1487667372.2824.23.camel@andred.net> (raw)
In-Reply-To: <1486631706.12234.7.camel@andred.net>
[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]
On Thu, 2017-02-09 at 09:15 +0000, André Draszik wrote:
> Thanks Denis for your advise,
>
> On Tue, 2017-02-07 at 11:22 -0600, Denis Kenzior wrote:
> >
> > [...]
> >
> > Generally the network shouldn't just detach you if you deactivated a
> > context, so my first guess would be that the modem firmware is doing
> > something silly. Do you have another modem to test by any chance?
>
> No... Are you saying it could (in theory) actually be the network itself
> indeed (i.e. not the modem (firmware))?
>
> > > I can get around that by disabling/re-enabling the modem, but I would
> > > like
> > > to avoid that...
> > >
> > > As a further point, whenever the modem reports that it has been
> > > disconnected
> > > but then the CellID changes, it magically reconnects, so I believe I
> > > should
> >
> > Even more evidence that seems to indicate a firmware issue. But who
> > knows.
>
> I got my hands on a more recent firmware version, once I get a chance to
> update my modem I will report back.
The most recent firmware available didn't make any difference to the
behaviour, neither did changing the mobile provider.
A colleague of mine is looking to implement something now that will
hopefully be upstreamable.
Cheers,
Andre'
next prev parent reply other threads:[~2017-02-21 8:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 11:49 telit modem NW DETACH =?unknown-8bit?q?Andr=C3=A9?= Draszik
2017-02-07 17:22 ` Denis Kenzior
2017-02-09 9:15 ` =?unknown-8bit?q?Andr=C3=A9?= Draszik
2017-02-09 16:04 ` Denis Kenzior
2017-02-21 8:56 ` =?unknown-8bit?q?Andr=C3=A9?= Draszik [this message]
2017-02-21 8:59 ` =?unknown-8bit?q?Andr=C3=A9?= Draszik
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=1487667372.2824.23.camel@andred.net \
--to=git@andred.net \
--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