Closed Bug 1151690 Opened 9 years ago Closed 9 years ago

[Nexus 5] Send and receive MMS fails

Categories

(Firefox OS Graveyard :: RIL, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: pmathur, Unassigned)

Details

(Whiteboard: [2.2-nexus-5-l])

Attachments

(4 files)

Steps to reproduce
1. Launch the Messages app on the Nexus 5 device. 
2. Compose an MMS to another number. Attach a photo and tap Send.
3. Wait a few minutes to receive confirmation that the MMS has been sent.

Expected Results
The "Sending..." message underneath the photo thumbnail changes to the timestamp that the MMS was sent. A ringtone is sounded.

Actual Results
The "Sending..." message underneath the photo thumbnail changes to a red warning icon to indicate that MMS was not sent. An error message is displayed: "Message not sent. There was a problem sending the message. Please try again."

Steps to reproduce (contd)
4. Using another phone, send an MMS to the Nexus 5 device.
5. The other phone confirms that the MMS was sent.

Expected Results
The Nexus 5 displays a notification for incoming MMS. The MMS is received and can be viewed in the Messages app.

Actual Results
The Nexus 5 does not display a notification for incoming MMS. The MMS is never received.

Test automation also confirms this. The script test_sms_with_attachments.py fails.
https://github.com/mozilla-b2g/gaia/blob/master/tests/python/gaia-ui-tests/gaiatest/tests/functional/messages/test_sms_with_attachments.py
Automation Smoke Test Report: 
http://mozilla-twqa.github.io/Gaiatest-Reports/2015/04/20150406002503-v2.2-flame/smoketest.html

Traceback (most recent call last):
File "/var/lib/jenkins/workspace/B2G.v2.2.pvt.flame.gaiatest.smoketest/tests/python/gaia-ui-tests/.env/local/lib/python2.7/site-packages/marionette_client_mozilla_b2g37_v2_2-0.1-py2.7.egg/marionette/marionette_test.py", line 268, in run
testMethod()
File "/var/lib/jenkins/workspace/B2G.v2.2.pvt.flame.gaiatest.smoketest/tests/python/gaia-ui-tests/gaiatest/tests/functional/messages/test_sms_with_attachments.py", line 36, in test_sms_send
camera.tap_select_button()
File "/var/lib/jenkins/workspace/B2G.v2.2.pvt.flame.gaiatest.smoketest/tests/python/gaia-ui-tests/gaiatest/apps/camera/app.py", line 96, in tap_select_button
Wait(self.marionette).until(lambda m: self.apps.displayed_app.name != self.name)
File "/var/lib/jenkins/workspace/B2G.v2.2.pvt.flame.gaiatest.smoketest/tests/python/gaia-ui-tests/.env/local/lib/python2.7/site-packages/marionette_client_mozilla_b2g37_v2_2-0.1-py2.7.egg/marionette/wait.py", line 143, in until
cause=last_exc)
TimeoutException: TimeoutException: Timed out after 30.0 seconds

Test Environment 
Gaia-Rev        a6351e1197d54f8624523c2db9ba1418f2aa046f
Gecko-Rev       https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/c3335a5d3063
Build-ID        20150406002503
Version         37.0
Device-Name     hammerhead
FW-Release      5.0
FW-Incremental  eng.cltbld.20150406.035814
FW-Date         Mon Apr  6 03:58:30 EDT 2015
Bootloader      HHZ12d
Component: Gaia::UI Tests → Gaia::Dialer
Attached image P4071377.JPG
The MMS sending, receiving is okay here, the automation issue is script problem, that is not reproducible by manual test.
Hi Parul, could you help to gather a RIL log if you can reproduce that again, thanks.
Flags: needinfo?(pmathur)
Whiteboard: [2.2-nexus-5-l]
This looks like an intermittent issue with the carrier in Taipei. Clearing the nom while we confirm this is an actual issue in the product.

Parul, how many times did the test failed? Could you reproduce the problem manually?
blocking-b2g: 2.2? → ---
I can reproduce the problem manually on the Nexus 5. Attached log with ril debugger enabled.

Steps to Reproduce:
1. Go to Settings > Developer and turn on 'RIL output in ADB'.
2. Execute the command |adb logcat -b radio -b main -v time|
3. Launch the Messages app on the Nexus 5 device. 
4. Compose an MMS to another number. Attach a photo and tap Send.
5. Wait a few minutes to receive confirmation that the MMS has been sent.

Expected Results
The "Sending..." message underneath the photo thumbnail changes to the timestamp that the MMS was sent. A ringtone is sounded.

Actual Results
The "Sending..." message underneath the photo thumbnail changes to a red warning icon to indicate that MMS was not sent. An error message is displayed: "Message not sent. There was a problem sending the message. Please try again."

Steps to reproduce (contd)
6. Using another phone, send an MMS to the Nexus 5 device.
7. The other phone confirms that the MMS was sent.

Expected Results
The Nexus 5 displays a notification for incoming MMS. The MMS is received and can be viewed in the Messages app.

Actual Results
The Nexus 5 does not display a notification for incoming MMS. The MMS is never received.

Test Environment
same build as in Comment 0
Flags: needinfo?(pmathur)
Unfortunately, there seems no MMS related logs enabled in the attached log.
Besides, I can't see any data connection established in the log. :(
Is the APN correctly configured in this nexus device?

Would you please follow the instruction in the link to have both logcat in main/radio with related debugging flags enabled & corresponding tcpdump  for further analysis?
https://github.com/bevis-tseng/Debug_Tools

Thanks!
Flags: needinfo?(pmathur)
Attached adb logcat with ril-related debug flags turned on. Repeated steps in Comment 3. Magic happened. Functionality now working as expected. Bug could not be reproduced.

== Steps to enable debug flags of ril, mms, network in runtime ==
Go to https://github.com/bevis-tseng/Debug_Tools and download script "enable_debug_flags.sh".
adb root
chmod +x enable_debug_flags.sh
./enable_debug_flags.sh
Wait for B2G restarting complete.

== Steps to capture the packets in the devices ==
Go to https://github.com/bevis-tseng/Debug_Tools and download binary "tcpdump".
Install attached tcpdump command into test device:
adb remount; adb push tcpdump system/bin/;adb shell chmod 777 /system/bin/tcpdump
Start capturing tcpdump:
adb shell tcpdump -i any -p -s 0 -w /data/capture.pcap

error: only position independent executables (PIE) are supported.
http://dan.drown.org/android/
Q: What does the error "error: only position independent executables (PIE) are supported" mean?
A: Android 5.0 brought the requirement that only executables compiled with the -fPIE flag. These packages were compiled for Android 4.4 and earlier, so they won't work on 5.0.
Flags: needinfo?(pmathur)
Attached image 2015-04-08-16-52-48.png
Attached screenshot of MMS sent and received.
Status: NEW → RESOLVED
Closed: 9 years ago
Component: Gaia::Dialer → RIL
Keywords: smoketest
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: