Feedback for v2.9

Release Information

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

  • The release will be staggered over the next couple of days from 31 Mar to 07 April 2025.
  • Release notes (will show up here once release is initiated)
  • To report issues with the build or applications raise an issue on gitlab

Feedback poll

We will also have a poll to rate this build.

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

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

8 Likes

The release is from 31.03 not sure for what your comment is…

1 Like

Right, it’s the 2.8 version! My fault.

1 Like

Maybe you could delete it and post it in the correct post for 2.8.

2 Likes

Fairphone | FP3+ | FP3 | previously on e-2.8-a14-20250221470208-community-FP3 | not rooted


Other Fairphoners, feel free to check what’s online for you:

/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

As of right now**, 2.9 community is available for FP3, FP4 and FP5, but 2.9 official is not (yet).

Fairphoners on older stable / official versions (Android 10, 11, 12) might also see some bigger progress now.


UPDATE 1 April: Release notes up now


UPDATE 3 April: Fairphone offiicial releases available now, too

6 Likes

On a different note, my suggestion to make the Feedback Poll a public vote in the future. This would allow /e/ staff much easier to find the comments which detail issues, especially once the topic has many comments. I do not think anyone would need to fear any negative repercussions of having their vote visible for others.

1 Like

Solana Saga ingot


New / fresh installation fails due to missing vbmeta-e-2.9-a14-20250323478432-community-ingot.img

The ZIP file recovery-IMG-e-2.9-a14-20250323478432-community-ingot.zip is missing the important file vbmeta.img Only three of the usual four .img files are contained in recovery-IMG-e-2.9-a14*.zip

Therefore vbmeta.img must be extracted from playload.bin (from e-2.9-a14-20250323478432-community-ingot.zip ).

Samsung Galaxy Tab S5e (LTE) gts4lv

  • Version of /e/OS which existed previously: e-2.1-t (A13)
  • Not rooted

Manually upgrading /e/OS-T (A13) to /e/OS-U (A14) without data loss.

  1. Installed first recovery-e-2.9-a14-20250323478432-community-gts4lv.img - IMPORTANT!
  2. Verification of recovery-e-2.9-a14 installation via reboot to e-recovery
  3. Running adb sideload e-2.9-a14-20250323478432-community-gts4lv.zip
  4. Running Reboot system now

That’s all :ballot_box_with_check:

1 Like

Vendor Name: Xiaomi

Device Name: Redmi K20 / Mi 9T

Code Name: davinci

Version of /e/OS which existed previously: 2.8-a14-20250220470208-community-davinci

Device Not rooted


Vendor Name: Oneplus

Device Name: 7 Pro

Code Name: guacamole

Version of /e/OS which existed previously: e-2.8-a14-20250221470208-community-guacamole

Device Not rooted

both devices work perfectly as always. no mistakes so far I am very happy with it. :slight_smile:

I noticed that after the update on 2.9… the mi9t always works better and softer, for example, when wiping and using. it is a true joy. :slight_smile:

many many thanks to the developer team for the perfect work :ok_hand: :+1:

1 Like

Vendor Name: Fairphone
Device Name: FP4
Code Name: FP4
Version of /e/OS which existed previously: 2.8 a14 official
Device Not rooted

Update to 2.9 was smooth.
Thank’s DevTeam

2 Likes

Fairphone 5 (murena bought)
FP5
2.8-t

Smooth display still broken. 90hz stops working after screen lock.

@Manoj could you please make somebody aware oft this issue? I’m pretty sure every FP5 murena user has a broken 90hz mode and I don’t see anybody official acknowledging the issue at gitlab.

I would really like to have 90hz as it was the only reason to buy it over a FP4.

Thank you.

3 Likes

Issue is marked under development which means we are working on the resolution. Will have team put a milestone around it.

4 Likes

Vendor Name: Fairphone
Device Name: FP4
Code Name: FP4
Version of /e/OS which existed previously: 2.8 a14 official
Device Not rooted

Update to 2.9 worked fine. Notes App still doesnt work with Murena Cloud sync?

2 Likes

Vendor Name: Google
Device Name: Pixel 6a
Code Name: Bluejay
Version of /e/OS which existed previously: 2.8-t-community
Rooted? Device Not rooted

Update went smooth. No issues detected so far with the new installation. Thanks dear team.
As announced the Notes app seems to sync again with the /e/cloud servers out of the box (yeah!).
What does not work (yet?) is the Notes cloud syncing with third party desktop apps. I used Iotas, a Flatpak Linux app that worked smoothly before the whole server issue started. Now it only produces a “server connection offline” error. But this is not related to /e/OS v2.9.

3 Likes

Vendor Name: Fairphone
Device Name: FP4
Code Name: FP4
Version of /e/OS which existed previously: 2.8 a14 official
Device Not rooted

Update to 2.9 worked fine, and process was incredibly fast.
Notes seem to sync again (no error message). Moreover no notes have disappeared. :+1:
When opening “Mail” app for the first time after update, new release version notes does open…but in an empty page (white page, nothing is showed).
For the rest, everything works well as before.
Thank you /e/ teams!! :pray:

2 Likes

Bonjour,

Depuis eOS 2.9T, je ne peux plus utiliser l’application de mail de murena.
ça me force le mot de passe généré via mon compte qui a été utilisé pour connecter mon compte murena sur mon téléphone car c’est actuellement le seul moyen de le connecter mais ce mot de passe généré ne permet pas de connecter mon compte mail via l’application mail de murena.

Cordialement,

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

1 Like

Maybe unrelated to the update, but the default E-Mail app cant check Mails in my murena account. Auth. Failed. Another mail account by a different provider works. Creating another app password does not help. Maybe its a generell Server issue atm

1 Like

May be related: Can't use my email app since eOS 2.9T

1 Like

Bonjour Ă  tous !

veuillez m’excuser, je ne parle pas français, c’est pourquoi je dois malheureusement faire appel à un traducteur.

J’ai exactement le même problème, mon adresse « Murena » n’accepte pas de mot de passe, même pas un nouveau « Application-Password ». Un compte mail complètement indépendant fonctionne normalement.

Meilleures salutations