MMS Does Not Send Nor Recieve On Sony 10 Xperia III & II With US T-Mobile & Red Pocket (Reseller)

[X0X0]

I have tried multiple Sony 10 Phones. Both Sony 10 Xperia II & III with Sailfish OS 4.4.72.

I had tried multiple combination for MMS Settings and Data Settings.

I have even tried copying other Sony and US T-Mobile users setups that are successful in having MMS sending and receiving, Like this setting:

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

2022-09-23 12:21:51 [mms-engine] Version 1.0.78 starting 2022-09-23 12:21:51 [mms-engine] Attaching to system bus 2022-09-23 12:21:51 [dbusaccess] Parsing “1;group(privileged)=allow” 2022-09-23 12:21:51 [ofonoext] Bus connected 2022-09-23 12:21:51 [mms-engine] Bus acquired, starting… 2022-09-23 12:21:51 [ofonoext] Name ‘org.ofono’ is owned by :1.11 2022-09-23 12:21:51 [mms-engine] ERROR: ‘org.nemomobile.MmsEngine’ service already running or access denied 2022-09-23 12:21:51 [mms-engine] E…

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

Also on the same page, a 2nd user with successful MMS transmission:

MMS settings:
Epc.tmobile.com
Protocol: IPv6
Authentication: none
Clear out all proxy info. Leave blank
Same MMS message center you already used.

And on my Sony 10 Xperia II, follwed these suggested setup from here:

VoLTE provider support

@robthebold @sa Please do the following: devel-su mkdir -p /vendor/oem/modem-config/S264.6/ mkdir -p /vendor/oem/modem-config/S264.8/ echo -n 'mcfg_sw/generic/euro/dtelekom/vlvw/de/mcfg_sw.mbn' > /vendor/oem/modem-config/S264.6/modem.conf echo -n 'mcfg_sw/generic/euro/dtelekom/vlvw/de/mcfg_sw.mbn' > /vendor/oem/modem-config/S264.8/modem.conf then reboot and enable 4g calling from the Cellular settings page. T-Mobile and US Mobile will register on the Xperia 10 II. Phone calls now work. SMS…

To get MMS working use the following:

**T-Mobile**

** MMS APN**
** Protocol: Dual (Important)**
** Proxy Address: 10.188.239.145**
** MMSC: http://10.188.239.145/mms/wapenc**
** Messages App → Settings → SMS Message Center Address: “+1206313004”,145**

** US Mobile**
** MMS APN**
** Protocol: Dual (Important)**
** Proxy Address: 10.188.239.145**
** MMSC: http://10.188.239.159/mms/wapenc**
** Messages App → Settings → SMS Message Center Address: “+1206313004”,145**

And for Red Pocket, too, I had tried these settings from the same page:

However, non of these setup works, even when I had to re-image Sony 10 Xperia II

Here are MMS logs from ‘mms-engine’:

