I would really like to see a proper nextcloud / owncloud account support for calendars and contacts.

A while ago, i believe Alan posted and you guys discussed that order for UBPorts to switch to wayland, the steps were:

1. Upgrade Mir to a newer version
2. Design the missing Wayland protocols to replace Mir protocol internally
3. Migrate the internal Mir to Wayland

Now that OTA-12 is soon out, and a newer (1.2 - but 1.8 was released recently?) Mir is in place, where are you guys with this project and how high does it rank on your priority scope?

Now that latest mir is almost done (i guess you guys are aiming OTA-9), what is next on your focus list? What's your priority in:

• mainline devices (pine / purism)
• anbox
• full wayland (replacing mir protocol)
• unity desktop
• hidl hardware layer
• whatever cool thing i missed

Do you have any plans to allow CARDDAV to be configured as CALDAV as part of the regular accounts section (instead of using commandline syncevolution)?

I'd love to hear what's in scope for OTA-3, and how things are progressing towards Halium / Xenial.

@sven This at least claims it does: https://archive.org/details/lineage-16.0-20200325-nightly-beryllium-signed

When you do, please check https://wiki.lineageos.org/verifying-builds.html to see if they are in fact officially signed.

On your blog post you've made some statements about the purism hardware that appear to have been copied of the crowdfunding page. In several Q&A sessions and blogposts, purism have however answered questions related to hardware that deviates from that. For instance, in this reddit Q&A they claim dual sim is in the current spec list https://www.reddit.com/r/IAmA/comments/87tbfl/todd_weaver_from_purism_doing_a_reddit_ama/

Could you have purism check the specs your posted are up to date? For me, dual sim is a Big Deal for instance

Dekko has some uncommon options, like under authentication type and force ssl/tls - you should probably try changing those around a little.

I noticed, for example, that GMAIL defaults to "plain" authentication but requires "login" ...

If that doesn't work, please join us at the dekko user group on telegram and we'll try to help!

I am fairly sure you do not need to build anything. The last link Roger posted was a link to compiled images. A boot.img and a system.img
But again no instructions on how to flash other than Rogers comment on using fastboot. I would have thought you use the same technique as the GSI but since he says this is not a GSI I am not sure.

I would simply try flashing them as if they were a GSI but I am currently dual booting to postmarket on a custom Gnome build I am working on and do not want to risk losing the changes until I have my install-able version matching the changes I have made on the phone directly. You can always reflash the phone back to stock and start over.

Yeah, exactly! Please download the system.img and boot.img artefacts from the CI job - CI will do the building for us.

It's not a GSI, and you need to flash with fastboot instead of twrp. IF you're on the right slot ( you can check with fastboot getvar current-slot ), the steps are:

• fastboot flash boot boot.img (flashes the boot.img to the boot partition of your current slot)

• fastboot flash system system.img (flashes system.img to the system partition of your current slot)

• fastboot reboot (reboots your phone on the current slot)

@antidroid said in Halium 9 / CI + OTA build:

@rogier-oudshoorn said in Halium 9 / CI + OTA build:

you have to flash on top of LOS 16, it won't boot on any other base.

I would just like to confirm you actually mean it has to be Lineage 16 and not any other Android 9 version that Lineage is based off of? Or do you just mean the equivalent version to LOS 16? If it has to be LOS 16 can you explain why? If it has to be LOS 16 does it matter which point release?

You'll need to run exactly LineageOS 16, not just any Android 9 version. I presume this is because LOS changed some of the partitions, and we need it to load their drivers, but i'm not sure. I'm running on the latest LOS16, and i suggest everyone does the same.

@sven This at least claims it does: https://archive.org/details/lineage-16.0-20200325-nightly-beryllium-signed

When you do, please check https://wiki.lineageos.org/verifying-builds.html to see if they are in fact officially signed.

@antidroid I found my copy of LOS 16 (for OP6) linked on XDA somewhere; i guess when we'll get to the installer stage i'll likely have fashboot or twrp flashable images for the installer to work with.

@totalrando said in Halium 9 / CI + OTA build:

@rogier-oudshoorn
fastboot flash boot system.img

Yeah, you should flash system.img to system, boot.img goes to boot ...

