912362 - [zffos1.1][P3][sms]The device does not indicate when the SIM memory for receiving messages is full

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::SMS, defect)

Description

[FangChen]

Built ID 20130823171628
Device: Ikura
QC RIL version: "ro.build.firmware_revision=V1.01.00.01.019.180"
gaia commit: 4916f82 Merge branch 'zte/ics_strawberry_cdr' of ssh://10.67.16.41:29418/quic/lf/releases/gaia into ics_strawberry_cdr
gecko commit: a1c2bb0 ZRL modify ACCEPT Http head for MMS

   A.- Overview Description (technical background, concise explanation of the bug):
    
    The device does not indicate when the SIM memory for receiving messages is full.
    ________________________________________________________________________________
    B.- Steps to Reproduce (initial conditions, required resources, step by step instructions to reproduce):
    1. Power on the device with a valid ANITE SIM that has no space for new messages.
2. Connect it to the Agilent 8960/Anite SAS equipment.
3. Register the device on the network, then send a class-2 short message to DuT.
    
    ________________________________________________________________________________
    C.- Actual Result (current bad behaviour that is reported as a bug):
    
    The device does not indicate when the SIM memory for receiving messages is full.
    ________________________________________________________________________________
    D.- Expected Result (correct behaviour wished):
    
    If the SIM memory is full, it should store the messages on the device, or at least indicate that the SIM memory is full.
    ________________________________________________________________________________

Comment 1

[KTucker [:KTucker][Inactive 3/4/2016]]

I think I'm encountering this issue in a different way on Buri v 1.2.0 Mozilla RIL

Environmental Variables
Device: Buri v 1.2.0 Mozilla RIL
Build ID: 20131011004001
Gecko: http://hg.mozilla.org/releases/mozilla-aurora/rev/c8e97fd5b94d
Gaia: 79abf09f2b5b6440f43cb5ae44ef6c85c0437e8d
Platform Version: 26.0a2

The user got stuck on the progress bar when exporting a large number of contacts to the SIM. When the user force closed the contacts app and tried again, the progress bar was stuck immediately when trying to export contacts to the SIM. My educated guess is that the SIM memory is full and that is why I am seeing this issue. If this is a different issue, please leave a comment and I will write up a new issue for what I am encountering.

Comment 2

[Julien Wajsberg [:julienw]]

Regarding comment 1, I really think the contacts storage and the messages storage are well separate on the SIM.

So this is a similar problem but I think the issues are still different.

Comment 3

[Julien Wajsberg [:julienw]]

Dear FangChen,

we don't store the messages on the SIM, but rather we store the messages on our flash storage in a database.

Therefore I don't understand what you want to achieve here.

Comment 4

[FangChen]

Hi,Julien
Class-2 message is a SMS must be saved in the sim

Comment 5

[Julien Wajsberg [:julienw]]

Hey Vicamo,

what do we do with class-2 messages currently?

Comment 6

[David Palomino [:dpalomino]]

Hi, 

AFAIK, we don't currently support class-2 SMS. Please, check this bug: 

https://bugzilla.mozilla.org/show_bug.cgi?id=911069

Thks!
David

Comment 7

[Vicamo Yang [:vicamo][:vyang]]

Please see bug 739143.

In original Android RIL design, it has a parcel RIL_REQUEST_REPORT_SMS_MEMORY_STATUS, which takes a boolean value indicating availability of device storage (note: not SIM storage).

There is also an unsolicited RIL_UNSOL_SIM_SMS_STORAGE_FULL event, but as you see here, an unsolicited event means its direction is from modem/rild to Gecko.

So basically what we can do here, limited by Android's RIL commands, is to implement RIL_UNSOL_SIM_SMS_STORAGE_FULL event handler and pass it to the content pages.  Bug 739143 was opened one and a half year ago, waiting someone to nominate it for some milestone. :)

(In reply to David Palomino [:dpv] from comment #6)
> Hi, AFAIK, we don't currently support class-2 SMS. Please, check this bug: 
> https://bugzilla.mozilla.org/show_bug.cgi?id=911069

That doesn't follow we don't have class-2 SMS logic.  Like what I had in that comment, we don't want to report binary SMS to content pages, not to say those can only be handled in modem.  Propagating such a message to database or the owner doesn't really help anything.

Comment 8

[Julien Wajsberg [:julienw]]

My problem here is that if we show something in content, which value will this have for the user ? Is there a way for the user to recover from this state ?

Comment 9

[Vicamo Yang [:vicamo][:vyang]]

(In reply to Julien Wajsberg [:julienw] from comment #8)
> My problem here is that if we show something in content, which value will
> this have for the user ? Is there a way for the user to recover from this
> state ?

No, unless we have the ability to read/write SMS on SIM, which is in bug 900312.

Comment 11

[Julien Wajsberg [:julienw]]

Hey Bevis, I'd close this bug as wontfix, what do you think ?

Comment 12

[Bevis Tseng[:bevis][:btseng](Exited)]

(In reply to Julien Wajsberg [:julienw] (PTO -> 2016) from comment #11)
> Hey Bevis, I'd close this bug as wontfix, what do you think ?

Agree. class 2 Text SMS became less important current phone because the storage of SMS in SIM is very small and expensive compared to the storage in the device and in the cloud.

Comment 13

[Julien Wajsberg [:julienw]]

as agreed