From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: Re: Connecting with Huawei E226
Date: Fri, 27 Aug 2010 10:02:03 +0200 [thread overview]
Message-ID: <1282896123.6841.76.camel@localhost.localdomain> (raw)
In-Reply-To: <AANLkTi=MnhCwboYS29E8Ut8c0D6FeFxLusndOnO4C3Jv@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1556 bytes --]
Hi Thiago,
> >> I forgot also to mention that I used list-context to see if the
> >> enable-modem was successful. The test B is the one that fails.
> >
> > From the logs it seems Test A is what fails since we never add any atoms
> > in that one. Basically the problem is that your modem firmware never
> > tells us that the SIM has been initialized by sending us a ^SIMST
> > notification.
> >
> > Kalle's patch relies on SIMST being delivered eventually. Since it
> > never does, oFono is under the impression that your SIM is invalid. We
> > probably need to query SYSINFO a few more times in this case, but it
> > seems all Huawei firmwares act slightly differently here.
>
> Is there something else I can do to help solve this issue? I tried
> another modem, a ZTE MF110, that is not working either. I installed
> wvdial on my MeeGo machine and was able to connect using both the
> Huawei and ZTE modems. I also tested the devices under Ubuntu Lucid
> and Fedora 13 (both with Networkmanager) and they worked out of the
> box.
the problem is that neither wvdial nor NM are proper telephony stacks.
They are both in the end just dialers. So that comparison is not helping
us since oFono has to do way more work before we can just "dial" an
Internet connection.
We get this fixed, but not as quick as you might like us too. The Huawei
and ZTE modems are showing race condition behavior. And that is mainly
because oFono is just too fast and they can't initialize the SIM fast
enough for us.
Regards
Marcel
next prev parent reply other threads:[~2010-08-27 8:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 20:31 Connecting with Huawei E226 Thiago Cangussu de Castro Gomes
2010-08-18 1:45 ` Denis Kenzior
2010-08-18 14:06 ` Thiago Cangussu de Castro Gomes
2010-08-18 17:02 ` Denis Kenzior
2010-08-18 22:26 ` Thiago Cangussu de Castro Gomes
2010-08-18 22:31 ` Denis Kenzior
2010-08-24 20:25 ` Thiago Cangussu de Castro Gomes
2010-08-24 22:16 ` Denis Kenzior
2010-08-24 22:58 ` Thiago Cangussu de Castro Gomes
2010-08-24 23:45 ` Denis Kenzior
2010-08-26 21:24 ` Thiago Cangussu de Castro Gomes
2010-08-27 8:02 ` Marcel Holtmann [this message]
2010-08-27 12:58 ` Thiago Cangussu de Castro Gomes
2010-08-27 18:14 ` Marcel Holtmann
2010-08-27 18:57 ` Thiago Cangussu de Castro Gomes
2010-08-27 20:51 ` Marcel Holtmann
2010-08-27 21:53 ` Thiago Cangussu de Castro Gomes
2010-08-28 6:21 ` Marcel Holtmann
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=1282896123.6841.76.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--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.