From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: Connecting with Huawei E226
Date: Wed, 18 Aug 2010 17:31:36 -0500 [thread overview]
Message-ID: <4C6C5F48.7080103@gmail.com> (raw)
In-Reply-To: <AANLkTi=x_xNOK3FJx85tJte5bp_eywT4+azmbgaLQ1vj@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1526 bytes --]
Hi Thiago,
On 08/18/2010 05:26 PM, Thiago Cangussu de Castro Gomes wrote:
> On Wed, Aug 18, 2010 at 2:02 PM, Denis Kenzior <denkenz@gmail.com> wrote:
>> Hi Thiago,
>>
>>>> The problem with the failed cases it that oFono / ConnMan combination is
>>>> simply too fast. It tries to access the Modem before it had the chance
>>>> to properly initialize the SIM card. We have pushed some fixes upstream
>>>> after the 0.26 release that should alleviate this.
>>>
>>> Thanks for the response. You are right, I can reproduce the problem
>>> even with connman turned off, by calling the test scripts before the
>>> modem is ready.
>>>
>>> I'm using both ofono and connman from git, with all the available
>>> updates so far. Does it mean that the fixes didn't solved the issue in
>>> my case? Could you point me to the patches?
>>
>> For your particular case these patches from Kalle would be helpful:
>>
>> [PATCH 1/2] huawei: poll sim state
>> [PATCH 2/2] huawei: postpone post_sim until SIM is ready
>>
>> However, they weren't integrated upstream due to some concerns. See the
>> entire thread for more details.
>
> I've applied the patches but unfortunately it didn't fixed the issue.
> Still can't connect when the modem is plugged after ofonod is started.
> I can send the logs if anyone thinks it's useful.
>
Sorry to hear you're having trouble. Kalle reported similar issues were
fixed with his patches on the E1552. Sending the logs would probably be
helpful.
Regards,
-Denis
next prev parent reply other threads:[~2010-08-18 22:31 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 [this message]
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
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=4C6C5F48.7080103@gmail.com \
--to=denkenz@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox