• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
UBports Robot Logo UBports Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

MMS users: call for testing

Scheduled Pinned Locked Moved General
69 Posts 12 Posters 19.1k Views 6 Watching
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • B Offline
      BlueFroggie @domubpkm
      last edited by 12 Nov 2021, 21:16

      On my Redmi Note 7 when I have cellular data on, some MMS come normally, and some in no longer time than 24 hours via SMS from the operator informing me to log in on the website to download MMS. It is frutrating enough, that usually I keep internet data off so the useless battery drain is not that big. I wonder if the script provided here coul help with that πŸ€”

      Redmi Note 7 user of UT (ota-19)

      K 1 Reply Last reply 12 Nov 2021, 22:23 Reply Quote 1
      • K Offline
        Keneda @BlueFroggie
        last edited by 12 Nov 2021, 22:23

        @bluefroggie said in MMS users: call for testing:

        I wonder if the script provided here coul help with that

        That's kind of exactly what this messaging app fix is about.

        2015-2023 : Meizu MX4 ☠️⚰️✝️
        2023-2024 : Nexus 5 ☠️⚰️✝️
        2024-***** : FPOS Fairphone 5 waiting UT for freedom πŸ˜‰
        πŸ‡²πŸ‡«πŸ‡¬πŸ‡§

        1 Reply Last reply Reply Quote 1
        • L Offline
          lduboeuf @domubpkm
          last edited by 13 Nov 2021, 00:31

          @domubpkm yes the procedure doesn't change

          1 Reply Last reply Reply Quote 0
          • J Offline
            jezek
            last edited by jezek 28 Dec 2021, 22:03

            Hello. The whole MMS redownload fix stack (nuntium, telepathy-ofono, history-service, messaging-app, telephony-service) has been merged. So I made a test if everything is alright.

            My phone was on RC channel, so I installed stable version and then RC version again to be sure the whole image is reinstalled and not only incremental updates.

            Then I used the nuntium-inject-push tool to inject an MMS message that produces a download error, to test if the error is propagated to messaging-app and the message can be re-downloaded. The test failed, cause in mesaging-app there was no re-download button, only the error message that tells you need to ask the sender to send again.

            After some logs reading and some experimenting, I found out that I needed to run only the sudo ubports-qa install telepathy-ofono 20 command (and then reboot) to be able to re-download erroneous MMS messages. After that everything works as intended.

            I don't know why there is the need to downgrade (that's what the QA script tells me) the telepathy-ofono package. The PR was merged, so if the telepathy-ofono libraries are compiled from the repository, everything should work automatically after upgrade.

            Can enyone confirm (or deny) my findings? Does anyone know what could cause this? Or am I doing something wrong?

            Thanks.

            Note: If anyone wants to test this and is struggling how to, cause my report here is incomprehensible, don't hesitate to write me, I'll try write step-by-step instructions.

            jEzEk

            F 1 Reply Last reply 28 Dec 2021, 22:24 Reply Quote 0
            • F Offline
              flohack @jezek
              last edited by 28 Dec 2021, 22:24

              @jezek Well that sounds bad. Everything should work in RC as expected, as everything was merged.

              My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

              J 1 Reply Last reply 29 Dec 2021, 16:56 Reply Quote 0
              • J Offline
                jezek @flohack
                last edited by 29 Dec 2021, 16:56

                @flohack said in MMS users: call for testing:

                @jezek Well that sounds bad. Everything should work in RC as expected, as everything was merged.

                So I tested again.
                Switched to stable.

                phablet@ubuntu-phablet:~$ apt list | grep -P 'nuntium|telepathy-ofono|history-service|messaging-app|telephony-service'
                history-service/now 0.3~0ubports4+0~20210526173549.20~1.gbp17c341 armhf [installed,local]
                messaging-app/now 0.1.3~0ubports0+0~20210927064939.80~1.gbpdcb599 armhf [installed,local]
                nuntium/now 1.4+ubports1+0~20210315192859.11~1.gbpb182b1 armhf [installed,local]
                telepathy-ofono/now 0.3+ubports+0~20200930080735.3~1.gbpdb5e35 armhf [installed,local]
                telepathy-ofono-ril-mc-plugin/now 0.3+ubports+0~20200930080735.3~1.gbpdb5e35 armhf [installed,local]
                telephony-service/now 0.4+0ubports3+0~20210817080913.31~1.gbpaae257 armhf [installed,local]
                

                Then switched to rc.

                phablet@ubuntu-phablet:~$ apt list | grep -P 'nuntium|telepathy-ofono|history-service|messaging-app|telephony-service'
                history-service/now 0.3~0ubports4+0~20211216130156.4~1.gbp88201f armhf [installed,local]
                messaging-app/now 0.1.3~0ubports0+0~20211220103430.85~1.gbp654469 armhf [installed,local]
                nuntium/now 1.4+ubports1+0~20211215170043.12~1.gbp054848 armhf [installed,local]
                telepathy-ofono/now 0.3+ubports+0~20200930080735.3~1.gbpdb5e35 armhf [installed,local]
                telepathy-ofono-ril-mc-plugin/now 0.3+ubports+0~20200930080735.3~1.gbpdb5e35 armhf [installed,local]
                telephony-service/now 0.4+0ubports3+0~20211220103455.35~1.gbp61321e armhf [installed,local]
                

                As you can see, the telepathy-ofono package didn't get updated to new build. It's still from year 2020.

                jEzEk

                L 1 Reply Last reply 29 Dec 2021, 20:30 Reply Quote 0
                • L Offline
                  lduboeuf @jezek
                  last edited by 29 Dec 2021, 20:30

                  @jezek same for me on devel. Strange because i received a MMS notification without issue

                  J 1 Reply Last reply 29 Dec 2021, 21:52 Reply Quote 0
                  • J Offline
                    jezek @lduboeuf
                    last edited by jezek 29 Dec 2021, 21:52

                    @lduboeuf said in MMS users: call for testing:

                    @jezek same for me on devel. Strange because i received a MMS notification without issue

                    Remember the time when I thought, that the stack was merged (and was not), because after my RC update error notifications still worked? It turned out, that the incremental updates didn't reinstall packages after the ubports-qa script updates. I think this is your case too. It works because binaries after the ubports-qa script are not updated/downgraded when doing incremental update (original package was not changed, so no need to be in incremental update). Try to update system to stable and than back to devel and you should not receive error notifications (Edit: I mean, the ones with re-download button).

                    jEzEk

                    R 1 Reply Last reply 29 Dec 2021, 22:50 Reply Quote 1
                    • R Offline
                      rik @jezek
                      last edited by 29 Dec 2021, 22:50

                      @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.

                      1 Reply Last reply Reply Quote 1
                      • J Offline
                        jezek
                        last edited by jezek 30 Dec 2021, 21:37

                        @lduboeuf @Flohack
                        I've been thinking, why the telepathy-ofono package 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

                        L 1 Reply Last reply 31 Dec 2021, 07:43 Reply Quote 0
                        • L Offline
                          lduboeuf @jezek
                          last edited by 31 Dec 2021, 07:43

                          @jezek this should be ok now. At least on devel telepathy-ofono has been updated

                          J 1 Reply Last reply 31 Dec 2021, 17:22 Reply Quote 1
                          • J Offline
                            jezek @lduboeuf
                            last edited by 31 Dec 2021, 17:22

                            @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

                            D L 2 Replies Last reply 31 Dec 2021, 17:34 Reply Quote 0
                            • D Offline
                              domubpkm @jezek
                              last edited by 31 Dec 2021, 17:34

                              @jezek screenshot20211231_182408170.png

                              .... 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).

                              F 2 Replies Last reply 31 Dec 2021, 19:34 Reply Quote 0
                              • F Offline
                                flohack @domubpkm
                                last edited by 31 Dec 2021, 19:34

                                @domubpkm Also the button is called "Download" and not "redownload" @lduboeuf πŸ™‚

                                My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                                L 1 Reply Last reply 1 Jan 2022, 21:06 Reply Quote 0
                                • F Offline
                                  flohack @domubpkm
                                  last edited by 31 Dec 2021, 19:35

                                  @domubpkm Yeah probably the download attempt needs a timeout when it would become available again

                                  My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                                  1 Reply Last reply Reply Quote 0
                                  • E Offline
                                    Emphrath
                                    last edited by 1 Jan 2022, 15:55

                                    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

                                    R 1 Reply Last reply 1 Jan 2022, 16:35 Reply Quote 0
                                    • D Offline
                                      domubpkm
                                      last edited by domubpkm 1 Jan 2022, 16:28 1 Jan 2022, 16:09

                                      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...
                                        screenshot20220101_164236016.png

                                      But about
                                      screenshot20220101_172049023.png
                                      The download (redownload) works !

                                      Best wishes 2022 to the whole UT UBports community

                                      1 Reply Last reply Reply Quote 0
                                      • R Offline
                                        rik @Emphrath
                                        last edited by 1 Jan 2022, 16:35

                                        @emphrath and @domubpkm have you confirmed your APN settings? With all the changes it is good to confirm those, there may have been something reset in them? I am re-installing RC now to check myself.

                                        R 1 Reply Last reply 1 Jan 2022, 16:50 Reply Quote 0
                                        • R Offline
                                          rik @rik
                                          last edited by rik 1 Jan 2022, 16:53 1 Jan 2022, 16:50

                                          @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>
                                          
                                          1 Reply Last reply Reply Quote 0
                                          • J Offline
                                            jezek
                                            last edited by jezek 1 Jan 2022, 17:16 1 Jan 2022, 17:12

                                            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-push gave 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 command initctl --user restart nuntium). After that the mms testing tool worked and mms notification and (re)download too.

                                            jEzEk

                                            D E 2 Replies Last reply 1 Jan 2022, 17:45 Reply Quote 1
                                            • First post
                                              Last post