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.

Hi @thedeafenguy,

So well, you want to get help from a forum that is not responsible, but you are not willing to fully inform people.
Since this forum is about UT, people wanting help you need more info than people on the Fairphone forum, and I still think they could be helped more there.
That means as much info as possible, like, do you have the device first hand, what OS and version was on the device before you got the feeling I could try a bit to put another OS on it. Did you install UT on the device exactly as instructed by the porter? Did UT run flawlessly afterwards? And so on ...

Why don't you ask the FP forum for advice?

So, I don't have a Fairphone or any Fairphone experience, but from what I understand, you must definitely have a newer Fairphone Android OS than what you were using before you installed UT.

And very importantly, after flashing and before booting the device, you should only boot into the bootloader so that you can check the <flag> fastboot flashing get_unlock_ability.
This value should be 1.

After booting the operating system, you should first carry out all other available updates.
Unfortunately, I cannot recommend locking the bootloader, as I simply have no experience with this.

Greetings Mario

Hi @AppLee

thank you for your comments
After some troubles returning to A11, I am back to A11

I would like to deactivate IMS, as you suggest, but the only menu in the settings/dev settings is "IMS settings display" subtitled "debug mode when IMS enable". Didn't find something on the web about it on A11. any advice ?

JN

@tonton_
doesn't work for me (fp4, UT20.04 OTA 5, Free provider), I have tried so many things...I think I have to find another OS. But it was working in 2023...

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

@kevin-lhotellier
You need a code to unlock Fairphone bootloader that only Fairphone can give you.
https://www.fairphone.com/en/bootloader-unlocking-code-for-fairphone/

And follow their process to unlock its bootloader (from step 2).
https://support.fairphone.com/hc/en-us/articles/10492476238865-Manage-the-Bootloader

Also be care that Fairphone 4 don't have the anti rollback protection like the FP5 has before downgrading it, or you could brick.

And if you succeed installing UT on it DON'T RELOCK THE BOOTLOADER, or it's a brick.

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?