I have updated to v3.1.1 on my device and it is working well
I updated to v3.1.1 but I am having issues (Please share the issue details on this thread)
I am not able to update to v3.1.1 (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.
It’s unclear to me how I myself can upgrade my (official) Murena Fairphone 5 from A13 to A14/A15 if I don’t want to wait for the OTA upgrade?
I can read that some people are doing a “dirty” upgrade by simply downloading the relevant image with a version corresponding to the one already installed but with a never Android and then doing a local update. Is that the way to do this? Are there any risks besides losing your data?
Looking forward to this, too Also because I want to experiment a bit with a Fairphone 3 on e-A13-official hopefully getting to e-A15-community by ADB sideload (not my daily driver FP3+).
will the build that fail this time be dropped from the supported devices? and will there be a separate announcement for that?
excitedly looking forward to 3.1 for my Redmi (sweet) so fingers crossed.
and a general thank you for everything that you do!
Further bad news, a number of the A15 builds are failing. The reason is there are changes happening upstream which then get pulled into the builds causing them to fail. Will not have the final list of devices which will get the A15 build, until all the build stops.
Dirty upgrade is not the recommended way by the /e/OS team, you would be doing things on your own risk and there is no guarantee it will work.
Since you are on official and have a Murena then you will have a locked bootloader. Then a dirty upgrade is not possible at all. You need to open the bootloader to flash anything on the device. By doing that you will lose your data. You will need to restore your data. If you wanna upgrade (you did not state which Android version you have at the momen I guess the current one) then you will need a fresh install.
HAL problems with LineageOS were one of the reasons I bought a new mobile one month ago and switched here (support for my old mobile stopped completely as Android raised its HAL requirements)… .
I really hope you manage to sort this issues out soon…
What do you mean, regarding the post you answered to?
Builds failing means there is no new version for devices for which builds are failing, so you can’t install a failed build or update to it, and you just stay on the version you currently have.
The version / build we release is the version to install. We do not release builds that failed. The zip files that we share show up in the output folder only if the builds succeed. Failed builds do not compile. During the build process we get a message on the command prompt that the build failed and a bunch of error messages.
We will release v3.1.1 in a day or two as now they are being QA tested and those builds you can flash on your device. You would get it OTA on your device.
We normally do not release builds during the weekend - just in case anything goes wrong it is always good to have all hands on deck. Will update later during the day if we have a decision on the release start date.
Release Date: 2 September 
Do not share test build information on the forum or in this thread
Also because I want to experiment a bit with a Fairphone 3 on e-A13-official hopefully getting to e-A15-community by ADB sideload (not my daily driver FP3+).
