Open gbdomubpkm opened 3 years ago
I can confirm this issue on Development channel build 2021-02-22 as well, MMS receiving works fine, but trying to send MMS just shows the following log in ~/.cache/upstart/nuntium.log
:
2021/02/27 14:15:22 cannot create new ContentType for image20210225_031829661.jpg of content type image/jpeg on : open : no such file or directory
Looking at the related code of nuntium it appears filePath
for the attachment is empty for some reason; I've brought this up in the UBports development group.
Also this might be new generic issue tracked on upstream @ https://github.com/ubports/ubuntu-touch/issues/1670.
Did you check the APN settings for MMS? This works fine for me with OTA 15 Stable
@wurser You have probably right (but i didn't test) for OTA-15 as it's about RC and DEV currently. But if the problem isn't fixed, you could reproduce for OTA-16, probably.. 😉
@UniversalSuperBox Thank you so much for the fix. I could test it in RC 10.
@UniversalSuperBox Sorry to say that but it doesn't work for me in RC 10 yet. But there is a progress : it says failure after the spinning wheel ! Same thing for little audio or picture file. I tried to send to myself or somebody else.
Edit : i confirm that the issue occurs too on the stable channel OTA-15 for me.
I was able to send an MMS message succesfully under Development channel build 2021-03-04, so I'll go ahead and close this now :) @gbdomubpkm's issue appears to be something else as it also happens on OTA-15 and I'm working with them directly to attempt resolving this.
@UniversalSuperBox
For info as it could be useful for you : RC 10 : my operator (and why not others!): the MMS context cannot be activated (shown in nuntium log)
Precision: it is ONLY the command line usr/share/ofono.. that allows me to have the internet (this line does not activate the MMS APN, alas as said, even if the parameters are shown as good and I check the MMS APN box).
I say ONLY because, if I put some nonsense in the APN's internet settings once the internet is activated, the internet will still work, checkbox checked or not.
And thanks again to @JamiKettunen for all the answers he gives me to THE problems I bring to him !!
OTA-16: no MMS confirmed alas. This is the black spot as MMS is a fundamental (for me).
I use MMS successfully on my Ubuntu Touch device with OTA 15 of the stable channel. Please check your APN settings. You can type "MMS" on our help page at https://volla.online/en/faqs/ In some cases a reboot is necessary to get the MMS feature working
The problem is real, and was identified by @NotKit on March 25 using the logcat_radio.txt that I provided him and captured during the error sending an MMS. No info since.
We need to be very precise to find a solution.
I can confirm, That cellular data connection is working as soon your SIM is activated in a Volla Phone with Ubuntu Touch OTA-16 (stable channel). I some cases you need to enter the APN setting for internet and MMS yourself.
If the APN settings are not working instantly, you may need to reboot. Then you can send and receive MMS.
We need to find our, what's different on your device.
We need to find our, what's different to your and my conditions on the Volla Phone.
Hello @wurzer At my level all the obvious settings and what is possible has already been tested for a long time. As already shown above, the MMS context cannot be activated (even if it seems to be set up in appearance).
So much the better if the MMS works for a majority of SIM categories and if the MMS works with your SIM.
As far as the SIM I own is concerned, I can confirm that MMS does not work on the STABLE channel, nor on the RC 13 channel tested today.
This is not a problem of my own SIM, but probably related to a category of SIM for which MMS does not currently work on the Volla (or on some Halium 9 devices ? I don't know).
NotKit will be able to confirm and enlighten you better than me on the nature of the malfunction(s) that I do not know exactly even if i gave him the logcat_radio.txt file referencing the MMS Error.
Hello @wurzer At my level all the obvious settings and what is possible has already been tested for a long time. As already shown above, the MMS context cannot be activated (even if it seems to be set up in appearance).
In which country are you located and which carrier do you use?
It is written at the beginning.... Bouygues SIM France
This annoying at this day unresolved issue is no more personal than other currently open bug reports do. This issue should be reopened (i can't do myself) as long as the situation remains as it is.
I can understand, that missing MMS feature is a critical issue. The challenge for my colleagues and me is, that we can't reproduce this issue. I can send and receive MMS with the correct APN settings. I assume, that we need a sIM of your carrier in this specific french network to reproduce the problem. We might need your ofono log or a community developer, who is able to reproduce the problem. Are you familiar with Ubuntu Touch logging?
Already mentioned: different logs have already been communicated. I couldn't do more. Only test a solution by being guided step by step if necessary. I am not a developer.
My current understanding of the problem is that particular carrier uses a single APN for both internet context and MMS (mmsbouygtel.com). Older ofono version used on Nexus 5 and other pre-Android 9 devices allowed to configure Internet + MMS type APN, but SailfishOS fork of ofono we use instead has hardcoded assumptions about there being a single APN context for internet and a separate one for MMS.
@gbdomubpkm also tried to configure separate different APNs for internet and MMS, but second context activation still fails on Volla Phone in this case. I suspect carrier may allow only one active context in this case, and older devices may workaround it by shortly disconnecting from Internet context.
I need to look more into ofono code we use to see if the assumption about contexts can be removed. If yes, this should also fix the problem we have with adding/removing contexts from Ubuntu Touch Settings UI.
Finally and after many tests, with a different APN for INTERNET (ebougtel.com) and for MMS (mmsbouygtel.com) and by activating (by linux command line) after each reboot of the Volla the context 2 MMS by being at the beginning on the type of connection 2g/3g with a 3g connection, then by going on the type of connection 2g/3g/4g with the 4g connection and by reactivating again the context 2 MMS, the MMS function work in 4g in the limit of this procedure and other limits.. It's a far from a perfect solution or a normal fix but better than nothing currently.
I can confirm, that I also can use two SIM cards:
It took indeed at least one reboot to have the setting properly working.
Hello. Any progress in solving the problem?
MMS works fine for most carrier and use cases.
Only two issues are known:
We are working on both issues.
In any case I strongly recommend, not to use command line tools to configure network access but only the system setting sof Ubuntu Touch.
Hi, would it be possible for you also to test the following steps I sent on this comment?
Thanks!
Hello @Pekkari I took some times because i did some tests. I installed PR-28 directly with the phone on OTA-19.
BUT i have good news 🙂. It works !
I managed to activate a single APN (internet + mms) by modifying a proposed APN after reboot, but not automatically as you thought.
The single APN is retained after reboot, which is also good news.
I don't have any more MMS context disabling if I activate flight mode and then deactivate it, or after a reboot.
I had trouble activating cellular data (internet) 'connection types' 2G and 2G/3G but in fact it seems to work and so does MMS.
It now seems possible to delete unnecessary APNs which is good news even if they tend to reappear (but not activate) after a reboot.
@NotKit and you did good work 👍👋
If i see something new, i will tell you.
Very good, thanks for the testing, and the patience. I'm certain we'll work in improving the apn area of system settings, and we'll certainly work in upstreaming those changes to ubports to let you have them later on through OTA instead of ubports-qa.
Yes. Ideally an update for OTA-20 would be nice. What would happen if I switched to RC 34 ?. Would I lose the PR? But i wouldn't do it because RC-34 was 'morph' buggy for me on the volla 😉
I highly recommend to keep the stable channel. other channels are automatically triggered build, which could contain errors. These builds are for developers and beta testers.
We expect hte OTA-20 update next month at least this year.
Hi @gbdomubpkm the solution to this problem only refers to ofono, there is no change in the indicators or the systems settings in any way, so I may suggest you open a different case for that so that we can analyse it for you. I haven't personally used the application side quite much, but I don't have any problem in doing some tests on my own. Please refer me the ticket you opened for it, and I'll put some thoughts.
@Pekkari Thank you for your answer. I'm not sure as i didn't get a clear answer on the forum https://forums.ubports.com/topic/6797/dekko-no-sound-notifications-with-ota-19/8 , but maybe it's a known issue not yet solved until OTA-19 for Halium 9 or 10 devices , as i have also no SOUND notification for Teleports. That's why i didn't open a new official issue somewhere for the problem i raised. My digression is over here 😉
Hello @Pekkari I'm always un OTA-19 currently. Is the mechanism included (finalized) in RC test OTA-20 ?
I'm afraid no, I'm on a sick leave, I can't work for now on this.
Okay. I was right to ask. First, I wish you a very good recovery. Will your actual MMS command line procedure work well on OTA-20 ? As it is, I see no point in switching to OTA-20. OTA-19 works very well as it is and is in balance. Webgl also works very well. I hope that this mechanism will be present on OTA-21.
I think your problem is related to the case, that the APN settings of network and MMS are the same. We are working on that issue, but it's not ready for a pull request, yet. I'm confident to have solution for OTA-21 this year. We already have a solution, but it's not stable yet.
Correct, and currently the tested solution doesn't work well, since I introduced code to skip creation of mms context, that currently crashes ofono, so I have to recommend to stay in the current setup until I can come up to this. Thanks for the recovery wishes!
Hello @wurzer. As i said before in my comments, https://github.com/ubports/ofono/pull/28 works well with OTA-19, that's why i prefer to stay on OTA-19 currently in case the procedure doesn't work so well on OTA-20.
Hello again @Pekkari i forgot to ask you this thing : In your advisory opinion, can I do (not yet done.. 😉 ) the procedure here over PR-28 without risk of compromising my balance??
Not right now, it will break your ofono, as commented right before.
Okay, thank you for confirming again to stay put!
hey @gbdomubpkm , check here this comment, you may be able to restore your current mms context if you do some further testing, I pushed the buggy code to another branch to let community continue testing.
ok thanks @Pekkari : you restored the PR-28 that was working if i understood well. But what does it mean exactly ? this PR-28 : should work with OTA-20 only ? Should work with OTA-20 AND https://forums.ubports.com/topic/6510/mms-users-call-for-testing/40 too ?
As long as the CI system doesn't say otherwise, it should work with any becoming OTA, so feel free to upgrade, and retest. That particular testing seems to be for other apps related, in principle it should work with both, but I can't put hand in fire for it.
Hello @Pekkari I'm on OTA-20... and... It seems not possible currently to restore mms context, ofono 28 failed to built ! 🙂
Going back to the alternative solution with two different apn, one for internet and the other for mms, which allowed me to send mms in 4g : I can now with OTA-20 only send mms in 2g, 3g, but the solution does not work anymore in 4g !
Yep, there was conflicts because we landed another fix, but the build succeded and it was tested against the ci. Weird that you couldn't at first. We didn't know 4G mms didn't work. I'll transmit the new internally to see what we can help. Please be patient with that tough. And thanks for your testing!
We didn't know 4G mms didn't work
Again, mms doesn't work NOW in 4g with my alternative solution (2 different apn) and OTA-20. MMS worked well in 4g with your PR-28 and OTA-19, or could work with alternative solution (2 different apn) and OTA-19 or OTA-18..
I have good news 🙂 the PR-28 has been installed !!
But i had an idea : i tried to install the PR under 3g network, NOT 4g and it worked !! Strange thing !
But now, if i am under 4g, i can send again mms !! Strange again 🙂
Hi,
I bleed the adjustment for ofono to stop creating the extra context. Can you please retest the pr 28 and report me back if it worked out of the box?
Thanks!
I haven't tested it yet. If everything works the way you want, should I get this that is to say only one APN ?
Yes, the expected behaviour is that you'll be able to reboot the device or restart ofono, without having an extra apn only for mms, it should stay as you show in the pic.
RC 8 Bouygues SIM (for me)
Not possible to send MMS (spinning wheel) and to receive MMS using messaging app.
The command line
/usr/share/ofono/scripts/set-context-property 0 Protocol IP
fixed internet (cellular data ok) but not MMS. APN MMS is ok. But since I hadn't tested the MMS function before the fix, I can't say more. Sms, calls are ok.