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

    Noble-based devel images now available on most devices with 20.04 devel image

    Scheduled Pinned Locked Moved OS
    39 Posts 19 Posters 5.2k Views 5 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.
      • Vlad NirkyV Offline
        Vlad Nirky @ghazouani
        last edited by

        @ghazouani
        Is there a place (here?) where I can report malfunctions on my Redmi Note 9 Pro with the latest daily release? I have a second phone where I test different things and can test on demand...

        1 Reply Last reply Reply Quote 0
        • N Offline
          nunesfl @Luksus
          last edited by

          @Luksus
          Hello
          I have a Xiomi Redimi Note 9 Pro, trying to update to 24.04 in order to test it... it works pretty well on 20.04...
          But every attempt I do, the installation stucks in the recovery screen with a message 'Error installing Ubuntu update, exit code: 256', it says to see the log but no log is generated...
          Would you have any clue why I may be receiving that error message ?
          Thanks,

          Vlad NirkyV LakotaubpL 3 Replies Last reply Reply Quote 0
          • Vlad NirkyV Offline
            Vlad Nirky @nunesfl
            last edited by Vlad Nirky

            @nunesfl
            Yes, the size on a partition is too small.
            You 'll have to add argument to the installer command.:
            ./ubports-installer_0.10.0_linux_x86_64.AppImage -f ./miatoll.yml
            and the miatoll.yml can be downloaded here:
            https://github.com/ubports/installer-configs/tree/fd9802a07cf67d489a78331af3426c416c677f23/v2/devices

            And check the three boxes during install
            And, also, the miatoll.yml have to be located in the same folder as the installer (not sure it's necessary but...)

            1 Reply Last reply Reply Quote 1
            • Vlad NirkyV Offline
              Vlad Nirky @nunesfl
              last edited by Vlad Nirky

              @nunesfl
              Beware that differents things are not working yet so it's not for a daily use phone...

              https://t.me/UTForMiatoll

              1 Reply Last reply Reply Quote 0
              • LakotaubpL Lakotaubp referenced this topic on
              • LakotaubpL Offline
                Lakotaubp @nunesfl
                last edited by

                @nunesfl Yours is not the only device getting this partition issue as @Vlad-Nirky has mentioned. My advice unless you really know what you are doing is to wait until you hear that a fix has been applied for the issue.
                The OP5 also has this issue and has for a few weeks now after initially been able to install 24.04. The fix has been applied for the FairPhone 5 not tried on the FP4 or the Pixel 3a yet.

                N K 2 Replies Last reply Reply Quote 0
                • N Offline
                  nunesfl @Lakotaubp
                  last edited by

                  Thank you @Lakotaubp , I was able to install 24.04 resizing partition! System seems quite usable, waydroid work well, just missing some apps that were working at 20.04 , but I believe it is just because they were not converted yet. Battery drain still an issue....

                  arubislanderA 1 Reply Last reply Reply Quote 1
                  • arubislanderA Offline
                    arubislander @nunesfl
                    last edited by

                    @nunesfl said in Noble-based devel images now available on most devices with 20.04 devel image:

                    Battery drain still an issue....

                    Compared to what exactly? Android, 20.04, something else?

                    And are you running the waydroid container all the time, or are you stopping the container when not in use? Otherwise waydroid is known to cause increased battery usage.

                    πŸ‡¦πŸ‡Ό πŸ‡³πŸ‡± πŸ‡ΊπŸ‡Έ πŸ‡ͺπŸ‡Έ
                    Happily running Ubuntu Touch
                    Google Pixel 3a (20.04 DEV)
                    JingPad (24.04 preview)
                    Meizu Pro 5 (16.04 DEV)

                    N 1 Reply Last reply Reply Quote 0
                    • N Offline
                      nunesfl @arubislander
                      last edited by

                      @arubislander
                      Compared with Lineage OS 20
                      WayDroid installed but not running, no WiFi, no Location, no NFC, no Bluetooth, and put in airplane mode.
                      Left the phone with 39%, after 8 hours it was 4%.

                      U 1 Reply Last reply Reply Quote 0
                      • U Offline
                        uxes @nunesfl
                        last edited by uxes

                        @nunesfl I must note that until yesterday I had a miatoll device running on Noble five days, placed on the table with wifi turned on, from the original battery charged 100% it only showed ~20%, here and there I unlocked it to look at the time and then locked it again. I would wonder if there is something with the battery specifically of your device

                        1 Reply Last reply Reply Quote 0
                        • K Offline
                          kugiigi @Lakotaubp
                          last edited by

                          @Lakotaubp I just reinstalled Noble on my Pro1-ax and it booted fine. I didn't do any extra steps so I guess it's fixed now?

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

                            @kugiigi Really not sure my OP5 still stops at recovery and I have not heard anything official.
                            Edit: Still the same on OP5 putting them back on 20.04 now. Will try again in a week or so unless I hear anything.

                            K 1 Reply Last reply Reply Quote 0
                            • K Offline
                              kugiigi @Lakotaubp
                              last edited by

                              @Lakotaubp Oh I see, then the fix might be done per device πŸ€”

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

                                @kugiigi One thing I remember is that my OP5 worked for about a week or so on 24.04 with updates then failed to boot past recovery. See how yours goes it maybe ok or a larger update may stop it. Interesting to find out.

                                K 1 Reply Last reply Reply Quote 0
                                • K Offline
                                  kugiigi @Lakotaubp
                                  last edited by

                                  @Lakotaubp It also got the error a few weeks ago then I just tried it again and it worked. Anyway, let's see if there's any news about it πŸ˜„

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