Hello,
I recently saw that a e/OS based on Android 12 is availble for the Fairphone 4.
If I understood the documentations correctly, I first need to install an Android 12 based stock firmware before I can install e/OS S.
But Android 12 stock does not exist yet for the Fairphone 4.
So how to proceed?
So, If I am using e/OS R, I have to flash back to the stock Android 11, to flash e/OS S (and have to reinstall all App and restore all data and settings)?
Did you bought from Murena Store? If you did, you must have 1.5 r stable. In that case, just refresh your update page in Definitions and youāll get the upgrade.
Ah, dev versionā¦ Me too I have an FP4 from Fairphone shop, but after I have installed eOS stable version. I think that migrate from dev to stable need a total refresh of the system. Or maybe just deactivate the option, but now I donāt find where this setting is.
You need to search in the forum to inderstand if dev version will have OTA upgrade.
Iām also an end user, thatās why I bought my FP4 from Murena store. But since then I learned a lot reading the documentation and I feel confidente to make simple things like sideloading. I really hope you find the answers and help you need.
Cheers
Me too Iām not a technician and here we are a bit off topic, I think. There are many threads about FP4 and eOS, in this forim and also in the Fairphone forum itself.
Said that, if I remember rightly (Iāve installed eOS on my FP4 months ago without problems), the security patch level is important if you want a loocked bootloader (and consequently have working SafetyNet, banking/tracing/identification apps). In that case the level as to be the same (or eOS had to be higher).
In the end, I suggest you to not install a higer version of o.s. eOS for FP4 had an OTA upgrade from R to S so you could get it after the migration to eOS.
I have a FP4 which I did not buy from Murena. Nevertheless, was able to upgrade to 1.5.1-s via OTA (the possibility showed up after manually searching for new versions). All went smoothly, just for the fingerprint sensor to work I had to restart a 2nd time.
Hi @confu, I am sure that it will be worth the wait !
I notice that you have joined a thread with the title Update FP4ā¦, while you are quite rightly trying to get good information about an install ā other contributors have mentioned Upgrade as well as Update ā I mention this because this use of language may get adjusted by machine translation !
Perhaps be aware that /e/OS in S is still very new ā¦ speculating you may be be one of the first to do a new install of /e/OS - S - on a Fairphone 4 !
Also I believe the Install and Upgrade pages which you have linked are in the process of being updated to reflect the new situation.
Hi, I have a FP4 (bought in a Orange shop) on which I installed e/OS myself last January.
The upgrade to 1.5.1-s went fine and smoothā¦ but I have serious trouble with the Wi-Fi now.
More precisely, I can connect to any network, but I can access the web only for a few minutes, after that Iām the dark.
I am then connected without having access.
To get it work again I have to reboot (disconnect/reconnect does not provide me internet access).
The biggest downside of it being that it drains my battery in a few hours if I donāt disable the Wi-Fi.
I tried on different networks (personal and professional) and the behavior is the same.
My question is: is an upcoming update fixing this?
Thanks!
ā¦ but @confu, I try to say this in the nicest possible way ā¦ this is the Update thread !
I can quite see that translated you may see yourself āupdatingā your new Fairphone ! but others here are Updating /e/OS or Upgrading their Android version.
You are doing an Install as I know you know !
It is pedantic, but on the forum we try to be a bit flexible but use each of the bold words as accurately as possible.
I am looking forward to hearing of your reply from the helpdesk, that will be safe !
Iām having the same problem. I can reset all wifi and connectivity and get internet for a few minutes, but then lose it again. I canāt remember which build i updated from originally though unfortunately, but i did update to 28 Oct and that worked fine, it was the 2 nov build that has caused the problems for me.