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

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

@dh297 Just for anyone that stumbles across this. I was actually just having the same issue, and I was using a Linux desktop with ubports-installer, and I still was getting the same exact issue as you. I did however do as Keneda suggested, and installed Android 11 (previously had Android 13). I ran ubports-installer again, and the installation worked perfectly after that. You can find an installation for Android 11 in the link below. https://support.fairphone.com/hc/en-us/articles/18896094650513-Installing-Fairphone-OS-Manually Good news is that it's actually very easy to reinstall Android 11. Your bootloader is probably already unlocked, so I think all there is to do is just download the right Android version that they give, and run the right script. I would do the Android setup on a Linux desktop though. It makes it a lot easier; rather than worrying about USB drivers and stuff. Good luck!

@randomusername Just tried typing Kernal in my FP4. When starting to type "Kernel" I get a row of suggestions. The highlighted one is the one suggested as the most likely fit for the word you are after. If I stop typing at Ke the highlighted suggestion is Keep. Add an r and the high lighted suggestion is Kernel. Try typing High and see what you get highlighted as you type. At this stage I am lost to understand how your FP4 could have been hacked by you installing UT and connecting it to the internet.

Hello @ezst036 I see the same settings as you: 16:9 8.3MP (or 4:3 12MP), and I did not find how to have a higher resolution.

@domubpkm hej thank you for your reply! I tried mitubo again it works. Before i got error codes when trying to watch or download. The last days a few things improved on my fp4! Still figuring out what changed. All in all its gotten more smoothe for sure. So thank you for reminding me to try mitubo again

@MrT10001 What if the computer does not see the device anymore?

@YomenT I had the same issue on a Oneplus 6T and found a way to manual switch audio output to USB-C (and back to speakers). Perhaps this will help? You would need to check which plughw device is USB-C https://forums.ubports.com/post/77157 (Not plug n play though)

Bluetooth on Focal a UT problem. I had this with a Pioneer digital radio. A developer told me to re-pair it several times. The theater was too weird for me which is why I uninstalled. What you can try is to delete the headphones once and pair them again. Calls were established but there was no sound and the described lost Bluetooth signal.

Yes, some like Open Camera can even use all cameras if you device has multiple. In regards to banking apps, there's no assurance they will work, it really depends on the app.

What happens to the device screen? It should display a virtual touchpad. If it does that and your external display at least detects it then that should mean it is compatible. There's a bug right now that wired external display only works once. After the initial connection, it'll just display black. You'll need to reboot to make it work again.

@s710 said in How to revert to Android?: Okay nevermind. Although the bootloader was already stating "DEVICE STATE - unlocked", and every reboot remindst of the bootloader being unlocked, I had to do fastboot flashing unlock_critical (which would ask again if I wanted to unlock the bootloader), and then the flashing tool for FF4 would run fine. Android was successfully reinstalled. Thanks for sharing! This post saved me quite some work.