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
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.
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
@tera Ok thank you, I found the solution 
Putting Firefox in "Dark theme" (about:addons -> Themes -> Dark) did nothing, but adding ui.systemUsesDarkTheme = 1 in about:config did the trick
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...
I posted a commit for updated installation instructions
Trying to understand the "no space left" issue...
Here is the file size:
16.04 Stable (version 23)
20.04 Devel (version 146)
When 16.04 is installed, the extracted size ( 1379+181 = 1560 Mo) corresponds to this partition:
df -h
Filesystem Size Used Avail Use% Mounted on
/dev/loop0 2.0G 1.6G 241M 88% /
What I don't understand is why 20.04 installation is failing; while the extracted size (1664+227 = 1891 Mo) should still be inferior to the 2 Go partition size... 
EDIT: I made a trial on my computer. Decompressing both rootfs and device tar.xz on an empty ext4 image file, the used space is 2,041,232 Kb; so more than the phone partition size!
There is not enough free space on the partition to hold the data. The deficit is about 170 MB.
Hello !
This message just to inform you that Chris Hoffmann (main porter of LineageOS for the FP2) just proposed us to test a newer kernel (3.4.113, compared to 3.4.0 on official FP OS) on this topic of the fairphone forum.
As Marius always say : new developments benefit to all OS, so I'm wondering if this newer kernel could benefits to the UBports project?
Could it be safe to try it "as it is" (boot.img) or is it unlikely to work?? (e.g. if some specific patches are needed for UT?)
/!\ I didn't tested it on Ubuntu Touch - proceed at your own risks /!
Olivier
EDIT: source code is here (I think this branch)
Trying to understand the "no space left" issue...
Here is the file size:
16.04 Stable (version 23)
20.04 Devel (version 146)
When 16.04 is installed, the extracted size ( 1379+181 = 1560 Mo) corresponds to this partition:
df -h
Filesystem Size Used Avail Use% Mounted on
/dev/loop0 2.0G 1.6G 241M 88% /
What I don't understand is why 20.04 installation is failing; while the extracted size (1664+227 = 1891 Mo) should still be inferior to the 2 Go partition size...
EDIT: I made a trial on my computer. Decompressing both rootfs and device tar.xz on an empty ext4 image file, the used space is 2,041,232 Kb; so more than the phone partition size!
There is not enough free space on the partition to hold the data. The deficit is about 170 MB.
Hello!
I noticed that a Focal 20.04 devel channel is available for Fairphone2
It was announced in Q&A 139 and discussed again in Q&A 145
Note that the installer shows also a "utnext" channel but this one is empty.
I tried today the installation with the UBPorts installer and although the installer says OK, the update fails on device...
Here is the last lines of /lcache/recovery/last_log:
Formating: data
Applying update: rootfs-667574dc2fe9dfc34749223cd8e4c79d16c281c877e5085dbb08d30fa80c8ba5.tar.xz
Applying update: device-62de4f47c45b06d837264a7300848242e6310a928e58c24d2cef022c9aaa4335.tar.xz
tar: write error: No space left on device
Update faled, please reboot and try again...
@jezek I guess you've found the answer by now, right? Just in case, I noticed today that there is a channel 16.04 and 20.04 for FP2 in the Ubuntu Installer, and a utnext channel as well.
Hello!
I listened to Q&A 121 and one of the outcomes was that Focal support is likely to devices with kernel at least 3.18, and unlikely below.
I'm curious to know how many of the 87 supported devices have kernel above 3.18, but I don't know how to find current kernel version of the ports...
With my two own devices I did 'uname -a' and found out that
Is there this information available for all others devices?
Is it written somewhere in source code or devices-specific manifest?
@tera Ok thank you, I found the solution
Putting Firefox in "Dark theme" (about:addons -> Themes -> Dark) did nothing, but adding ui.systemUsesDarkTheme = 1 in about:config did the trick
@jezek said in Halium 7.1 Test Channel:
@Flohack As @TobsEnd claimed, there is a lineageOS for FP2, so it would make more sense to skip the 7.1 and go for 9 instead. The Waydroid project, which works on halium 9 looks very promising.
Is it even teorically-possible to run Waydroid on (hypotically) Halium 9-FP2 ?
From this post I read that (as Waydroid is based on Treble) a phone with android 9 as base (for vendor partition,...) is required 
(I hope I'm wrong )
Hello!
Unlike Marius that never sleep , I heard in Q&A102 that with Documentation in dark mode, Yumi goes to sleep: :sleeping_face: 
[...] he completed his work on the Documentation theme. The layout is easier to navigate, as it adopts some conventions which are well established elsewhere. It also now has a dark theme and in that theme Yumi goes to sleep, which is cute.
But it's not clear for me how to put docs.ubports.com in dark mode, how do you do that? I tried navigating from a webbrowser in dark mode but nothing changes...
Cheers,
Oli
@007fred50 said in Fairphone 3 (FP3):
Nice it works now ! thanks
Hello Fred! So you were able to downgrade your FP3+ to Android 9 then install UT GSI; and Ubuntu Touch is working on FP3+?
If that is the case it's nice, it means we can develop a unique image for both FP3 and FP3+
Hello !
This message just to inform you that Chris Hoffmann (main porter of LineageOS for the FP2) just proposed us to test a newer kernel (3.4.113, compared to 3.4.0 on official FP OS) on this topic of the fairphone forum.
As Marius always say : new developments benefit to all OS, so I'm wondering if this newer kernel could benefits to the UBports project?
Could it be safe to try it "as it is" (boot.img) or is it unlikely to work?? (e.g. if some specific patches are needed for UT?)
/!\ I didn't tested it on Ubuntu Touch - proceed at your own risks /!
Olivier
EDIT: source code is here (I think this branch)