It would make sense. If that is technically possible.
1 Like
This was the standard once, if my memory serves me right. It should be again.
2 Likes
After the builds are complete and before the publishing, the QA team does a sanity check on the release. The location service causing reboots is an example that there can be multiple test cases / scenarios that still do not get checked out and need to be added as test cases. The testing process needs to be made more robust. We have taken this as a feedback to improve our systems.
14 Likes
The 3.1.4 A14 community build has come OTA to my spare phone, a Xiaomi Poco F3 āAliothā
Havenāt tested it extensively yet.
Now waiting for the update for my FP6.
1 Like
Vendor Name: Xiaomi
Device Name: Mi 9SE
Code Name: grus
Version of /e/OS which existed previously: e-3.1.1-a14-20250901522231-community-grus
Device Not rooted
Vendor Name: Xiaomi
Device Name: Redmi K20 / Mi 9T
Code Name: davinci
Version of /e/OS which existed previously: e-3.1.1-a14-20250831522231-community-davinci
Device Not rooted
Vendor Name: Oneplus
Device Name: 7 Pro
Code Name: guacamole
Version of /e/OS which existed previously: e-3.1.1-a14-20250901522231-community-guacamole
Device Not rooted
ota update installation without error 
It all works perfectly as always at the moment.
All smartphones runs very smoothly with 3.1.4ā¦
No mistakes so far excellent work. 
A big thanks to the development team for the wonderful work. 
Your issue is with FRP, it is not /e/OS specific. You can read this thread.
You replied to my post? Itās related to screen locking ways, your link points to bootloader locking problems, non relevant I thinkā¦
Hello, yes I was replying to you. As I said, your issue is related to FRP. You can read the thread from the beginning and, if you feel the need, the other threads that are linked. This was the same issue you have.
1 Like
The following devices will not be receiving the A15 builds in v3.1.4 release. The reason as mentioned earlier are upstream changes which came after the code freeze. We will target release of A15 build for these device along with the v3.2 release .
| Vendor | Device Name | CodeName |
|---|---|---|
| ASUS | ZenFone 8 | sake |
| Essential | Essential PH-1 | mata |
| F(x)tec | ProĀ¹ | pro1 |
| Fairphone | FP3/3+ | FP3 |
| Fairphone | FP4 | FP4 |
| Pixel 4a 5G | bramble | |
| Pixel 4a | sunfish | |
| Pixel 8a | akita | |
| Pixel 5a | barbet | |
| Pixel 3 | blueline | |
| Pixel 3a XL | bonito | |
| Pixel 9 Pro Fold | comet | |
| Pixel 4 XL | coral | |
| Pixel 3 XL | crosshatch | |
| Pixel XL | marlin | |
| Pixel 5 | redfin | |
| Pixel 3a | sargo | |
| Lenovo | Z5 Pro GT | heart |
| Lenovo | Z6 Pro | zippo |
| LG | G7 ThinQ | g710ulm |
| Motorola | Moto G7 | river |
| Motorola | edge 40 pro | rtwo |
| Motorola | moto g84 5G | bangkk |
| Motorola | Moto Z3 Play | beckham |
| Motorola | edge 20 | berlin |
| Motorola | edge 2021 | berlna |
| Motorola | moto g power 2021 | borneo |
| Motorola | moto g10 | capri |
| Motorola | moto g30 | caprip |
| Motorola | moto g9 power | cebu |
| Motorola | moto g32 | devon |
| Motorola | edge 30 | dubai |
| Motorola | Moto G6 Plus | evert |
| Motorola | moto g 5G - 2024 | fogo |
| Motorola | moto g34 5G | fogos |
| Motorola | moto e7 plus | guam |
| Motorola | moto g9 | guamp |
| Motorola | moto g42 | hawao |
| Motorola | Moto G 5G / Motorola One 5G Ace | kiev |
| Motorola | Moto G7 Plus | lake |
| Motorola | moto z3 | messi |
| Motorola | edge 30 neo | miami |
| Motorola | Moto G 5G Plus / Motorola One 5G | nairo |
| Motorola | Moto Z2 Force | nash |
| Motorola | Edge S / Moto G100 | nio |
| Motorola | Moto X4 | payton |
| Motorola | edge 20 pro | pstar |
| Motorola | moto g52 | rhode |
| Motorola | moto g82 5G | rhodep |
| Motorola | moto g200 5G | xpeng |
| Nubia | Mini 5G | TP1803 |
| OnePlus | 7 | guacamoleb |
| OnePlus | 7T | hotdogb |
| OnePlus | 9 | lemonade |
| OnePlus | 9 Pro | lemonadep |
| OnePlus | Nord N200 | dre |
| OnePlus | 5T | dumpling |
| OnePlus | 7 Pro | guacamole |
| OnePlus | 7T Pro | hotdog |
| OnePlus | 8 | instantnoodle |
| OnePlus | 8 Pro | instantnoodlep |
| OnePlus | 8T | kebab |
| OnePlus | 9R | lemonades |
| OnePlus | 9RT | martini |
| OnePlus | 11 5G | salami |
| Razer | Phone 2 | aura |
| Realme | 10 Pro 5G | luigi |
| Realme | 9 Pro 5G | oscar |
| Samsung | Galaxy A52 4G | a52q |
| Samsung | Galaxy S10 5G | beyondx |
| Samsung | Galaxy Tab S5e | gts4lv |
| Samsung | Galaxy Tab S7 | gts7lwifi |
| SHIFT | SHIFT6mq | axolotl |
| Sony | Xperia XA2 Ultra | discovery |
| Sony | Xperia 10 | kirin |
| Sony | Xperia 10 Plus | mermaid |
| Sony | Xperia 1 II | pdx203 |
| Sony | Xperia 5 II | pdx206 |
| Sony | Xperia 5 III | pdx214 |
| Sony | Xperia 1 III | pdx215 |
| Sony | Xperia 1 V | pdx234 |
| Sony | Xperia XA2 | pioneer |
| Sony | Xperia XA2 Plus | voyager |
| Xiaomi | Poco F1 | beryllium |
| Xiaomi | Mi 6 | sagit |
| Xiaomi | POCO F3 / Redmi K40 / Mi 11X | alioth |
| Xiaomi | Mi 10T / Mi 10T Pro / Redmi K30S Ultra | apollon |
| Xiaomi | Mi MIX 2 | chiron |
| Xiaomi | Redmi K20 / Mi 9T | davinci |
| Xiaomi | Mi 8 | dipper |
| Xiaomi | Mi 8 Pro | equuleus |
| Xiaomi | Redmi Note 8 / 8T | ginkgo |
| Xiaomi | Redmi 7A / 8 / 8A / 8A Dual | Mi439 |
| Xiaomi | Redmi 4A / 5A / [Note 5A / Y1 - Lite] | Mi8917 |
| Xiaomi | Redmi 3S | Mi8937 |
| Xiaomi | Mi A3 | laurel_sprout |
| Xiaomi | Mi MIX 3 | perseus |
| Xiaomi | Mi MIX 2S | polaris |
| Xiaomi | Redmi Note 10 Pro | sweet |
| Xiaomi | Mi 8 Explorer Edition | ursa |
| Xiaomi | Redmi Note 7 Pro | violet |
2 Likes
@Manoj Could you please sort in alphabetical order?
Thanks in advance!
1 Like
Yeah, you are right - looks like the issue I have. unfortunately I locked bootloader after rebooting , what was worse I flashed community build. I think Iāll wait for official and then start fixing procedureā¦
I deleted my Vote and report since my problems are not related to /e/OS/. Now as I understood the solution, I need to:
- wait for the official FP5 ROM with SPL newer than 1 Sep 25 (since this was included in /e/OS/ 3.1.4)
- install factory ROM
- login to my google Account
- wait for /e/OS with SPL newer than installed factory ROM
- logout from google account
- install /e/OS/ carrying about SPLs, unlocking and locking order and so.
- lock the phone and enjoy it.
is it correct, in general?
Thanks for pointing that out. Have corrected the list now.
1 Like
If you do this and check the state before locking, you will 100% not brick your device. If SPL date is equal, it works too.
āBy default the update check interval [of App Lounge] is now set to weekly instead of daily so Play Store APIs are less frequently used.ā
So the app that is supposed to fix critical vulnerabilities in our banking and health apps and that is malfunctioning regularly, is now maybe checking for updates 7 times less often? I donāt knowā¦
Off topic addition, SPL dates
Trying to avoid filling Build Feedback with unnecessary detail.
I think that will not be critical to your decision
ā¦ and same date is ok ā¦ Fairphone Android without lock is ignored.
If you need to continue perhaps add to an FRP thread.
- Vendor Name: Oneplus
- Device name: 9 pro
- Device CodeName: Lemonadep
- Version of /e/OS or Stock which existed previously: v3.1.1
- Is the device Rooted / Not rooted: not rooted
Update was fast, no errors. Everything working. Thank you for your hard work!
The OTA installation went smoothly, and the new system is already running on the phone.
My observations:
- On version 3.1.1 the Find My Device feature didnāt work as it should, and on version 3.1.4 it got even worse.
- I still miss camera functionalities, such as the ultraāwide mode.
- Several times on the forum many users have asked that quick settings (WiāFi, mobile data, etc.) should not be accessible from the lock screen. Every discussion about this was quickly closed. I donāt see that this important security feature was implemented in version 3.1.4.
The device is: Xiaomi Redmi Note 10 Pro.
Vendor Name: Nothing
Device Name: Phone (1)
Code Name: Spacewar
Version of /e/OS which existed previously: e-3.1.1-a15-20250829521742-community-Spacewar
Device Not rooted
ota update installation without error
If you search for it in the smartphone selector page, you wonāt find it.
https://doc.e.foundation/devices
the link is missing but thanks to @ronnz98 for sharing the link
https://doc.e.foundation/devices/Spacewar/install
Everything works so far, but I noticed something.
I activate the location without a-gps and without fake gps and deactivated after a few seconds then GPS connections are created in the background that do not end anymore.
only a restart solves this problem.
i activate and switched off the location again everything starts from the beginning.
in version 3.1.1ā¦ no connection was made after the location was switched off.
Otherwise, everything works a big thank you to the development team for the hard work.
Ok -
but where is the release (not OTA) for FP5??
Its a dangerous situation in my opinion, your homepage (Install /e/OS on a Fairphone FP5 - āFP5ā) lists 3.1.4 already the whole day - with security level 1.9.'25 - but if you click that link listed there (official) (/e/OS official FP5 download) it forwards you to a downloadpage where just 3.1.1 (with presumably older security patch date) is availableā¦
2 Likes
Thanks for mentioning this. Unfortunately, I fell into this trap today. I installed /e/ OS on my Fairphone 5 from Fairphone OS FP5.VT2D.C.054 with security patch level 05.08.2025 using the shell script. Before I compared with the installation website, which says "
/e/OS build : A15 official (Security patch: 2025-09-01)". However, I downloaded IMG-e-3.1.1-a15-20250827521151-official-FP5.zip via the link provided there. At that point, I wasnāt sure about the different /e/ OS versions and assumed the patch level was 2025-09-01. Luckily, after installing it, I checked the patch level again in the settings and saw that it was 2025-08-01. I therefore did not lock the bootloader. Unfortunately, however, it is also not possible to update to version 3.1.4. I get the message āYou are running the latest /e/OSā and when I refresh, the message āNo new updates foundā appears.
- Is this because I didnāt lock the bootloader, or is 3.1.1 actually the latest version for Official?
- If the latter, when can I expect to be able to update to 3.1.4?
- Am I correct in assuming that I should be able to lock the bootloader after an update?
Since I urgently need the device, I would temporarily go back to stock using the original installation file if this takes longer. That should be safely possible with locking, right?
Alternatively, I could also bridge the gap with limited use for a few days. In that case, however, I would have the following question: Am I correct in assuming that an unlocked bootloader would primarily be a security problem in the event of physical access, i.e., theft, etc.? In my case, I wouldnāt put much data on it in this state anyway.
Otherwise, I like /e/OS so far. Thank you for your work.
1 Like