Vendor Name: Fairphone
Device name: FP4
Device CodeName: FP4
Current Version: e-3.0.2-a14-official
Hello,
I’m waiting the official e-3.0.4 version. When it will be released ? Nor now, I’m on Android 14. Could I upgrade to Android 15 with e-3.0.4 version on the FP4 ? How it will work ?
Thanks.
FP4 A-15 will come with e-3.0.4 and should be available within the few next days.
No issues so far.
Many, many thanks to the team for continuing to maintain the s10e!
Upgrade to 3.0.4.-a15 by adb sideload.
Same here — I reflashed the recovery using Heimdall and sideloaded the ROM.
The only thing that could be improved is better alignment with the LineageOS documentation, as they provide a more recent version of Heimdall and updated drivers, which worked for me. The current documentation on /e/OS did not.
Thanks the team
No issues so far. It seems to be more responsive/faster.
Many, many thanks to the team for continuing to maintain the s10e!
Upgrade to 3.0.4.-a15 by local update.
Also updated Samsung S5e and S6 WiFi to A15 by local update. No issues so far.
Vendor Name : Fairphone
Device name : Fairphone 3
Device CodeName : FP3
Version of /e/OS which existed previously : 3.0.4-a14-community
Current version of /e/OS : 3.0.4-a15-community
Device Not rooted
I successfully did the upgrade from a14 to a15 with adb sideload without any data loss. In my case, my bootloader is locked (reason : Fairphone - FP3 - FP3+ Documentation Suggestions - #79 by Mamalo) and it causes no problems.
In my case, just one bug : the navigation hint is shown permanently (also reported by @urs_lesse ) above :
In menu Navigationsleiste/navigation bar also the invert of the layout of the navigation bar is not working (my phone S10e/a15). Moving the switch remains without result. Also no change after restart.
That may be a general issue in this version (?) same on my pixel 4a
Everything works fine so far. Thanks 
Vendor Name:
_ Fairphone
Device name:
_ FP3 /(+)
Device CodeName:
_ FP3
Previous Version:
_ from: e-3.0-t-20250601497058-community-FP3
_ to: e-3.0.4-t-20250710507811-community-FP3
_ to: e-3.0.4-a15-20250713508366-community-FP3
Rooted
_ yes
Updated from 3.0-t to 3.0.4-t yesterday and made the jump to 3.0.4-a15 today. Had a small issue where I couldn’t sideload the a15 image via ADB because of an “denying OTA because it’s a SPL downgrade” error (the date of the 3.0.4-t image was > the date of the 3.0.4-a15 image), so I transferred the image to my device and updated via Settings → Updater → Local update. This went over without a hitch.
Haven’t used my phone much yet but no issues so far.
For finding the update I needed to activate “show all available updates” in updater options.
After that the update was smooth. All tried apps (Signal, VR-SecureGOplus, FUTO, Bliss launcher, phone, …) work as expected.
Thank you Dev-Team!
Samsung
Tab S5e (SM-T725)
gts4lv
before: 3.0.1-a14-20250608498955-community-gts4lv
then (OTA): 3.0.4-a14-20250709507533-community-gts4lv
now (dirty upgrade via “local update”): 3.0.4-a15-20250713508366-community-gts4lv
not rooted
this device suffers from issues with navigation bar as well.
I did not manage to get the navigation bar to work - no clue - it just did not appear, even after reboot … only gesture-navigation works (flawless) (gesture navigation was ON before upgrade/update, I just tried to switch over to navigation bar for testing purpose)
apart from that: no other issues detected yet … great work! Thanks Devs for the upgrade!!!
Samsung
Galaxy S7 (SM-G930F)
herolte
before: 3.0.1-s-20250609498926-official-herolte
now: 3.0.4-s-20250711508139-official-herolte
not Rooted
Thanks a lot for keeping that hardware alive!
Only issue is that issue 8625 is still relevant for my device (just mentioning because fix is planned for 3.2 anyways)
Be advise if you’re on FP3 official, the update to 3.0.4 will NOT upgrade you to A15, but you will remain on A13…
All seems to be working, thanks to the dev team.
FP5
Previous: 3.0.1-t-2025 June 06 official-FP5
New version: 3.0.4-t-20250709 507786-official-FP5
Many thanks to the team. Update came through today. With the exception that the new version is still A13, all is well.
Everything works fine so far. Thanks
So I misinterpreted this information from Manoj, thinking that the Fairphone 4 would be eligible for the upgrade to Android 15.
But this only applied to the ‘Community’ builds and not the official versions.
I apologise to anyone I may have misled by saying that version 3.0.4 would be an ‘upgrade version’.
Anyway, that being said, here’s my feedback:
Vendor Name: Fairphone
Device name: Fairphone 4
Device CodeName: FP4
Version of /e/OS or Stock which existed previously: 3.0.1 a14-official
Is the device Rooted / Not rooted: Not rooted
Update was smooth and fast. No issue at all.
Note: VoWiFi (WiFi calling) still not working on FP4. Issue has been raised: FP4: WiFi calling doesn't work since /e/OS 3.0 (#8771) · Issues · e / Backlog · GitLab
For the rest everything seems to work pretty well.
Thank you!
3.0.4-a15-community was built a few days later than 3.0.4-a14-community, and since official usually tends to lag behind community a few days (for reasons), 3.0.4-a15-official might still come for manual install, at least I think it’s too early to say it will not.
But not as an OTA upgrade via the updater yet anyway.