IodeOS bugs on FP5

Hello,
I use Iode OS (currently version 6.5) on a FP5, and it has many unusual bugs since the last release.
I wonder whether it is

  • specific to my device/installation ?
  • due to FP5 or IodeOS 6.5 or FP5 + IodeOS 6.5 ?
  • do lineage OS and other forks have the same issues ?

If you use FP5 with Iode OS or another OS, do you have these issues ?

Thank you in advance for your answers

Best,
T.

What issues? Can you name some of them?

2 Likes

Thank you for your answer !!
Here are some bugs

  • Unvolontary rebbot when I turn on Bluetooth
  • cannot install apps in private space
  • cannot reinstall uninstalled preinstalled apps
    I sm waiting for Iode support answer

I think that ic there is a bug, I will install the “official android” and I will turn back to Iode when corrected
Thanks again
Thomas

Actually I don’t know how to diagnose where these bugs come from
Maybe a good idea could be to try another OS to see if there is any change ?

I can’t comment on the second issue but I don’t have the other issues on CalyxOS here.

Thank you @beedaddy
I think I will give a try
May I ask a question : I think that in case of Iode, the bootloader remains unlocked, whereas in case of Calyx OS it is relocked
Actually I don’t know exactly what is bootloader (the system that load boot, probably…) but does that make a difference that it is locked or unlocked ?

No you can lock. Only with LOS you cant lock the FP bootloader. With the other ROMs e/OS, Iode, Calyx you can relock

You mean Iode Os by LOS ?
Thank you for this information
May I ask what is the difference between locking and unlocking

No I mean Lineage OS and it does not support to relock the bootloader, while the others do

Thank you for the precision,
What are the consequences of relocking or not ?

  • relocking causes a factory reset, so all data on the phone is deleted
  • locked bootloader means no one can flash SW using fastboot into any slot without your knowledge when you give the device out of hands (at least you’d notice the deleted data caused by a necessary unlock for flashing)
  • if you disable “OEM unlock” in addition (in developer settings) then no one (e.g. a thief) can reflash your device without getting into the user mode (and a factory reset will AFAIK trigger the factory reset protection and lock the device to the currently signed in Google account). So it might render the device into a brick for a thief
  • :exclamation: locked bootloader may lead to a hard bricked device when doing some kind of OS downgrade

Thank you for these information :slight_smile:
@beedaddy I eventually installed CalyxOS, and it is fine
Except that, like on IodeOS, the only camera app recognized by the messages app is the default one
com.android.camera2
Maybe it is the same for all the forks of LineageOS ?

Besides, as for IodeOS, WhatsApp notices that I use a custom rom, and CalyxOS device can only be used as a companion device. I don’t know whether there is any way for spoofing it, I am going to have a look at CalyxOS documentation
Thanks again

Sorry, I didn’t know about the WhatsApp issue (I don’t use it). But I’m surprised… Other messaging Apps seem just to work (Threema, Signal, Element, …).

Indeed, it seems specific to WhatsApp
I only use Signal, and WhatsApp
Signal runs normally

Hi @Volker

 Can I pitch in here?

I have the same problems as @Thomas75015 with iodeOS, see here Weird WLAN/reboot/SIM problems with iodeOS on FP5 (fairphone 5) - Apps & Core Settings - iodé community

Now I do not dare to switch back to /e/-OS, since the security patch level of my phone with iode is “5. Mai 2025” and the security patch level of the current eOS is “2025-05-01”. (Install /e/OS on a Fairphone FP5 - “FP5”)
Or for the “stock OS” doesn’t even mention a security patch level, only a release date.

I left my bootloader open when switching to iode OS

Can someone tell me how to get back to some other OS without bricking my phone due to the antirollback trigger?

Cheers!

This is what confuses me, @ThomasM seemed to switch to some calyxOS .
Did you (@ThomasM) check witch the security patch level, or did you not care and were you just lucky to not roll back by accident?
Or did it just not matter and even a roll back is possible?

Thanks

At least, I found out, why there are two patch level dates in may 2025:

https://source.android.com/docs/security/bulletin/2025-05-01?hl=de#Common-questions-and-answers

Or for June the same:

https://source.android.com/docs/security/bulletin/2025-06-01?hl=de

Android seems to release to patch level dates on first and fifth of the month.

  • IodeOS decided to use patch level 5.5.2025
  • e-OS seemed decided to use patch level 1.5.2025
  • stock ROM from FP website is unclear, only says

Version: FP5.UT2Q.B.125
Release date: 23 June 2025

Don’t know the patch level from this info

Thank you @Tobias-ix
Actually I don’t know what is a security patch, nor what is a roll back…
Besides, I am French, and not totally fluent with these technical terms
Thanks again

At least I found out that the patch level of the latest stock ROM is 5.6.2025.

Someone at /e/-OS explained it to me: here Vendor Security Patch Level (SPL) in Fairphone 5 - #17 by sophimae - Fairphone - /e/OS community

1 Like

Just leave your bootloader open (unlocked) when installing /e/OS as you did with iodèOS. Then the patch level is irrelevant and you can’t brick your phone.

1 Like