@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.

@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.

Thank you for your effort, and hints/help. I had only written the initial post in the hope of a miracle, that there would be another way out than asking fairphone support for an EDL to clean the bootloader.;--()) @MrT10001 said in fp4: another brick in the wall: ... If Law enforcement can do it and do it on locked, encrypted iPhones (they are difficult to get into iOS unless you have expensive tools), expect the criminal fraternity to have to ability to do it. I don't have $2k to buy an EDL device, and I certainly don't belong to a criminal organisation, ...damn, now I could use something like that ...;-)lol No I don't have a FP (yet) as they are expensive here in comparison to other devices and from what I have seen agree! But it was one of the most comparable thing I found for linux- and lineage-derivates without PWM. and read have issues that involve sending them back to FP to recover - read here. I should have read this things before!;-)

@Inali Thank you for the effort, maybe this site helped a little bit. The solution i've found is a simple: sudo ufw allow out on waydroid0 to any. I was (and still am) confused about the 2 devices and how they "work" together. Now that i know which interface to deal with i can, of course, precise this rule, but i have another (Android-) firewall in the waydroid container that can handle this.

This issue has been solved by troubel-shooting with the dev Lional. Fix: Prevent app suspension in UTTT was toggled on for "Batter-saver" which caused chargin troubles and the phone keeps a better chage. Thanks for the quick respond.

@mihai said in reflash after installing Ubuntu Touch: UBports installer(0.10.0) (I, ve updated it, first I, ve used a beta version) says: "The device halium_arm64 is not supported" Boot into fastboot mode to solve it. @mihai said in reflash after installing Ubuntu Touch: I think I am in the fastboot mode : "the bootloader is unlocked and ..." That is the normal booting process with unlocked bootloader, not in fastboot mode To enter fastboot mode: Make sure your Fairphone 4 is fully powered off Keep holding volume down and plug in USB-C cable to the charger/computer You're now in fastboot mode Reference: https://forum.fairphone.com/t/no-fastboot-on-fp4-after-ubuntu-touch/96618/2

@Vulpex As the author of that post, I'll be interested to hear whether it helps with audio via USB-C on FP. I've been trying all kinds of things to get audio to switch to USB-C on plugin on my OnePlus 6T, but without success so far It's noteworthy that this issue (or two very similar issues) occurs on two different devices