MMS does not send nor download on T-Mobile on the Xperia 10 iii

General
#4

Please, can you share your MMS settings, and data access point settings, and other settings to have MMS work for T-Mobile on Sony 10 Xperia III, in the US?

MMS is not sending nor receiving on my phone.

Thanks

1 Like
#5

Connect name: T-mobile
Access point name: epc.tmobile.com
Protocol: Dual
Authentication: None
Proxy: 10.188.239.14
MMS message center address: http://10.188.239.145/mms/wapenc

2 Likes
#6

Trying these settings

#7

Same problem on my end.

#8

I have TMO US and my MMS works on 10iii

MMS settings:

Epc.tmobile.com
Protocol: IPv6

Authentication: none

Clear out all proxy info. Leave blank

Same MMS message center you already used.

Hope this helps

#9

Thank you, unfortunately that did not resolve the MMS not sending nor being recieved.

I tried these steps too from: Sailfish 4.4 T mobile network denied

# Make sure repositories point to right version
devel-su ssu re 4.4.0.58
devel-su ssu rr adaptation-common
devel-su -p pkcon refresh
devel-su -p pkcon install ofono-ril-binder-plugin
# Reboot device
devel-su -p version --dup

Sailfish OS 4.4.0.72
US T-Mobile

1 Like
#10

Could you install mmslogger, start it then attempt a mms send and receive? Post or pm the santitized log. On more than one occasion now, including one personally, the GSMT carrier (TMobile USA) and all their MVNO have sometimes not correctly provisioned new (port in service) and new (new msisdn) profiles. The result can be notices about ‘http status 7’ and ‘http status 12’ meaning unauthorized for mms (over wap) and unauthorized for data respectively.

1 Like
#11

I believe I recall seeing a status 12, but I am not certain. I found that with the settings shown on one of these emails I can download MMS, but still am unable to send it. I will try to get logs this evening.

#12 
Connect name: T-Mobile
Access point name: epc.tmobile.com
Protocol: IPv6
Authentication: None
Proxy: None
MMS message center address: http://10.188.239.145/mms/wapenc

With no proxy address worked on download…

2 Likes
#13

I missed a digit on the end of the proxy, would like to edit the original comment, but don’t know how.
Correct setting:
Proxy: 10.188.239.145

#14

With this I can download, however I cannot send </3

1 Like
#15

I’m in Aus with Vodafone and had the same issue. I’ve found a workaround now - When I disable mobile data access there is no problem sending nor receiving.
I reenable after

#16

can you send mms messages? this is the config that I’ve been using to download, but can’t send sadly.

#17

would you mind sharing your mms settings?

#18

Yes I can happily serve and receive when mobile data turned off.

APN live.vodafone.com
Protocol: IP
Authentication: PAP or CHAP
Proxy: 10.202.2.60
Port 8080
Message centre: http://pxt.vodafone.net.au/pxtsend

1 Like
#19

I have TMO USA and can both send and receive MMS messages on 10iii with 4.5.0.19 using settings from XOXO’s post with the last octet correction of 145 in the proxy address.

I recall having to call T-Mobile and them having to do something to my account to reset it, but it was an easy thing they did, reboit my phone and it’s worked since.

I have had group text convos where many messages come in rapid succession. Sometimes I’ll have a few stuck in “downloading” stage and never receive them. Sometimes I have received them days or weeks later, which had led to occasional awkward or comical situations due to losing original context.

Overall, MMS and SMS operations are usable for me.

2 Likes
#20

Lemme try that after I update

#22

How did it go for you?

#23

Hello @hackman238

Apologies for not supplying the MMS logs earlier.

These are the logs from mms-egine.log

Is this line relevant?

2024-04-24 15:24:51 [mms-task-send] ERROR: Missing Message-ID

Do note, that I had just replaced the T-Mobile SIM card with a new one, a fresh one that had been only used on the Sony Xperia 10 III at hand.

Also, on the same phone, I can receive media MMS, but I cannot send any media MMS.

Thank you

