@Vlad-Nirky Sorry for the late reply. I tried to follow the steps of post #2 but I couldn't complete them: stop network-manager sudo systemctl stop network-manager Failed to stop network-manager.service: Unit network-manager.service not loaded. /etc/init/ofono.override sudo /etc/init/ofono.override sudo: /etc/init/ofono.override: command not found

I had the same issue. The solution was simple. When i received the phone there was Android 13 on it. I had to downgrade to Android 11. Do this (yes all data will be lost) https://support.fairphone.com/hc/en-us/articles/18896094650513-Install-Fairphone-OS-manually an then ubports installer again with ubuntu touch Then mobile data works fine

@nicoladastra eSim is currently work in progress, but as Kugiigi mentioned it might work in some cases...

@Papa-Emeritux Not related with Android 11. I had the same issue with an UT device running Focal. I reflashed with Noble => Fingerprint didn't work. I flashed Android 13 without doing anything except turning on the developer mode. Then used the installer. Boom, the fingerprint worked. I guess flashing Android erase the registered fingerprints. And with preexisting fingerprints, a fresh installation of Ubuntu Touch does not work...

I made some tests. Data works perfectly with 3G (on the same phone). Definitively a problem with 4G and Free operator (France).

@stanwood well, thanks. Maybe the porters can do it within a new update. I don't want to risk to much. To use fastboot in linux is fine with me, but it should be safe. Otherwise its ok like it is and thanks to all (su)porters of the FP4, it's a nice device.

I was able to boot into bootloader by long pressing power + volume up buttons on the Fairphone. Afterwards UBports installer was able to find the device and install UT OTA-8. So everything runs fine again. Thanks so much

It's been awhile since I've used the installer, it surely has changed since then. Thanks for the hints.

@gandalf and at all, thanks for your informations and tips. I am using it now and works fine. I just need firefox sometimes, so battery drain is no problem for me.

@kugiigi said in is 5G already supported on Fairphone 4?: Even 4G is gone in your place? It depends on the operator. Sure there is one having solid coverage of any signal anywhere around, but it costs 4 times more. I don't miss the slow pre-5G access anyway.

@stanwood I totally agree with you in terms of connecting audio headphone with Type - C. I have tried connecting it while using Android OS and it was working normally. The same headphone did not work at all while using UT 20.04. Only 3.5 as well blue tooth headphones are working properly. Looking forward to take this issue into consideration and be solved with upcoming updates. Thumbs Up.....

@MrT10001 Thx. That's it. I always tried to push the power button, too.

@Vulpex Sure, because restarting Lomiri would clear up a lot of stuff, no true reboot would be needed most of the time.

@janmv I'm glad to hear your good news! Well done, and I hope you'll enjoy Ubuntu Touch.

@elysian893 I guess you did install UT yourself? To do so, if I'm right, you first have to revert back to Android 11 before installing Ubuntu Touch. The reason is that the device has been ported on Android 11 and thus it needs specifically those vendor firmware from Fairphone. If in the meantime the device has been upgraded to A12 or 13, then there are large chances that you will get issues on the general use.

A pity. Than i'll have to deal with that and re-enable it after every call.

@Keneda Just a few 2 cents her: Yes for porting we often set the Android build to build a so-called userdebug image. That ensures certain behaivour, but I am unsure if we really need that. So it could be that the FP4 kernel built during our porting build is set to debug since userdebug target is being used. Someone could explore this by trying to build their own port with instructions from porting group and then see which flag is being used. It would be good to finally address this, since debug kernels are potentially slower than release.

@bbiw One way to improve the documentation is writing down everything you learn and contributing that as documentation. In that way slowly the documentation situation will improve.

@DrPi Same thing happened to me. I fired up my Pixel 3a after being off for a long time. Running OTA-4. Checked for updates, found apps to update but not OTA-5. Following your suggestion, I switched from English to UK English. It then found OTA-5 immediately and is now updating.