At the weekend I updated iodeOS V2.5 to V3 Over the Air (OTA) with no issues. All my data was intact, only the bluetooth cache needed to be cleared to enable bluetooth. The only extra work was ensuring I backed up my SD Card as Android 12 insists on reformatting my SD Card before I can use it.
A quick update on the iodéOS updater (also posted in the iodéOS forum):
Updated Over the Air (OTA) from V3.0 to V3.1. No data loss, no issues seen so far, smooth update. Used WiFi to download. Biggest imeadiate improvement, which may be a placebo, was the perceived improvement of the quality of the pictures using the Open Camera app. Probably loads of improvements I have just not noticed yet.
Just realized, that sometimes (not always) I don’t receive SMS. I was wondering what might cause this. I checked the APN settings, which seem to be ok. So far I have some possible ideas:
I’m using Signal for my SMS handling, but never tried it before.
MicroG, never had it either installed before. Maybe its not forwarding some specific message correctly?
The problem is especially keeping me from setting up my banking-app, which wants to send me an Login-ID, so that they see, that my Nr is correct…
After a while there is always this message saying: couldn’t send the message. That’s why I think MicroG could be a problem.
My F2 broke in a bicycle accident, so I got the only FP4 in a shop nearby yesterday. On FP2 I’d tried many OS and stayed on LOS. when I came across iodé OS it seemed exaclty what I need. I followed the instructions after one boot in horrible Google android to unlock bootloader. Flashing seemed to work fine, but it took me hours to get to recovery mode:
“Volume up+Power” did nothing at all. For a while I had a loop between boot logo and Faiphones warning message about an unlocked bootloader. From booltloader mode I allways got back to the same mode when I choosed Recovery on the top menu After hours and several times reflashing recovery and erasing everything, I reached recovery mode with executing “fastboot reboot fp4-iodeOS-recovery.img”. All the rest was easy and everything seems to work fine (beside ugly trebuchet launcher).
Update concerning the OEM unlock option:
I did the Update 3.0->3.1 yesterday. Since then it’s possible to unlock the OEM option in delevoper settings again. I did not check it directly before the update. Anyway it’s available again.
Do you think it’s worth resetting the phone and trying to lock the bootloader?
Hi. I saw that Iodé has some really nice things like the ad blocker and A12 and I’m interested in trying it. But I have some concerns. Can I go back to Fairphone OS with no Problems (everything works like google play services) or is that not possible?
Thanks for your help.
You can go back however as Iode uses their own avb custom keys you would have to delete them, and it might make a a bit more difficult… Whatever you do be very careful with locking the bootloader, currently its very easy to brick the FP4… There are several Posts around this here in the forum