MMS users: call for testing
-
For the use case "cellular data off", it is working nicely except when i'm with bad signal ( see issue above ) .
This is already a huge step for MMS users, in its worst case scenario we will have the same state as it is today on Devel/RC/Stable ( just ask user to resend)
-
@lduboeuf said in MMS users: call for testing:
For the use case "cellular data off", it is working nicely except when i'm with bad signal ( see issue above ) .
This is already a huge step for MMS users, in its worst case scenario we will have the same state as it is today on Devel/RC/Stable ( just ask user to resend)I think it is not a showstopper for deploying to next OTA. It's working better than before and there are no regressions. Also it will motivate me more to fix the bad signal issues, when the changes land to stable.
I will definitely tackle the issues, but I had to change my HW and installed manjaro on it and now I have a little fight with crossbuilderand the lack ofaptanddpkg[-architecture,-parsechangelog]commands on the system.Thank you all for support.
-
I've discovered, that the patches are already in RC, so if you are on RC channel (and dev channel too), there is no need to apply the above mentionedubports-qacommands. This also means that the patches will probably be in the next OTA. Just saying. I'm happy. Thank you all.I've been wrong. Read furher, why.
jEzEk
-
-
@jezek humm i probably miss something, i don't see the PR already merged
-
@lduboeuf Or am I wrong? Is there a possibility that the patch is not in RC (and dev) and the applied
ubports-qachanges persisted 2 RC upgrades and I drew a bad conclusion? Can anyone answer this conundrum, or do I have to do full reinstall to check? -
I'm not 100% sure, but debian packages could be not totally overwritten. I already noticed that when working on Lomiri, where RC or devel updates didn't overwrites my modified files. It would overwrite it though if the same file was modified.
-
So I red the OTA-19 call for testing and after browsing though the github QA page I have come to the conclusion, that I've been definitely wrong about the patch landing in RC and maybe in OTA-19 update.
I'm sorry for putting your (and my) hopes up. Maybe next time.Does anyone know how to be in the next OTA update?
jEzEk
-
Does anyone know how to be in the next OTA update?
idk, maybe @UniSuperBox or @Flohack can say ?
-
@jezek said in MMS users: call for testing:
Does anyone know how to be in the next OTA update?
Very sad you're not in OTA 19 as MMS is one of smartphones key features regarding phone part...
-
Well there is always a next OTA
If you want to make sure your stuff is in, best is at the beginning of a cycle to drive this topic forward. We have reduced personnel these days, its easy that stuff slips...My languages: 🇦🇹 🇩🇪 🇬🇧 🇺🇸
-
@jezek Such your personal investment in the essential MMS reliability mechanism
is worth this very usefull nechanism be incorporating as soon as possible. -
-
@flohack said in MMS users: call for testing:
Well there is always a next OTA
If you want to make sure your stuff is in, best is at the beginning of a cycle to drive this topic forward. We have reduced personnel these days, its easy that stuff slips...OK, the OTA-20 cycle starts around these days. Where to push, to land the MMS patch in OTA-20? Thanks.
-
-
@flohack the initial issue ( amongst others ) is here:
https://github.com/ubports/ubuntu-touch/issues/17The top related PR is in messaging-app https://github.com/ubports/messaging-app/pull/260 and you can see other pre-required
PRs in the comment in the correct order.[Edit]:
Well the very first issue post is here https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1603957
I think you can add it to your tweet :)...
That time please thanks @jezek -
Hey everyone, I am confused at the state of this? In my Pixel 3a XL MMS is working if wifi is off and if NOT a group MMS. So this is good, but I don't remember if that is due to @fredldotme incorporating the fixes only for the P3a or if it is in "mainstream" UT Dev / RC / Stable?
I am wondering about the status of these patches first.
Then I would like to start at least looking at the issue of needing wifi to be OFF for MMS to work. My thought would be try and determine how we could "force" MMS to always use the cellular data connection and "ignore" wifi. For me this seems like a better beginning point than currently where MMS will fail if wifi is enabled. Would I look into ofono or nuntium or other for this? If anyone had a link to the existing issue report for this it is a good start. Pointers? I can also add this to a new thread if it is best.
-
@rik Yes, that is another story and better on another topic.
From what i understand, nuntium call lomiri-download-manager ( https://github.com/ubports/nuntium/blob/b182b1a4ff41910dd3d1a4b064df2f56505be923/mms/download.go#L34 )
see project https://gitlab.com/ubports/core/lomiri-download-manager
But i don't get where we can force using cellular data instead of wifi -
Why do we need cellular data instead of using any kind of internet connection (other SIM or wifi) for fetching the content of the MMS? Is there a special reason why?
In my case my main SIM-card does not have a mobile-data-volume, for this I have a second SIM-card in my E4.5. So I'm using only the second card for internet-connection or wifi at home. From this point of view it's not possible for me to receive a MMS.
If I remember it right, on my old Nokia's the was no need of a mobile-data-volume or a datapass. If there was an incoming MMS the phone build up a internet-connection only for downloading the content of the MMS and then stopped the connection. There was no payment needed for this kind of connection (AFAIR). -
@kristatos This is because the Multimedia Messaging Service protocol is processed by the operator via cellular data.
It is not possible to handle mms via WiFi currently on Ubuntu Touch without VoWiFi relay.
Maybe this will be the case in the future...(?)
