/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 Information
Upcoming Release: v3.1.1
Status: Started
- Release Notes
- The release will be staggered as usual.
- ETA : 2 September (started)
Date got pushed forward from last week as A15 builds failed on multiple devices. We continue running the builds and expect to be able to release them this coming week.
Key Features:
-
Revolut fix (for devices with locked bootloader only) -
Second batch of devices on A15 to be released
- The final list would only be available once we complete the builds as the builds fail on some devices due to upstream changes. While we would attempt to recover and retry the process, if the A15 is not possible on a particular device, we will share the device details here.
-
Various issues and fixes
For the FP6 users on A15 pick up v3.1.2 release dated September 3 build directly. We will remove the 28 August build
–
FP5 A14 to A15 OTA OS upgrade is being released along with v3.1.1 - the current release.
FP5 A13 to A15 OTA OS upgrade will come along with v3.3 - that is expected in 2 months time.
/e/OS - A15 - /e/OS V
Status: Released - First batch of device builds available
Highlights:
-
First batch of device builds on A15 has been released
Known Issues:
-
Some device builds failed during compilation due to last-minute upstream code updates
-
These builds will be released in v3.1.1
Important Announcements
A12 - /e/OS S - Support Ending
Effective Immediately:
-
Support for A12 (/e/OS S) discontinued -
Official A12 builds are an exception. They will continue getting A12 builds until we are ready to migrated to A13 or higher
-
This aligns with our policy of supporting three OS versions simultaneously -
All supported devices will be pushed to higher OS versions where possible
Recommendation for Users:
- We recommend users on A12 community builds should migrate to the A12 official build
Take a backup before proceeding
Server Outage Status
Current Status: RESOLVED
Murena Cloud Services and File Drive Access
-
Access restored for all users
-
Apps enabled on the Murena Cloud Dashboard
-
Sync for some apps may not work - see details here
-
NextCloud Desktop client works with
client synchronizationenabled
MurenaRecovery Folder
-
Being enabled and made visible for all users
-
Started with premium users, expanded to all impacted users -
The folder Will be visible for several months (end date TBD)
Important Actions for Users:
-
Back up your device data to avoid overwriting older files
Notes Sync
-
Cloud sync possible post v2.9 release
-
If not syncing after v2.9 upgrade,read the next section. Backup local notes before proceeding
Client Synchronization Setup
To enable data sync between device and cloud:
-
Log into your Murena account
-
Go to Dashboard → Your Profile (top right)
-
Navigate to Settings → Client Synchronization (left sidebar)
-
Enable the checkbox
Note: Only enable if you want device and cloud data to be in sync. Keep unchecked if you prefer separate data storage.
Documentation Updates
Documentation Released
-
Murena Find - replacement for Spot (documentation updated)
Version Naming Convention Update
New Standard: Using OS version numbers instead of letters
-
/e/OS V→ A15 -
/e/OS U→ A14 -
/e/OS T→ A13 -
/e/OS S→ A12 -
/e/OS R→ A11 -
/e/OS Q→ A10 -
/e/OS P→ A9 -
/e/OS O→ A8 -
/e/OS N→ A7
This change eliminates confusion in version tracking.
Security Information
Security Patch Release Process
Complete explanation available here
Upcoming Releases
A15 Device Lists (Draft)
Existing Devices:
New Devices:
Release Schedule
Ongoing Development
🛠️ Active Development Tasks
/e/OS GSI on T (A13)
-
Team exploring OTA availability
-
App development for compatibility detection
-
ETA to be shared
Previous Releases & User Feedback
Feedback Threads
Murena Cloud and Self-Hosting
Murena Cloud
Current Version: 29.0.16.4
Resources:
Self-Hosting
Current Version: v26.0.8.23
Resources:
Status:
-
Next release planning in progress
-
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 Upgrades
-
FP5 - Fairphone: U (A14) → V(A15)
-
FP4 - Fairphone : S (A12) → T (A13)
-
S9/9+ - Samsung : 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)
🧪 Testing Phase
- avicii - OnePlus : S (A12) → U (A14)
📋 To Be Planned
-
FP5 - A13 → A15 (v3.3)
-
FP3
📖 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
Miscellaneous Information
Real-Time Status
🎫 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
For Free Users
📱 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
Newsletters
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 -
Share feedback on the dedicated Telegram channel
Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services
Won’t we get the update to FP6 this week or am I misunderstanding something?