I’m using /e/ Q latest version (0.18-20210827132307) on my Galaxy A5 2017 (A5y17lte).
Since few weeks, i’ve got trouble sending MMS. Randomly, when sending MMS, they stay in “sending…” status and never got send. After a while (few minutes) they go in “sending fail, push to retry” status. If i retry, then it’s the same. I need to restart phone, then sending the MMS work again.
I don’t know if it can help but my girlfriend who is on LineageOS 17 with a Xiaomi Mi 9T (Davinci) has exactly the same behaviour. Sometimes it’s impossible for her to send MMS with the native app unless she restart her phone.
Empty the cache of the app is not helpful for both of us. We are both on ‘Orange’ network.
Any idea to solve this very annoying problem. I use MMS a lot and it happen almost everyday.
Are you using QKSMS (or /e/'s fork of it) as your primary messaging app? I’ve noticed that sometimes I can’t send a message unless the “Attachment Compression” is set to the default of 300k (annoying because it means I’m sending crap pictures to people, but I don’t think it impacts receiving).
A couple of weeks ago i tried to send a picture with the build in app. It was not sendt, so I hit the “retry” 2 times, no luck. Then I turned on the Wifi, and the picture and the text was sendt.
I wunder why.
I’m on a S9+ with /e/ preinstalled from e.foundation. Latest update 0.18-o-20210828132316-stable-star2lte
I speculate: carrier mmsc endpoints are cataloged at apns-conf.xml, to fetch an image in an mms you’ll need a data connection (wifi or mobile). I think what happens when people claim “sending mms without data connection” is the phone maker implemented some control messages that made the device turn on a connection and off again when sending/receiving an mms with encoded contents.
In my case, my data connection is always ON.
I’m currently testing Simple SMS during few days/weeks and i will get back here to update the thread with the results.
i thik, this problem occur only with pictures. I left Simple SMS as i don’t like the app. I’m currently testing QKSMS (the official version) and it “seems” to be OK for now. I will be checking it again during the next weeks and get back here.
In the thread you mention, they didn’t seem to find any solution for this problem.
I think with the original QKSMS app (which is also in a newer version i guess), the problem is gone. I will get back here in few weeks to confirm that.
May be /e/ team will update QKSMS fork in the next OTA…
But it has been open for a long time, and there is no indication of any plans to do anything about it. It is not in the list of issues allocated to v0.20
The latest version of QKSMS available in F-Droid is 3.9.4. I would strongly recommend using that rather than /e/’ Message app as your default messaging app, until /e/'s version gets updated