Blockquote
022-10-16 10:21:56 [mms-engine] Version 1.0.78 starting
2022-10-16 10:21:56 [mms-engine] Attaching to system bus
2022-10-16 10:21:56 [dbusaccess] Parsing “1;group(privileged)=allow”
2022-10-16 10:21:56 [ofonoext] Bus connected
2022-10-16 10:21:56 [mms-engine] Bus acquired, starting…
2022-10-16 10:21:56 [ofonoext] Name ‘org.ofono’ is owned by :1.11
2022-10-16 10:21:56 [mms-engine] Acquired service name ‘org.nemomobile.MmsEngine’
2022-10-16 10:21:56 [ofonoext] Interface version 8
2022-10-16 10:21:56 [mms-ofono] Modem ‘/ril_0’
2022-10-16 10:21:56 [mms-connman-nemo] Default SIM at /ril_0
2022-10-16 10:21:57 [mms-ofono] Name ‘org.ofono’ is owned by :1.11
2022-10-16 10:21:57 [mms-ofono] 1 modem(s) found
2022-10-16 10:21:57 [mms-ofono] SIM ril_0 is present
2022-10-16 10:22:33 [dbusaccess] Parsing /proc/6441/status
2022-10-16 10:22:33 [mms-attachment] /tmp/mms_Cnx4Ym/mms2022-10-16T102156/msg/390/encode/Archipelago_of_Turku.jpg: image/jpeg; name=Archipelago_of_Turku.jpg
2022-10-16 10:22:33 [mms-attachment] /tmp/mms_Cnx4Ym/mms2022-10-16T102156/msg/390/encode/smil: application/smil; charset=utf-8; name=smil
2022-10-16 10:22:33 [mms-dispatcher] Encode[390] READY
2022-10-16 10:22:33 [mms-settings-dconf] Attaching to /imsi/310260544370145/mms/
2022-10-16 10:22:33 [mms-settings-dconf] max-message-size = 307200
2022-10-16 10:22:33 [mms-task-encode] Created /tmp/mms_Cnx4Ym/mms2022-10-16T102156/msg/390/m-send.req (1032369 bytes)
2022-10-16 10:22:33 [mms-task-encode] Message is too big, need to resize
2022-10-16 10:22:33 [mms-task-encode] Resizing /tmp/mms_Cnx4Ym/mms2022-10-16T102156/msg/390/encode/Archipelago_of_Turku.jpg
2022-10-16 10:22:33 [mms-attachment] Decoder-assisted resize (3072x2304 → 1536x1152)
2022-10-16 10:22:33 [mms-task] Encode[390] READY → WORKING
2022-10-16 10:22:33 [mms-attachment] Resized /tmp/mms_Cnx4Ym/mms2022-10-16T102156/msg/390/encode/convert/Archipelago_of_Turku.jpg
2022-10-16 10:22:33 [mms-task-encode] Created /tmp/mms_Cnx4Ym/mms2022-10-16T102156/msg/390/m-send.req (410703 bytes)
2022-10-16 10:22:33 [mms-task-encode] Message is too big, need to resize
2022-10-16 10:22:33 [mms-task-encode] Resizing /tmp/mms_Cnx4Ym/mms2022-10-16T102156/msg/390/encode/Archipelago_of_Turku.jpg
2022-10-16 10:22:33 [mms-attachment] Resizing (3072x2304 → 1024x768)
2022-10-16 10:22:33 [mms-attachment] Resized /tmp/mms_Cnx4Ym/mms2022-10-16T102156/msg/390/encode/convert/Archipelago_of_Turku.jpg
2022-10-16 10:22:33 [mms-task-encode] Created /tmp/mms_Cnx4Ym/mms2022-10-16T102156/msg/390/m-send.req (201977 bytes)
2022-10-16 10:22:33 [mms-task] Encode[390] WORKING → DONE
2022-10-16 10:22:33 [mms-dispatcher] Encode[390] DONE
2022-10-16 10:22:33 [mms-dispatcher] Send[390] READY
2022-10-16 10:22:33 [mms-task] Send[390] READY → NEED_CONNECTION
2022-10-16 10:22:33 [mms-connection-nemo] MMS modem path /ril_0
2022-10-16 10:22:33 [mms-ofono] ril_0: not attached
2022-10-16 10:22:33 [mms-connection-nemo] MMS context /ril_0/context2
2022-10-16 10:22:33 [mms-connection-nemo] MessageProxy: 10.188.239.14:8080
2022-10-16 10:22:33 [mms-connection-nemo] MessageCenter: http://10.188.239.145/mms/wapenc
2022-10-16 10:22:33 [mms-connection-nemo] Activate /ril_0/context2
2022-10-16 10:22:33 [mms-ofono] Activating /ril_0/context2
2022-10-16 10:22:34 [mms-ofono] Settings.Interface: rmnet_data3
2022-10-16 10:22:34 [mms-ofono] Settings.Method: static
2022-10-16 10:22:34 [mms-ofono] Settings.Address: 29.58.23.40
2022-10-16 10:22:34 [mms-ofono] Settings.Netmask: 255.255.255.240
2022-10-16 10:22:34 [mms-ofono] Settings.Gateway: 29.58.23.41
2022-10-16 10:22:34 [mms-ofono] Settings.DomainNameServers: 10.177.0.34 10.177.0.210
2022-10-16 10:22:34 [mms-ofono] Interface: rmnet_data3
2022-10-16 10:22:34 [mms-connection-nemo] Interface: rmnet_data3
2022-10-16 10:22:34 [mms-ofono] IPv6.Settings.Interface: rmnet_data3
2022-10-16 10:22:34 [mms-ofono] Context /ril_0/context2 is active
2022-10-16 10:22:34 [mms-connection-nemo] Connection 310260544370145 opened
2022-10-16 10:22:34 [mms-dispatcher] 310260544370145 OPEN
2022-10-16 10:22:34 [mms-dispatcher] Send[390] NEED_CONNECTION
2022-10-16 10:22:34 [mms-task-http] MMS interface address 29.58.23.40
2022-10-16 10:22:34 [mms-task-http] MMS proxy 10.188.239.14:8080
2022-10-16 10:22:34 [mms-task-http] /tmp/mms_Cnx4Ym/mms2022-10-16T102156/msg/390/m-send.req (201977 bytes) → http://10.188.239.145/mms/wapenc → /tmp/mms_Cnx4Ym/mms2022-10-16T102156/msg/390/m-send.conf
2022-10-16 10:22:34 [mms-transfer-list] Transfer /msg/390/Send started
2022-10-16 10:22:34 [mms-task] Send[390] NEED_CONNECTION → TRANSMITTING
2022-10-16 10:22:34 [mms-ofono] Settings.Netmask: 255.255.255.255
2022-10-16 10:22:34 [mms-ofono] IPv6.Settings.Address: 2607:fb90:7829:b7e0:3ca0:cb90:f4f5:2187
2022-10-16 10:22:34 [mms-ofono] IPv6.Settings.Gateway: fe80:0000:0000:0000:c405:22d5:343c:f52c
2022-10-16 10:22:34 [mms-ofono] IPv6.Settings.PrefixLength: 64
2022-10-16 10:22:34 [mms-ofono] IPv6.Settings.DomainNameServers: fd00:976a:0000:0000:0000:0000:0000:0009 fd00:976a:0000:0000:0000:0000:0000:0010
2022-10-16 10:22:41 [mms-task-http] HTTP status 7 (Connection terminated unexpectedly)
2022-10-16 10:22:41 [mms-task] Send[390] TRANSMITTING → SLEEP
2022-10-16 10:22:41 [mms-transfer-list] Transfer /msg/390/Send finished
2022-10-16 10:22:51 [mms-connection-nemo] Deactivate /ril_0/context2
2022-10-16 10:22:51 [mms-ofono] Deactivating /ril_0/context2
2022-10-16 10:22:51 [mms-ofono] IPv6.Settings.PrefixLength: 0
2022-10-16 10:22:51 [mms-ofono] Interface:
2022-10-16 10:22:51 [mms-ofono] Context /ril_0/context2 is not active
2022-10-16 10:22:51 [mms-dispatcher] 310260544370145 CLOSED
2022-10-16 10:22:51 [mms-connection-nemo] Released /ril_0
2022-10-16 10:22:56 [mms-task] Send[390] SLEEP → READY
2022-10-16 10:22:56 [mms-dispatcher] Send[390] READY
2022-10-16 10:22:56 [mms-task] Send[390] READY → NEED_CONNECTION
2022-10-16 10:22:56 [mms-connection-nemo] MMS modem path /ril_0
2022-10-16 10:22:56 [mms-connection-nemo] MMS context /ril_0/context2
2022-10-16 10:22:56 [mms-connection-nemo] MessageProxy: 10.188.239.14:8080
2022-10-16 10:22:56 [mms-connection-nemo] MessageCenter: http://10.188.239.145/mms/wapenc
2022-10-16 10:22:56 [mms-connection-nemo] Activate /ril_0/context2
2022-10-16 10:22:56 [mms-ofono] Activating /ril_0/context2
2022-10-16 10:22:57 [mms-ofono] Settings.Interface: rmnet_data1
2022-10-16 10:22:57 [mms-ofono] Settings.Method: static
2022-10-16 10:22:57 [mms-ofono] Settings.Address: 21.171.203.145
2022-10-16 10:22:57 [mms-ofono] Settings.Netmask: 255.255.255.252
2022-10-16 10:22:57 [mms-ofono] Settings.Gateway: 21.171.203.146
2022-10-16 10:22:57 [mms-ofono] Settings.DomainNameServers: 10.177.0.34 10.177.0.210
2022-10-16 10:22:57 [mms-ofono] Interface: rmnet_data1
2022-10-16 10:22:57 [mms-connection-nemo] Interface: rmnet_data1
2022-10-16 10:22:57 [mms-ofono] IPv6.Settings.Interface: rmnet_data1
2022-10-16 10:22:57 [mms-ofono] Context /ril_0/context2 is active
2022-10-16 10:22:57 [mms-connection-nemo] Connection 310260544370145 opened
2022-10-16 10:22:57 [mms-dispatcher] 310260544370145 OPEN
2022-10-16 10:22:57 [mms-dispatcher] Send[390] NEED_CONNECTION
2022-10-16 10:22:57 [mms-task-http] MMS interface address 21.171.203.145
2022-10-16 10:22:57 [mms-task-http] MMS proxy 10.188.239.14:8080
2022-10-16 10:22:57 [mms-task-http] /tmp/mms_Cnx4Ym/mms2022-10-16T102156/msg/390/m-send.req (201977 bytes) → http://10.188.239.145/mms/wapenc → /tmp/mms_Cnx4Ym/mms2022-10-16T102156/msg/390/m-send.conf
2022-10-16 10:22:57 [mms-transfer-list] Transfer /msg/390/Send started
2022-10-16 10:22:57 [mms-task] Send[390] NEED_CONNECTION → TRANSMITTING
2022-10-16 10:22:57 [mms-ofono] Settings.Netmask: 255.255.255.255
2022-10-16 10:22:57 [mms-ofono] IPv6.Settings.Address: 2607:fb90:82ab:8c30:7115:6f1b:4bf1:d2d9
2022-10-16 10:22:57 [mms-ofono] IPv6.Settings.Gateway: fe80:0000:0000:0000:5499:d3dd:e9b9:dbc9
2022-10-16 10:22:57 [mms-ofono] IPv6.Settings.PrefixLength: 64
2022-10-16 10:22:57 [mms-ofono] IPv6.Settings.DomainNameServers: fd00:976a:0000:0000:0000:0000:0000:0009 fd00:976a:0000:0000:0000:0000:0000:0010
2022-10-16 10:23:03 [dbusaccess] Name ‘:1.104’ timed out
2022-10-16 10:23:04 [mms-task-http] HTTP status 7 (Connection terminated unexpectedly)
2022-10-16 10:23:04 [mms-task] Send[390] TRANSMITTING → SLEEP
2022-10-16 10:23:04 [mms-transfer-list] Transfer /msg/390/Send finished
2022-10-16 10:23:14 [mms-connection-nemo] Deactivate /ril_0/context2
2022-10-16 10:23:14 [mms-ofono] Deactivating /ril_0/context2
2022-10-16 10:23:14 [mms-ofono] IPv6.Settings.PrefixLength: 0
2022-10-16 10:23:14 [mms-ofono] Interface:
2022-10-16 10:23:14 [mms-ofono] Context /ril_0/context2 is not active
2022-10-16 10:23:14 [mms-dispatcher] 310260544370145 CLOSED
2022-10-16 10:23:14 [mms-connection-nemo] Released /ril_0
2022-10-16 10:23:19 [mms-task] Send[390] SLEEP → READY
2022-10-16 10:23:19 [mms-dispatcher] Send[390] READY
2022-10-16 10:23:19 [mms-task] Send[390] READY → NEED_CONNECTION
2022-10-16 10:23:19 [mms-connection-nemo] MMS modem path /ril_0
2022-10-16 10:23:19 [mms-connection-nemo] MMS context /ril_0/context2
2022-10-16 10:23:19 [mms-connection-nemo] MessageProxy: 10.188.239.14:8080
2022-10-16 10:23:19 [mms-connection-nemo] MessageCenter: http://10.188.239.145/mms/wapenc
2022-10-16 10:23:19 [mms-connection-nemo] Activate /ril_0/context2
2022-10-16 10:23:19 [mms-ofono] Activating /ril_0/context2
2022-10-16 10:23:20 [mms-ofono] Settings.Interface: rmnet_data3
2022-10-16 10:23:20 [mms-ofono] Settings.Method: static
2022-10-16 10:23:20 [mms-ofono] Settings.Address: 21.171.203.145
2022-10-16 10:23:20 [mms-ofono] Settings.Netmask: 255.255.255.252
2022-10-16 10:23:20 [mms-ofono] Settings.Gateway: 21.171.203.146
2022-10-16 10:23:20 [mms-ofono] Settings.DomainNameServers: 10.177.0.34 10.177.0.210
2022-10-16 10:23:20 [mms-ofono] Interface: rmnet_data3
2022-10-16 10:23:20 [mms-connection-nemo] Interface: rmnet_data3
2022-10-16 10:23:20 [mms-ofono] IPv6.Settings.Interface: rmnet_data3
2022-10-16 10:23:20 [mms-ofono] Context /ril_0/context2 is active
2022-10-16 10:23:20 [mms-connection-nemo] Connection 310260544370145 opened
2022-10-16 10:23:20 [mms-dispatcher] 310260544370145 OPEN
2022-10-16 10:23:20 [mms-dispatcher] Send[390] NEED_CONNECTION
2022-10-16 10:23:20 [mms-task-http] MMS interface address 21.171.203.145
2022-10-16 10:23:20 [mms-task-http] MMS proxy 10.188.239.14:8080
2022-10-16 10:23:20 [mms-task-http] /tmp/mms_Cnx4Ym/mms2022-10-16T102156/msg/390/m-send.req (201977 bytes) → http://10.188.239.145/mms/wapenc → /tmp/mms_Cnx4Ym/mms2022-10-16T102156/msg/390/m-send.conf
2022-10-16 10:23:20 [mms-transfer-list] Transfer /msg/390/Send started
2022-10-16 10:23:20 [mms-task] Send[390] NEED_CONNECTION → TRANSMITTING
2022-10-16 10:23:20 [mms-ofono] Settings.Netmask: 255.255.255.255
2022-10-16 10:23:20 [mms-ofono] IPv6.Settings.Address: 2607:fb90:82bc:8c94:3ca0:cb90:f4f5:2187
2022-10-16 10:23:20 [mms-ofono] IPv6.Settings.Gateway: fe80:0000:0000:0000:8511:57e8:5315:6156
2022-10-16 10:23:20 [mms-ofono] IPv6.Settings.PrefixLength: 64
2022-10-16 10:23:20 [mms-ofono] IPv6.Settings.DomainNameServers: fd00:976a:0000:0000:0000:0000:0000:0009 fd00:976a:0000:0000:0000:0000:0000:0010
2022-10-16 10:23:27 [mms-task-http] HTTP status 7 (Connection terminated unexpectedly)
2022-10-16 10:23:27 [mms-task] Send[390] TRANSMITTING → SLEEP
2022-10-16 10:23:27 [mms-transfer-list] Transfer /msg/390/Send finished
2022-10-16 10:23:37 [mms-connection-nemo] Deactivate /ril_0/context2
2022-10-16 10:23:37 [mms-ofono] Deactivating /ril_0/context2
2022-10-16 10:23:37 [mms-ofono] IPv6.Settings.PrefixLength: 0
2022-10-16 10:23:37 [mms-ofono] Interface:
2022-10-16 10:23:37 [mms-ofono] Context /ril_0/context2 is not active
2022-10-16 10:23:37 [mms-dispatcher] 310260544370145 CLOSED
2022-10-16 10:23:37 [mms-connection-nemo] Released /ril_0
2022-10-16 10:23:42 [mms-task] Send[390] SLEEP → READY
2022-10-16 10:23:42 [mms-dispatcher] Send[390] READY
2022-10-16 10:23:42 [mms-task] Send[390] READY → NEED_CONNECTION
2022-10-16 10:23:42 [mms-connection-nemo] MMS modem path /ril_0
2022-10-16 10:23:42 [mms-connection-nemo] MMS context /ril_0/context2
2022-10-16 10:23:42 [mms-connection-nemo] MessageProxy: 10.188.239.14:8080
2022-10-16 10:23:42 [mms-connection-nemo] MessageCenter: http://10.188.239.145/mms/wapenc
2022-10-16 10:23:42 [mms-connection-nemo] Activate /ril_0/context2
2022-10-16 10:23:42 [mms-ofono] Activating /ril_0/context2
2022-10-16 10:23:43 [mms-ofono] Settings.Interface: rmnet_data1
2022-10-16 10:23:43 [mms-ofono] Settings.Method: static
2022-10-16 10:23:43 [mms-ofono] Settings.Address: 21.171.203.145
2022-10-16 10:23:43 [mms-ofono] Settings.Netmask: 255.255.255.252
2022-10-16 10:23:43 [mms-ofono] Settings.Gateway: 21.171.203.146
2022-10-16 10:23:43 [mms-ofono] Settings.DomainNameServers: 10.177.0.34 10.177.0.210
2022-10-16 10:23:43 [mms-ofono] Interface: rmnet_data1
2022-10-16 10:23:43 [mms-connection-nemo] Interface: rmnet_data1
2022-10-16 10:23:43 [mms-ofono] IPv6.Settings.Interface: rmnet_data1
2022-10-16 10:23:43 [mms-ofono] Context /ril_0/context2 is active
2022-10-16 10:23:43 [mms-connection-nemo] Connection 310260544370145 opened
2022-10-16 10:23:43 [mms-dispatcher] 310260544370145 OPEN
2022-10-16 10:23:43 [mms-dispatcher] Send[390] NEED_CONNECTION
2022-10-16 10:23:43 [mms-task-http] MMS interface address 21.171.203.145
2022-10-16 10:23:43 [mms-task-http] MMS proxy 10.188.239.14:8080
2022-10-16 10:23:43 [mms-task-http] /tmp/mms_Cnx4Ym/mms2022-10-16T102156/msg/390/m-send.req (201977 bytes) → http://10.188.239.145/mms/wapenc → /tmp/mms_Cnx4Ym/mms2022-10-16T102156/msg/390/m-send.conf
2022-10-16 10:23:43 [mms-transfer-list] Transfer /msg/390/Send started
2022-10-16 10:23:43 [mms-task] Send[390] NEED_CONNECTION → TRANSMITTING
2022-10-16 10:23:43 [mms-ofono] Settings.Netmask: 255.255.255.255
2022-10-16 10:23:43 [mms-ofono] IPv6.Settings.Address: 2607:fb90:82bf:639c:7115:6f1b:4bf1:d2d9
2022-10-16 10:23:43 [mms-ofono] IPv6.Settings.Gateway: fe80:0000:0000:0000:f8dd:5675:8f86:6437
2022-10-16 10:23:43 [mms-ofono] IPv6.Settings.PrefixLength: 64
2022-10-16 10:23:43 [mms-ofono] IPv6.Settings.DomainNameServers: fd00:976a:0000:0000:0000:0000:0000:0009 fd00:976a:0000:0000:0000:0000:0000:0010
2022-10-16 10:23:50 [mms-task-http] HTTP status 7 (Connection terminated unexpectedly)
2022-10-16 10:23:50 [mms-task] Send[390] TRANSMITTING → SLEEP
2022-10-16 10:23:50 [mms-transfer-list] Transfer /msg/390/Send finished
2022-10-16 10:24:00 [mms-connection-nemo] Deactivate /ril_0/context2
2022-10-16 10:24:00 [mms-ofono] Deactivating /ril_0/context2

