MMS users: call for testing
-
@jezek Good explanation. I think you are right because at this time the devel and rc images both have the same package versions, so switching between them would not change those bits.
Previously when rc didn't have the new packages this technique of going between rc and devel would ensure you would get them installed when going to devel, but now as you note going to stable then to rc or devel is needed.
-
@lduboeuf @Flohack
I've been thinking, why thetelepathy-ofonopackage didn't got updated. The last build (according to apt) was 2020-09-30. When I look at commits, that includes the sentdateempty MR. After this commit, no new builds of xenial branch are updated in debian packages. The next MR after this date are some debian/changelog changes. I remember we had troubles with debian packaging in nuntium, caused by my forgotten TODO in debian/changelog. I'm not really sure, but i think I read somewhere, that the debian/changelog updates are made automatically and not by hand by users. Could this be the case of this? Does anyone has more insights to debian packaging? -
@jezek this should be ok now. At least on devel telepathy-ofono has been updated
-
@lduboeuf said in MMS users: call for testing:
@jezek this should be ok now. At least on devel telepathy-ofono has been updated
Ahaaa, I see, they updated the changelog and bumped the version to take effect. I will test soon and tell results.
However, I wonder, why the other changelogs (nuntium, history-service, messaging-app, telephony-service) didn't needed to be updated?
This brings me to another question. Shouldn't the other changelogs (and the telepathy-ofono too) be updated with the description of changes, my credentials, version, etc... too? @lduboeuf , you are the maintainer of messaging app, what do you say to the debian/changelog changes in the app?
jEzEk
-
.... and just a problem a few minutes ago. I can't download my image and I can't stop the wheel from spinning. Is it possible to stop the spinning wheel, to restart the download without deleting the MMS? Volla RC 45 of today. No problem in RC 44 redownload for me (Volla).
-
My languages: 🇦🇹 🇩🇪 🇬🇧 🇺🇸
-
@domubpkm Yeah probably the download attempt needs a timeout when it would become available again
-
On halium-devel (376) for bacon, at the moment mms seems to be broken. No notification whatsoever, while the former build gave me the standard mms error. So sth has changed, just not as intended it would seem
-
Confirmed, for me does not work/ no longer in RC.
For checking that :- I sent an MMS to myself after exiting the flight mode and reactivating my MMS settings : MMS received/works.
- Then, I tried to download (redownload) the MMS of somebody and still this wheel turns endlessly...
But about
The download (redownload) works !Best wishes 2022 to the whole UT UBports community
-
-
@domubpkm @Emphrath I just re-tested and things seem to be working for me:
- Reset to current "RC"
- Re-configured APN entries
- Wifi ON: sent a MMS photo to UT from Google Voice (Web)
- Ooops message with download link received on UT
- Turn OFF wifi on UT: wait 2 minutes, retried download. Successfully received picture.
- Wifi ON: sent a MMS group photo to UT from Google Voice (Web)
- Oooops message with download link received on UT to individual sender thread
- Turned off wifi: wait 2 minutes, retried download. Not successful a few times (maybe was too fast), then tried again, and was successful in getting the group MMS photo (to a group already created in messaging app). NOTE that the "spinning download" button did NOT remove itself, but kept spinning even though the photo was downloaded. I think this is a bug but is somewhat understood because the group MMS "ooops" message comes to the individual sender thread, but the group MMS message when downloaded goes to the group thread so it is confused how to clean it up.
@domubpkm was your "spinning download" MMS by chance a group MMS?
So in summary, I do sometimes see the message not get received after 1 minute, but eventually by trying again (and again) it does come. I don't see any regression since the recent updates from a few days ago, this matches the experience I was seeing on "Devel" over the past weeks.
My specifications:
Pixel 3a XL
US Mobile (T-Mobile USA MVNO)
APN Settings:Used For: Internet Name: T-Mobile Internet APN: epc.tmobile.com <User Name and Password BLANK> Used For: MMS Name: US Mobile MMS APN: pwg MMSC: http://pwg.mmsmvno.com/mms/wapenc <Proxy, Proxy Port, User Name, Password ALL BLANK> -
I've tried the new RC v133 upgrade (switched to stable and than RC) and now the (re)download works.
@domubpkm I know about the occasional problem with the spinning download button. The problem is, that sometime nuntium crashes (& restarts) due to some race condition (that was already there when I first touched the code). Also, when there are problems with mobile signal & re-connection after flight mode, such troubles may occur. And I also have forgot to check the dbus result, when attempting message (re)download. That's why it sometime misbehaves.
For now, if you want to get rid of the pending state, you'd have to edit the message database by hand and change the state back to temporary error state.
Next week I will try to get a detailed look at it.
@emphrath said in MMS users: call for testing:
On halium-devel (376) for bacon, at the moment mms seems to be broken. No notification whatsoever, while the former build gave me the standard MMS error. So sth has changed, just not as intended it would seem
I've tried halium-devel on FP2. The tool for testing MMS messages
nuntium-inject-pushgave me an error, when I tried to push an message, cause it didn't found dbus addres in nuntium logs. I checked and in there were no logs for nuntium added, which is weird, because there should be. So I restarted nuntium (using commandinitctl --user restart nuntium). After that the mms testing tool worked and mms notification and (re)download too. -
@jezek Thank you, you confirm that there is a problem. For your temporary solution thank you again but it's a bit of gibberish for me so I'll wait
-
@flohack said in MMS users: call for testing:
@domubpkm Also the button is called "Download" and not "redownload" @lduboeuf
Yes, i think we should keep "Dowload" and modify the text before, but next OTA i guess
-
@jezek I'll try your nuntium workaround tomorrow if the last devel update doesn't fix it. Thanks for the tip
-
L Lakotaubp referenced this topic on
-
@jezek well after installing the 377 update, I tested again and failed. So i tried ur workaround. The command informs me that nuntium is a running process with such PID... But I want to restart it don't I ??? A sudo before that command gives me an error: upstart is not set in this environment and therefore the command cannot locate the upstart instance... Can I test again or did the command fail ?
-
-
@jezek said in MMS users: call for testing:
However, I wonder, why the other changelogs (nuntium, history-service, messaging-app, telephony-service) didn't needed to be updated?
telepathy-ofono had a bad last changelog version number which makes CI not increment the correct version digit i guess.
This brings me to another question. Shouldn't the other changelogs (and the telepathy-ofono too) be updated with the description of changes, my credentials, version, etc... too? @lduboeuf , you are the maintainer of messaging app, what do you say to the debian/changelog changes in the app?
IMO yes core services should have the debian changelog updated , but i never know what version digit to update.
But not sure for messaging-app because it has not been updated since long time ago.
IDK what would be the best practice.
I would say that it should be the maintainer responsability -
@jezek On Volla RC test OTA-22, after reactivating the disabled cellular data (not flight mode), I was unable to download two MMS: endless spinning wheel.
-
@domubpkm said in MMS users: call for testing:
@jezek On Volla RC test OTA-22, after reactivating the disabled cellular data (not flight mode), I was unable to download two MMS: endless spinning wheel.
I wrote a bug report here, but can also be a different cause for your case:
https://github.com/ubports/nuntium/issues/18
