Created attachment 8594905 [details] attachments.zip Description: When a user of a flame device is sent an MMS of too many photos, they will observe that their phone will not recognize a message attempt was sent to them. When any number of pictures is sent (less than 6 though probably depends on size) is sent to their phone, the device will notify the user with a message notifcation and all pictures will be downloaded at once. However, if a limit is reached then it as if the phone never received the message. PreReq: * separate device that can send +6 images at once (performed with iPhone) * 6 images (total size = 850 kb) Repro Steps: 1) Update a Flame to 20150420010204 2) Send MMS from separate device to this device, composed of 6 or more photos. 3) Await notification on flame device for MMS to be received Actual: Device does not receive message; no sign of message receiving attempted Expected: * Device downloads all MMS * Device notifies user that a MMS was attempted but was too large to handle Environmental Variables: ----------------------------------- Device: Flame 3.0 Build ID: 20150420010204 Gaia: cb41d8421da5dc4f16ea566ea2917a9b7f828154 Gecko: 50b95032152c Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b Version: 40.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0 Device: Flame 2.2 BuildID: 20150420002502 Gaia: c15a2b6d3a783813959c2b3bffd2a131f4270b9e Gecko: cc02ee38b252 Gonk: ebad7da532429a6f5efadc00bf6ad8a41288a429 Version: 37.0 (2.2) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0 Device: Flame 2.1 BuildID: 20150420001205 Gaia: bbe983b4e8bebfec26b3726b79568a22d667223c Gecko: b85d4f4a6d61 Gonk: ebad7da532429a6f5efadc00bf6ad8a41288a429 Version: 34.0 (2.1) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 ----------------------------------- Repro frequency: 5/5 See attached: images used as zip
Observed that this is directly related to the amount of memory sent over the images, rather than the number of images. Tested by sending 8 images, total of about 130kb, and they downloaded fine. Retitling for this behavior.
Summary: [Messages] Sending a Flame device 6 photos in one MMS will not be received; no notification that a MMS was attempted to be sent → [Messages] Sending a Flame device over 850kb of images in one MMS will not be received; no notification that a MMS was attempted to be sent
NI on component owner for nomination decision. We're not receiving an error that the MMS failed to receive on the user end and on the sending end it looks like it went through.
QA Whiteboard: [QAnalyst-Triage+]
Flags: needinfo?(pbylenga) → needinfo?(jlorenzo)
Something is not clear: did we receive the MMS? I mean, do you see it and can you display it if you open the Messages app and the conversation manually ?
Hello Julien, No message was received when a MMS of this size was sent to device. I've observed on other phones that they will produce a 'Message Receipt Failed' message, where the device understood it could not process the message it attempted to receive, so it notified the user so they could take additional action. However, on flame devices, there is no notification that a message was attempted, as if the user received nothing at all.
This qawanted request was handled by the original reporter.
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage?]
Flags: needinfo?(felash) → needinfo?(ktucker)
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Sorry Oliver, it's still not completely clear to me: when you enter the Messages app, do you see the message (even undownloaded), or everything happens as if nobody sent the message.
It's as if nobody sent the message. I attempted to send this 850kb package from my iPhone -> flame device. Flame created no new thread, and had no indication.
Flags: needinfo?(onelson) → needinfo?(felash)
Thanks, then it's likely an issue in RIL. We should at least see an errored message. Some more questions for you Oliver, sorry that I didn't ask you before but they come separately to me ;) 1. can you disable "Auto Retrieve" in the Messaging Settings and try again? 2. can you receive the same message on other phones? 3. can you enable RIL debugging and attach the logs from when you try to receive the message? Thanks !
Component: Gaia::SMS → RIL
Flags: needinfo?(felash) → needinfo?(onelson)
Suddenly wondering if the iphone tries to send this big message using iMessage... because it's higher than some threshold, or because you already sent a message to this same phone number while the SIM was in an iPhone.
> 2. can you receive the same message on other phones? Especially Android phones, so that we can rule out the possible issue with iMessage.
Clearing the NI, while we get a bit more information about the issue.
Created attachment 8596708 [details] logcat_ril_2sms_then_6pic_mms.txt Answers inserted into reply-thread (In reply to Julien Wajsberg [:julienw] from comment #8) > Thanks, then it's likely an issue in RIL. We should at least see an errored > message. > > Some more questions for you Oliver, sorry that I didn't ask you before but > they come separately to me ;) > > 1. can you disable "Auto Retrieve" in the Messaging Settings and try again? Disabling Auto-Retrieve will result in the Actual Results for this issue still: no message is received. > 2. can you receive the same message on other phones? Tested against: * Samsung Galaxy S II GT-i9100 Smartphone (GINERBREAD.XWKF3): no message received * Nokia Lumia 635 (Windows): no message received * Samsung Alias 2: received a 'Message Receipt Failed' message These were all performed with 'iMessages' disabled on the sending device. > 3. can you enable RIL debugging and attach the logs from when you try to > receive the message? > The log didn't seem to produce anything, again the message of 6 pictures was not received in any way on the flame device, however I'll attach the log regardless. Of note, I sent 2 short text messages directly before to sample the log: "Test" and "Round two". > Thanks !
Flags: needinfo?(onelson) → needinfo?(felash)
OK so I'd say it's a network issue and we can't do anything. I don't know why "Samsung Alias 2" behaves differently: do you use the same carrier? I'm gonna close this INVALID because no phone can actually receive this message. Thanks for the testing !
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.