An affected user should Report an issue. Seems many new users are affected.
In the above link please see the paragraph about new users with login difficulties. If affected please come back here and ask in the open forum for an Admin to message you privately in order that you can provide ID.
Direct FP6 link FP6 Issues · e · GitLab.
Just installed /e/ on my FP6 (3.1.2) and mobile network is dropping every second. Locked my bootloader so I can’t even go back given that the security patch on /e/ is higher…
@aibd reporting it on Gitlab doesn’t work since they don’t accept gmail for registration.
…
The Report an issue page has instructions for this case.
Pinging @Manoj while you re-read 
.
thanks. I filled out one and someone did so as well a few minutes before me:
at this point, the phone is pretty unusable with SIM enabled at least for me as it starts heating up. Hopefully they fix it soon.
Have you tried to fiddle with the APN settings within the sim settings?
https://community.e.foundation/t/mobile-data-issues-on-fp6-e-3-1-2/74510/9?u=anotherelk
Different phone, but why not …
Could this be a solution to my problem?
I know absolutely nothing about this procedure, so I would need some help if it happens to fix the issue. Thanks 
Any provider to be taken seriously has a guide for this online, search the support area of your provider for apn or for the guide to configure mobile internet on Android.
Settings in /e/OS should be at Settings - Network and internet - SIMs - Access point names.
The 3 dot menu there has Reset to default.
everything seems correct. I also tried moving it to 2G/3G but it’s the same issue. The entire SIM card seems to drop and even calls and SMS struggle.
now getting Selected service unavailable.
According to other people, this seems to happen because latest build doesn’t seem to fetch the IMEI correctly.
I think it keeps failing because the same IMEI is being published by multiple people on the network, leading to disconnects, and it’s probably why they haven’t caught it while testing.
‘Early adopter problematic’
You can now hit refresh button like 5 times then you should get the update forced.
Vendor Name: Fairphone
Device name: Fairphone 5
Device CodeName: FP5
Version of /e/OS or Stock which existed previously: 3.0.4 A13
Current android version: 3.1.1-a15-20250827521151-official-FP5
Is the device Rooted / Not rooted: Not Rooted
Unfortunately since the update, Android Auto doesn’t work for me anymore. There already is an issue raised for this on gitlab, but this only concerns the build for FP6. Any more users having this issue? Or know how to add this to the gitlab issue?
Hello Manoj,
Update went smooth and fast. No issues so far.
Same here.
I shut down the phone (long press on Power+Vol. down) and restarted - afterwards the update started again, finished fast and now everything is working.
Yes, that worked for me too. Thanks a lot for the tip !
FP6 + A15 problem fixed now.
Thank you so much to the team for the quick fix. To me, how people react to an event is more important than the event itself.
Despite this issue being very severe, I appreciate how it has been handled by the team. You have my support.
I installed via fastboot /e/OS-a15 official on FP5, so far everything works fine.
My previous system was iodié 6.6
First I reinstalled the original android 15 then eos.
bootloader locked
thanks
When you went back from e/os to original android, did you sideload android? Or did you use fastboot to load individual img files?
Fastboot
Version : FP5.VT28.C.042
Release date: 21 July 2025
Security patch level : 05 June 2025
Latest FP6 version: the physical privacy switch to enable/disable camera and microphone stopped working. How do I provide proper debug logging? (If necessary.)
Vendor Name: Fairphone
Device name: Fairphone 5
Device CodeName: FP5
Version of /e/OS or Stock which existed previously: none, Google Android 14 - security level May 2025
Is the device Rooted / Not rooted: Not rooted
I just succesfully installed /e/OS version 3.1.1-a15-20250827521151-official-FP5 on a clean Android 14 FP5 device. I succesfully locked the bootloader after the installation and sofar everything seems to function correct on the Android 15 official release. Of course this is a clean setup, so not much tested yet.