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

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

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)

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.

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?

@unisuperbox said in Ubuntu Touch Q&A 110 Saturday 9th October At 19:00 UTC:

I've had some really long conversations with people who told me that I should stop using "if you want it, you have to do it yourself" as a default response. I really don't know what else to do though. It doesn't mean the question is bad... I might want the thing someone is asking for more than whatever I'm going to work on this week. But I also have obligations to a lot of stakeholders.

Well, as someone who asked a question that triggered this, I apologize. This is really not what i was looking to achieve, and i guess i should have known better then to ask a question around something this obvious.

@unisuperbox said in Ubuntu Touch Q&A 110 Saturday 9th October At 19:00 UTC:

There is something a bit deeper than that, though. Something that a simple "just stop caring whether you're disappointing people, you can only do so much in a 2-week period" can solve... It's hard to put that underlying thing into words.

Please don't feel bad about your response! It's the truth as you see it, even when it is hard to say. In life, there's no way to please everyone (and definately not the entire internet). Focus on what you think you want and can achieve. Just say no to things that aren't. You may need to politely explain this every two weeks for a while though ...

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?

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