Trying to understand the "no space left" issue... Here is the file size: 16.04 Stable (version 23) ubports 356 Mo compr., 1379 Mo extr. device 69 Mo compr., 181 Mo extr. 20.04 Devel (version 146) rootfs 456 Mo compr., 1664 Mo extr. device 88 Mo compr., 227 Mo extr. 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.

@DeadBattery My fairphone 2 works with OTG, version is 16.04 devel, (2023-04-17)

I'm replying to my own post, in case it serves anyone: this bug on the Fairphone 2 is with the newer Fairphone camera module only. So I put the first generation camera module inside (I still had it in a drawer somewhere) and now the phone turns off fine. I don't care much about camera quality on this device anyway.

@Ced You're welcome ^^

@Opolork There are no plans to do anything about Xenial channels for now. It could be the end of the year before decisions are made.

@ultrasonicnoise Hmm ... so if that APN is no longer in the file, then maybe it is not matching the "3" in the name field and so it defaults to what the provider or sim card sets? (I am assuming that is what it uses to match ... ) Sorry, not sure what to suggest from here ... ?? <provider primary="true"> <name>3</name> <gsm> <network-id mcc="234" mnc="20"/> <apn value="three.co.uk"> <usage type="internet"/> <name>3 Internet</name> </apn> <apn value="3internet"> <plan type="postpaid"/> <usage type="internet"/> <name>Internet</name> </apn> <apn value="three.co.uk"> <usage type="mms"/> <name>3 MMS</name> <mmsc>http://mms.um.three.co.uk:10021/mmsc</mmsc> <mmsproxy>217.171.129.2:8799</mmsproxy> <!-- mms.three.co.uk --> </apn> </gsm> </provider>

@keneda I thought so. Thank you very much for confirming.

@lduboeuf I have experienced that also a few times with my fp2. To me it seems like a bug...

@redxxiii Thank you.

@unaegeli next time, just answer after you first try, not after twenty ones and two month. So, did you use UT tweak tool to remove cache and config data? Maybe Ghostcloud only works for Nextcloud instances? As you are mentioning UBsync, did you check logs? Try the the LogViewer App. Maybe its an issue regarding server certificates? You should use a public one like lets encrypt. We could test your FP2 using my personal nextcloud instance. Let me know, if you want to investigate this any further.

@tim The Halium 7.1 is in worse state then the current "legacy" port and it doesn't have stable releases (yet?). Last time I checked the camera didn't work and I don't think much work has been done on it since. I didn't have to install Android when switching from one port to the other. If the instructions don't say you should, I expect it's not necessary, but I could be wrong ofc.

@rjdan I tested with a 34' Samsung ultra wide monitor today. All the same issues as the Asus zenscreen. The UI was surprisingly less pixelated compared to the 15' zenscreen. Is the response time much better with a MS dongle?

Kudos to Tobiyo Kuujikai (@Fuseteam) on UBports Welcome & Install (https://t.me/WelcomePlus) for helping me solve this. The phone was stuck at the boot splash. Get to recovery mode and then run the installer. The installer says 'Cleaning up' , 'Erasing cache partition'. Put it back in recovery mode. Click continue on installer.

Hi @Flohack. Thanks for making Halium. :thumbs_up_light_skin_tone: :thumbs_up_light_skin_tone:

@jezek I have FP2 on Stable channel (so 5.1). I took the charger out yesterday evening to test, it's now a bit over 50%. Wifi was on. I didn't use it much, mostly looking at time occasionally and a bit of web browsing, but not much (maybe couple of minutes total). Two weekends ago I managed to drain the battery in an hour or so I think, but I was constantly using the camera, so that's prob expected. So yes, I'd say it's over 24h battery lifetime (assuming "normal" usage).

Hello, I have solved because the connection problems did not come from the smartphone but from the operator. A website that monitors the performance of operators on the internet confirmed what I said. :cat_face:

Sometimes I use the night clock app. It s a kind of screen saver

@kunai Please mark as solved to help others Thanks https://forums.ubports.com/topic/6311/how-to-ask-a-question-and-then-mark-it-as-solved