975352 - [Sora][Message][SMS]The type message can't be replaced.

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: RIL, defect, P1)

Description

[sync-1]

Firefox OS v1.3
 Mozilla build ID: 20140208004002
 
 DEFECT DESCRIPTION:
 ->The type sms can't be replaced.
 
  REPRODUCING PROCEDURES:
 ->Use "now sms"tool send the same type sms;
 
  EXPECTED BEHAVIOUR:
 ->The same type sms should be replaced.
 
  ASSOCIATE SPECIFICATION:
 
  TEST PLAN REFERENCE:
 
  TOOLS AND PLATFORMS USED:
 
  USER IMPACT:
 
  REPRODUCING RATE:100%
 
  For FT PR, Please list reference mobile's behavior:

Comment 1

[sync-1]

Attachment: Now SMS

Comment 2

[Julien Wajsberg [:julienw]]

Is it a bug for NowSMS or for Firefox OS' Messages app?

Comment 3

[Jason Smith [:jsmith]]

(In reply to Julien Wajsberg [:julienw] from comment #2)
> Is it a bug for NowSMS or for Firefox OS' Messages app?

Enpei - Do you know?

Comment 4

[Enpei]

(In reply to Jason Smith [:jsmith] from comment #3)
> (In reply to Julien Wajsberg [:julienw] from comment #2)
> > Is it a bug for NowSMS or for Firefox OS' Messages app?
> 
> Enpei - Do you know?

Sorry, I do not familiar with this area. But reporter can try to send the same replacement type messages to other OS smartphone either Android or iOS to see if those can complete the replacement job or not. Otherwise maybe needs to check with account carrier to see if their SMSC support SMS replacement or not.

Comment 5

[Vance Chen [:vchen][skype:vance.lucida][[e-mail]]]

if you are talking about the Replace Short Message Type defined in the 3GPP SMS Spec 23.040, then we do not support that in FFOS.

For detail information about Replace Short Message Type, please refer to the attached spec, section "9.2.3.9 TP-Protocol-Identifier (TP-PID)"

Comment 6

[Vance Chen [:vchen][skype:vance.lucida][[e-mail]]]

Attachment: TP-99126.pdf

Comment 7

[Julien Wajsberg [:julienw]]

FWIW I really think the user reported a bug that is happening in NowSMS itself.

Comment 8

[田旻]

(In reply to Julien Wajsberg [:julienw] (away until 5th May) from comment #7)
> FWIW I really think the user reported a bug that is happening in NowSMS
> itself.
reproduce procedure:
1. Open NowSMS, send a sms with its message type being 4 to FFOS and Android phone. Its content is "type-4 message 1".
2. Send a a sms with it message type 4 to FFOS and Android phone. Its content is "type-4 message 2". When the new message received, the old one ("type-4 message 1") is disappear both in the thread and notification in Android phone. However, FFOS just deal with it as normal message, there isn't any replacement at all.

Comment 9

[田旻]

(In reply to Julien Wajsberg [:julienw] (away until 5th May) from comment #7)
> FWIW I really think the user reported a bug that is happening in NowSMS
> itself.

You can also see the sms replacement type description in 3GPP SMS Spec 23.040.

Comment 10

[Vance Chen [:vchen][skype:vance.lucida][[e-mail]]]

(In reply to 田旻 from comment #9)
> (In reply to Julien Wajsberg [:julienw] (away until 5th May) from comment #7)
> > FWIW I really think the user reported a bug that is happening in NowSMS
> > itself.
> 
> You can also see the sms replacement type description in 3GPP SMS Spec
> 23.040.

Hi Tianm -

As mentioned in Comment#5, we don't support PID replacement message type in FFOS

Thanks

Vance

Comment 11

[Julien Wajsberg [:julienw]]

Vance, do you know if we eventually want to support this?

I guess we'll need both Gaia and Gecko changes if we do this.

Comment 12

[Vance Chen [:vchen][skype:vance.lucida][[e-mail]]]

(In reply to Julien Wajsberg [:julienw] (away until 5th May) from comment #11)
> Vance, do you know if we eventually want to support this?
> 
> I guess we'll need both Gaia and Gecko changes if we do this.

I don't think we want to support this unless there is a strong demand from carriers(so far I don't see any carrier asking for this feature)

Comment 13

[Julien Wajsberg [:julienw]]

I guess it's a WONTFIX then, thanks!

Comment 14

[Jack Liu]

Hi Vance, 

DT still consider it as blocking issue, please help waive it if there is no plan to implement in 1.3.

BTW, in which version will it be implemented?

Thanks.

Comment 15

[Julien Wajsberg [:julienw]]

In current plan, it will never be implemented.

If DT want it we can add it in the backlog though.

Comment 16

[Vance Chen [:vchen][skype:vance.lucida][[e-mail]]]

Hi Jack, per discussion, please also directly raise this item with the DT roadmap team so we have tracking of these requirements. DT needs to prioritize all their asks.

Comment 17

[Jack Liu]

Hi Vance, 

Have asked internal team member to contact with DT, will post all updates here.

Thanks.

Comment 18

[田旻]

Qualcomm said they have had interfaces to support the replacement messages. Thus it's only decided by us weather to imply this function. 
However, our SPM think this bug is important to us...