1077754 - [MMS] User will receive an endless sending message when sending an MMS with a non activated sim card.

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: RIL, defect)

Description

[John Thomas [:Johnt]]

Attachment: logcat_20141003_1609.txt

Description:
If the user attempts to send an SMS while a non active sim card they will receive an endless sending message.


Repro Steps:
1) Update a Flame to 20141003000203
2) Insert a non activated SIM card into device.
3) Send SMS to another device.

Actual:
The SMS will have a message saying "sending" that will never actually send.

Expected:
It is expected that user will receive a message explaining that they need an active sim card or to enable wifi.

Flame 2.1 KitKat Base (319mb)(Full Flash)

Environmental Variables:
Device: Flame 2.1
BuildID: 20141003000203
Gaia: 9861c61ec302fb0316c753a2e1c0f592180515fd
Gecko: da68900d1c66
Gonk: 2c909e821d107d414f851e267dedcd7aae2cebf
Version: 34.0a2 (2.1)
Firmware: V180
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Note: The 2.0 does not have an endless "sending" message but instead an endless spinning wheel.


Repro frequency: 100%
Link to failed test case: https://moztrap.mozilla.org/manage/case/12708/
See attached: Logcat
Video: https://www.youtube.com/watch?edit=vd&v=wRXEHUQRrjs

Comment 1

[John Thomas [:Johnt]]

This issue DOES occur on the Flame 2.2 KitKat Base (319mb) and Flame 2.0 KitKat Base (319mb)(Full Flash)

Description: The SMS will have a message saying "sending" that will never actually send.

Flame 2.2 KitKat Base (319mb)(Full Flash)

Environmental Variables:
Device: Flame 2.2 Master
BuildID: 20141003040207
Gaia: d711d1e469eeeecf25a02b2407a542a598918b2c
Gecko: b85c260821ab
Gonk: 2c909e821d107d414f851e267dedcd7aae2cebf
Version: 35.0a1 (2.2 Master)
Firmware: V180
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0

Flame 2.0 KitKat Base (319mb)(Full Flash)

Environmental Variables:
Device: Flame 2.0
BuildID: 20141003000204
Gaia: fa797854bfe708129ed54a158ad4336df1015c39
Gecko: 9b7fd1f78a15
Gonk: 2c909e821d107d414f851e267dedcd7aae2cebf
Version: 32.0 (2.0)
Firmware: V180
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Comment 2

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

Hi,

Sorry to tell you that the attached log didn't enable the RIL related debug flags.
May I have your help to enable the flags with the "enable_debug_flags.sh" in the following link and collecting the related logcats for further analysis?
https://github.com/bevis-tseng/Debug_Tools
(Note: tcpdump is not necessary for this bug.)

After enabling the debug flags of the test device, you can capture main/radio logcats at the same time:
(you can open mutitple consoles to collect different logcats at the same time)
1. adb logcat -v threadtime > logcat_main.txt
2. adb logcat -v threadtime -b radio > logcat_radio.txt

To clarify if it's modem/vendor related issues,
Please ensure to provide these 2 logcats from both MOZ build & CAF build for further comparison.

Thanks!

Comment 3

[John Thomas [:Johnt]]

Attachment: logcat_main.txt

Comment 4

[John Thomas [:Johnt]]

Attachment: logcat_radio.txt

Comment 5

[John Thomas [:Johnt]]

Logcats attached accordingly. Currently we use the build available in PVT so I wasn't sure where to find access to the CAF and MOZ builds.

Addtionally I wanted to further eleaborate in better detail on some more thorough repro steps.

Repro Steps:
1) Update a Flame to 20141003000203
2) Insert a non activated SIM card into device.
3) Deactivate Wifi if currently connected. (Disable data as well.)
4) Send an MMS to another device. (instead of SMS)

Comment 6

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

(In reply to John Thomas [:Johnt] from comment #5)
> Logcats attached accordingly. Currently we use the build available in PVT so
> I wasn't sure where to find access to the CAF and MOZ builds.
> 
> Addtionally I wanted to further eleaborate in better detail on some more
> thorough repro steps.
> 
> Repro Steps:
> 1) Update a Flame to 20141003000203
> 2) Insert a non activated SIM card into device.
> 3) Deactivate Wifi if currently connected. (Disable data as well.)
> 4) Send an MMS to another device. (instead of SMS)

Okay. If it's MMS not SMS, I think the symptom is expected by current design.
By current design, we don't have better feedback to know the status of MMS connection from RIL. (For the non-active SIM case, the data connection will never be able to established. MmsService will wait and feedback error until the MMS retry-timer is timeout).

We expect this could be enhanced after Bug 904514 (NetworkManager enhancement was done).

Comment 7

[Derek Harris [:DerekH] - Dont need info. Last day 6/5/15]

Not nominating to block, based on comment 6. This seems to be expected for now, but may be enhanced later.

Comment 8

[BMO Automation]

Firefox OS is not being worked on