/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.
Releases
Current
- v4.2
- [Release Note]( Releases · e / os /
Releases · GitLab)
- [Release Note]( Releases · e / os /
- Feedback and voting
- ETA: 18 Aug to 24 Aug (staggered release)
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.
Milestones
- Releases planned for the future are marked as milestones in GitLab.
Murena Account Recovery Email
- Ensure your Murena Workspace account (e.email or murena.io) has a recovery email.
- New accounts and existing accounts without a recovery email will face reduced functionality for 30 days, after which they will be marked for deletion.
To check if your Murena account has a recovery email, click here.
- The link requires you to log in to your Murena Workspace.
- If your account is disabled, contact me (@Manoj) on this forum and I can assist with re-enabling it.
Password Reset
- We receive multiple requests for password resets. Users have reported instances of being locked out of the Murena password after resetting their Murena Workspace password. A fix for this is targeted for v4.3.
- Please note that users can reset their own Murena Workspace password using the ‘Forgot Password’ link.
- If a user is unable to reset the password on their own, requests to the support team for a password reset will not be entertained unless the user can confirm ownership of the device or account.
- To prove ownership, you will be required to share the recovery ID or any other details requested by the infra team.
- For assistance or guidance with a locked password, contact me (@Manoj) on the forum.
Documentation
Tips for using GitLab or the Forum
- Always use the search feature first before raising new bugs or creating new posts.
- If others have already raised similar issues, please add your details to the existing thread.
- When creating new issues on GitLab or new posts on the forum:
- Share details of your device (model, build, and any other information that could help others debug the issue).
- Never share personal details such as your email address when raising issues or creating posts on the forum or in non-confidential GitLab issues.
Anyone with a /e/OS GitLab account can now edit the Documentation site.
A brief explanation of how users can edit the Documentation site
The process for editing the /e/OS Documentation site is as follows:
- Share your /e/OS GitLab ID with me (@Manoj). I will pass it to the team member who will grant you the necessary access to the documentation project.
- Once access is granted, your changes will be created as a Merge Request (MR).
- The MR must then be reviewed.
- The MR can be rejected or approved. If rejected, reasons will be shared.
- Once approved, the content is published and appears on the documentation site
Some important guides on the Documentation site
- Murena Passwords
- Murena Sign
- Currently compliant with SES only. We are working on AES support.
- Murena Meet
- Murena Vault
- Backup
- Google data migration
Please note that some of these features are still in beta. Additional development, detailed testing, and improvements are in progress. We look forward to your comments and feedback.
A guide explaining what Bootloader relocking means.
How to Report an issue in /e/OS
- Create the bug in GitLab.
- If you encounter an issue creating an ID, create or use your Murena Workspace ID as suggested here.
Security-related documentation
- Security Patch Release Process explained here
We will be sharing a detailed document about our security policy.- Security updates tracking page. A guide to help track public security updates release by release from v3.0 upwards. This will include initial tracking tables for A12 to A16, covering release date, Android Security Bulletin, browser security update, and vendor security update.
Murena Cloud and Self-Hosting
Murena Cloud
Current Version: 32.0.6.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 the Nextcloud scan link
- Enter https://murena.io
Note: If the Murena Cloud patch number differs from the Nextcloud patch number, the rating may appear as “bad”. This is normal — patches are tested before deployment.
OS OTA Information
Note: OTA upgrades are available for official or stable builds only.
All official builds are candidates for upgrade to A16 or the next OS version for which a build is possible.
The absence of a device with an official build from this list does not mean the device has been abandoned. We continue efforts to build for all official devices ever sold on the Murena Store. Release dates for these builds will be shared when available.
📢 Completed
- FP6 – FP6 – A15 → A16
- FP3 – FP3 – A13 → A15
- OnePlus – Nord – avicii – A12 → A16
- Teracube – 2e – zirconia – A12 → A15
- FP5 – Fairphone – A13 → A15
- FP5 – Fairphone – A14 → A15
- Galaxy S9* – A12 → A15
- GS290* – A12 → 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 ETA v4.3
- FP5 – FP5 – A15 → A16
- OnePlus – Nord – avicii – A14 → A16
- 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 that have an official build. The plan is to upgrade all of them to the latest possible build. This may not be feasible for every device, as some are too old and have already reached EOL from the vendor and may not work on the latest OS versions. Devices marked “No updates” fall into this category.
| Vendor | Name | CodeName | Current OS | Upgrade OS |
|---|---|---|---|---|
| Fairphone | FP6 | FP6 | A16 | Already on 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 that requires a format before the OS can be upgraded. This essentially means data loss. If we are able to build an A15 build for these devices, users will have to install it manually and must first take a full backup of all data.)
Check the section titled A16 Updates below.
📖 What is an OS OTA Upgrade?
Traditional Process:
Download the correct OS build from the supported device list
Download the stock ROM from the vendor site (for some devices)
Back up your data
Install the stock ROM, then the /e/OS ROM
Restore backups if needed
OTA Benefits:
Simplifies the entire process
Requires significant development and testing
A17 or A16 Updates
-
We plan to update all devices currently on A12, A13, A14, and A15 to A16 or A17 once it becomes /e/OS-compatible
-
If any device is unable to handle A16 or A17 builds, we will share that information.
-
The team expects that A16 will not be buildable or installable on some older-generation devices such as the Samsung S7 or S8. There could be more. While the team will try to OS upgrade these devices, if the attempt fail we will have to drop these devices from the supported list.
-
As you may be aware, A12 no longer receives security patches. This will next affect A13 and subsequent versions. This is standard Google policy for end-of-life (EOL) of older Android versions.
-
All devices we sell in our shop that have official builds are priority candidates for OTA OS upgrades to A16.
- Official builds receive OTA OS upgrades.
- Community devices require manual upgrades.
(Ideally, take backups before upgrading the OS on any device.)
Miscellaneous Information
Real-Time Service Status
eCloud Real-Time Status
/e/OS Real-Time Status
New GitLab Account Creation
- If you are trying to create a new /e/OS GitLab ID and encounter issues with the email address, you can 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
2–3 day response wait period due to high volume of requests.
Contact
Murena Helpdesk Contact Form
For Free Users
Forum
GitLab Issues
Telegram Channels
Warning: Old helpdesk email addresses 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 the 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
Murena
/e/OS Website
Documentation
Report Bugs
How to Report Bugs
Telegram Channels
Available Channels
Social Media
XDA
X
Mastodon
LinkedIn
Medium
Newsletters
eFoundation News
Murena Promotions
To send in your donations: Use the email address 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 do not 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
