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

    Xenial rc fails to boot on Meizu MX4

    Scheduled Pinned Locked Moved Support
    55 Posts 5 Posters 11.5k Views 2 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.
      • ThePossessorT Offline
        ThePossessor @advocatux
        last edited by

        @advocatux right now I am using german, but the effect is the same with english.

        0_1530953670442_screenshot20180707_105136362.png

        advocatuxA 1 Reply Last reply Reply Quote 0
        • advocatuxA Offline
          advocatux @ThePossessor
          last edited by advocatux

          @thepossessor thank you. I'm asking because I don't know why on xenial (on vivid works fine) setting my phone to Spanish gives me en_US.UTF-8 as locale.

          Edit: I was wrong, there's the same issue on vivid.

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

            @advocatux That little Spanish enclave of Texas and New Mexico?

            advocatuxA 1 Reply Last reply Reply Quote 0
            • advocatuxA Offline
              advocatux @Lakotaubp
              last edited by

              @lakotaubp 😄 😄 😄

              Yes, I was thinking about something like that, but now my phone is under an El Alamo situation. I'm reinstalling UT with wipe option to see if I can reproduce the issue 🙂

              LakotaubpL 2 Replies Last reply Reply Quote 0
              • LakotaubpL Offline
                Lakotaubp @advocatux
                last edited by

                @advocatux Mine is en_GB.UTF-8

                advocatuxA 1 Reply Last reply Reply Quote 0
                • advocatuxA Offline
                  advocatux @Lakotaubp
                  last edited by

                  @lakotaubp okay, thank you!

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

                    @advocatux My nexus with the above was a none wipe. Will check the mx4 later thats been well wiped

                    advocatuxA 1 Reply Last reply Reply Quote 0
                    • advocatuxA Offline
                      advocatux @Lakotaubp
                      last edited by advocatux

                      @lakotaubp to see the current state of the art, I'm using Ubuntu 18.04 and the latest snap installer this time. So far I've got 2 errors, something about a problem with eaccess that I ignored, and another one when the installation stopped due to some "download error, checksum did not match on file".

                      I've deleted the cache, and I'm trying again 🙂

                      Edit: it worked flawlessly the second time

                      1 Reply Last reply Reply Quote 0
                      • advocatuxA Offline
                        advocatux
                        last edited by

                        Just to keep you updated, I filed this bug report https://github.com/ubports/ubuntu-touch/issues/751

                        In short, when checking out locale on the device it gives you the right answer but if you use adb shell the answer is always en_US.UTF-8 because that's what is set in stone on /etc/default/locale (wrongly)

                        1 Reply Last reply Reply Quote 1
                        • T Offline
                          TartanSpartan
                          last edited by TartanSpartan

                          Works ok for me, using a bespoke Ubuntu (not-Android) model of the MX4.

                          1 Reply Last reply Reply Quote 0
                          • ThePossessorT Offline
                            ThePossessor
                            last edited by

                            @Lakotaubp just to keep you posted.

                            Last night's update seems to have fixed the boot failure problem. Now only 1 of 10 boot attempts fails. The next attempt then is ok again .

                            Back to normal. 🙂

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

                              @thepossessor Thanks for letting me know, and a big welcome back to the Luxembourg timezone 😀

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