I have updated to v3.2 on my device and it is working well
I updated to v3.2 but I am having issues (Please share the issue details on this thread)
I am not able to update to v3.2 (Please share the issue details on this thread)
0voters
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
Refer this guide to share more details in your feedback
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.
Release Notes are looking very good! Excited for the update
I hope this update also fixes a bug where updates are not being avaible in app lounge unless one clears the cache and restarts the phone (which also doesnât always display new updates).
3.2-community for the FAIRPHONE is available now. I briefly checked and all other Fairphone versions are not available yet. Feel free to check yourself:
UPDATE 28 October 11:15 (Berlin time): All four community versions up
If you want to update via ADB sideload, make sure to remove the IMG- part from the URL (so it reads something like https://ota.ecloud.global/community/FP3/e-3.2-a15-20251025540112-community-FP3.zip before triggering the download.
UPDATE 30 October 12:00 (Berlin time): Three out of four official versions up
Good job e-os dev team. Everything OK (so far ). @manoj documentation says: âupload for kebab /e/OS build : A14 community.â and when clicking you have the webpage to download the A15 image. As a suggestio, you can replace âAxx communityâ by âlatestâ.
For the community the way I use for updating from A14 to A15:
If you are on community then it is as @N200 pointed out a clean install for major upgrades.
If you search the Forum you will find out that lots of people didnât domit that way and it kinda depends on the major version and the device how âeasyâ it will be. Try looking up your device but usually users would use the local update feature. If not obvious do a BACKUP of your data