All of lore.kernel.org
 help / color / mirror / Atom feed
From: JH <jupiter.hce@gmail.com>
To: ofono@ofono.org
Subject: Re: Unsalble cellular connection
Date: Fri, 02 Aug 2019 20:46:06 +1000	[thread overview]
Message-ID: <CAA=hcWRsgAiz6YUVRkiFh8d6Aa_q6qdcw-5NtOerum-8vqaCbQ@mail.gmail.com> (raw)
In-Reply-To: <CAKSBH7HcH-0KMEF5M+b7FmB1ysy_L=HGYuV0GZ89y56v6tgo0Q@mail.gmail.com>

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

Hi Giacinto, thanks for your response.

On 8/2/19, Giacinto Cifelli <gciofono@gmail.com> wrote:
> Hi jupiter,
> most likely the network dropped the context without signaling.
> What kind of modem is it? And would you know also the chipset?

It is uBlox SARA-R4 chipset, did you mean it could be caused by weak
LTE signalling level? It is a prototype device, the hardware was
designed by an contractor. Any simple way to show LTE signalling level
in connman or ofono log files? The trouble is it connected well at
startup, then dropped it, it is hard to convince the hardware
contractor it is hardware problem unless I have strong evidence that
is not the software problem.

Thank you very much.

Kind regards,

- jupiter

  reply	other threads:[~2019-08-02 10:46 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-01 11:01 Unsalble cellular connection JH
2019-08-01 18:16 ` Giacinto Cifelli
2019-08-02 10:46   ` JH [this message]
2019-08-02 17:43     ` Giacinto Cifelli
2019-08-07 10:27       ` JH
2019-08-09  3:59         ` Giacinto Cifelli
2019-08-09 12:56           ` JH
2019-08-11 11:57             ` JH
2019-08-11 13:37               ` Giacinto Cifelli
2019-08-12  6:54                 ` JH
2019-08-12 22:09                   ` JH
2019-08-13  6:42                     ` Jonas Bonn
     [not found] <CAA=hcWSVcULFW4jo5q9RsxW4igozgM99oJN6KoZ8UaSLdLhD7g@mail.gmail.com>
2019-08-13 15:00 ` Jonas Bonn
2019-08-14 11:11   ` JH
2019-08-14 13:00     ` Jonas Bonn
2019-08-15 11:33       ` Daniel Wagner
2019-08-15 12:45       ` JH
2019-08-15 14:58         ` Daniel Wagner
2019-08-17 11:53           ` JH
2019-08-17 11:55             ` JH
2019-08-17 14:09               ` Jonas Bonn
2019-08-17 22:29                 ` JH
     [not found] <CAOf5uw=2U6MkcKP8OzWNyzwvxjAvYLdXuDASFVEjnWvMQ0fjHw@mail.gmail.com>
2019-08-19  1:51 ` JH
2019-08-19  5:38   ` Jonas Bonn
2019-08-19 14:18     ` JH
     [not found] <CAOf5uw=6hQkfhAt=OWH+mim30NyOHU6Z8GVMJ6yKCEf=1NFw8w@mail.gmail.com>
2019-08-19  7:50 ` Jonas Bonn
2019-08-19  7:56   ` Jonas Bonn
     [not found] <CAOf5uw=fQe4cuTfdciqW3hmXHXv-tY2UYd4aLfMVxF5Lx65jbw@mail.gmail.com>
2019-08-19  8:17 ` Jonas Bonn

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='CAA=hcWRsgAiz6YUVRkiFh8d6Aa_q6qdcw-5NtOerum-8vqaCbQ@mail.gmail.com' \
    --to=jupiter.hce@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.