HTTP status 7 suggests to me the account needs to be reprovisioned as it’s missing services. Let’s check the contexts first though. Can you run by terninal curl https://raw.githubusercontent.com/rilmodem/ofono/master/test/list-contexts --output list-contexts-ofono.py then python3 list-contexts.py and post the output?
We have a reason to believe that this MMS issue is fixed on 4.5.0.19.
1 Like
This is fixed for me X10 III iff I disable mobile data.
Then I can send and receive. Otherwise it’s a no go.
So only via wifi? Is that what you mean by disabling mobile data?
@jovirkku More info on this, please! I’m very interested in getting outbound MMS working, but I didn’t notice anything in the xxx.19 release notes so I hadn’t rushed to do the upgrade.
Yes so I disable Mobila Data and the MMS functionality works.
The MMS Access Point is still valid.
I then re-enable Mobile Data for regular usage.
On 4.5.0.16 (January) we fixed the issue of “Manual MMS download is broken” which turned out to be a sandboxing error: the Messages app was lacking the MmsEngine permission. This Jolla bug was linked to [4.3.0.12] MMS works, but MMS retry fails, stays Waiting forever
Then there was another Jolla bug, “When receiving MMS, ‘Problem with downloading MMS’ is shown”, reported originally in this post which was linked to the Jolla bug. One of our developers was able to reproduce the issue while travelling in Lithuania. He was getting an “mms-task-http] HTTP status 7 (Connection terminated unexpectedly)”.
However, after upgrading to 4.5.0.16, the problem vanished and he was able to receive MMS messages.
From this, we concluded that the problem with downloading MMS was fixed.
But I failed to see that the problem in sending MMS was bundled into this same post. There was no particular fix for outbound messages. It would be best to make a new report on the remaining/current MMS problems here, using the OS release 4.5.0.19.
2 Likes
outbound messages actually worked FINE before this upgrade, when you could get the IPv6 routing to work right (otherwise, inbound/outbound both failed). outbound only STARTED failing (when inbound also worked) in SFOS 4.5.
this bug, Manual MMS download is broken, is definitely fixed in SFOS 4.5, but unfortunately MMS is now even less usable, because some folks cannot send MMS at all, ever.
2023-05-11 21:35:25 [mms-task-http] HTTP status 200 [application/vnd.wap.mms-message] 18 byte(s)
2023-05-11 21:35:25 [mms-task] Send[9091] TRANSMITTING -> DONE
2023-05-11 21:35:25 [mms-transfer-list] Transfer /msg/9091/Send finished
2023-05-11 21:35:25 [mms-task-send] ERROR: Missing Message-ID
i dont think anyone actually created a bug report for that part yet
T-Mo, USA. Looks like the last MMS I sent successfully was late january and first failure was Feb 2. That could have cirresponded to version update, I suppose. More recently, inbound MMS stopped downloading. This didn’t seem to be update related… Found accidentally they would download when on wifi with mobile data off.
This might have something to do with T-Mo having different VOLTE settings. I’ve changed my APC to Fast.t-mobile.com and MMS message center address to "http://mms.msg.eng.t-mobile.com/mms/wapenc
It still will look like it fails sending MMS, but will send it. Improvement over it not sending it at all anymore, but not ideal.
Any updates regarding Sony Xperia 10 III ans not being able to receive and send MMS messages? Issue started after updating Sauldish OS to, 4.5.0.19 or 4.5.0.18 .
T-Mobile service.
Thanx
1 Like
Hi. My MMS messaging has been working on T-Mo USA, both send and receive, on 10 III. My son’s 10 II has also been working. Our last successful MMS sends/receives were this past Saturday. Monday I was notified of someone trying to send me an MMS, but my 10 III couldn’t download it. Wednesday was the next attempt someone made to my phone, and it failed.
Yesterday I asked if my son’s MMS was working. He said it was the last he tried, which was Saturday. I tried sending one to him, and him to me. Neither worked.
I think something changed on Sunday or Monday.
Are there any other users who were working but who now, as of this week, cannot send or receive MMSes on T-Mobile USA with either 10 III or 10 II?
Try to change http in https, just to see if the operator has upgrade the protocol or with the https restart to work as usual.
10 II T-Mo USA. Last succesful MMS sent in January. I can receive, but only on wifi. Usually. occasionally one comes thru on mobile data. Iccasionally I even have to turn off mibile data onve I get home to download a message. Particularly annoying when peiole send me thise damn group textxs that come in by MMS and I tell them I’ll get back ehen I get home and download and decipher.
lotsa typos, sorry, narrow 10II screen and no autocorrypt on sfos firum…
Hello, thank you for your suggestion, I do not changing http to https had made a noticeable difference, issue of not sending nor receiving MMS is the same.
Perhaps Jolla should communicate with T-Mobile via their official channels to obtain any necessary setup that is required to enable a smooth transmission of MMS via their devices.
1 Like
You were lucky to have both Models, Xperia III and Xperia II to work, and MMS to function until last week. My Xperia II had been a peper weight device for more than a year since I absolutely cannot connect it with T-Mobile, or I think their resellers, in the US.
MMS working on GSM-T network on a 10ii. APN: pwg, Protocol: Dual, Authentication : None, Proxy address: 10.188.239.145, Proxy port: 80, MMSC: http://pwg.mmsmvno.com/mms/wapenc
1 Like
OK, hopefully someone else ends up also benefitting from this…
My MMS reception and my son’s have both been resolved…No changes on our devices. I called T-Mobile, told them that both our phones worked for years, and a few Mondays ago they stopped. It took quite a while to get through tier 1 tech support’s list o’ things to do, and ultimately she submitted a ticket for tier 2 to investigate.
I didn’t get contacted or notified that things were resolved. Oddly enough, it was a Monday when it stopped working and this past Monday when they started working. The first indication was a friend sent me a photo via MMS. Then I received a group text that I could actually download, open and read.
I then sent tests to and from my son’s phone and his worked, too.
I simply don’t know how much of this is on T-Mobile USA and how much is with Sailfish. But perhaps some others may have similar success.
1 Like
Thank you for sharing this experience with us; Perhaps the next logical step then is to contact T-Mobile support as you did.
I wonder if it is possible if you can somehow give them a call back, or so and inquire what T-Mobile support had done to resolve the issue, if you do still have the case number or ticket number.
With Red Pocket service; they would do a ‘reset’ on my phone number that is associated with my account to resolve previous issues. Of course, I am not sure what ‘reset’ entitles other than as if I just had obtained the phone number account.
Thank you