/e/OS Weekly Development and Testing Activities
-
Summary of weekly development and testing activities by /e/OS developers and volunteers.
-
Updated content is marked with the
emoji.
Release Updates
Current v3.6
- Release Notes
- Feedback and voting
- ETA: 17 to 23 March
Previous v3.5
Devices that did not get the v3.5 build
(Build failed due to last minute code changes upstream. We will work on releasing them with v3.6. If there are plans to drop these devices, users will be informed in advance.)
| Vendor | Device Name | CodeName | OS |
|---|---|---|---|
| Xiaomi | Redmi Note 10S | rosemary | A15 |
| Motorola | Moto One Vision/Motorola P50 | kane | A14 |
| F(x)tec | Pro¹ X | pro1x | A14 |
| Nubia | Mini 5G | TP1803 | A14 |
| Gigaset | GS 290 (official) | GS 290 | A12 |
Upcoming Milestones
(Release planned in the future are marked as milestones in gitlab)
OS Version Release
/e/OS - A16
Planned release along with v 3.6 in March 2026 
The list of devices which will get the upgrade to A16 will be shared. Upgrades will be manual for community builds and OTA for official builds. Manual upgrades will require users to download and install the builds over existing build. A backup of data is advised in all cases.
Status: 
under testing.
View the complete list of supported devices
Ensure your Murena Workspace account (e.email or murena.io ) has a recovery email set. New Accounts without a recovery email will face reduced functionality for 30 days and post that will be marked for deletion. The process will be the same for existing accounts without a recovery email
To check if your Murena account has a recovery email set click here
- Link will require you to log in to your Murena workspace.
Documentation
Please note that we have transitioned to a process requiring all Murena accounts to have a recovery email. The recovery email ID is is an external email address that can be used to recover your account details should you lose access to your Murena email for any reason.
- Accounts without a configured recovery email will experience reduced functionality for a period of 30 days. After the 30-day period, such accounts will be marked for deletion. The deletion does not happen automatically.
- All users with Murena workspace IDs (murena.io, e.email) are requested to set a recovery email immediately if one has not already been configured.
- Check the documentation that mentions this requirement.
- Please do not wait for your account to be disabled, Set the recovery email ID today, if not done already
- What to do if you have not set a recovery email ID and you account is already disabled?
- Contact me @manoj and I should be able to help you with the unlocking.
We are planning on updating our documentation site. Besides making navigation easier the plan is to make user contribution easier. Currently under planning stage, will share details once there is any progress on it.
Migrate your data from google cloud to your Murena account. Follow the instructions in this guide.
Want to report an issue in /e/OS. Create the bug in Gitlab. If you are facing an issue in creating the ID, check this suggestion.
Security Information
Security Patch Release Process explained here
- We will be sharing a detailed document about our security policy.
Previous Releases & User Feedback
Feedback Threads
Community builds dropped for these devices
-
We will be moving to supporting one build type for devices which have an official build.
-
Which means we will not be linking the community builds in our documentation. While the community builds will continue to be built, they will not be linked in our documentation. They will be available for OTA updates.
-
We plan to eventually have only official builds for these devices. Where devices have the same OS version in community and official we would recommend users to migrate to the official builds. Take a backup before proceeding. Also, it would be a manual install process.
-
Where the official builds are on a lower level compared to the community builds, we plan to migrate them to the higher OS level for official builds as well.
-
This change in the community builds links not showing up in the documentation for these devices can be expected from the upcoming v3.4
Devices which will be impacted
| Vendor | Device Name | CodeName | Official OS version | Community OS version |
|---|---|---|---|---|
| Gigaset | GS290 | GS290 | A12 | A12 |
| Samsung | Galaxy S7 | herolte | A12 | A12 |
| Samsung | Galaxy S7 edge | hero2lte | A12 | A12 |
| Samsung | Galaxy S8 | dreamlte | A12 | A12 |
| Samsung | Galaxy S8+ | dream2lte | A12 | A12 |
| Teracube | Teracube 2e | zirconia | A12 | A12 |
| Teracube | Teracube 2e | emerald | A12 | A12 |
| Samsung | Galaxy S9 | starlte | A12 | A13 |
| Samsung | Galaxy S9+ | star2lte | A12 | A13 |
| Fairphone | FP3/FP3+ | FP3/FP3+ | A13 | A15 |
| Pixel 5 | redfin | A13 | A15 | |
| Nothing | CMF phone 1 | tetris | A14 | A14 |
| OnePlus | nord | avicii | A14 | A14 |
| SHIFT | SHIFTPhone 8 | otter | A14 | A14 |
| Teracube | Teracube 2s | saphire | A14 | A14 |
| Volla | Volla tablet | mimir | A14 | A14 |
| Fairphone | FP4 | FP4 | A14 | A15 |
| Pixel Tablet | tangorpro | A14 | A15 | |
| Fairphone | FP5 | FP5 | A15 | A15 |
| Fairphone | The Fairphone | FP6 | A15 | A15 |
| Pixel 7 | panther | A15 | A15 | |
| Pixel 8 | shiba | A15 | A15 |
Murena Cloud and Self-Hosting
Murena Cloud
Current Version: 31.0.10.11
Resources:
Self-Hosting
Current Version: v26.0.8.23
Resources:
Status:
Self-hosting guide update pending
🔍 How to Check NextCloud Version
Method 1: Murena Settings
Go to Murena Settings
Look for “NextCloud xx user documentation”
Method 2: NextCloud Scan
Visit NextCloud scan link
Input https://murena.io
Note: If MurenaCloud patch number differs from NC patch number, the rating may appear as bad. This is normal - patches are tested before deployment.
GSI (Generic System Image)
Current Version: /e/OS A10 v1.17
Resources:
Next Version: /e/OS T (A13) - skipping A11 and A12
Release dates to be announced
OS OTA Information
✅ Completed
Teracube -zirconia - S(A12) → V(A15) 🆕
Teracube : S(A12) → V(A15) 🆕
FP5 - Fairphone: S (A13) → V (A15)
FP5 - Fairphone: U (A14) → V(A15)
FP4 - Fairphone : S (A12) → T (A13)
S9/9+ - Samsung : R (A11) → S (A12)
GS290 - Gigaset : R (A11) → S (A12)
GS290 - Gigaset : Q (A10) → R (A11)
avicii - OnePlus : A12
FP3 - Fairphone : S (A12) → T (A13)
S7/7+ - Samsung : R (A11) → S (A12)
FP4 - Fairphone : T (A13) → U (A14)
S8/8+ - Samsung : R (A11) → S (A12)
Note: OTA upgrades are for official or stable builds only
Under Development and Testing
-
avicii - OnePlus : S (A12) → A16 ETA v3.6
-
FP4 - Early 2026
To Be Planned
- FP3
- tangorpro - Google Pixel tablet 7
- Murena One - A12 - A15
- GS290* - A12 - A15
- Galaxy S9* - A12 - A15
- Galaxy S8* - A12 - A15
- Galaxy S7* - A12 - A15
(Devices marked with an ‘*’ have an issue with FDE encryption which requires format before the OS can be upgraded. This essential means there would be data loss. If we are able to build a A15 build for these devices, the user will have to manual install it and that would require first taking a backup of all data.)
Check the section titled A16 Updates below
📖 What is OS OTA Upgrade?
Traditional Process:
Download correct OS build from supported device list
Download stock ROM from vendor site (for some devices)
Back up your data
Install stock ROM, then /e/OS ROM
Restore backups if needed
OTA Benefits:
Simplifies the entire process
Requires significant development and testing
A16 Updates
- We plan to update all devices currently on A12, A13, A14 and A15 to A16
- In case any device is not able of handling the A16 builds we will share that information.
- The team expects that A16 would not be buildable or installable on some of the older gen devices like the Samsung S7 or S8. There could be more.
- For such devices we we will work on getting them to the highest OS version possible.
- As you may be aware A12 does not receive security patches anymore. This will next impact A13 and so on. This is a standard Google policy to end of life (EOL) older Android versions.
- All devices we sell in our shop, with official builds are priority candidates for OTA OS upgrades. The difference is the official builds get OTA OS upgrades. Community devices will require manual upgrade.
- Will share dates and ETA once I get them from the team.
Miscellaneous Information
Real-Time Service Status
/e/OS Real-Time Status
New Gitlab account creation
- If you are trying to create a new /e/OS Gitlab ID and facing issues with the email ID, you can try and create a Murena Workspace ID and use it to log into Gitlab. Check the updated documentation here
🎫 Helpdesk Services
For Paying Murena Customers
Murena device purchasers
Paid Murena cloud account holders
Active donors from the past year
Response Time
5-10 day response wait period due to high volume of requests.
Contact
Murena Helpdesk Contact Form
For Free Users
Warning: Old helpdesk email IDs are no longer monitored.
📱 Device and Vendor Announcements
Gigaset GS290
Sales stopped (vendor ceased production)
Support continues for existing users
Murena One
Sales stopped
Support continues for existing users
Murena Two
Sales stopped
Support continues for existing users
Pre-Flashed Devices
Available in EU, US, Canada, and Australia. Check the complete list on the Murena shop
Purchase via Murena Shop
🌐 /e/OS Website and Social Media Links
Official Websites
Telegram Channels
Social Media
Newsletters
To send in your Donations : Use the email ID donation@murena.io
Important Notice
Do Not Post Test Build Information on the Forum
Why this is important:
Test builds are untested and may cause device issues
These builds can potentially soft brick user devices
Such information can confuse other users who don’t see these builds in the updater
Not all forum users are experts in custom ROM installation
For Interested Testers:
If you understand custom ROMs and can perform basic testing
Join the testing team
Share feedback on the dedicated Telegram channel
Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services
/e/OS web installer 0.14 is online!