/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 Release v4.1.1
- Feedback for v4.1.1 - /e/OS Smartphone Operating System / Build Feedback - /e/OS community
- Release notes
- ETA: 20 July - 27 Iuly
- The release is staggered across devices
What is a staggered release
Please note that all /e/OS releases are staggered releases.
Which means, during the release days, every day a small set of devices are released.
The reason we do our releases in this manner, is we support 250+ devices.
If we release all builds at the same time the servers will crash as we will have thousands if not millions of simultaneous hits on the servers.
Official builds usually get released during the last days of the release process.
The release process usually takes about 7 to 10 days.
Upcoming Milestones
Releases planned in the future are marked as milestones in gitlab
Roadmap for 2026
Check out Gaël’s article on the roadmap for /e/OS and Murena in 2026
Murena Account Recovery Email
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 click here
- Link will require you to log in to your Murena workspace.
- In case your account is disabled, you can contact me - @Manoj on this forum and I can assist with getting the account re enabled.
Documentation
Check out the new look Documentation site.
Now anyone with a /e/OS Gitlab account can edit the Documentation site. Share your /e/OS gitlab ID with me @Manoj and I can get you the required access to edit the documentation. Your changes will be created as a Merge Request and after it has been reviewed and approved it will get published.
Devices with official builds will not have community builds showing up in the installation guides.
-
The community versions of the devices we sell or sold has been removed from the documentation.
-
We would prefer users to eventually shift to the official builds. That way the maintenance of the devices is easier and more efficient.
-
For now the community builds are being built and can be access by adding community to the device image download link replacing official. For example: /e/OS community starlte download
Check out the new features that came along with v4.0 release. Some of the features are- Murena Passwords
- Murena Sign
- Currently compliant with SES only. We are working on AES.
- Murena Meet
- Murena Vault
- Backup
- Google data migration
Documentation on all the new features being updated and modified based on feedback from user and testing teams.
Please note some of these features are in the beta phase. Additional development, detailed testing and improvement are in progress. We look forward to your comments and feedback on these features.
Want to report an issue in /e/OS.
- Create the bug in Gitlab.
- If you are facing an issue in creating the ID, create or use your Murena workspace ID as suggested here.
Security Information
Security Patch Release Process explained here
- We will be sharing a detailed document about our security policy.
Curent and Previous Releases and User Feedback
Murena Cloud and Self-Hosting
Murena Cloud
Current Version: 32.0.6.11
Resources:
[Release Notes]( v32.0.6.11 · e / infra / ecloud / nextcloud · GitLab)
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
Note: OTA upgrades are for official or stable builds only
All official builds are candidates for upgrade to A16 or the next OS for which build is possible.
A device with an official build name if not mentioned in this list does not mean the device has been abandoned. We continue efforts to build for all official devices we ever sold on the Murena Store. Dates of release of these builds will be shared when available.
📢 Completed
-
FP3 - FP3 - A13 → A15
-
OnePlus - Nord - avicii - A12 → A16
-
Teracube -2e - zirconia - A12 → A15
-
FP5 - Fairphone: A13 → A15
-
FP5 - Fairphone: A14 → A15
-
FP4 - Fairphone : A12 → A13
-
S9/9+ - Samsung : A11 → A12
-
GS290 - Gigaset : A11 → A12
-
GS290 - Gigaset : A10 → A11
-
FP3 - Fairphone : A12 → A13
-
S7/7+ - Samsung : A11 → A12
-
FP4 - Fairphone : A13 → A14
-
S8/8+ - Samsung : A11 → A12
🧪 Under Development and Testing
- FP4 - FP4 - A14 → A16
- FP6 - FP6 - A15 → A16
- FP5 - FP5 - A15 → A16
- OnePlus - nord - avicii - A14 - A16
- Galaxy S9* - A12 → A15 :crossed_finger
- GS290* - A12 → A15 (v4.1.1) :crossed_fingers
- Teracube - emerald - A15 → A16
- Teracube - sapphire - A14 → A16
- Teracube - zirconia - A15 → A16
- Murena One - A12 → A16
📋 To Be Planned
This is the consolidated list of all devices which have an official build. The plan is to upgrade all to the latest build possible. This may not work for all devices as some are too old have already hit EOL from vendor and may not work on latest OS versions. Devices with ‘No Update’ come in this category.
| Vendor | Name | CodeName | Current OS | Upgrade OS |
|---|---|---|---|---|
| Fairphone | FP6 | FP6 | A15 | A15 to A16 |
| Fairphone | FP4 | FP4 | A14 | A14 to A16 |
| Fairphone | FP3/3+ | FP3/3+ | A15 | A15 to A16 |
| Fairphone | FP5 | FP5 | A15 | A15 to A16 |
| Gigaset | GS6/Pro | GS6_venus | A16 | Already on A16 |
| Gigaset | GS290 | GS290 | A12 | A12 to A16 |
| Pixel 5 | redfin | A13 | A13 to A16 | |
| Pixel 7 | panther | A15 | A15 to A16 | |
| Pixel 8 | shiba | A15 | A15 to A16 | |
| Pixel Tablet | tangorpro | A14 | A14 to A16 | |
| Murena | One | One | A12 | A15 or A16 |
| Murena | Two | Two | A13 | A13 to A16 |
| Nothing | CMF Phone 1 | tetris | A14 | A14 to A16 |
| OnePlus | Nord | avicii | A16 | A12 to A16 |
| Samsung | S9 | starlte | A15 | A12 to A16 |
| Samsung | S9+ | star2lte | A15 | A12 to A16 |
| Samsung | S7 * | herolte | A12 | No updates |
| Samsung | S7+ * | hero2lte | A12 | No updates |
| Samsung | S8 * | dreamlte | A12 | No updates |
| Samsung | S8+ * | dream2lte | A12 | No updates |
| SHIFT | SHIFTPhone 8 | otter | A14 | A14 to A16 |
| Teracube | 2e | zirconia | A15 | A14 to A16 |
| Teracube | 2e | emerald | A15 | A14 to A16 |
| Teracube | 2e | sapphire | A14 | A14 to A16 |
| Volla | volla tablet | mimir | A14 | A14 to A16 |
(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 upgrade to A16.
- Official builds get OTA OS upgrades.
- Community devices require manual upgrade.
(Ideally in all cases, take backups while upgrading the OS of your device)
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
) No offence to Manoj, I just think that he is busy and that the Murena Operations team has not answered him yet.
