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

    OTA-19 Call for Testing Companion Post

    Scheduled Pinned Locked Moved OS
    10 Posts 6 Posters 1.6k Views 3 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.
      • flohackF Offline
        flohack
        last edited by flohack

        Hello everyone!

        The expected release date for Ubuntu Touch OTA-19 is Friday, September 17.

        This forum post is a companion to the OTA-19 Call For Testing

        Please post any general observations you have while testing the current image in the RC channel, as compared to OTA-18, in this thread. The current release candidate (RC) is 2021-W36

        If you have any comments on any of the specific issues in the OTA-19 tracker, please post them in the issue thread so they are easier to track. OTA-19 tracker: https://github.com/orgs/ubports/projects/28

        Please note that only critical and security fixes will be able to enter OTA-19 as this point, normal bug fixes and new features will need to wait for our next release. Please do not discuss normal bug fixes and new features here.

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

        S cregoxC 2 Replies Last reply Reply Quote 4
        • S Offline
          sven @flohack
          last edited by sven

          @flohack I switched from stable to RC and the installed version is reported as 2021-W36 (not 2021-W27, OnePlus 3T). It broke the perfectly working HotSpot :-(, now I need several tries to turn it on.

          VollaPhone22 (dual-boot of VollaOS and UT 20.04 OTA-5), Pocophone F1 (pmOS, edge)

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

            @sven Corrected the labelling to 2021-W36. Unfortunately, since no one was working on Hotspot this is deemed to be a device-specific issue probably, and needs to be looked into by the porter. Sorry to not having more infos on this.

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

            1 Reply Last reply Reply Quote 0
            • MrT10001M Offline
              MrT10001
              last edited by

              Working on the install. I have tried the Samsung galaxy Note 4 updating through the phone update channel which caused it to hang at reboot. Reinstalled through the installer (Ubuntu, not Windows) which resolved it. Same thing with the OnePlus Two, it hangs at the initial phone boot screen, You can get to recovery, and thats it. Reinstalled using Windows installer without formatting and booted fine into phone with all my settings intact. My Redmi Note 7 updated through the phone update normally. I have not had this issue with OTA-17 to OTA-18. With the Samsung Note 4 I thought it may have bricked as I could not get it off the inital Samsung logo boot screen, even after battery removal, but managed by removing the battery, pressing the power on switch, leaving it for 5 minutes, putting battery in and then booting to the bootloader.

              Xiaomi Redmi Note 7.... And more...
              I have too many devices...

              1 Reply Last reply Reply Quote 0
              • cregoxC Offline
                cregox @flohack
                last edited by

                @flohack is it possible and simple enough to revert back to stable afterwards?

                MoemM 1 Reply Last reply Reply Quote 0
                • MoemM Offline
                  Moem @cregox
                  last edited by

                  @cregox said in OTA-19 Call for Testing Companion Post:

                  @flohack is it possible and simple enough to revert back to stable afterwards?

                  Yes, but OTA-19 is out by now.

                  Is currently using an Op5t
                  Also owns an Op1, a BQ E4.5 and an Xperia X, as well as a BQ tablet and a Pinetab2. Please, someone... make it stop.

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

                    @moem
                    I'll add : wich means OTA 19 is stable now, so going to RC (that maybe now is beyond OTA 19) from stable OTA 18 and going back to stable means updating to stable OTA 19, and no way to go back to OTA 18.

                    Edit : @cregox Anyway switching channel from stable to rc or the opposite is simple, just be sure to have at least 70% battery and phone plugged to charger.

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

                    cregoxC 1 Reply Last reply Reply Quote 1
                    • cregoxC Offline
                      cregox @Keneda
                      last edited by

                      @keneda why 70% battery?

                      i believe even 15% on my volla x should be plenty enough!

                      did you mean 2h juice left? 😏

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

                        @cregox
                        Because with 70% you are sure you will not have any problem of powering loss during update, wich could lead to a brick...

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

                        cregoxC 1 Reply Last reply Reply Quote 0
                        • cregoxC Offline
                          cregox @Keneda
                          last edited by

                          @keneda makes me wonder if and how that ever really happens anymore.

                          sounds like an issue prior to ext3.

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