@openvanchary the patch is right there in the link you gave...

@tigerpro Nice! So I have to be more careful when tweaking with Halium then. I'll update when I can when Halium is running on my laptop. I finally saw the word GIT in the apt install, so I guess I see where "build" is going

@RoyD the current effort to port Halium / UT to BQ devices are only on these models, at least for now: https://github.com/Halium/projectmanagement/issues?utf8=✓&q=is%3Aissue+is%3Aopen+bq Maybe you can ask https://aquaris-dev.org/ if there's any chance to port LineageOS to U2

Finally some progress: We have fixed the system image for deb and are hoping now that it can be actually installed from our servers!

@doniks I will do this. Thanks!!

Or maybe not. You might want to do telnet debugging with the break=bottom kernel cmdline parameter.

@mprotic yes, that's @mariogrip's work [image: 1549033884045-ut-pinephone.jpg]

@rvan I agree, having a productive discussion about a topic like this helps people get a better picture of what people look for. I wanted to port my Asus tablet, but when I out it back to stock (the custom ROM that was on it was causing bootloop issues) it still had reliability issues. I might try just doing Linux on it, but that is gonna be after I get UT working better on my note 4 and maybe one other device. What would you consider to be a good candidate for a portable UT device?

I suppose you are on 18.10 as well, so you may want to join in on https://forums.ubports.com/topic/2140/how-to-setup-crossbuilder-in-ubuntu-18-10 instead.

@mariogrip remote: A default branch (e.g. master) does not yet exist for ubports/community-ports/cancro remote: Ask a project Owner or Maintainer to create a default branch Please create a default branch or assign permissions ,Thank you

@lakotaubp pressure intensifies XD

@advocatux thanks for the link , I joined and will ask a bit later when I have more time to concentrate.

I have this issue too. Is there a workaround? N5. 16.04dev

full dmesg : https://pastebin.com/raw/TGeyuyW6

I had Meizu Pro 5 Ubuntu Edition but run into the https://forums.ubports.com/assets/uploads/files/1528013524195-8a15d567-ca4b-44ca-a1ce-84fdb7e0aec7-image.png screen when first trying to update it to Ubports 16.04/stable channel. Somehow now later I managed to flash - with ubuntu-device-flash - from within 16.04 ubuntu installation (actually, 16.04 lxd container with usb vendor specific passthrough). I did that by booting to Ubuntu's recovery installation with power button + volume up - this is where you might need the recovery-turbo.img but I had it flashed already. I verified that from within my lxc container (where I had added lxc config device add CONTAINERNAME meizu usb vendorid=18d1) I was able to see the device with 'adb devices'. Then I ran ubuntu-device-flash --server=http://system-image.ubports.com touch --device=turbo --channel=ubports-touch/15.04/stable - I thought it got stuck after downloads, but actually then it started the "Pushing" phase. And even more to my surprise, it rebooted to flashing phase with Ubuntu prorgress bar going back and forth, and then booted into working Ubports installation! Even though I specified "15.04/stable", it seems it too pointed to 16.04 already, ie OTA-5. The greatest thing was that since I didn't need to specify --bootstrap or --wipe, it was even the same installation I used as my main phone back in the days, so I had all my apps and photos intact.