Closed Bug 1227558 Opened 9 years ago Closed 6 years ago

[Sony Z3C] MMS read report doesn't work

Categories

(Firefox OS Graveyard :: RIL, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: pensacola_m2000, Unassigned)

Details

(Keywords: foxfood)

Attachments

(1 file)

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0
Build ID: 20151029151421

Steps to reproduce:


Device details: OS version: 2.5.0.0 prerelease
                Build identifier: 20151019102225
                Platform version: 44.0a1
                Build number: eng.worker.20151019.100643
                dogfood

Go to Messages - Settings - Enable read reports
Send a MMS
Make sure the MMS has been read


Actual results:

At the moment there is no read report sent. Message report inform the user about the delivery, no read report, or any other notification.


Expected results:

FFOS is capable of returning MMS read report when the sender is requesting that
Keywords: foxfood
Hi,

Is it possible to have the adb logcat with RIL output enabled in Settings/Developer/RIL Output in ADB for further analysis?
In addition, read report might not be supported in some carriers.
Is it possible to double confirm this by testing with other reference phone and the same test sim?

Thanks!
Flags: needinfo?(pensacola_m2000)
(In reply to Bevis Tseng[:bevistseng][:btseng] from comment #1)
> Hi,
> 
> Is it possible to have the adb logcat with RIL output enabled in
> Settings/Developer/RIL Output in ADB for further analysis?
> In addition, read report might not be supported in some carriers.
> Is it possible to double confirm this by testing with other reference phone
> and the same test sim?
> 
> Thanks!

Hi,

I've reproduced the issue and attached some logs. I will try to reproduce this with Flame too asap.
Attached file logRIL.txt
Flags: needinfo?(pensacola_m2000)
(In reply to Marcela Oniga from comment #3)
> Created attachment 8692151 [details]
> logRIL.txt

Unfortunately, I cannot see any SMS PDU from the network which represents a MMS read report.
That means somehow there is a problem between recipient and the MMSC in the carrier.
If the MMS message was read by the recipient and the read report was replied to the MMSC, we should be able to see a NEW_SMS in the attached log.

BTW, it will be helpful to narrow down the problem if we got following information:
1. Is it happened all the time? (reproducible rate 100%?)
2. What is the carrier of the sender and the receiver?
3. What's the behaviour in other reference phone like Android?
   (This will be helpful to identify whether it's an carrier specific issue instead.)

In addition, when capturing the adb logcat next time, please enable both the RIL and the MMS output to ADB. (Sorry for not mentioning the MMS part in comment 1.)
The log shall be started betfore the MMS is sent and shall be stopped few minutes later after MMS is received and read by the recipient.
(In reply to Bevis Tseng[:bevistseng][:btseng] from comment #4)
> (In reply to Marcela Oniga from comment #3)
> > Created attachment 8692151 [details]
> > logRIL.txt
> 
> Unfortunately, I cannot see any SMS PDU from the network which represents a
> MMS read report.
> That means somehow there is a problem between recipient and the MMSC in the
> carrier.
> If the MMS message was read by the recipient and the read report was replied
> to the MMSC, we should be able to see a NEW_SMS in the attached log.
> 
> BTW, it will be helpful to narrow down the problem if we got following
> information:
> 1. Is it happened all the time? (reproducible rate 100%?)

100% reproducible on sony device

> 2. What is the carrier of the sender and the receiver?

Same carrier: Orange

> 3. What's the behaviour in other reference phone like Android?
>    (This will be helpful to identify whether it's an carrier specific issue
> instead.)

I will test as soon as possible.

> 
> In addition, when capturing the adb logcat next time, please enable both the
> RIL and the MMS output to ADB. (Sorry for not mentioning the MMS part in
> comment 1.)
> The log shall be started betfore the MMS is sent and shall be stopped few
> minutes later after MMS is received and read by the recipient.

Both RIL and MMS Output in ADB were enabled while capturing the attached logs. And I can confirm that I've started to log before sending MMS and it was stooped after the MMS was read.
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: