No MMS with Wifi ON
-
@Timespansoul said in No MMS with Wifi ON:
@lduboeuf If this is a global issue shouldn't it be mentioned on the ubports website in the Global issues section? To claim that MMS in/out is working properly is a bit misleading.
It "should" yes. The thing is that MMS has never been a priority on UT since most core developpers never use it. In many countries MMS is over priced and never been widely used.
Remember 3 years ago, MMS where even lost if you were not on 4G....A thing that can be done is to notify user in messaging-app that cellular data must be On when trying to send or receive a MMS content.
Could you file an issue on messaging-app repo ?:https://gitlab.com/ubports/development/core/messaging-app/-/issues
Which version of oFono is Focal running?
We use ofono from Sailfish os fork.
Am I correct in saying that ofono is the issue? Does ofono need a fork for Touch?
I'm having a hard time finding the info that explains who is supposed to toggle the interface, ofono or nuntium?
I found this chart that helped me better understand Nuntium's role:
https://github.com/ubports/nuntium/blob/xenial/docs/architecture.md
Most of the articles I'm finding are quite dated.
I guess the main question is which layer is supposed to toggle the interface?
I don't know precisely, but probably nuntium, ofono and maybe network manager.
see https://gitlab.com/ubports/development/core/packaging/ofono-sailfish/-/issues/13Don't hesitate to add comment there.
-
@lduboeuf said in No MMS with Wifi ON:
The thing is that MMS has never been a priority on UT since most core developpers never use it.
Well, SMS, then MMS is part of the basics with mobile phones features.
UT is designed for "normal" people, so Devs should consider basic features like kind of mandatory to support, I think.MMS always worked for me since I have my MX4 in 2015, and I would definitely not be on UT if they weren't.
-
@Keneda I agree, it should be part of basic feature of a phone. But expectef things can be very complex to do.
I'm also concerned about that and was very surprised the first time i've used UT that MMS were lost since the beginning of UT if not on cellular data.
Thanks to @jezek and @peat_psuwit it is now more reliable -
@lduboeuf
You three greatly improved messaging in UT
PS : some typos in your post ^^
-
Thanks for all the work the everyone put into this and is putting into this. Adding the ability to redownload makes it semi-functional. Good work.
The more I research the more complicated it seems to get. There is documentation of this issue in iOS, Android, Ubuntu, Sailfish and possibly more.
Depending on the circumstances the issue was solved with an update, a downgrade, a setting in the messages app, calling the carrier, certain developer settings toggled on, or writing a fork haha. In many cases it wasn't solved at all and turning off wifi has become the accepted usage.
I mean, I'll agree that this is a basic feature and should work, but this is happening across the board for different reasons, making this very complicated and leading to the possibility there is no "one solution". So it's hard to blame UB for this. Especially when you consider that there are juggernauts who are worth billions not addressing the issue either haha.
There may be some compatibility issue? All I know is the more you know the less confusing it gets. Or is it the more you know the more you don't know? haha. I will continue to investigate.
-
Hello, I must oppose the claim that receiving MMS message is not possible while WiFi on is a global issue.
At least on FP2, which still runs xenial UT, I can receive MMS message, when WiFi on. Just tested it right now. Turned on WiFi & mobile data, telegramed someone to send me a MMS message and received the message without problem.
jEzEk
-
I send a MMS to myself with my focal Volla with wifi ON. it's ok.
-
@jezek This is interesting. Could you verify that it also works via Messaging app?
Edit: Great work by the way. Thanks for adding the downloading feature.
Time --Oneplus Nord N100--
-
@domubpkm Which app are you using?
-
@Timespansoul messaging app using wifi connected to an hotspot.
-
@domubpkm Interesting.
So I created a hotspot on another phone.
I connected to hotspot and these are my results.
Wifi ON - MMS message sends however it's received as a message from the phone number of the hotspot. So that means the message sent via wifi ultimately using data from another device. This is not what we want. We want data to be the preffered interface for mms messages.
Wifi OFF - MMS is not received.
Could I suggest that you perform the test under the same conditions? Wifi ON Data ON, no hotspot. This information will help.
Also can you receive MMS with hotspot?
In any case ip route states that wifi is the prefferred interface. With wifi off MMS works flawlessly. It circles back to the question, what is the mechanism that toggles this when an MMS message is sent?
-
@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
