I bought my FP5 from the Fairphone website with eos 2.9 T installed.
I tried to install version 3.0.4 A14, but I received the message os system corrupted, impossible to use’.
So I went back to the original version and managed to install another Android ROM (iodé), and I was able to lock the bootloader.
I’d like to go back to EOS.
Thanks for your advice.
Hello,
my mobile data are working as expected too. As you, my IP hiding works but I can’t use internet without IP hiding. I can’t access to some website because they refused IP hiding. I need to be able to use the internet with the exposed IP but this is not the case since e/os 3.x.
Regards.
So it has. That’s a bit alarming. Is something wrong with it?
…I’m in the same position, and about to start using it as my daily driver…
(I don’t think I’d notice if my installation also had this sort of problem, I’m afraid, as I’m planning to run it as an F-Droid based phone and am ignoring / disabling microG, App Lounge, etc as much as possible)
This is not a support thread but as I understand it, the /e/OS build should be equally capable as FairphoneOS to reflash all required partitions.
As said
…
I don’t know about reasons of this vanish or consequences to keep it on a device, but for now I am using it minimally until a full reflash with a new official one.
Merci
Vendor name: Xiaomi
Device name: POCO X3 NFC
Device CodeName: Surya
Previous version: e-2.9-a14-20250323478433-community-surya
New version : e-3.1.1-a15-20250829521741-community-surya
Not rooted
I made a dirty flash. All went well except that App Lounge doesn’t install or update any app. I tried with an anonymous login and a google account.
No problem with Aurora ou F-Droid. So for most applicatons I can live without App Lounge.
Except for one banking app. This app check whether the app is installed by the Play Store. App Lounge has the same app id as the Play Store, so this app accept installation from App Lounge but not from Aurora.
In my experience, App Lounge is the weakest point of /e/os . There are often problems with this app in various releases.
Just realized again these days that one of the single best features of Murena is this one 
No problem updating my FP4.
On the other hand, the microphone during Signal calls (or with phone) is really too low. It’s becoming very annoying on this phone.
I don’t know if there’s a ticket on the gitlab for me to check.
literally have it bookmarked for daily check. 
Posted earlier that on my FP4 I updated, I’m on 3.1.1-Official
I have run into an issue with the “Hide my IP” function, after reading some threads. While my device says “Real IP Hidden” it is not in fact hidden. Sites are detecting my real IP.
Also, I saw a notice briefly on the bottom of the screen “Orbot configuration invalid”
I use another VPN usually, however, I wanted to see if mine was acting like some of the others.
How I seemed to have fixed it, was to
The VPN and Globe indicator came on in the tray, and I tested it with a browser, and received some rando IP.
So maybe that will help someone.
Hi,
I have installed /e/os on a FP6 with an official-FP6 build (version 3.0.4). Now that 3.1.1 is released, Settings>update on my phone doesn’t find it.
Is this normal ?
How can I get the release ?
Thanks in advance.
The v3.1.1 /e/OS release, like all releases is staggered across days in a week. The reason is we support 200+ devices. A simultaneous release of all devices all builds will crash the systems. For some devices we support 3 OS versions, which adds to the number of builds being published.
Also it helps if there are issues with the release then we can pause the release, check the problem and restart the release.
We release about 25% of builds in a day. You can check the updater over the next couple if you release is showing up in the updater. A hack to confirm the build is to tap the updater 6 - 7 times as sometimes the screen may not refresh.
I made several other tests to try to understand the App Lounge problem.
I think that this is related with a communication with a server.
I was able to made different test by forcing the app to stop and by clearing memory and cache.
I had ±20 apps to update. By clicking “update all”, the app displayed some error messages saying that there is a problem related to a “support rule (localisation…” ( the end of the message was not readable). The app also asked continuously to renew the session (each renew failed).
Then, I had the idea to use a VPN and change the country… and I manage to make it work by selecting Andora !
This lead me to think that App Lounge tries to connect to a server which is protected by some kind of network protection which is active for some reason and block some ip addresses / origin.
Another information that may help support engineers: the problem was present for all applications types (Open Source and PWA included), so even apps from F-Droid repository failed to be installed/upgraded.
Hope this help. And again, thanks for the great work and to support so many devices !
Thanks for investigating the problem. In my case the App Lounge for many months usually asks for renewing the session, but in background it is updating the eligible apps. If I want to get rid of the question, I select “ignore” while selecting “renew” will show the question again - not so this morning.
Today tapping on the register “updates” will load some data (the traffic meter in the status bar shows it), but then hangs with a permanent curling. Only a forced termination from apps settings makes App Lounge usable again.
Usually I wait for automatic updates every week or after reboot. After reboot works this morning.
only an Android 13 [e-3.1.1-t-20250828521480-official-redfin.zip] version for my official Pixel5 redfin.
Update went smooth but with e-3.1.1-a14 now the App Lounge will no longer get any response from the Server. When starting the app, looking for categories, searching apps or app updates inside t App Lounge the spinning wheel on the black screen lasts forever without any result.
Already cleared the app cache and also deleted all app data without any feedback from the app.
So installing new apps or updating existing apps is not possible anymore. Therefore this version is not usable.
I use App Lounge with my Google Playstore Account login (to install my paid apps). Using it in anonymous mode did not change the behaviour.
Does any other OP8T user has the same issue?
Ah phew, it’s back now (with the same contents/hashes as before).
(Alongside, for the first time, an official FP5 A15 build – maybe the appearance of that is what caused the glitch – but I’m still avoiding A15 until I know whether it has a problem with the fingerprint sensor.)
I thought locking bootloader was only possible on official builds…
Warning: The bootloader is lockable in official builds only. The procedure to lock the bootloader will not work on community builds.
source