No MMS with Wifi ON
-
@Timespansoul MMS can't be sent when wifi connected to a hotspot and cellular data (SIM card) of the the Volla is off : seems normal to me.
When cellular data is on (SIM card) and wifi is on, but not connected to a hotspot, MMS sent and receive to myself. Works too when wifi connected to the hotspot as i said before.
-
@domubpkm said in No MMS with Wifi ON:
I send a MMS to myself with my focal Volla with wifi ON. it's ok.
Oh interesting, it does not work for me, only cellular data On only works... ( for the story, this is a reason why i've started to make "battery-saver", to not have to toggle Off wifi, wait and toggle On cellular data )
But indeed would be better if managed in the OS
-
@domubpkm I was quick to say it was sent via wifi because MMS needs data on to work.
I tested through hotspot with data off and MMS doesn't send.
Hotspot vai WiFi
Wifi ON/Data ON - MMS sends but is displayed as being sent from the number of the hotspot. MSS not received.WiFi ON/Data OFF - MMS fails. Which like you said makes sense.
Regular WiFi
WiFi ON/Data ON - MMS fails.
WiFi OFF/Data ON -MMS works correctly
These results are confusing. Different carriers, different devices etc..
One thing we can say is we're using the same OS and the same app.
Are you running just regular OTA?
It would be nice to know the difference in our setups. It might help pinpoint the issue.
-
@domubpkm I'm with Koodo and MMS over wifi is only part of prepaid plan. Who is your carrier and do they permit MMS over wifi?
(Just spitballing here)
-
@Timespansoul said in No MMS with Wifi ON:
Could you verify that it also works via Messaging app?
MessagingApp is basically just an app that reads/writes to a sqlite db. Everything about MMS (checking, downloading, storing into db) is done in background and is handled by more processes. So your question about Messaging app is kind of irrelevant. And yes, I used the Messaging app to see if the MMS message was successfully delivered.
I've already did some research and written somewhere about this already. If I recall correctly, I didn't find the cause, but narrowed it down to some package. Try to search this forum and/or gitlab/github.
-
In case it's useful, for me MMS has always sent and received independently of wifi being on or off. To make extra sure, I just tested on both Oneplus 5 (20.04 stable) and Oneplus 5T (16.04 stable). MMS sent and received with wifi on.
I didn't know about carriers offering MMS over wifi. I wonder if that could interfere somehow. My carrier offers "WiFi Calling" (including MMS), but lists it as not compatible with my device.
If it helps in your investigating, @timespansoul, I am on Freedom Mobile (Canada). I used to be on Public Mobile, which uses the Telus network just like Koodo does, and routinely sent and received MMS with wifi on (until earlier this year when Telus killed MMS altogether on older phones, which is another story and not UT specific).
Good luck! And thanks a million to all who've gotten MMS working as well as it does!
-
@wally Hi Wally. Thanks for the information. However I don't think it's the carrier seeing that the phone works fine on Android.
I've been chipping away at this and I may have made some progress.
I ran dbus-monitor with WIFI ON and I get the following errors:
signal time=1720759145.762483 sender=:1.125 -> destination=(null destination) serial=9 path=/com/lomiri/applications/upload/71ad36df33494b66932af165b0932c88; interface=com.lomiri.applications.Upload; member=networkError
struct {
int32 4
string "Socket operation timed out"
}
signal time=1720759145.762587 sender=:1.125 -> destination=(null destination) serial=10 path=/com/lomiri/applications/upload/71ad36df33494b66932af165b0932c88; interface=com.lomiri.applications.Upload; member=error
string ""
signal time=1720759145.764784 sender=:1.16 -> destination=(null destination) serial=78 path=/org/ofono/mms/302220038430713/2022a4829890738c364544eb5dd49edf; interface=org.ofono.mms.Message; member=PropertyChanged
string "Status"
variant string "TransientError"dbus-send gave me the ID of sender=:1.125 as lomiri.
So lomiri is timing out for some reason.
sender=:1.16 turns out to be nuntium which spits the string "TransientError"
Maybe someone can work with this info. I'll keep digging on my downtime.
I'm trying to find the string "Socket operation timed out" with no luck yet.
Time --Oneplus Nord N100--
-
@Timespansoul This is the output in question with Wifi OFF
signal time=1720756414.055570 sender=:1.116 -> destination=(null destination) serial=9 path=/com/lomiri/applications/upload/f27c482491d94ec6b866ba2ca6444cd4; interface=com.lomiri.applications.Upload; member=progress
uint64 16384
uint64 30988
signal time=1720756414.061558 sender=:1.116 -> destination=(null destination) serial=10 path=/com/lomiri/applications/upload/f27c482491d94ec6b866ba2ca6444cd4; interface=com.lomiri.applications.Upload; member=progress
uint64 30988
uint64 30988
signal time=1720756414.325241 sender=:1.116 -> destination=(null destination) serial=11 path=/com/lomiri/applications/upload/f27c482491d94ec6b866ba2ca6444cd4; interface=com.lomiri.applications.Upload; member=progress
uint64 0
uint64 0
signal time=1720756414.326396 sender=:1.116 -> destination=(null destination) serial=12 path=/com/lomiri/applications/upload/f27c482491d94ec6b866ba2ca6444cd4; interface=com.lomiri.applications.Upload; member=finished
string "/home/phablet/.local/share/lomiri-upload-manager/Downloads/9d38aa4fa57ee906f34e139da50acc4e.m-send.req.response"
signal time=1720756414.329149 sender=:1.16 -> destination=(null destination) serial=66 path=/org/ofono/mms/302220038430713/9d38aa4fa57ee906f34e139da50acc4e; interface=org.ofono.mms.Message; member=PropertyChanged
string "Status"
variant string "Sent"That's all I got for now.
-
@Timespansoul said in No MMS with Wifi ON:
@wally Hi Wally. Thanks for the information. However I don't think it's the carrier seeing that the phone works fine on Android.
I've been chipping away at this and I may have made some progress.
I ran dbus-monitor with WIFI ON and I get the following errors:
signal time=1720759145.762483 sender=:1.125 -> destination=(null destination) serial=9 path=/com/lomiri/applications/upload/71ad36df33494b66932af165b0932c88; interface=com.lomiri.applications.Upload; member=networkError
struct {
int32 4
string "Socket operation timed out"
}
signal time=1720759145.762587 sender=:1.125 -> destination=(null destination) serial=10 path=/com/lomiri/applications/upload/71ad36df33494b66932af165b0932c88; interface=com.lomiri.applications.Upload; member=error
string ""
signal time=1720759145.764784 sender=:1.16 -> destination=(null destination) serial=78 path=/org/ofono/mms/302220038430713/2022a4829890738c364544eb5dd49edf; interface=org.ofono.mms.Message; member=PropertyChanged
string "Status"
variant string "TransientError"dbus-send gave me the ID of sender=:1.125 as lomiri.
So lomiri is timing out for some reason.
sender=:1.16 turns out to be nuntium which spits the string "TransientError"
Maybe someone can work with this info. I'll keep digging on my downtime.
I'm trying to find the string "Socket operation timed out" with no luck yet.
Would be better imo if technical discussion appear in https://gitlab.com/ubports/development/core/packaging/ofono-sailfish/-/issues/13
-
@lduboeuf Thanks, I'll post it there as well.