Blockquote
If more information is needed, or logs, I am more than happy to work with one of SailfishOS engineers.

Thank you

[X0X0]

I have tried Red Mobile SIM (T-Mobile US) on PinePhone Pro yesterday; and I am amazed how swift the PinePhone Pro imaged with “Developer Release 202210180430” Manjaro ARM, Plasma Moblie, was able to Send and Receive MMS messages (source pictures from the camera).

What is causing SailfishOS on my both Sony 10 Xperia II and III not to do so?

I don’t think it is a carrier issues as much it is Sailfish OS.

Regards

[Ras72]

I saw something about message being too large.

I set my message size to “extra large”. Perhaps that’s something that can help you?

[hackman238]

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?

[jovirkku]

We have a reason to believe that this MMS issue is fixed on 4.5.0.19.

[lakeboy]

This is fixed for me X10 III iff I disable mobile data.
Then I can send and receive. Otherwise it’s a no go.

[svalmont]

So only via wifi? Is that what you mean by disabling mobile data?

[robthebold]

@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.

[lakeboy]

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.

[jovirkku]

@jovirkku

We have a reason to believe that this MMS issue is fixed on 4.5.0.19.

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.

[teleshoes]

@jovirkku

There was no particular fix for outbound messages.

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

[robthebold]

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.

[svalmont]

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.

[X0X0]

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

[Ras72]

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?

[robang74]

@X0X0

MMS message center address: http://10.188.239.145/mms/wapenc

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.

[robthebold]

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…

[X0X0]

@robang74

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.

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.

[X0X0]

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.

[X0X0]

@Ras72

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?

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.