Open Source Telephony
 help / color / mirror / Atom feed
From: Rolf Offermanns <rolf.offermanns@gmx.net>
To: ofono@ofono.org
Subject: Huawei K3715 and E172 test results
Date: Thu, 02 Sep 2010 17:45:25 +0200	[thread overview]
Message-ID: <4C7FC695.90809@gmx.net> (raw)

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

Hi All,

I did some tests with the following setup:

- Meego Netbook 1.0.x
- ofono git (1.9.2010)
  + Patch "[PATCH 1/2] huawei: poll sim state" from Kalle
- connman git (31.8.2010)
  + Patchset "[ofono-refactor-v2 PATCH xx] oFono API breakage, take 2"
  + Patchset "[service-leak PATCH xxx] fix service leak"
- EeePC 1005HA
- Huawei K3715 (Vodafone Mobile Connect USB)
- Huawei E172  (Vodafone Mobile Connect USB)

Below is a summary of the results. I have separate logfiles for each
test run with "OFONO_AT_DEBUG=1 ofonod -n -d '*'" output. Shall I post
them here?

Please let me know what I can do to improve the Huawei support.

Thanks to Kalle and Pekka for helping out on IRC.

-Rolf


Test run 1: Huawei K3715 with unlocked SIM (no PIN required)
================================================================================
1. Start ofonod after modem has settled
   -> Everything is fine
   -> Modem shows up in connman
2. Unplug / plug
   -> First sysinfo shows sim_state: 0
   -> Later sysinfo calls return sim_state: 1 (checked in Minicom)
   -> Modem not detected in connman
3. Unplug / plug
   -> same as 2.
4. Unplug / plug
   -> same as 2.
5. Unplug / plug
   -> same as 2.

Summary: Modem only works if already settled before ofonod starts.


Test run 2: Huawei K3715 with locked SIM (PIN required)
Note: Whenever a "PIN required" showed up, I used the "tests/enter-pin"
script.
================================================================================
1. Start ofonod after modem has settled
   -> Everything is fine
   -> Modem shows up in connman
2. Unplug / plug
   -> same as 1.
3. Unplug / plug
   -> enter-pin throws "DBus.Error.NoReply" exception
   -> Modem not detected in connman
4. Unplug / plug
   -> same as 3.
5. Unplug / plug
   -> same as 1.

Summary: Modem works if already settled before ofond starts and
sometimes when plugged in.


Test run 3: Huawei E172 with unlocked SIM (no PIN required)
================================================================================
1. Start ofonod after modem has settled
   -> Everything is fine
   -> Modem shows up in connman
2. Unplug / plug
   -> First sysinfo shows sim_state: 255 (handled by Kalles patch)
   -> Next SYSINFO shows sim_state: 1
   -> Modem not detected in connman
3. Unplug / plug
   -> First sysinfo shows sim_state: 255
   -> Next SYSINFO shows sim_state: 0(!)
   -> Then a SIMST reply comes in (not there in 2.)
   -> Modem not detected in connman
4. Unplug / plug
   -> First sysinfo shows sim_state: 255
   -> Next SYSINFO shows sim_state: 0(!)
   -> No SIMST reply
   -> Modem not detected in connman
5. Unplug / plug
   -> First sysinfo shows sim_state: 255
   -> Next SYSINFO shows sim_state: 1
   -> Modem shows up in connman

Summary: Modem works if already settled before ofond starts and seldom
when plugged in. Several different behaviours are observed.



Test run 4: Huawei E172 with locked SIM (PIN required)
Note: Whenever a "PIN required" showed up, I used the "tests/enter-pin"
script.
================================================================================
1. Start ofonod after modem has settled
   -> Everything is fine
   -> Modem shows up in connman
2. Unplug / plug
   -> AT chat gets out of sync early (no "right" reply after ATE0)
   -> Modem not detected in connman
3. Unplug / plug
    -> same as 1.
4. Unplug / plug
    -> same as 1.
5. Unplug / plug
   -> First sysinfo shows sim_state: 255
   -> Next SYSINFO gets no reply
      -> This happened quite often in other tests. The modem is still
         delivering replies to previous commands and the SYSINFO
         request seems to get lost.
   -> Modem not detected in connman

Summary: Modem works if already settled before ofond starts and seldom
when plugged in. Several different behaviours are observed.



             reply	other threads:[~2010-09-02 15:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-02 15:45 Rolf Offermanns [this message]
2010-09-03 19:09 ` Huawei K3715 and E172 test results Denis Kenzior
2010-09-06  7:01   ` Rolf Offermanns
2010-09-08 19:08   ` Kalle Valo

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=4C7FC695.90809@gmx.net \
    --to=rolf.offermanns@gmx.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