[Porting] Call for Testers
FellFromTheSky last edited by
forgot to say that for some reason I don't know, the smartphone automatically start to the android bootloader (the one with the robot), after being powered off.
@fellfromthesky uh thats a though question, in principle yes. But if you do so, and you would ever have an issue with Ubuntu Touch that prevents it from booting, you could never access your data again so we do not recommend this under all circumstances.
The problem is less visible for Android phones where the apps save most data in the cloud, and also cloud backup is possible. But we are simply not there yet to support such options.
FellFromTheSky last edited by
I'll let the smartphone as it is right now until the official release.
Hey, I have a Pixel XL and am 100% willing to test! My Pixel is fully functional and I have plenty of spare devices.
@yagya Thanks! Unfortunately neither of them has recovery working, and this blocks us a bit for making a wider test. I will come back as soon as we have solved this.
I just installed Ubport on my Google Pixel XL Marlin and for now I did not see any problem!
I have a Pixel with 25.11 GB free space.
But with Android 10
May I help testing ?
Hi guys, just an update, I am trying to solve the puzzle of Pixel/XL having a too small system partition for our installer. I am near a solution, but need a bit more time. Before thats solved more testing makes on sense since that problem would be a major blocker for that device. So, sit back and relax, I hope to come back with an installer config soon
And BTW also SIM card is not detected so Pixel is really in early state only.
Hi there @Flohack , I've recently flashed my Pixel XL and am quite happy with the result thus far, hoping to do more testing for you when a new revision is available!
Any update on the progress on this device? Cheers!
@daereth Yes, unless I can solve the automatic install there is not much progress. Currently system partition is too small. I try an alternate way of loading the rootfs, or b) we could repartition the flash.
I am not sure if repartitioning is something we oculd be happy with though.
cregox last edited by cregox
i want to test it, but not read this whole topic. where should i start?
@cregox uh yes install instructions were stored in a pad but this got obviously corrupted. I will clean them up. Please standby until you find my sentence "Update 19.08.201" on top, I start right away
The pad is here: https://pad.ubports.com/p/HaliumHowToTestInstall - and you can guess from its current state that its better not to follow those instructions
Unfortunately the device cannot be released into the installer as it has a too small system partition, but we are working on a solution for that.
@flohack It seems the images have been removed from the nextcloud server, which is too bad, because your halium-boot and vendor images were also working with droidian.
I've been struggling to build and package the kernel myself, but your images work.
If you get a chance to rebuild, would you please add waydroid support? All you need in your defconfig is
.I have it working on my bootimage, but it has other problems.
@preflex Mobile data was also working on droidian with your halium-boot. It's really flaky though. I'm not sure what the trick is to get it to connect.
SMS was also working.
Voice calls would connect, but no audio.
Everything else seemed to work.
I have Nexus 6P just flashed with OTA-18, would love to help in testing
@preflex I can put them up again but they were heavily outdated you are better off loading them from here: https://ci.ubports.com/job/UBportsCommunityPortsJenkinsCI/job/ubports%2Fcommunity-ports%2Fjenkins-ci%2Fmarlin-sailfish/job/main/ - you can use boot right away, and vendor is inside the tar.gz file on the same page.
With that you always get the latest possible versions.
@flohack Curiously, the newer boot.img just bootlooped when trying to load droidian.
When building my own kernel based on your repo, I had problems with the dtbs. After patching in the dtbs from your old kernel, i was able to get it to boot (and get waydroid running), but had no wifi.
@preflex Strange. I did only one commit on the kernel config lately:
Maybe those SELinux changes are doing that? It seems to work for UT.