Feedback for v3.1.1

/e/OS Smartphone Operating System Build Feedback
63

Vendor Name: Fairphone
Device name: FP4
Device CodeName: FP4
Version of /e/OS or Stock which existed previously : 3.0.4 a15-community
Not rooted

Updated via OTA, worked fine. For some reason I thought the camera issue with 48Mp images was to be fixed. Was the same. So I manually installed the 3.1.1-a14-official via ADB, locked the bootloader, and rebooted.

Did a basic setup and checked the camera, and it works as it should.

64

Vendor Name: Google
Device name: Pixel 9
Device CodeName: ----
Vesion OS: A15 stock
Rooted

I’m facing a persistent issue with the Pixel 9: it’s impossible to get e-recovery working, whether with version 3.0.4 or 3.1.1.
Every attempt ends with a “boot fail”, and e-recovery never starts.

Key points:

  • No problem installing LineageOS, iodĂ©, or GrapheneOS — they all work fine.
  • I always start from a stock Android 15 image for my tests.
  • The issue occurs every time, regardless of the /e/os version tested.
  • I correctly extract the three images (boot.img, dtbo.img, vendor_kernel_boot.img) from LineageOS and strictly follow the installation procedure.

Yet, I always get the same failure.
Does anyone have an idea or a lead to explore?

65

Vendor Name: Fairphone
Device name: FP5
Device CodeName: FP5
Version of /e/OS or Stock which existed previously : 3.0.4 a14-official
Not rooted

Install and boot were fine, now I am on 3.1.1 (Fp5) (official) and everything looks ok so far, many thanks.

But
A14? I expected a release of A15 to be honest. Perhaps I misunderstood something, but when does A15 (official) follow for Fp5?

2 Likes
66

I flashed IMG-e-3.1.1-a15-20250830521751-community-FP6, and locked, it works! Except i only get notification sounds and badges on the app icons in the home launcher
 Nothing in status bar, lock screen or notification center and setting passcode does not work


< reboot fixed notifications, still not able to set lockscreen pincode >

< I didnt know i had to log out of my Google account before factory reset, device is apparently in FRP mode
 Perhaps this is why i cant set lock screen pin code >

67

Vendor Name: Fairphone
Device name: Fairphone 4
Device CodeName: FP4
Version of /e/OS or Stock which existed previously : 3.0.4 a14-official

The system update was incredibly quick and efficient (no more than 5 minutes).

Still on version A14 for now.

All applications seem to be working properly, no issues to report.

Thank you to the entire development team!

68
  • Vendor Name: Fairphone
  • Device name: Fairphone 4
  • Device CodeName: FP4
  • Version of /e/OS or Stock which existed previously: 3.0.4 official
  • Is the device Rooted / Not rooted: Not rooted
  • Bootloader locked: Locked

Duration: About 60 min. incl. reboot using caffeine mode.
Everything works fine so far - incl. open camera, which now uses 48 MP resolution.
Thanks a lot :+1:

69

Since you expected it via the updater it seems you are waiting for a so-called OTA upgrade to a new Android version, which needs to be specially prepared and tested by the developers, so will take extra time. You can follow proceedings weekly here 
 Topics tagged development-updates

Current status 


It doesn’t seem to be there yet for manual install for official either, but it should be there somewhen since it’s there for community.

1 Like
70
  • Vendor name: Fairphone
  • Device name: FP5
  • Device CodeName: FP5
  • Previous version: /e/OS 3.0.4-t-20250709507786-official-FP5
  • Not rooted

I unlocked the bootloader, installed 3.1.1-a14-20250828521479-official-FP5 with the fastboot-based shell script (took about 2m30s), and re-locked the bootloader, all without incident.

It’s a new phone and I had not been seriously using it before the upgrade, so I’m not very alert to regressions or app incompatibilities. However, I did notice a couple of glitches:

  • In the map app OsmAnd~ (version 5.1.7), the rendering engine “Version 2 (OpenGL)” is unavailable (greyed out) – I wonder if this indicates some problem with 3D/graphics acceleration, but I haven’t investigated how to diagnose that. I’m pretty sure this is a regression from the previous (Android 13) OS version, as I remember playing around with the 2.5D mode with that. (I think that was with OsmAnd~ 5.0.5, mind.)
  • I noticed error messages about “Pico TTS” while I was lawnmowering the settings menus. When I went into Settings > Accessibility > Text-to-speech output, the following two warnings popped up, one after the other.
    (Pico TTS must have come with the OS image, I didn’t touch it. I don’t know whether this is a regression, as I’m not sure whether I entered this menu under Android 13. Pico TTS nevertheless seems to work, as far as I can tell.)
    • “Pico TTS: This app isn’t compatible with the latest version of Android. Check for an update or contact the app’s developer. [ OK ]”
    • “Pico TTS: This app was built for an older version of Android. It might not work properly and doesn’t include the latest security and privacy protections. Check for an update or contact the app’s developer. [ OK ]”

