Open Source Telephony
 help / color / mirror / Atom feed
From: Alexander A Khryukin <alexander@mezon.ru>
To: ofono@ofono.org
Subject: Re: huawei e1550
Date: Mon, 18 Oct 2010 12:30:14 +0400	[thread overview]
Message-ID: <1287390614.2921.0.camel@mezon.ru> (raw)
In-Reply-To: <1286974459.10204.6.camel@mezon.ru>

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

В Срд, 13/10/2010 в 16:54 +0400, Alexander A Khryukin пишет:
> В Срд, 13/10/2010 в 15:14 +0300, Kalle Valo пишет:
> > Alexander A Khryukin <alexander@mezon.ru> writes:
> > 
> > >> Sorry, I wasn't able to immeadiately say from the logs what went wrong.
> > >> Can you get a log which includes AT commands? It would help a lot.
> > >> 
> > >> Just run this command to get the logs:
> > >> 
> > >> OFONO_AT_DEBUG=1 /usr/sbin/ofonod -n
> > >> 
> > >> What's the exact version of ofono you are using? Huawei has had some
> > >> changes lately. 
> > >> 
> > >> Also is the SIM configured to ask for PIN or not? I'm guessing no from
> > >> the log, but can't be sure.
> > >
> > > Ok.I connect modem to usb-port, and log it
> > >
> > > OFONO_AT_DEBUG=1 /usr/sbin/ofonod -n
> > 
> > Sorry, I forgot -d switch from the command which enables the debug
> > messages. So it should be like this:
> > 
> > OFONO_AT_DEBUG=1 /usr/sbin/ofonod -n -d
> > 
> > > http://pastie.org/1212535
> > 
> > I didn't immeadiately find anything wrong in the AT logs. So basically
> > your modem disappers from the bus and then comes back. Can a firmware
> > crash cause that?
> > 
> > The last commands were:
> > 
> > ofonod[838]: PCUI: > AT+CSCB=1\r
> > ofonod[838]: PCUI: < \r\nOK\r\n
> > ofonod[838]: PCUI: > AT+CSCB=0,"4096,4097,4098,4099,4100,4101,4102,4103,4104,4105,4106,4107,4108,4109,4110,4111,4352-4356"\r
> > 
> > Can you try the patch below? Maybe it gives us some hint what's
> > happening.
> > 
> > diff --git a/plugins/huawei.c b/plugins/huawei.c
> > index b20d83c..13ef192 100644
> > --- a/plugins/huawei.c
> > +++ b/plugins/huawei.c
> > @@ -624,8 +624,6 @@ static void huawei_post_online(struct ofono_modem *modem)
> >                                                                 data->pcui);
> >  
> >         ofono_sms_create(modem, OFONO_VENDOR_HUAWEI, "atmodem", data->pcui);
> > -       ofono_cbs_create(modem, OFONO_VENDOR_QUALCOMM_MSM,
> > -                                               "atmodem", data->pcui);
> >         ofono_ussd_create(modem, OFONO_VENDOR_QUALCOMM_MSM,
> >                                                 "atmodem", data->pcui);
> > 
> 
> 
> git apply --stat p.patch
> Working =)
> Now compile.
> 
> 
> 
> _______________________________________________
> ofono mailing list
> ofono(a)ofono.org
> http://lists.ofono.org/listinfo/ofono

bump



  reply	other threads:[~2010-10-18  8:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-08 12:20 huawei e1550 Alexander A Khryukin
2010-10-08 12:43 ` Alexander A Khryukin
2010-10-08 18:25   ` Kalle Valo
2010-10-13 11:50     ` Alexander A Khryukin
2010-10-13 12:14       ` Kalle Valo
2010-10-13 12:42         ` Alexander A Khryukin
2010-10-13 12:51           ` Kalle Valo
2010-10-13 13:57             ` Alexander A Khryukin
2010-10-14  9:03             ` Alexander A Khryukin
2010-10-13 12:54         ` Alexander A Khryukin
2010-10-18  8:30           ` Alexander A Khryukin [this message]
2010-10-29 11:39             ` Alexander A Khryukin

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=1287390614.2921.0.camel@mezon.ru \
    --to=alexander@mezon.ru \
    --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