Open Source Telephony
 help / color / mirror / Atom feed
From: Ryan Raasch <ryan.raasch@gmail.com>
To: ofono@ofono.org
Subject: Re: SIM PIN unlock
Date: Wed, 28 Oct 2009 15:17:15 +0100	[thread overview]
Message-ID: <4AE8526B.7000305@gmail.com> (raw)
In-Reply-To: <200910271110.18713.denkenz@gmail.com>

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



Denis Kenzior wrote:
> Hi Ryan,
> 
>> Ok. I have narrowed it down a little.
>>
>> It seems to be the CRSM command reading the
>> SIM_EFLI_FILEID when it succeeds.
>>
>> ofonod[6326]: > AT+CRSM=192,28421\r
>> ofonod[6326]: < \r\n+CRSM: 144,
>> ofonod[6326]: < 0,850D00046F05040001FFAA03020000\r\n\r\n
>> ofonod[6326]: < \r\nOK\r\n
>>
>> goes no further....
> 
> The parser is stuck because your modem is spewing garbage.  atgen plugin uses 
> the _really_ strict gsmv1 syntax.  I suggest you make a custom driver for your 
> device that uses the gsm_permissive syntax.
> 
This worked! Thank you. Could this be another option in modem.conf 
(Syntax=[Permissive,GSM1])?

>> 	ofono_sim_read(sim, SIM_EFLI_FILEID,
>>          	                OFONO_SIM_FILE_STRUCTURE_TRANSPARENT,
>>                  	        sim_efli_read_cb, sim);
> 
> This is wrong and won't get you very far as there are about 20 other SIM files 
> that we read.

I knew it was wrong, it was not a fix, just a localized point where my 
device was failing.


Regards,
Ryan

> 
> Regards,
> -Denis
> 

  reply	other threads:[~2009-10-28 14:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-26 12:59 SIM PIN unlock Ryan Raasch
2009-10-26 16:06 ` Denis Kenzior
2009-10-26 16:57   ` Ryan Raasch
2009-10-26 17:45     ` Andrzej Zaborowski
2009-10-27 15:45       ` Ryan Raasch
2009-10-27 16:10         ` Denis Kenzior
2009-10-28 14:17           ` Ryan Raasch [this message]
2009-10-28 21:26             ` Denis Kenzior

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=4AE8526B.7000305@gmail.com \
    --to=ryan.raasch@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