1054836 - [dolphin] dolphin shows wrong time in the read report of MMS using Airtel SIM

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: RIL, defect)

Description

[Peipei Cheng (needinfo if you need my action)]

Steps to reproduce
------------------------------------------------------------------------
0. Insert Airtel SIM and wait for sim card camp properly.
1. Enable Read report for MMS
2. Send MMS from Airtel SIM and read the MMS, wait for read report
   --> read report shows wrong time.

According to partner developer, the time on read report is GMT（Greenwich Mean Time） time.

I think this issue might be operator specific. because I tested on China Mobile and China Unicom SIM but could not get read report. Partner QA will help provide a video or screenshot of this issue.

We already have the slog here: https://mega.co.nz/#!0oECmBAC!4kUGPQ__ZwxnxCZGzUGNMdERDJwA3UT6xepFNYz6OCU

Comment 1

[Peipei Cheng (needinfo if you need my action)]

shawn, could you please take a look? let me know if you need further information.

Comment 2

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

Hi Peipei,

According to the log, the read report is a normal MMS message instead of the one defined in OMA standard.
Can vendor double confirm if it was the same to the screenshot in bug 1039185 under Airtel network:
https://bug1039185.bugzilla.mozilla.org/attachment.cgi?id=8464485

If yes, 
I think this is operator-specific issue, because the timestamp is a text description and is the message body of the message: "Your message to xxx, has been read on Date 2014-xx-xx XX:XX GMT".
There is nothing we can do in device-side.

In addition, I think the behavior shall be same in other reference phone.

Comment 3

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

NI for vendor to confirm the analysis in comment 2.

Comment 4

[Peipei Cheng (needinfo if you need my action)]

Thank you very much bevis! I will check with vendor and update later. Keep ni on me.

Comment 5

[Peipei Cheng (needinfo if you need my action)]

STR Video: https://mega.co.nz/#!cgNmCa5Y!_xFszOtKM2-9MpvLO3GFpmrA5wdYRXsuCjB6LzA_DGA

I checked with vendor. From the video they provide, the issue is the same as the screenshot listed in comment 2. So this should be operator issue.

Thanks again for Bevis's help!

I would close this bug as wontfix.