Open Source Telephony
 help / color / mirror / Atom feed
From: Daniel Wagner <wagi@monom.org>
To: ofono@ofono.org
Subject: Re: [RFC v3] Readout technology form Option HSO modems
Date: Wed, 09 Jun 2010 15:06:00 +0200	[thread overview]
Message-ID: <4C0F91B8.9090306@monom.org> (raw)
In-Reply-To: <20100609113456.GA9175@pc0043.bmw-carit.intra>

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

> This version just relys on CREG appearing _after_ the OCTI OSSYSI
> [OUWCTI] sequence. I've uploaded a log of the current version with
> timestamps added.
>
> http://pastebin.com/qUMsh6sk
>
> An intereseting sequence in the log file is from line 376 to 401.
> This is roaming from 2g to 3g, but OUWCTI is comming late
> so that CREG doesn't pick up the late OUWCTI. On line 396 then
> OUWCTI appears (2 seconds after CREG) but the next CREG is 28 seconds
> away.

Here is another log with a lot of roaming.

http://pastebin.com/LZhHSkmK

There are many OUWCTI withouth OCTI OSSYSI updates. It toggles between 
UMTS and HSPA. connman_netreg_status_notify is called very seldom 
because there is no CREG. So this approach doesn't work good enough.

I think at least updates on OUWCTI should immediately use 
connman_netreg_status_notify.

What about having a separate connman_netreg_tech_notify call? This would 
make the code here much simpler? And Huawei modems could also use the 
same function for tech updates.

cheers,
daniel


      reply	other threads:[~2010-06-09 13:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-09 11:34 [RFC v3] Readout technology form Option HSO modems Daniel Wagner
2010-06-09 13:06 ` Daniel Wagner [this message]

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=4C0F91B8.9090306@monom.org \
    --to=wagi@monom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox