My question:
Is the halium-7.1 UT build for FP2 that was set-up during the live-porting-session could be made available for enthusiastic FP2 testers like me ?

Hello ! I just finished watching the Live-porting session of Halium on FP2, this is awesome to see the process behind the scenes !

I get a little lost on the kernel-backporting part, though

Is it possible to test the new image on my FP2, and how? I'm really curious how the new halium-7.1 port change FP2 stability...

@jjurgen @elastic Hello friends and nice Sunday I watched the Community Update 21 and the team was asked about a possible support for a multiboot solution (minute 40 in the video). They answered that this is already possible with kernel patches but it is difficult to maintain. As they are focussing on Anbox for the "Android apps one cannot do without" they hope multiboot will not be anymore necessary...

However, on the comments below the video, user Martin Kozub said the following:

Just as mentioned in the video dualboot with Android is possible but it can even work with the regular Ubuntu Touch recovery. See this manual for MX4 (but it should be possible to adapt for any device) https://iubuntu.cz/dualboot-mx4.html

Today in Youtube suggestions I say this "pre-UBports" video, showing an elegant dual-boot app on a Nexus device. Installation instuctions can still be found but as the repo was last updated in 2014 I seriously doubt this can help us somehow...

Hello ! That is a good experimentation, and having a working multi-boot can be a great added value

From the Fairphone forum, it seems that the order of installation could be crucial! Quoting @z3untu :

It 100% doesn’t work as a second rom right now. It could maybe work, if you install EFIDroid (from Android), create a second rom (from Android), flash Ubuntu Touch (via recovery/fastboot), put the boot.img from Ubuntu Touch into the correct location (don’t know where right now), flash the boot.img from EFIDroid and then theoretically it could maybe work.

Ubuntu Touch as a secondary rom isn’t supported yet but I meant that it might work as the primary rom.

Thank you ! I converted it to "DAV.RST" and proposed a commit https://github.com/ubports/docs.ubports.com/commit/d4e2bbb77e9a4a0d59f9a5d0916eada74ac84155

Does it need to be validated by someone ( @UniSuperBox ?) to appear in the doc?

Hi !
Half year ago I did a wiki post on carddav synchronisation.
Now the wiki redirects to the docs.ubports.com, this wiki page is not anymore accessible...
Is it possible to access the old wiki, so I can convert the article to RST and commit it to the docs?

Thanks,
Olivier

Thank you for your answer, @WLBI !
I find quite funny that Ubuntu needs a Microsoft device for convergence

Anyway, as you also first tried with an incompatible device, it seems that the protocol is not as universal as I initially tough...

Hello !
To try convergence on my FP2 I bought a HDMI wireless dongle with a button to switch between two modes: Miracast and DLNA.
I plugged it on a TV, connected my UbuntuTouch FP2 device to it remotely. The dongle appeared in the available external displays. Once selected, the screen on the TV became black (instead of the dongle's welcome screen) and the screen on my FP2 grey with a message "you can use this touchscreen as a pointer".
Waiting a couple minutes didn't change anything, the TV screen remained desperately black...

What is funny it that I decided to take a screenshot (vol +& vol -) and once back in the "smartphone mode", I opened it: the image show the desktop of a big screen, with my UT apps displayed! So somehow UbuntuTouch was able to switch to "convergence mode" but not to correctly send the signal to the dongle...
How can I debug this?

Best regards,
Olivier

Note: I didn't connected any wireless mouse/keyboard, is it necessary?
Note2: I tested both Miracast and DLNA screencasting on LineageOS and it worked, so the dongle is not defect.

I posted a commit for updated installation instructions