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

    The MMS lost story

    Scheduled Pinned Locked Moved OS
    133 Posts 16 Posters 54.9k 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.
      • mardyM Offline
        mardy @jezek
        last edited by mardy

        Hi Jezek,

        Ok, I admit defeat in the telephony-service testing battle. I've written some code, to test the redownload function, but I couldn't make the tests run. The crossbuilder don't run test.

        as a matter of fact, crossbuilder always runs the tests when not cross-building. In other words, if the target architecture is the same as the host architecture, tests will be run. I tried now with telephony-service in my PC and tests are run (and pass), in the xenial branch.

        Just run

        crossbuilder --architecture=amd64
        

        on your branch and you should see the tests being executed.

        jezekJ 1 Reply Last reply Reply Quote 1
        • jezekJ Offline
          jezek @mardy
          last edited by

          @mardy Thank you, will try. One defeat doesn't mean, I (we) can't win at the end.

          jEzEk

          1 Reply Last reply Reply Quote 0
          • lduboeufL Offline
            lduboeuf
            last edited by lduboeuf

            Hi, as @UniSuperBox said on last Q&A , the feature is ready for testing:

            You need to be on devel or RC ( since 2021/06/09 )
            From a terminal, run that commands one by one:

            sudo ubports-qa install PR_nuntium_8
            sudo ubports-qa install telepathy-ofono 20
            sudo ubports-qa install history-service 35
            sudo ubports-qa install telephony-service 20
            sudo ubports-qa install messaging-app 260

            And reboot

            Test Plan example:
            Make sure it works as before, send/receive MMS, multiple ones
            Disable cellular-data, receive a MMS and check if MMS notification is here with the download button
            Change proxy settings in APN or put wrong settings and check for notification reception

            D 1 Reply Last reply Reply Quote 0
            • D Offline
              domubpkm @lduboeuf
              last edited by

              @lduboeuf Technically, there is nothing to prevent from doing it on the most recent RC if you don't want to switch (again) to dev ?

              lduboeufL 1 Reply Last reply Reply Quote 0
              • lduboeufL Offline
                lduboeuf @domubpkm
                last edited by

                @domubpkm it should be good on RC too. Last builds are from one week or two.

                1 Reply Last reply Reply Quote 1
                • lduboeufL Offline
                  lduboeuf
                  last edited by

                  @jezek

                  Did some test this morning, i have a use case where the message is staying in the "pending state" ( so we can't click redownload button anymore ) even after reboot. It is with bad signal and by putting wrong info in MMS settings
                  In history db the message is x-ubports-nuntium-mms-error-activate-context but the status is still in Pending state

                  nunitum logs:
                  2021/06/11 09:15:26 Trying to set Active property to true for context on true /ril_0/context2
                  2021/06/11 09:15:26 Cannot set Activate to true (try 1/3) interface on /ril_0/context2: org.ofono.Error.NotAttached: GPRS is not attached
                  2021/06/11 09:15:32 Failed to activate for /ril_0/context2 : failed to activate context
                  2021/06/11 09:15:32 Cannot activate ofono context: no context available to activate

                  jezekJ 1 Reply Last reply Reply Quote 0
                  • jezekJ Offline
                    jezek @lduboeuf
                    last edited by

                    @lduboeuf It seems you found a bug. You should fill an issue. I have some idea, where the problem is and I will elaborate under the issue. This is a veeery long thread and I don't want to make it any longer. We should close it.

                    Is the bug a big bug? Can we deploy to stable with this bug, or we need to fix it before deploying? Because there is a bigger issue here. I don't have time now to do any work on ubuntu touch due to personal and technical issues. And it will not change (at least) this month.

                    jEzEk

                    lduboeufL 1 Reply Last reply Reply Quote 0
                    • lduboeufL Offline
                      lduboeuf @jezek
                      last edited by lduboeuf

                      @jezek I don't think that issue is a blocker as it may come in rare situations and moreover will end with the same situation than it is today ( just ask user to send it again). I wll look if i can work around that on messaging app.

                      Yes agree for this thread becoming too long. I would add it in a nuntium PR instead of an issue since it is not merge yet.

                      Hope you will recover soon :). Btw i bet this will not land on OTA-18. Not enough feedback from users and big code base 🙂

                      [Edit]: not possible to work around it on messaging-app

                      1 Reply Last reply Reply Quote 1
                      • R Offline
                        rocket2nfinity
                        last edited by

                        Not sure if this is still needed, but latest ubports email said to test.

                        Fixes MMS perfectly on Nexus 6P

                        1 Reply Last reply Reply Quote 0
                        • R Offline
                          Rondarius
                          last edited by Rondarius

                          It does not solve the mms problem for me. I still get the oops message with Download. I have tried all the suggestions too and nothing works. I am on N6P Devel.

                          4 Google Pixel 3A
                          1 Google Nexus 6P
                          2 Google Nexus 5
                          2 Pinephones
                          2 Sony Xperia X

                          1 Reply Last reply Reply Quote 0
                          • R Offline
                            Rondarius
                            last edited by

                            I tried another operator and MMS works, both send and receive MMS. I will contact my operator to see if there is a solution to this.

                            4 Google Pixel 3A
                            1 Google Nexus 6P
                            2 Google Nexus 5
                            2 Pinephones
                            2 Sony Xperia X

                            1 Reply Last reply Reply Quote 0
                            • LakotaubpL Offline
                              Lakotaubp
                              last edited by

                              As @jezek and @lduboeuf suggested this thread is very long and far to hard to follow. So I will lock it. A fix has been posted so please as asked try it and report issues in the normal way and let's see how it goes.

                              1 Reply Last reply Reply Quote 0
                              • LakotaubpL Lakotaubp locked this topic on
                              • First post
                                Last post