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

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.

While i appreciate all the effort that has gone into Morph, i really do miss firefox - and especially the addblock plugins. The postmarketOS crowd has taken a different path to the browser issue, and that is to skin firefox to make it usable-ish on phones: https://gitlab.com/postmarketOS/mobile-config-firefox

How hard would it be to have this skinned firefox operable in ubuntu touch?

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)?

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!

After dropping my previous phone on the street, wrecking it, i got myself a nice shiny second hand OP6 to have a UBPorts phone. Whilst searching for possible devices, i noticed a lack of reports on the forum on how well the port is - so here goes my review for the OP6.

TL:DR;
You can daily drive it if you have to. Notable problems are lack of sleep mode (so you're going to have to charge it overnight), and that the camera crashes immediately (which i can live with).

Mobile data, both sims, bluetooth, wifi etc all work.

How to get it
Please check here: https://github.com/ubports-oneplus6/documentation
There's a discord group referenced, joining there will allow you to ask questions about OP6 and OP6T.

Longer review
First off, the OP6 is a nice piece of hardware. Fast chip, good screen, decent battery, and a headphone jack. It plays out well running ubports - it's very smooth (much better then my old BQ), and even without sleep functional it'll last you the day easily.

Stability wise, it's pretty OK. So far i've seen one spontaneous reboot per day. Keeping many apps open is no issue at all (including a 10-tab morph). Some apps (Futify for instance) do disappear - but i assume that's because of Futify. Also, very important, I haven't missed any calls yet.

Looking for the future, with the GSI not getting updates anymore, I'm looking forward to getting a "real" OTA-able phone setup. I'll post some more when I have been able to drive it.

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 needs "full system access" because it runs a service in the background that's not suspended. This is the only way to attain that permission (for now) sadly. This service checks your mail every X minutes, so it's kind of important.

For reference, you can find the sourcecode here: https://gitlab.com/dekkan/dekko

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

@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.

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)

@3T_Ed There's, as usual on todays internet, a lot of things wrong in that article. It seems written by a pro-purism guy, grabbing arguments left and right without a lot of actual fact checking. For instance, he claims ubuntu touch has received only 26 commits since canonical left - which is not only plain wrong but a very easy thing to actually verify.

It works! The latency is actually very good, but in general the experience is buggy:

• Not every connection attempt succeeds
• It randomly breaks every now and then
• The launcher is usually gone at reconnect (it only shows when you tickle the top menu)
• My 16:10 desktop screen looks stretched (it probably pushes 16:9)
• Lots of papercuts in the desktop environment / apps, such as mouse scroll wheel not working everywhere, certain apps (such as morph) being slow, top menu resizing / only showing what it would show on a phone screen, etc

Is there anything you'd like to me expand on in a ticket on gitlab, and attach certain logfiles?

I've seen a lot of talk about Halium flash by; is there any overview of the Halium ports already available or being worked on?

@Lakotaubp OP6 is an A/B phone, which means it has 2 boot partitions and 2 system partitions. Dual booting this phone is a matter of telling it to boot from A, or B. It does certainly have problems - for instance, and android update might decide to install on the other side, overriding your ubports installation - but it's plausible.

@totalrando You can simply decide to keep your phone on "A" and just boot ubports, ignoring the other side. On your second question, please don't manipulate phone partitions. They aren't like laptop partitions, and messing with it can easily hard brick your device. I'd recommend you just keep them as is, run ubports, and maybe one day, we can do seamless upgrades using A/B as google once intended.

Maybe, if you know exactly what you are doing, you'll be able to pull it off. But I'm not nearly qualified enough to try, nor to tell you to do it

I have a microsoft wireless adapter - not sure which one though. I'll create tickets if i know which repo and what logs i have to attach.

@antidroid said in [Halium 9 / GSI] using the Oneplus 6:

Does anyone have a timeline for when a newer GSI will be available for testing? Or better when the 6/6T will get UBports installer integration and OTA support?

@totalrando said in [Halium 9 / GSI] using the Oneplus 6:

@antidroid I'm not totally sure there is a set timeline: I think basically someone needs to upload a recovery image and then basically submit it for inclusion. With the update you mentioned, it sounds like 6/6T are right around the corner for inclusion. Sadly, I have yet a few days to wait for the power of the FAJITA.

The switch to an OTA based build (that you can flash with fastboot) is work in progress. I've got a recovery booting (but lacking adb and there's mountpoint issues), and there's some associated issues with the regular boot now as well.

Please find us on discord or telegram if you think you can help