From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: Reg: Memory capacity exceeded
Date: Mon, 20 Sep 2010 07:44:45 -0500 [thread overview]
Message-ID: <4C97573D.90406@gmail.com> (raw)
In-Reply-To: <B668883EB5DD7144ADFC248A72176EA802A519E5@fioues07.ebgroup.elektrobit.com>
[-- Attachment #1: Type: text/plain, Size: 1216 bytes --]
Hi Jeevaka,
On 09/20/2010 07:39 AM, Jeevaka.Badrappan(a)elektrobit.com wrote:
> Hi,
>
>> Of course, one can argue whether this feature really has some real
>> world relevance or is purely theoretical.
>>
>> I wonder if it is a type approval requirement to support?
>
>> I'm afraid there is a PICS case for this thing. I cannot recall how we
> got N900 through this particular hoop, but probably we just waived this
> particular test case irrelevant.
>
> correct. There is a USIM conformance case on this message capacitiy
> exceeded information. As per the 3GPP 31.121 specification section 8.2:
>
> "If all SMS data field are full and furthermore all memory capacity
> reserved for SMS inside the ME is filled up to maximum and a SM(Short
> Message) was rejected, then this shall be indicated in the SMS Status
> file.(EFsmss)"
The thing is, oFono configures SMS for direct delivery (e.g. no SM/ME
storage). And even if direct delivery does not work (e.g. crappy modem
or Class 2 / Class 3 messages) oFono still removes the SMS as soon as it
is delivered. We should never hit a sim/me memory full conditions.
So I don't see how this test case even applies.
Regards,
-Denis
next prev parent reply other threads:[~2010-09-20 12:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-20 10:45 Reg: Memory capacity exceeded linux mobile
2010-09-20 10:56 ` Marcel Holtmann
2010-09-20 11:09 ` Jeevaka.Badrappan
2010-09-20 12:25 ` Aki Niemi
2010-09-20 12:29 ` Pekka Pessi
2010-09-20 12:39 ` Jeevaka.Badrappan
2010-09-20 12:44 ` Denis Kenzior [this message]
2010-09-20 14:08 ` Jeevaka.Badrappan
2010-09-20 14:11 ` Denis Kenzior
2010-09-20 12:53 ` Aki Niemi
2010-09-21 6:34 ` linux mobile
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=4C97573D.90406@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.