1114657 - [SMS][MMS] MMS messages cannot be sent or received without Data/WiFi if the device has not previously connected with a Data/WiFi network in AT&T Network.

Status: RESOLVED DUPLICATE of bug 1115486

(Firefox OS Graveyard :: RIL, defect)

Description

[Martin Shuman [:Marty]]

Attachment: logcat-MMS-without-Data.txt

Description:
If the device is booted without a Cellular Data or WiFi connection enabled, the device will always time out after 5 minutes when trying to send an MMS. (the behavior shown in bug 1072609)
If the user connects to a Cellular Data or WiFi network, *sends or receives an MMS*, then disconnects/disables those connections, the device will then be able to send and receive an MMS properly without a Data/WiFi connection.

Note: It is not enough to just enable, then immediately disable the network connection.  The device needs to either send or receive an MMS message while that connection is enabled (an SMS will not work).

If the phone is rebooted with Data and WiFi disabled, it will again be unable to send or receive MMS messages until a network connection is re-established.
   
Repro Steps:
1) Update a Flame device to BuildID: 20141222040204
2) Boot the device with Data and WiFi DISABLED.
3) Open the messages app send an MMS message (add an attachment, or a subject line to an SMS)
4) Wait for the message to send or time out
5) Open the notification tray and turn ON Cellular Data
6) Send a second MMS Message
7) Open the notification tray and turn OFF Cellular Data
8) Send a third MMS Message
  
Actual:
The first MMS message cannot be sent without a network connection, but the Third MMS message CAN be sent without a network connection.  

Expected: 
All MMS messages are sent properly, both with and without a Cellular Data or WiFi connection.
  
Environmental Variables:
Device: Flame 2.2 Master (319mb)(Kitkat Base)(Full Flash)
BuildID: 20141222040204
Gaia: ca6e91e09ef3ab417a0f6b6d6668d43597d85700
Gecko: b915a50bc6be
Gonk: e5c6b275d77ca95fb0f2051c3d2242e6e0d0e442
Version: 37.0a1 (2.2 Master)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Note: The attached logcat is a capture of attempting to send an MMS without a network, Waiting 5 minutes for the sending message to time-out, enabling WiFi and sending an MMS successfully, then disabling WiFi Data and again sending an MMS successfully.

Repro frequency: 10/10
See attached: logcat

Comment 1

[Peter Bylenga [:PBylenga]]

QAWanted for Branch Checks.

Comment 2

[Cody Roesch [:croesch]]

All branches were affected by this bug. The base build v188-1 actually sent every message without a data or wifi connection which is curious.

Tested with Shallow Flash on 319mb using Engineering builds.

This bug repro's on Flame KK builds: Flame 2.2 KK, Flame 2.1 KK, Flame 2.0 KK

Actual Results: The 3rd sms sent when not having any Data or Wifi connection is actually sending successfully. 

Repro Rate: 6/6

Environmental Variables:
Device: Flame 2.2 KK
BuildID: 20141222042411
Gaia: c5b03a9b40a37947d44a71eccd9017e76632f796
Gecko: c357fb08cc10
Version: 37.0a1 (2.2) 
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
-----------------------------------------------------------------
Environmental Variables:
Device: Flame 2.1 KK
BuildID: 20141222071650
Gaia: 1a58335917b23c170d85bf821f658e964c935b23
Gecko: 5509822354a9
Version: 34.0 (2.1) 
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
-----------------------------------------------------------------
Environmental Variables:
Device: Flame 2.0 KK
BuildID: 20141222071429
Gaia: ce83ea7b8e3fa2d1c3fd771fc22b654c18b3c381
Gecko: 7d0adaf6c447
Version: 32.0 (2.0) 
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
-----------------------------------------------------------------
Environmental Variables:
Device: Flame v188-1 Base
BuildID: 20141021162107
Gaia: 8c5c956ee6909408e29f375cc7d843a03d92f3d8
Version: 32.0 (2.0)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Comment 3

[Joshua Mitchell (Inactive)]

NI SMS owner for blocking call / assignment

Comment 4

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

The behavior looks similar to what we have fixed in bug 1058282.
It seems there is still something wrong of the routing to proxy.mobile.att.net when 1st MMS is sent.
Would you please help to follow the instructions in the link below to collect 
1. adb logcat with more debug flags enabled and 
2. tcpdump for further analysis.
https://github.com/bevis-tseng/Debug_Tools

Thanks!

Comment 5

[Martin Shuman [:Marty]]

Attachment: TCPDUMP

Comment 6

[Martin Shuman [:Marty]]

Attachment: logcat-MMS-Verbose.txt

Comment 7

[Martin Shuman [:Marty]]

Attachment: logcat_radio-MMS-Verbose.txt

Comment 8

[Martin Shuman [:Marty]]

I've uploaded a Main Logcat, a Radio Logcat, and a TCPDump capture using the scripts provided.  Let me know if you need anything else.

Comment 9

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

(In reply to Martin Shuman [:Marty] from comment #8)
> I've uploaded a Main Logcat, a Radio Logcat, and a TCPDump capture using the
> scripts provided.  Let me know if you need anything else.

Thanks for collecting this.
I'll look into these to see if there is anything abnormal!

Comment 10

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

BTW, I've tested the same scenario locally but not able to reproduce this.
It seems only reproducible under AT&T network.

Comment 11

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

After further analysis, I'd like to set this bug as duplicated to bug 1115482 for better classification of related DNS problems.

To workaround bug 1115482 in AT&T network, user could change the mms proxy in the MMS apn from "proxy.mobile.att.net" to 172.26.39.1, then the device shall be able to send/receive MMS without Data/WiFi.

Comment 14

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

[removing nomination as it's duplicate]