Xenial rc fails to boot on Meizu MX4
-
@thepossessor Have done it just now. Goodnight
-
@lakotaubp thanks alot
-
@thepossessor out of curiosity, if you type
localeon your phone terminal? What's the output? -
@advocatux right now I am using german, but the effect is the same with english.
-
@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-8as locale.Edit: I was wrong, there's the same issue on vivid.
-
@advocatux That little Spanish enclave of Texas and New Mexico?
-
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
-
@advocatux Mine is en_GB.UTF-8
-
@lakotaubp okay, thank you!
-
@advocatux My nexus with the above was a none wipe. Will check the mx4 later thats been well wiped
-
@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
-
Just to keep you updated, I filed this bug report https://github.com/ubports/ubuntu-touch/issues/751
In short, when checking out
localeon the device it gives you the right answer but if you useadb shellthe answer is alwaysen_US.UTF-8because that's what is set in stone on/etc/default/locale(wrongly) -
Works ok for me, using a bespoke Ubuntu (not-Android) model of the MX4.
-
@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.
-
@thepossessor Thanks for letting me know, and a big welcome back to the Luxembourg timezone
