I took time to test with the different update channels available and VoLTE works with current 24.04-0.1/daily channel (update 2025-10-19/3).

@arubislander I followed your path (Android 11 -> UT 20.04) and it feels a lot better now in terms of battery lifetime, random shutdowns etc, so thanks a lot for that! The phone call quality is still a bit mediocre but no disconnections and no weird artifacts/noises, so better on this problem too! Thanks for helping!

Hi again, I flashed Android 11 and UT 20.04 after that and I am really happy for now. I switched on WiFi and 2G only, no other connections. The battery went from 89% to 86% within 7 hours, so that is very okay for me. Check! Thanks everyone for helping! greetz Chev Chelios

@arubislander Thanks for the reply. Hardware issue? Could be! The strange thing about all this is that there was no constant deterioration. It was more up and downs. One version worked, then one worked unreliably, then one worked, and with version 1, I appear to be almost completely lost. That's why I was wondering that it might be a good idea to ask here if anybody could confirm a problem - or not confirm it. Had there already been anyone telling me clearly that their Faiphone 4 actually worked with version 1, I would have contacted the shop that sold that new mobile to me lately. ... But I am not the only one that has a Fairphone 4 with UT on it, I suppose? Well, I think I'll wait one or two days more. If nobody replies, I will try another 'daily'-version ... and then report.

@cristodcgomez sorry I was unclear: I have also tried selecting "restart" from the bootloader screen as per your hint above, and that also didn't result in the phone being recognized by ADB. My extra attempt was to go through the recovery menu, which just locks the device when I select the fastboot option. At this point I feel like something went wrong in the UT install that has messed up my phone's ability to access fastboot.

Is it possible to modify eSIMs via apps in Waydroid?

I couldn't really leave it, so I just tried again, and now it worked? I did: Double Checked: Android is version 11 (Build fp4.fp4k.a.179.20230116 $ fastboot flashing unlock FAILED (remote: ' Device already : unlocked!') fastboot: error: Command failed $ fastboot flashing unlock_critical FAILED (remote: ' Device already : unlocked!') fastboot: error: Command failed Checked All three boxes (Including User Wipe)... Maybe you were right, Luksus (and thanks!), that I somehow missed the first check box, but alas, I'm a happy camper.. Regards Grisen

Hi MrRoughwood, Congratulations! And it's a very good decision to start with “stable.” Greetings Mario

Thank you @Keneda !!

@ MrT10001 I’ll wear that badge proudly. @ johndoe Thanks for the advice. I’ll keep it in mind and won’t change anything. @ liam Sorry to hear that. I’m really not an expert. So I can’t understand the issue you experienced with the battery and Postmarket on your device. Perhaps you should try again some time with UT? (Possibly a real expert should say something to that suggestion) With me the installer showed some flaws. I was absolutely not sure about how successful the install would be since it didn’t show anything like “Congratulations! Ubuntu Touch is now installed.” The final screen just showed that formatting was still at work. I could only see on the mobile itself that it was possible to start UT (since there was a reboot and I was asked to define a passkey) and that the amount of free space on the device was big enough to believe that everything was more or less OK. Hope you can still use your device somehow.

@ikoz I think i have found the solution. After allowing outgoing traffic to 188.166.175.79 port 5001 the notifications seem to work. lsof, netstat and a little bit more googling helped me. After disabling ufw; lsof and netstat were showing the IP and port after a notification came in. Port 443 is needed, too. Unfortunately logging with ufw does not work, but who cares, i didn't need it. Thanks for pushing me into the right direction, this warning app could save a life.

Most accounts nowadays force users to use app passwords when using 3rd party apps. Most likely this is what you need.

@nogoogle Bad news... Maybe you'll have to return to Android and test to be sure the hardware has no issue.

@rubencarneiro Can you give infos about that ? You were some time ago involved in doing logos for devices, how can it be done now, someone should fill an issue on device git ?