(For the purposes of the poll, I have nevertheless chosen the “it is working well” option.)

Feedback for v3.1.4
71

Can you help me:

I have an FP5 with the Android 15 version.

How to install the latest version of eos and lock the “Bootloader”

Thank you

72

Have just upgraded from 3.0.4-T to 3.1.1-T, on my Samsung Galaxy S10+

Upgrade stalled/crashed part way through (while the phone was in recovery mode). I had to forcefully restart it, but afterwards, the update seems to have picked upwhere it had left off before phone restart, and completed successfully.

I am fully upgraded to 3.1.1-T. Functionality seems to be there, but I haven’t done any involved testing yet.

73

The update from 3.0.4 to 3.1.1 (A15) worked very well on my Samsung Galaxy S10+. No problens during update. Everything seems to work.
e_beyond2lte-user 15 BP1A.250505.005 eng.root

74

Hi @Drb welcome to the /e/ forum.

This is the Install page for fp5 Install /e/OS on a Fairphone FP5 - “FP5”. As you plan to lock the bootloader you should choose official of the Different Build Types available. Android 15 official has not yet been published or announced at this point but it is expected. Any update on this will be seen in Development Updates. [1]

Before you start please be sure to understand the anti-rollback hazard and I suggest take a screenshot of your Android SPL as shown in Settings > About phone > (tap on) Android version.

(There is also (for the adventurous) Web Installer linked from
Info about Fairphone FP5 - FP5. Do not expect Android 15 at this time until this is reported available.)

  • Do not hesitate to open a new thread if you need further support.

[1] a15 when available will appear here /e/OS official FP5 download

2 Likes
Impossible to reinstall eos, corrupt system error
76

Hello,
I have a Samsung Galaxy S10 (“beyond1lte” I guess), rooted.
In general, I update eOS as soon as a new version is available, so I guess that the previous version is the last before v3.1.1.
Unfortunately, the update is not going well. The phone is stuck on a black screen with a white “e” and a progress bar that is almost complete but has not moved for several hours.
I don’t know what to do


FP3 Updater crashes before reboot and update to OTA 3.0.4
Phone crashes after Update
77

When I switch off the automatic choice and renew the netprovider list, there is no provider showing up, only the connected one, mostly not even this one.
Is this a bug?
OnePlus6T Community Version 3.1.1. Fajita

Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online servicesphone

78

Thank you for your answer, I no longer see the update 3.1.1, I downloaded it yesterday, can I install it without worries?
So I have to install an official Android version anterior to the version of EOS before installing EOS.
Is that right?

79 
Vendor Name: Samsung
Device name: S10e
Device CodeName: beyond0lte
Version of /e/OS or Stock which existed previously: 3.0.4 A13 community
Is the device Rooted / Not rooted: Not rooted
Bootloader locked: Unlocked

I had the same issues on a Samsung Galaxy S10e (“beyond0lte”), the update was also stuck at around 95%.
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.

3 Likes
80

You started from

From this I guessed that you wanted to do a new install from FairphoneOS. Now I think you are asking a different question ?? Do you have a Murena supplied FP5 ??

I cannot explain why this build was withdrawn – is that the main question?

As a post in build-feedback the observation will be noted.

can I install it without worries?

If the build which appears later is different you may worry, idk.

81

Samsung S10+
beyond2lte
Update from 3.0.4-t to 3.1.1-t
Device not rooted

Install progress stopped 1mm before the end. I see the e logo and the progress bar below, not finished. Device on charging. Is this the soft brick? What should /shouldn’t I do to attempt to recover?

82

Well, this is what I missed earlier:

  • shut down by Vol Down and Power, power up again and let the process finish
83

:pray:
This works well on my Samsung S10 too!

1 Like