@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?
So I have been trying to get my ofono stack working, as of now it seems like the android stuff can't access its own stuff in the /proc folder.
The list of what isn't working as of this writing is:
Cellular (Ofono sees the cellular modem but can't access its own folder in /proc)
Bluetooth (completely untested)
Rotation (sensors are found but no values generated)
GPS (test_gps segfaults in halium-boot but not in hybris-boot)
S-Pen (kernel sees it as a input device but disables it for some reason)
If anyone reading this has a note 4 and wants to take on any of these tests let me know your findings and I will update the list as issues are resolved. I also welcome any advice anyone may have if they read this and are not in telegram but have an idea of what's going on.
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
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.
Well, @doniks, I have tried creating files of various sizes with dd and doing an adb push with them, and there are some results:
-Images of 1 GB or 1,5 GB are not created by an error of insufficient space in halium-install
-Images of 2 GB or more are created but when I try to push it to the phone vía adb push (filename) /data it gives me an error of not enough partition size.
I have tried it not only with Ubuntu Touch images, also with Plasma Mobile rootfs and Halium reference rootfs.