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.2k 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.
      • jezekJ Offline
        jezek
        last edited by jezek

        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 mentioned ubports-qa commands. 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

        AppLeeA lduboeufL 2 Replies Last reply Reply Quote 1
        • AppLeeA Offline
          AppLee @jezek
          last edited by

          @jezek said in MMS users: call for testing:

          Thank you all.

          Thank YOU :thumbs_up:

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

            @jezek humm i probably miss something, i don't see the PR already merged

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

              @lduboeuf Or am I wrong? Is there a possibility that the patch is not in RC (and dev) and the applied ubports-qa changes 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?

              jEzEk

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

                @jezek

                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.

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

                  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

                  lduboeufL KenedaK D 3 Replies Last reply Reply Quote 0
                  • lduboeufL Offline
                    lduboeuf @jezek
                    last edited by

                    @jezek

                    Does anyone know how to be in the next OTA update?

                    idk, maybe @UniSuperBox or @Flohack can say ?

                    1 Reply Last reply Reply Quote 0
                    • KenedaK Offline
                      Keneda @jezek
                      last edited by

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

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

                      1 Reply Last reply Reply Quote 1
                      • flohackF Offline
                        flohack
                        last edited by

                        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: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

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

                          @jezek Such your personal investment in the essential MMS reliability mechanism πŸ‘‹ is worth this very usefull nechanism be incorporating as soon as possible.

                          rikR 1 Reply Last reply Reply Quote 0
                          • KenedaK Offline
                            Keneda @lduboeuf
                            last edited by

                            @lduboeuf said in MMS users: call for testing:

                            @keneda no idea πŸ˜‰

                            Now we know, so sad... 😭

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

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

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

                              jEzEk

                              flohackF 1 Reply Last reply Reply Quote 2
                              • flohackF Offline
                                flohack @jezek
                                last edited by

                                @jezek its more than one patch probably, @lduboeuf can propose the order - its a bit delicate to not make it wrong.

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

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

                                  @flohack the initial issue ( amongst others ) is here:
                                  https://github.com/ubports/ubuntu-touch/issues/17

                                  The 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 πŸ˜‰

                                  1 Reply Last reply Reply Quote 1
                                  • rikR Offline
                                    rik @domubpkm
                                    last edited by

                                    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.

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

                                      @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

                                      rikR 1 Reply Last reply Reply Quote 0
                                      • K Offline
                                        kristatos
                                        last edited by kristatos

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

                                        BQ Aquaris E4.5 (UT 16.04)
                                        Vollaphone (UT 20.04)

                                        stanwoodS 1 Reply Last reply Reply Quote 0
                                        • stanwoodS Offline
                                          stanwood @kristatos
                                          last edited by

                                          @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...(?)

                                          Redmi Note 9S Stable
                                          If God has a computer, it must be a GNU/Linux

                                          1 Reply Last reply Reply Quote 1
                                          • rikR Offline
                                            rik @lduboeuf
                                            last edited by

                                            @lduboeuf said in MMS users: call for testing:

                                            @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

                                            Alfred suggested I file an issue at the general Ubuntu Touch github repo until we sort out where exactly changes may be needed. I found this one already listed here: https://github.com/ubports/ubuntu-touch/issues/1753 so I think we can keep following the "need to turn wifi off for MMS to work bug there" but my ignorant thought was to somehow use iptables / routing rules somehow to force using the cellular data network interface? Not sure if possible at all.

                                            About group MMS messages not working, I see an old issue related to the OPO there, not sure if I should add to it or start a new issue? OPO uses legacy canonical ofono etc that may not overlap with current halium 9 ports?? Here is the OPO issue for it: https://github.com/ubports/ubuntu-touch/issues/383

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

                                              @rik said in MMS users: call for testing:

                                              About group MMS messages not working, I see an old issue related to the OPO there, not sure if I should add to it or start a new issue? OPO uses legacy canonical ofono etc that may not overlap with current halium 9 ports?? Here is the OPO issue for it: https://github.com/ubports/ubuntu-touch/issues/383

                                              Yes MMS group has never worked well on UT according to ticket report. Don't forget to thumb up or add a comment in the issue report.
                                              MMS is a feature that most core developers don't use, so hard to find a motivated developer..

                                              E 1 Reply Last reply Reply Quote 0
                                              • First post
                                                Last post