I would like to say thank you in between, that sometimes comes too short. I have been using the FP5 as a daily driver for some time now and apart from the points mentioned above (e.g. video recording/playback, battery drain maybe due to esr91, problems sending/receiving SMS and missing torch) it really works great!
Incidentally, videos work in the browser, e.g. at spiegel.de and also on youtube.
So a big thank you to you for all the time and effort you put in to give us the port!
I checked a bit what could be causing those coredumps and I suspect both udisksd and pulseaudio (and android.hardware.audio.service-fp5) only happen when those services exit. I included all of the so far done fixes for ngfd in my build which could help with those ngfd a bit but might not fix all of those yet. Not sure about those others yet but at least I will do some bluetooth testing to see if I can see those crashes myself.
Regarding my unability to connect to WiFi: I visited three cafes offering free WiFi during the last time. One had a WiFi with a captive portal and I was able to connect, in the other two I couldnāt connect (donāt know if the had a captive portal).
Missing flashlight support for FP5 will be included in next release, one package was just missing so I included it to be installed.
jolla-settings-system-flashlight ? Can it just be installed today manually?
Yes, it can be installed manually if already needed
How would you feel about the black camera spot on the upper end of screen (of FP5)?
I guess it doesnāt bother so much with the notifications and so onā¦
Itās not particularly pretty, but it hasnāt bothered me so far. Nowadays, most websites have headers, and I just donāt push the content all the way up on those that donāt (or on apps without headers). Iāve never had a situation where critical information was hidden. Of course, that doesnāt mean that these situations canāt occur.
EDIT: notifications are shown below the hole.
Hello!
Iām testing Sailfish on Fairphone 4. 
Installation script on Windows failed miserabily because it claims my device is not unlocked, even if it is.
Looking at the code in flash-on-windows.bat the instruction is:
:: Check that device has been unlocked
@call :getvar secure
findstr /R /C:"secure: no" %tmpflashfile% >NUL 2>NUL
if not errorlevel 1 GOTO no_error_unlock
On my unlocked phone:
fastboot getvar all
(bootloader) unlocked:yes
(bootloader) secure:yes
So I modified the script to look at unlocked instead of secure, as it is already done in the linux script flash-config.sh
"getvar_fail_if unlocked no"
Corrected code is:
:: Check that device has been unlocked
@call :getvar unlocked
findstr /R /C:"unlocked: yes" %tmpflashfile% >NUL 2>NUL
if not errorlevel 1 GOTO no_error_unlock
Thanks for finding that issue, it seems I had forgotten to fix the windows flashing scripts on both fp4 and fp5. I fixed those now and the fix will be included in next release.
Hello!
I made a try for Waydroid on Fairphone 4 (SFOS installed onto Android 13 factory).
I followed the guide you mentioned, then I had waydroid-runner which closed the Android session as soon as it opened it.
I connected my PC with SSH (easier for me to debug) and typed waydroid log, it gave me the error
dnsmasq: failed to create listening socket for 192.168.240.1: Address already in use
which corresponds to the last section of the guide (Troubleshooting):
devel-su systemctl disable --now dnsmasq
devel-su systemctl restart waydroid-container
The solution worked.
Now the waydroid-runner is stuck at āWaiting for Android UIā.
Log are reporting in loop:
(010469) [12:53:44] Failed to get service waydroidplatform, trying again...
(010469) [12:53:45] Failed to get service waydroidplatform, trying again...
Iāve done some research on the web (1,2,3,4,5,6,7ā¦), but havenāt found a working solution yet.
There is a kernel fix in 5.0.0 build for FP4 related to containers, not sure if that affects also waydroid.
Did anyone succeed in running waydroid on FP5?
Sailfish OS 5.0.0.62 alpha2 releases are now available for FP4 and FP5. Update instructions and changelog added to the initial post in the thread. FP2 will get the update later after I fix the broken WLAN in it when using 5.0.0.62. I will try to finally get the VoLTE issues solved soon, and also the WPA2/WPA3 mixed mode WLAN issue still needs fixing.
It works like a charm, so smooth and all works very well! 1+ mal
And thank you.
The only thing that doesnāt work is Waydroid. Maybe one day youāll fix this or have an solution.
Waydrod Lineage version is 18.