Feedback for v3.1.4

Release Information

Please share feedback on v3.1.4 build for your device and let us know how it is working with applications that you use.

:point_right: Release Date: Staggered over a week . Start date to be shared

:point_right: Release Note - will show up once the release has been initiated


Feedback poll

We will also have a poll to rate this build.

  • I have updated to v3.1.4 on my device and it is working well
  • I updated to v3.1.4 but I am having issues (Please share the issue details on this thread)
  • I am not able to update to v3.1.4 (Please share the issue details on this thread)
0 voters

:point_right: To report issues with the build or applications raise an issue on gitlab. Ideally first discuss the issue here and check if users of the same device on this build are having the same issue.

When sharing your feedback or issues, Please add the following details

  • Vendor Name

  • Device name

  • Device CodeName

  • Version of /e/OS or Stock which existed previously

  • Is the device Rooted / Not rooted

Refer this table for vendor, codename details

Refer this guide to share more details in your feedback


:warning: Do not share test build information on the forum or in this thread

  • This thread has been created specifically for posting information on official and community /e/OS builds.

  • To understand the difference between build types refer this guide

  • Please do not post information or links to /e/OS test builds on the forum.

  • The test builds are as yet untested and under development, and may in some cases cause user devices to soft brick.

  • Such information can confuse other users who do not see these builds in the updater.

  • Remember not all users who come to this forum are experts in installing and formatting custom ROMs and can end up seriously damaging their devices by trying out these test builds

  • If you are genuinely interested in helping with the testing activities and also understand how to fix and do some minor level of testing on custom ROMS, you are welcome to join the testing team

  • As part of the testing team you can share your comments on the dedicated testing telegram channel.

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

3 Likes
  • Vendor Name
    Fairphone
  • Device name
    FP6
  • Device CodeName
    ?
  • Version of /e/OS or Stock which existed previously
    /e/OS 3.1.1-a15-20250827521151-official-FP6
  • Is the device Rooted / Not rooted
    Not rooted

I just got that phone yesterday, never used /e/OS before. It is working better than expected, but it shows me that I’m on the latest update already. What am I doing wrong? Or is this not an official update yet?

It’s simply not available yet, see

/e/OS community FP3 download or /e/OS official FP3 download
/e/OS community FP4 download or /e/OS official FP4 download
/e/OS community FP5 download or /e/OS official FP5 download
/e/OS community FP6 download or /e/OS official FP6 download

4 Likes

Do you have set Developer options > Connect to /e/OS Test channel?

Okay, my fault then… Thank you anyway…

To @aibd - no, I didn’t set developer options. I just missinterpreted this whole thread as some official update and not developer/test channel…

I might do that (and update to 3.1.4 once the build is available), are there any risks involved?

And just ignore my uninformed spam from above, thank you for clarifying things for me

Not your fault most probably!
If you want the official OTA Release then dont touch that setting and just wait until the OTA Update is shown.
I think joyfullbison should not have posted in this thread as not to confuse other users :wink:

2 Likes

Vendor Fairphone
Device name The Fairphone (Gen. 6)
Device CodeName FP6
Version of /e/OS or Stock which existed previously E/OS 3.1.3-a15—?----official-FP6
Is the device Rooted / Not rooted not rooted

After activating dev-channel I could upgrade from 3.1.3-a15 to 3.1.4-a15…
Everything looks good so far :slight_smile:
I really like the FP6 with /e/OS
thanks to all who make it possible!

with kind regards
gp

One needs to fully understand the risk associated with change of keys mentioned here Feedback for v3.1.1 - #401 by aibd and the associated lead up Feedback for v3.1.1 - #396 by Manoj

but … OP

3 Likes

hello winkman and argeman

My apologies.

Although I’m a bit confused as this tread was maked for sharing v3.1.4 feedback.

So I have deleted my post as per your request to avoid confusion.

3 Likes

Does this address the US/EU region change rebooting problem? This is continuing to be a major headache for me.

1 Like

Yes, the fix for the rebooting is a part of the v3.1.4 build.

3 Likes

Hi, could you please explain your issue more precisely? My FP6 didn"t randomly reboot in US but in EU it does all the time, altough les than before (currently running 3.1.3).

The details are here: Week 37, 2025: Development and Testing Updates - #11 by p4tr1ck

When should I expect this to be rolled out to my device? I’m still waiting, five days after “release.”

Builds could not be completed this week. We had some issues with the build servers and a lot of builds pilled up. Expect to start the release early this coming week.

1 Like

I’ll try to be patient, but it’s very frustrating to see you guys roll out two broken updates back to back like this, then drag your feet on a fix - particularly for a phone you sell in your own store.

3 Likes

I would have some suggestions in that regards, as to how you could modulate the development and release cycles for murena phones vs. The rest of the supported devices, but I would not know the best place to send those suggestions.

The release cycles are the same for all devices. We cannot have separate cycles for devices as it would strain the build machines.

Understood. That makes sense too.

I am with @Borple on this one though.

There should be something done for the Murena phones to prevent dysfunctions as bad as unexpected reboots for over two week, making the phone literally unusable.

Being a dev I understand the challenge but i am also thinking of normie users who want to escape web giants and turn towards pre-installed solutions, who experience this problem.

Unless Murena is only targeting the tech community, I think there has to be better pre-release QA to enable general adoption of /e/os in the general population.

3 Likes

Ideally, I would like the official builds to be released slightly later than the community builds. Currently, there is only a day or two between them, which doesn’t seem like enough time to discover any last-minute bugs. In my opinion, official builds should be released at least a week after community builds, to allow time to postpone them if any bugs are discovered.

7 Likes