I am fairly sure you do not need to build anything. The last link Roger posted was a link to compiled images. A boot.img and a system.img
But again no instructions on how to flash other than Rogers comment on using fastboot. I would have thought you use the same technique as the GSI but since he says this is not a GSI I am not sure.

I would simply try flashing them as if they were a GSI but I am currently dual booting to postmarket on a custom Gnome build I am working on and do not want to risk losing the changes until I have my install-able version matching the changes I have made on the phone directly. You can always reflash the phone back to stock and start over.

Yeah, exactly! Please download the system.img and boot.img artefacts from the CI job - CI will do the building for us.

It's not a GSI, and you need to flash with fastboot instead of twrp. IF you're on the right slot ( you can check with fastboot getvar current-slot ), the steps are:

• fastboot flash boot boot.img (flashes the boot.img to the boot partition of your current slot)

• fastboot flash system system.img (flashes system.img to the system partition of your current slot)

• fastboot reboot (reboots your phone on the current slot)

@antidroid said in Halium 9 / CI + OTA build:

@rogier-oudshoorn said in Halium 9 / CI + OTA build:

you have to flash on top of LOS 16, it won't boot on any other base.

I would just like to confirm you actually mean it has to be Lineage 16 and not any other Android 9 version that Lineage is based off of? Or do you just mean the equivalent version to LOS 16? If it has to be LOS 16 can you explain why? If it has to be LOS 16 does it matter which point release?

You'll need to run exactly LineageOS 16, not just any Android 9 version. I presume this is because LOS changed some of the partitions, and we need it to load their drivers, but i'm not sure. I'm running on the latest LOS16, and i suggest everyone does the same.

It's a sideeffect of the GSI - the way forward is to fix the CI images to have a proper 64 bit build.

@totalrando It won't. You can re-lock the bootloader only through fastboot oem. On older oneplus devices flashing OOS could also lock the bootloader, but i haven't see that happen on OP6 yet.

Well, the point of CI is that it builds for you

The architecture thingie is caused by the GSI, the CI version doesn't have these issues.

The GSI build isn't likely to get updates, but there's a build in progress on the regular build track. You can find the setup here: https://gitlab.com/ubports/community-ports/android9/oneplus-6

Status
Essentially, we're looking for developers. The gitlab builds work, and are flashable, but the following aspects are missing / work in progress:

• There's a kernel bug that breaks suspend; right now suspend is disabled (so it'll run through battery quickly) https://gitlab.com/ubports/community-ports/android9/oneplus-6/oneplus-enchilada-fajita/-/issues/2

• Recovery is available, but non-functional (lacks functional ADB). https://gitlab.com/ubports/community-ports/android9/oneplus-6/oneplus-enchilada-fajita/-/issues/3

• Camera app won't start

• Features regular reboots

• It generally lacks polish

If you're interested and capable of helping out, please join us on the discord here https://discord.gg/haVG9Ga

If you're not a developer, the GSI is more stable - but the CI builds feature a more recent rootfs. It's your choice.

How to flash
The CI build produces a boot.img and a system.img As you imagine, they're flashable through fastboot. Be warned - you have to flash on top of LOS 16, it won't boot on any other base.

You can download artefacts from the pipeline, right now this is the last merged build: https://gitlab.com/ubports/community-ports/android9/oneplus-6/oneplus-enchilada-fajita/-/jobs/993648342/artifacts/browse

Hi guys,

• In general, this is the documentation for the GSI that we know works: https://github.com/ubports-oneplus6/documentation. The GSI really only works on top of OOS 9 or LOS 16; you have to have a running android first.

• OP6/6T do not have a seperate recovery partition, which means that installing TWRP isn't very easy. To do this in android, you have to boot it first with 'fastboot boot' and then it knows how to install itself inside of the boot images. This of course doesn't work for Ubuntu Touch. You'll have to wait for me (or someone else) to figure out the recovery setup. Right now, it boots but it doesn't do ADB yet.

• PostmarketOS is a very different beast then Ubuntu Touch; it uses a mainline kernel, open drivers, alpine linux, and really resembles a traditional linux distro. It also doesn't use recovery for updates (it doesn't do OTA, but uses a traditional package manager). Installing postmarketOS is therefor also different (and doesn't require a running android)

Hope this helps!