Closed
Bug 1072609
Opened 11 years ago
Closed 7 years ago
[MMS] Wrong error message displayed when user sends MMS without a data connection under AT&T network
Categories
(Firefox OS Graveyard :: RIL, defect)
Tracking
(b2g-v2.0 affected, b2g-v2.1 affected, b2g-v2.2 affected)
RESOLVED
WONTFIX
People
(Reporter: jschmitt, Unassigned)
Details
(Whiteboard: [2.1-exploratory-2])
Attachments
(5 files)
Description:
The error message does not accurately explain the reason why MMS is not sending.
Repro Steps:
1) Update a Flame device to BuildID: 20140924063013
2) Disconnect from Cell Data/Wifi Networks
3) Open SMS app
4) Create a new Message and type in a valid phone number
5) Select the 'Attach' icon
6) Select Camera and take a picture
7) Send the MMS
Actual:
A wrong error message is displayed.
Expected:
The error messages tells the user to connect to a Data network.
Environmental Variables:
Device: Flame 2.1
BuildID: 20140924063013
Gaia: 020e6283a033e8fbcf65e7ed81c5b75ba0095f22
Gecko: d6b762814638
Version: 34.0a2 (2.1)
Firmware: V180
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Notes:
Repro frequency: 100%
See attached: screenshot
| Reporter | ||
Comment 1•11 years ago
|
||
Issue also occurs on 2.2 Flame 319MB KK and 2.0 Flame 319MB KK.
Environmental Variables:
Device: Flame 2.2 Master
BuildID: 20140924013003
Gaia: ff6dbb006e4e60edba697639aa2a2a199b07069b
Gecko: 1e2993c99323
Version: 35.0a1 (2.2 Master)
Firmware: V180
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0
Environmental Variables:
Device: Flame 2.0
BuildID: 20140924003005
Gaia: 263e3b201dca967ec5346e35901aa981ca47dce7
Gecko: 35d791e16d31
Version: 32.0 (2.0)
Firmware: V180
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Whiteboard: [2.1-exploratory-2]
Comment 2•11 years ago
|
||
Hi Bevis, it looks like data and mms are sharing the same apn and disconnect case. Do you think that we are able to detect this case and return the corresponding error code from platform?
Flags: needinfo?(btseng)
Comment 3•11 years ago
|
||
(In reply to Steve Chung [:steveck] from comment #2)
> Hi Bevis, it looks like data and mms are sharing the same apn and disconnect
> case. Do you think that we are able to detect this case and return the
> corresponding error code from platform?
No, MMS shall be able to be sent even when data is disabled and data/mms shares the same APN.
(MMS data connection will still be setup/release for MMS transaction.)
Currently, there is a known issue in Bug 1058282:
In Flame device, there is a DNS query problem when only MMS connection is available.
NI to reporter to have both adb logcat & tcpdump to double confirm the root cause:
https://github.com/bevis-tseng/Debug_Tools
Component: Gaia::SMS → RIL
Flags: needinfo?(btseng) → needinfo?(jschmitt)
| Reporter | ||
Comment 4•11 years ago
|
||
I was unable to get a tcpdump, adding a QAwanted tag to do the steps provided in Comment 3.
Flags: needinfo?(jschmitt)
Keywords: qawanted
Comment 5•11 years ago
|
||
Attaching ADB logcat & tcpdump from latest Flame 2.1.
Environmental Variables:
Device: Flame 2.1
BuildID: 20141006062615
Gaia: 778ebac47554e1c4b7e9a952d73e850f58123914
Gecko: bc87917b3b95
Version: 34.0a2 (2.1)
Firmware: V180
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Comment 6•11 years ago
|
||
Updated•11 years ago
|
QA Contact: aalldredge
Comment 7•11 years ago
|
||
When I attempted to upload the tcpdump bugzilla told me that it was an empty file. I have tried multiple times to get a proper tcpdump but I have been unable to get one using your steps linked in comment 3. Have the steps to obtain a tcpdump changed recently?
Flags: needinfo?(btseng)
Comment 8•11 years ago
|
||
Hi Adam,
We have a bug fix of the same issue on Bug 1058282 recently in master build.
Would you please use the nightly build in m-c branch to give it a trial again?
If the symptom is gone, we could mark this bug as duplicated to Bug 1058282.
Thanks!
Flags: needinfo?(btseng)
Comment 9•11 years ago
|
||
2.2 Flame nightly results:
MMS does not send with data and wifi off, and "Message Not Sent" error is shown.
(Note: Error message does not read: "Connect to data network to send message".) Further, the Expected Results in comment 0 are NOT seen.
(Full Flash)
Device: Flame Master
Build ID: 20141009040206
Gaia: 7b92615bdc97e5c675cd385ec68bc5e47e0c5288
Gecko: f0bb13ef0ee4
Version: 35.0a1 (Master)
Firmware Version: v180
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
Keywords: qawanted
QA Contact: aalldredge → ddixon
Updated•11 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
Comment 10•11 years ago
|
||
(In reply to Duane Dixon [:ddixon] from comment #9)
> 2.2 Flame nightly results:
>
> MMS does not send with data and wifi off, and "Message Not Sent" error is
> shown.
> (Note: Error message does not read: "Connect to data network to send
> message".) Further, the Expected Results in comment 0 are NOT seen.
The expected behavior mentioned in comment 0 is not TRUE.
There is no dependency for the MMS connection with the toggle of Data connection/WiFi.
Then MMS message shall be sent directly except the following condition:
- The selected SIM for MMS is not the active one.
(A dialog will be popped up to ask user to switch the active SIM for data access)
>
> (Full Flash)
>
> Device: Flame Master
> Build ID: 20141009040206
> Gaia: 7b92615bdc97e5c675cd385ec68bc5e47e0c5288
> Gecko: f0bb13ef0ee4
> Version: 35.0a1 (Master)
> Firmware Version: v180
> User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0
According to the log in comment 6, the root cause looks the same to bug 1058282 comment 14:
10-06 12:21:46.488 1781 1781 I Gecko : -@- MmsService: Failed to ensureRouting: Error: Failed to resolve 'proxy.mobile.att.net', with status: 2152398878
However, the test result in comment 9 looks totally different from the result in Bug 1058282 Comment 32. :(
Bug 1058282 describes the same symptom to this bug and was verified fixed in comment 32.
The only difference is that the test build seems newer in bug 1058282 Comment 32.
Set qawanted for the following 2 requests:
1. Can we have last nightly build and verify this symptom again and clarify the difference to bug 1058282?
2. If the MMS message is still not able to be sent, can we have both adb logcat & tcpdump for further analysis? (https://github.com/bevis-tseng/Debug_Tools)
Thanks!
Keywords: qawanted
Comment 11•11 years ago
|
||
Hi Bevis,
Can't reproduce on Flame v2.0 and Woodduck v2.0.The MMS can be sent sueccessfully when disable WIFI and data connection.
-----------------
Flame device information:
Gaia-Rev 9c7dec14e058efef81f2267b724dad0850fc07e4
Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/c17df9fe087d
Build-ID 20141019160201
Version 32.0
Device-Name flame-kk
FW-Release 4.4.2
FW-Incremental 34
FW-Date Tue Sep 30 14:06:36 CST 2014
Bootloader L1TC00011840
Woodduck device information:
Gaia-Rev a273ab9c18e9184eb02722b25c73e2ba7680cc09
Gecko-Rev e7df4dde2d9dbedee942333d34eaea2afe32bebc
Build-ID 20141017100433
Version 32.0
Device-Name soul35
FW-Release 4.4.2
FW-Incremental 1413510704
FW-Date Fri Oct 17 09:52:15 CST 2014
Comment 12•11 years ago
|
||
This symptom only happened at AT&T network according to the log analysis in comment 10 and the fix was provided in bug 1058282 for v2.1 and m-c.
I set qawanted in comment 10 because it's still failed according to comment 9.
I'd like to know whether this is a duplicated bug to bug 1058282.
If not, we need the corresponding adb logcat & tcpdump for further analysis.
Thanks!
Updated•11 years ago
|
Summary: [MMS] Wrong error message displayed when user sends MMS without a data connection → [MMS] Wrong error message displayed when user sends MMS without a data connection under AT&T network
Comment 14•11 years ago
|
||
Sorry, I was unable to pull a tcpdump from my phone (the results were blank).
Actual Results: Flame (2.2, 2.1) device fails to send an MMS without data or wifi connection enabled.
Full Flash, nightly.
Device: Flame Master
Build ID: 20141023040204
Gaia: 27a1d1baaa8e375b70e043efee67d5f2206c330b
Gecko: 88adcf8fef83
Version: 36.0a1 (Master)
Firmware Version: v188
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
Device: Flame 2.1
Build ID: 20141023001201
Gaia: 1e48e3e40e0780c0cd07a3457e5fe2efeeb542d1
Gecko: 09fb60a37850
Version: 34.0 (2.1)
Firmware Version: v188
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage?]
Flags: needinfo?(ddixon) → needinfo?(jmitchell)
Keywords: qawanted
Updated•11 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
QA Contact: ddixon
Comment 15•11 years ago
|
||
Comment 16•11 years ago
|
||
(In reply to Duane Dixon [:ddixon] from comment #15)
> Created attachment 8510530 [details]
> mms_no_data_logcat
Hi,
Sorry to said that
It seems that the ril/mms/network related logs was not enabled.
Can you follow execute the enable_debug_flags.sh script in https://github.com/bevis-tseng/Debug_Tools and then capture capturing the logcat?
(We expect to see "MmsService" related logs when sending MMS.)
Thanks!
Flags: needinfo?(ddixon)
Comment 17•11 years ago
|
||
Flags: needinfo?(ddixon)
Comment 18•11 years ago
|
||
(In reply to Duane Dixon [:ddixon] from comment #17)
> Created attachment 8511264 [details]
> no_data_logcat_with_flags
The debug flag was enabled. However the log was not captured completely (too short).
I didn't see any logs related to "MmsService" to identify what the problem is. :(
Flags: needinfo?(ddixon)
Comment 19•11 years ago
|
||
Flags: needinfo?(ddixon)
Comment 20•11 years ago
|
||
(In reply to Duane Dixon [:ddixon] from comment #19)
> Created attachment 8512030 [details]
> full_data_logcat
There is still no MMS related log captured.
Take the log in comment 6 for example, we can see some MmsService related log for sending as followed:
10-06 12:21:43.238 1781 1781 I Gecko : -@- MmsService: Running protocol version: 1.1
10-06 12:21:43.238 1781 1781 I Gecko : -@- MmsService: send: aParams: {}
10-06 12:21:43.238 1781 1781 I Gecko : -@- MmsService: createSavableFromParams: aParams: {}
10-06 12:21:43.258 1781 1781 I Gecko : -@- MmsService: createSavableFromParams: normalize phone number from 4257501710 to 4257501710
However, for all the logs in comment 15, comment 17, comment 19,
I cannot see anything related to this.
I am not able to do any analysis about this bug. :(
Comment 21•7 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•