2024-04-24 15:24:19 [mms-engine] Version 1.0.81 starting
2024-04-24 15:24:19 [mms-engine] Attaching to system bus
2024-04-24 15:24:19 [dbusaccess] Parsing "1;group(privileged)=allow"
2024-04-24 15:24:19 [ofonoext] Bus connected
2024-04-24 15:24:19 [mms-engine] Bus acquired, starting...
2024-04-24 15:24:19 [ofonoext] Name 'org.ofono' is owned by :1.9
2024-04-24 15:24:19 [mms-engine] Acquired service name 'org.nemomobile.MmsEngine'
2024-04-24 15:24:19 [ofonoext] Interface version 8
2024-04-24 15:24:19 [mms-ofono] Modem '/ril_0'
2024-04-24 15:24:19 [mms-connman-nemo] Default SIM at /ril_0
2024-04-24 15:24:19 [mms-ofono] Name 'org.ofono' is owned by :1.9
2024-04-24 15:24:20 [mms-ofono] 2 modem(s) found
2024-04-24 15:24:20 [mms-ofono] SIM ril_0 is present
2024-04-24 15:24:49 [dbusaccess] Parsing /proc/6551/status
2024-04-24 15:24:49 [mms-attachment] /tmp/mms_obEIvB/mms2024-04-24T152419/msg/4258/encode/t-2-4_4937441879_o.gif: image/gif; name=t-2-4_4937441879_o.gif
2024-04-24 15:24:49 [mms-attachment] /tmp/mms_obEIvB/mms2024-04-24T152419/msg/4258/encode/2.txt: no conversion required
2024-04-24 15:24:49 [mms-attachment] /tmp/mms_obEIvB/mms2024-04-24T152419/msg/4258/encode/2.txt: text/plain; charset=utf-8; name=2.txt
2024-04-24 15:24:49 [mms-attachment] /tmp/mms_obEIvB/mms2024-04-24T152419/msg/4258/encode/smil: application/smil; charset=utf-8; name=smil
2024-04-24 15:24:49 [mms-dispatcher] Encode[4258] READY
2024-04-24 15:24:49 [mms-settings-dconf] Attaching to /imsi/310260313386119/mms/
2024-04-24 15:24:49 [mms-settings-dconf] max-message-size = 1048576
2024-04-24 15:24:49 [mms-task-encode] Created /tmp/mms_obEIvB/mms2024-04-24T152419/msg/4258/m-send.req (43527 bytes)
2024-04-24 15:24:49 [mms-task] Encode[4258] READY -> WORKING
2024-04-24 15:24:49 [mms-task] Encode[4258] WORKING -> DONE
2024-04-24 15:24:49 [mms-dispatcher] Encode[4258] DONE
2024-04-24 15:24:49 [mms-dispatcher] Send[4258] READY
2024-04-24 15:24:49 [mms-task] Send[4258] READY -> NEED_CONNECTION
2024-04-24 15:24:49 [mms-connection-nemo] MMS modem path /ril_0
2024-04-24 15:24:49 [mms-ofono] ril_0: not attached
2024-04-24 15:24:49 [mms-connection-nemo] MMS context /ril_0/context2
2024-04-24 15:24:49 [mms-connection-nemo] MessageProxy: 10.188.239.145
2024-04-24 15:24:49 [mms-connection-nemo] MessageCenter: http://10.188.239.145/mms/wapenc
2024-04-24 15:24:49 [mms-connection-nemo] Activate /ril_0/context2
2024-04-24 15:24:49 [mms-ofono] Activating /ril_0/context2
2024-04-24 15:24:49 [dbusaccess] Parsing /proc/7508/status
2024-04-24 15:24:50 [mms-ofono] Settings.Interface: rmnet_data2
2024-04-24 15:24:50 [mms-ofono] Settings.Method: static
2024-04-24 15:24:50 [mms-ofono] Settings.Address: xx.xx.202.31
2024-04-24 15:24:50 [mms-ofono] Settings.Netmask: 255.255.255.192
2024-04-24 15:24:50 [mms-ofono] Settings.Gateway: xx.xx.202.32
2024-04-24 15:24:50 [mms-ofono] Settings.DomainNameServers: 10.177.0.34 10.177.0.210
2024-04-24 15:24:50 [mms-ofono] Interface: rmnet_data2
2024-04-24 15:24:50 [mms-connection-nemo] Interface: rmnet_data2
2024-04-24 15:24:50 [mms-ofono] IPv6.Settings.Interface: rmnet_data2
2024-04-24 15:24:50 [mms-ofono] Context /ril_0/context2 is active
2024-04-24 15:24:50 [mms-connection-nemo] Connection 310260313386xxx opened
2024-04-24 15:24:50 [mms-dispatcher] 310260313386119 OPEN
2024-04-24 15:24:50 [mms-dispatcher] Send[4258] NEED_CONNECTION
2024-04-24 15:24:50 [mms-task-http] MMS interface address xx.xx.202.31
2024-04-24 15:24:50 [mms-task-http] MMS proxy 10.188.239.145
2024-04-24 15:24:50 [mms-task-http] /tmp/mms_obEIvB/mms2024-04-24T152419/msg/4258/m-send.req (43527 bytes) -> http://10.188.239.145/mms/wapenc -> /tmp/mms_obEIvB/mms2024-04-24T152419/msg/4258/m-send.conf
2024-04-24 15:24:50 [mms-transfer-list] Transfer /msg/4258/Send started
2024-04-24 15:24:50 [mms-task] Send[4258] NEED_CONNECTION -> TRANSMITTING
2024-04-24 15:24:50 [mms-ofono] Settings.Netmask: 255.255.255.255
2024-04-24 15:24:50 [mms-transfer-list] Update flags => 0x11
2024-04-24 15:24:50 [mms-ofono] IPv6.Settings.Address: xxxx:fb90:b720:cea8:e8ba:dea8:c583:5258
2024-04-24 15:24:50 [mms-ofono] IPv6.Settings.Gateway: xxxx:0000:0000:0000:10a1:d38c:f388:2f15
2024-04-24 15:24:50 [mms-ofono] IPv6.Settings.PrefixLength: 64
2024-04-24 15:24:50 [mms-ofono] IPv6.Settings.DomainNameServers: xxxx:976a:0000:0000:0000:0000:0000:0009 xxxx:976a:0000:0000:0000:0000:0000:0010
2024-04-24 15:24:51 [mms-task-http] HTTP status 200 [application/vnd.wap.mms-message] 18 byte(s)
2024-04-24 15:24:51 [mms-task] Send[4258] TRANSMITTING -> DONE
2024-04-24 15:24:51 [mms-transfer-list] Transfer /msg/4258/Send finished
2024-04-24 15:24:51 [mms-task-send] ERROR: Missing Message-ID
2024-04-24 15:24:51 [mms-dispatcher] Send[4258] DONE
2024-04-24 15:25:01 [mms-connection-nemo] Deactivate /ril_0/context2
2024-04-24 15:25:01 [mms-ofono] Deactivating /ril_0/context2
2024-04-24 15:25:01 [mms-ofono] IPv6.Settings.PrefixLength: 0
2024-04-24 15:25:01 [mms-ofono] Interface: <none>
2024-04-24 15:25:01 [mms-ofono] Context /ril_0/context2 is not active
2024-04-24 15:25:01 [mms-dispatcher] 310260313386119 CLOSED
2024-04-24 15:25:01 [mms-connection-nemo] Released /ril_0
2024-04-24 15:25:01 [mms-engine] All done
#24

i am also TMO in USA on 10III. i also cannot send MMS. receive works fine, but only when connected to wifi.
i suspect IPv6 issues. ive tried many combinations of settings/proxies/IPs/etc (10.188.239.158 seems to work best) and none have ever worked for me in 4.5.

however, mms send USED to work, before 4.5, but only OFF the wifi. (back then, there was the permanent-retry-failure bug, which was the worst, so this is at least better.)
…but reflashing 4.4 did not work, so something may have changed on T-Mobile’s side in the mean time.

as an aside, T-Mobile Digits works quite well in SFOS android-app-support with microg, and this is how i send the occasional MMS message when i have to.